This article will describe the procedure to update the vSEC:CMS components from earlier versions.
When you download the latest version of vSEC:CMS you will find the different installation packages that make up the vSEC:CMS. It may be that all of the installation packages are not required for your specific setup, therefore only deploy the updated installation packages required for your specific environment. From version 5.8 the different installation packages are:
Where X.X.X is the specific product version number.
Important: Any client side component that is updated should be at least the same version of the server. If you install client components that are versions ahead of the server then you may face issues when using the client.
Updating on Server Side
Important: On the server, it is recommended to make a backup copy of the current installed version of the vSEC:CMS before performing the update. Copy the folder that the current version is installed in. For example, if the current version is installed in C:\Program Files (x86)\Versatile Security\vSEC_CMS T-Series OR C:\Program Files (x86)\Versasec\vSEC_CMS vSEC:CMS stop the vSEC:CMS Windows service (named vSEC:CMS Service) and make a backup copy of this folder on your system. It will be necessary to change the permissions on the dat folder, which is located in the root of the currently installed version, to allow the currently logged on Windows user access to this folder.
Important: If the vSEC:CMS is configured to use MS-SQL it is important to make a backup of the current SQL table on your SQL server before performing any updates.
1. Download the latest installer as provided from your vendor
2. Stop the vSEC:CMS Service on the server. If you have other services running you will be prompted to stop them as well. Select Yes in this case.
Important: If for whatever reason the CMS services don’t stop gracefully it will be necessary to manually stop the services. This can be done from Windows Task Manager. Open Windows Task Manager and from the Details tab select the following services if they are still running and click the End task button:
- AdmServer.exe – this is the vSEC:CMS Operator Console Service
- ApiServer.exe – this is the vSEC:CMS API Service
- RsdmServer.exe – this is the vSEC:CMS RSDM Service
- UssServer.exe – this is the vSEC:CMS User Self Service
- CmsServer.exe – this is the vSEC:CMS Service
3. Start the installer on the server where the current version resides;
4. Click I Agree to proceed;
5. The installer will determine that a version currently resides on the server and will prompt you to perform an update. Click the Update button to perform the upgrade;
You will be prompted to ensure that you have a valid Support and Maintenance (S+M) subscription for the product. Otherwise doing an upgrade without such a subscription in place is not allowed.
6. On completion of the upgrade click Close. You can now use the updated vSEC:CMS to perform operations as necessary.
Updating on Client Side
If performing an update on this component, it is necessary to perform the update on any client where the vSEC:CMS Operator Console (OC) application is installed.
1. Download the latest installer as provided from your vendor;
2. Start the installer on the client where the current version resides;
3. Click I Agree to proceed;
4. The installer will determine that a version currently resides on the client and will prompt you to perform an update. Click the Update button to perform the upgrade;
5. On completion of the upgrade click Close. You can now use the updated OC to perform operations as necessary.
Updating vSEC:CMS Client
From version 5.7 the vSEC:CMS Client components, vSEC:CMS USS, vSEC:CMS RSDM and vSEC:CMS VSC, are packaged as an MSI installer. Please refer to the article Installing the vSEC:CMS MSI Client for instructions on updating the client components.