Details:

Before Attempting This Software Update:

#1 Do NOT upgrade if you're using OpenEdge for Card Service and you're currently using Evosus version 6.4 or below.

#2 If you are currently running an Evosus version 6.2.xxx or lower then STOP and contact your Evosus Account Manager.

#3 Designate who will install the software update. 

 - The person you designate to install the update should have a reasonable understanding of installing software on a server AND will need to log in to Windows as Administrator to complete the installation. Note this is NOT the same as logging into Windows as a user who has Administrator rights. Failing to install Evosus while logged into the computer with the original Administrator credentials will result in issues running Evosus as designed. Some of our clients have a local IT provider install the update, but this is not required so long as you follow the download instructions we provide. 

#4 Schedule the software update sometime between Monday and Thursday. If you complete a software update over the weekend and run into issues that require assistance you will be billed for after hours emergency assistance.

 - Note that you will not be able to download the software update installer between the hours of 11PM PST to 5AM PST as the installer download lives on Evosus servers that are down during those hours for scheduled routine maintenance.

#5 Prepare for the time commitment the software update will require depending on your hardware/networking environment.

 - The update needs to be installed on your server and/or any computers where Evosus is installed locally - Some of our clients have a single host PC or SQL Server and employees access Evosus using local installs on their desktops. That means you would need to update the host PC or SQL Server and then update all of the employee desktops where Evosus is installed. Some companies have one or more terminal servers where users remotely access Evosus. In this case, you would need to update the terminal server(s) along with any local installs of Evosus that may exist. Many companies with terminal servers still utilize local installs of Evosus at the main location where the servers reside.



Step by Step Instructions:

Step 1: Verify You're Eligible to Install The Evosus Version Update


Are you using a supported operating system?

Version 6.7 is not compatible with older operating systems. Review the list below to determine if you meet the requirements. Contact you Account Manager if you have questions about upgrading the operating system on your server.


Host PC/Local Installations

Windows 10 Pro


Server

Windows Standard Server 2012 R2 with all updates(supported until 10/9/18)
Windows Datacenter Server 2012 R2 with all updates(supported until 10/9/18)
Windows Standard Server 2016
Windows Datacenter Server 2016


Are you using a supported version of SQL?

Version 6.7 is not compatible with older versions of Microsoft SQL Server. Talk to your tech if you don't know what version of SQL you are using. Contact your Account Manager if you have questions about upgrading your Microsoft SQL Server.

2014 with all updates
2016
2017


Are you on Evosus version 6.3.x or greater?

You have to be on Evosus version 6.3.X or above to upgrade to version 6.7. If you're on version 6.0.X, 6.1.X, or 6.2.X you'll need our help to upgrade. Contact your Account Manager and we can schedule a time to help with your upgrade.

How do you figure out what version of Evosus you're using?

#1 Log into Evosus.

#2 Select Help > About in the toolbar at the top of the screen.

#3 The version of Evosus you are using is at the top of the screen that appears.


Are you using Evosus Card Services?

If you do not use integrated card processing, you can upgrade to version 6.7 right now.

DO NOT UPGRADE if you're using OpenEdge for integrated card processing and you're currently using Evosus version 6.4 or below. Please contact your Evosus Account Manager before moving forward.


Are you logged in as an ADMINISTRATOR?

You must be logged in to the computer (not Evosus) as ADMINISTRATOR to install the application. Installing/updating Evosus while logged into a non-administrative account WILL cause problems. If you don't have access to an ADMINISTRATOR account, you need to contact your IT Support and have someone with access to that account install the application.


Step 2: Read and Share The Release Notes

Review the release notes so that you understand what changes are included in this release. You should also distribute them to all Evosus users to ensure they are prepared for the changes.



Step 3: Download The Installation File

Click here to download the installer. The installer is not available between 11 PM PST and 5AM PST because our servers on performing nightly maintenance tasks during these hours. 



Step 4: Move The Installation File to the Evosus Share Folder on Your Server

