Table of Contents:
Pre-Installation Tasks
Installation Tasks
Post-Installation Tasks
Things To Note
Pre-Installation Tasks
Disclaimer:
As with any software upgrade or new release, it is strongly encouraged to fully test the new build within your environment prior to deploying network wide. You can test the new EPS Console by completing Steps 1 - 10 (under the Upgrading procedure section). Upon completing these 10 steps, you can create an EPS Client Packager and test on a few systems within your network as you get familiar with all the new settings and configurations.
1. Please make sure you save a copy of your Product Key as it will be required at the very end of the install process to activate your EPS Console.
2. A link to download the new Thirtyseven4 EPS 7.2 is available on our Downloads page.
3. Please note you can always take advantage of our Knowledge Base articles or email our technical support team at support@thirtyseven4.com for additional upgrading tips and procedures.
4. It is critical that all existing antivirus and security programs have been properly removed. You do not have to remove the current Thirtyseven4 EPS Client (the migration process will uninstall the old version and reinstall the new one automatically). A reboot is also highly recommended after uninstalling your existing antivirus application and prior to installing the EPS 7.2 Console.
5. The following Windows services must be Started and their Startup Type set to Automatic: Computer Browser and Windows Installer.
Installation Tasks:
1. Download and run the EPS 7.2 setup file.
2. After running the file, the screen below will appear as the system extracts the files for installation. The title bar of this window may display the words “Not responding” (this is normal depending on what other applications and processes are currently running). Let the extraction continue until finished.
3. After successful extraction, a Welcome screen will be displayed.
Click “Next” to continue.
4. The next screen displays the Thirtyseven4 End User License Agreement. You will have to scroll down and click ‘I Agree’ to continue.
Click “Next”.
5. The next screen will ask you where you’d like the EPS 7.2 Console installed. The default location will on the C:\ drive but you can install the Console to any desirable drive (ie. D:\, etc.)
Click “Next”
6. If you are installing the upgrade on the same server hosting your existing Console, the installation wizard will detect the existing Console setup and display the following prompt during installation:
Please note: This screen will not appear if you are installing EPS 7.2 on a new server.
Click “Yes” to proceed with the Multiserver installation. In Multiserver installation mode a user will now have up to 90 days to complete the migration of their existing clients to the new client (previously it was only 30 days).
7. The next screen verifies that IIS is installed and all required components are enabled. If not, the console will automatically install the required components. Once IIS is configured correctly. click “Next”
8. The next two screen ask for port assignments. For these options, we highly recommend proceeding with the defaults. However, if the default ports are already being used in your network, you can configure any unused ports.
Click “Next”.
Click “Next”
9. The next screen will ask you to assign an Administrator password and a Client password. The passwords can’t be the same. Also, it is very important that you retain these passwords. If your Administrator password is lost, you can utilize our new Forgot Password to retrieve your forgotten password.
Click “Next”
10. After clicking Next, the installation will process and both the Thirtyseven4 EPS 7.2 Console and the EPS 7.2 Client will get installed. Upon successful installation, you will be given the opportunity to perform the initial update via the Update Manager.
Click “Finish” at the last screen.
Post-Installation Tasks:
1. Import Groups & Policies.
•Login to the Endpoint Security Console you will be redirecting your clients from.
•Navigate to Clients > Manage Groups.
•Press Export at the top right. This will create an acexpgrp.db file in your downloads folder.
•Navigate to Clients Manage Policies and check the box next to the policies you would like to import into the new console.
•Press Export. This will create an acexport.db file.
•Copy both the acexpgrp.db and acexport.db files to the machine hosting the newly installed Thirtyseven4 EPS console.
•Open the new console and navigate to Clients > Manage Groups > Import.
•Select the acexpgrp.db file and press OK.
•Navigate to Clients > Manage Policies > Import.
•Select the acexport.db file and press OK.
•Once both your Groups and Policies have been imported, please navigate to Manage Groups and right-click on the groups to set their respective policies.
2. Start the Migration Process.
•With the new console now installed, you will need to initiate the redirection process.
•Login in to the old Thirtyseven4 Endpoint Security Console.
•Navigate to Admin Settings > Redirection.
•Input the IP Address of the machine you installed the new console on.
•Input the Client Communication Port displayed during the installation process.
•Configure the redirection type. (Available options differ by version.)
•Press Apply. You will receive a confirmation pop-up.
Things to Note:
1. Since the consoles use different SSL ports, you can open both EPS Console WebPages at the same time to watch the clients depopulate from your old console and populate in the new console.
2. Do NOT uninstall the existing Admin Console/EPS Console until ALL systems have been successfully converted over to the new Thirtyseven4 Endpoint Security version. *Please note: it is possible that not every system will move over. This is because the remaining systems may be showing Offline due to the systems being retired, re-imaged, etc.
3. When redirecting your clients from one console to the next, some clients may get a message asking them to reboot their machine to finish the migration process. This will not force the user to reboot, but if the user ignores the prompt, the machine will show in the new console under Home > Protection > Client Deployment failed until rebooted.
4. The Secure Browser shortcut will populate on the client desktop. | 
