search

ash37 / Subway-Maintenance

1 stars 0 forks source link

POS antivirus update #228

Closed ash37 closed 11 years ago

ash37 commented 11 years ago

International Stores Only Prerequisites for connecting to the FWH ESET Console: The following must be present in order to connect to the ESET Console:

  1. POS system running Windows XP or Windows 7 32bit based computer system.
  2. Active high-speed Internet connection.
  3. NOD32 Antivirus version 4.x. If the first 2 requirements are not met, the system cannot connect to the Console and would therefore need to submit a NOD32 waiver, a POS waiver, or a Credit Card waiver. How to get a POS system connecting and identified on the FWH ESET Console: These steps are for systems that meet the first 2 requirements, but do not have NOD32 V4.x installed.
  4. Install NOD32 using the file located at the following link (http://www.erikreilly.com/EZ/NOD32_Dec152011.msi) a. During the install, select, “Typical Install” when prompted. b. When asked for a username and password, select, “Set parameters later.” c. When prompted to select from the drop-down list, choose, “Enable detection of unwanted applications.”
  5. After NOD32 is installed, it must be configured to connect to the Console. a. Open NOD32 by clicking Start>Programs>ESET>ESET NOD32 Antivirus>ESET NOD32 Antivirus b. Click Setup, if you see “toggle advanced mode” click it c. Click Enter entire advanced setup tree, scroll down to the bottom and click on Remote Administration d. Put a check the box next to Connect to Remote Administrator server, change interval between connections to 0, enter the primary server address eset.subway.com, and click OK e. Wait 30 seconds and recheck the settings, if a connection to the server is made, the interval will automatically change to 60, 120, or 180. If that change does not happen, then the Internet is not working, or there is an external firewall blocking the connection. (See below)
  6. Once the system has been confirmed to be connecting, it now must be identified on the Console with the correct store number. a. Email the MAC address of the system to esetadmin@subway.com along with the store number. Please allow 24-72 hours for processing. i. Click Start, Run, enter cmd and click OKii. From the command line type getmac iii. If you see more than one Physical address, be sure to include them all in the email Follow these steps if the system already has NOD32 V4.x installed.
  7. Verify NOD32 is configured to connect to the Console. a. Open NOD32 by clicking Start>Programs>ESET>ESET NOD32 Antivirus>ESET NOD32 Antivirus b. Click Setup, if you see “toggle advanced mode” click it c. Click Enter entire advanced setup tree (password is subway40), scroll down to the bottom and click on Remote Administration d. Connect to remote administration server is checked, change the interval between connections to 0, primary server address is eset.subway.com, click OK at the bottom e. Wait 30 seconds and repeat the steps above and check the interval between connections has changed to either 180 or 120. If the interval does not change there is either an issue with the Internet, or an external firewall is blocking the connection (see below)
  8. Once the system has been confirmed to be connecting, it now must be identified on the Console with the correct store number. a. Email the MAC address of the system to esetadmin@subway.com along with the store number. Please allow 24-72 hours for processing. i. Click Start, Run, enter cmd and click OK ii. From the command line type getmac iii. If you see more than one Physical address, be sure to include them all in the email Firewall issue: If all the settings in NOD32 V4.x are configured correctly, but is not connecting, the firewall is most likely blocking the connection. Some firewall configurations need to be made in order for NOD32 to connect to our Console. Since all firewalls are different, these are all the potential setting changes that can be made, add the one(s) that correspond with your firewall settings. You may need to contact your Internet Service Provider for assistance in setting these up. Once the firewall has been configured, revisit steps 1 and 2.1. Add the NOD32 kernel program (ekrn.exe) to allowed programs and allow outbound and inbound access
  9. Add the FWH ESET Console server address (eset.subway.com) into the allowed sites.
  10. If you require the IP address, keep in mind this may change over time, you can add the IP 205.210.145.23
  11. NOD32 uses the following ports to connect so these may need to be opened, 2221, 2222, 2223, and 2224 Wireless Connection: If you are using a wireless card to connect to the Internet, the PC name would need to be changed in order to identify the system on the Console.
  12. Click Start > Settings > Control Panel
  13. Double click on System
  14. Click the Computer Name Tab
  15. Click Change – where is says Computer Name, type sby-XXXXX where X is the store number and click OK
  16. Reboot the system
  17. If you have multiple systems in the store follow the following naming convention a. Sby-XXXXX-M for Main POS b. Sby-XXXXX-S for secondary POS or Drive Thru c. Sby-XXXXX-T for training systems d. Sby-XXXXX-BO for back office systems