If you don't know where your Windows Evosus Share folder is, the file's location can be found inside of Evosus System Parameters. Go to Administration > System > Evosus Defaults > System Parameters > Open the System tab > Evosus Share UNC Path field.

Create a folder in the Evosus Share folder for the installer. For example, create a new folder in the share titled "6.7 Release".

 - The name of the folder isn't important. Creating a new folder just keeps the installers organized for you.

 - Move the Release.zip folder to the folder that you just created on the Evosus Share folder.

 - Extract the installer. For example, right click on the Release.zip folder and select Extract All from the menu that appears.

Four files are extracted:

 - Install_Evosus: This is probably the only file that you'll need.

 - Install_EvosusBrowser: Only needed for first time installations and is typically for Evosus use only. Do not install this on any computer other than the SQL Server

 - Install_Evosus_On_PC_Silently: Only used if you have a large number of local installs and knowledge of centralized software distribution. We do not support a specific implementation for remote software execution.

 - Install_Evosus_On_TerminalServer: A batch file that puts the terminal server in install mode prior to the update and into execute mode once the update is complete. If you are not logged into Windows as ADMINISTRATOR, this will not work correctly.


Step 5: Run the Evosus Version Update Installer On Your Servers

If your hardware/networking environment includes a SQL server and a Terminal Server (RDS Server) it's important you identify what one of those servers is used to run your Evosus Services, we call this the Evosus Service Host as this is where you need to run the Evosus update first!

 - The Evosus Service Host runs your Evosus Windows Services such as the Evosus Daemon Service, Evosus Mobile Service, and more.

To verify which server functions as your Evosus Service Host, log into Evosus and select Help > About. The server appears in the Evosus Service Host Computer field. You can also go to Administration>System>Evosus Defaults>System Parameters. On the System tab, locate the Evosus Service Host parameter. The server name in this field is the server hosting the Evosus Windows Services.



Terminal Server (RDS Server)

Follow these steps to install Evosus on your terminal server.

Step 1: Log into the Windows on the server as ADMINISTRATOR.

 - Contact your local IT support if you're not able to log into Windows as ADMINISTRATOR. This is NOT the same as logging in with a user who has Administrator rights!

 - The update will not install correctly if the Windows account does not have the proper permissions.

Step 2: Verify that all users have logged out of Evosus. This includes users with a local install of Evosus and users logged into terminal server sessions.

 - Users cannot be disconnected or idle. They must be logged out completely.

 - Use the Remote Desktop Services Manager to check the status of all users. You can also use this tool to send messages to users, and log them off.

Step 3: Put the server in install mode. This keeps users from connecting to the server.

 - Go to Start>Run.

 - Type cmd and hit ENTER.  A DOS command window will appear.

 - Type change user /install and hit ENTER.

 - Leave this window open.

Step 4: Locate the Evosus share folder that you created in Step 4 above.

Step 5: Copy the Install_Evosus_On_TerminalServer.exe file to the local computer

Step 6: Right click on the Install_Evosus_On_TerminalServer.exe file and select Run as Administrator.

Step 7: Follow the prompts to complete the install.

 - Users not logged off - There is an active session of Evosus running on the terminal server. You must log all users OFF the terminal server prior to starting the update.

 - Windows Mobile or Daemon services failed to stop during the installation - If this happens, wait 2 – 3 minutes and attempt to run the installation again. If the installer fails again due to running services, wait another 2 – 3 minutes and attempt to run the installation again.

 - Contact your Evosus Account Manager if you continue to have issues.

Step 8: Once the installation is complete, return the server to execute mode. If you miss this step, users will not be able to access Evosus.

 - Return to the cmd prompt outlined in Step 3 above.

 - Type change user /execute and hit ENTER.

Step 9: Run the Evosus application and login.

Step 10: The database upgrade script will appear. DO NOT close Evosus until the upgrade script is complete.

 - If Evosus does not open or errors appear when attempting to open, make sure no one else is on the machine or logged into Evosus. Then reinstall the software.

 - If errors continue, contact your Evosus Account Manager.

 - If you did not update the Evosus Service Host first, you will receive a message that the upgrade script cannot be completed. The message will identify which computer is the Evosus Service Host. You must update this computer first, including logging into Evosus to run the upgrade script, then run the update on all remaining servers and local installs.

Step 11: Exit Evosus and reboot the terminal server. At this point, you can begin updating local installs of Evosus if you have any in your business.


SQL Server or Host PC


Follow these steps to install Evosus on your SQL server, or local workstations.

Step 1: Verify the Evosus Service Host has already been updated. The Evosus Service Host must be the first thing upgraded.

 - You must update the Evosus Service Host server first, and then reboot it and update any remaining servers.

 - The Evosus Service Host runs your Evosus Windows Services: Evosus Daemon Service, and Evosus Mobile Service.

 - This is typically only a concern if you have multiple terminal servers OR if your Evosus Windows Services are located on a different server than your terminal server.

 - To verify which server functions as the Evosus Service Host, log into Evosus and select Help > About. The server appears in the Evosus Service Host Computer field. You can also go to Administration>System>Evosus Defaults>System Parameters. On the System tab, locate the Evosus Service Host parameter. The server name in this field is the server hosting the Evosus Windows Services.

Step 2: Log into the Windows on the server as ADMINISTRATOR

 - Contact your local IT support if you're not able to log into Windows as ADMINISTRATOR

 - The update will not install correctly if the Windows account does not have the proper permissions.

Step 3: Verify that all users have logged out of Evosus.

Step 4: Locate the Evosus share folder that you created in Step 4 above.

Step 5: If the shared Evosus folder does not reside on this Server\Host PC, Copy the Install_Evosus.exe file to the local computer

Step 6: Right click on the Install_Evosus file and select Run as Administrator.

Step 7: Follow the prompts to complete the install.

Step 8: Once the installation is complete, run the Evosus application and login.

Step 9: The database upgrade script will appear. DO NOT close Evosus until the upgrade script is complete.

 - If Evosus does not open or errors appear when attempting to open, make sure no one else is on the machine or logged into Evosus. Then reinstall the software.

 - If errors continue, contact your Account Manager.

 - If you did not update the Evosus Service Host first, you will receive a message that the upgrade script cannot be completed. The message will identify which computer is the Evosus Service Host. You must update this computer first, including logging into Evosus to run the upgrade script, then run the update on all remaining servers and local installs.

Step 10: Exit Evosus. At this point, you can begin updating local installs of Evosus if you have any in your business.



Step 6: Update The Evosus Version On Any Local Installations of Evosus 

Repeat the steps below on all local installations. Evosus will not run on local machines if their version of Evosus does not match the version installed on the server!!!
If you have a terminal server, you do not have to perform these steps on workstations that access the application using the terminal server.

#1 Log into the workstation using the Windows Username ADMINISTRATOR.

 - Installing the application while logged into a non-administrative account WILL cause problems. If you don't have access to an ADMINISTRATOR account, you need to contact your IT Support and have someone with access to that account install the application.

#2 Locate the Evosus share folder that you created in Step 4 above.

#3 Open the Software Installation Folder

#4 Copy the Install_Evosus.exe file to the local computer.

#5 Right click on the Install_Evosus file and select Run as Administrator.

 - You must select the Run as Administrator option even though you're logged in using an administrator account.

#6 Follow the prompts to complete the install.

 - Why is the installer asking for the SQL server instance? If the installer cannot locate the SQL server, it will ask you where it is located. Enter the path to the instance. For example, if your SQL server is named SQLSERVER, the path to your SQL server instance would be SQLSERVER\Evosus.

#7 Once the installation is complete, run the Evosus application and login.

#8 Verify that the application is running correctly. For example, verify that no error messages appear when the application is launched.