Update Procedure
The following provides more information about the process used by the Update Manager to update the DSM environment.
Create Update Packages
The Update Manager automatically determines and displays the status of the update packages. If the packages are not current, click “Prepare Packages” to create the required packages and prepare them for distribution.
If you choose to skip this step and not to use the newly created packages, any following actions are processed using the packages that currently exist in your environment.
The polling cycle of the Distribution Service (in charge of the ORG Master Share) must complete, before distribution to all depots can start. By reducing the polling interval in the DSMC to 5 minutes, for example, you can determine when the distribution will start. The default value is 60 minutes.
Package Distribution
This page lists all the depots to which packages have been distributed.
There are different ways of checking the distribution status depending on your version of DSM:
Update from 7.0
When you click on Create Packages the update packages are created in the Global Software Library and can be viewed in the DSMC. The following packages are created: DepotAll, DepotMasterOnly, DepotPrepackagedApps, DepotDocs.
Click Show Distribution Status on the context menu to determine the distribution status.
Update from 7.1 or 7.2
When you click on Create Packages the update packages are created in the Global Software Library and can be viewed in the DSMC. The following packages are created: DepotAll, DepotMasterOnly, DepotPrepackagedApps, DepotDocs.
To determine the distribution status, you can either open the Distribution tab in the DSMC or open Infrastructure Monitoring.
Update from 2013.2
The Update Manager automatically checks the current distribution status when you click Check Distribution Status.
BLS Readiness
Run this check to identify whether it is possible to immediately update the BLS. To start the check, click Check BLS Readiness.
To run an update, the following requirements must be met:
- “Long-running tasks” must not be running. These are tasks the BLS processes in the background and which can take a very long time.
- The number of messages in the Auxiliary Service‘s message queue must not exceed 100 messages. A higher value indicates that the Auxiliary Service is either not running or that the message load is too high. This service is needed to process the progress of the update and to display the results in the Update Manager.
- The system runs a check to ensure that the configured BLS authentication account is a DSM supervisor
Check System Requirement
Use this check to ensure that the Management Points meet the installation requirements of the new version. For example, to check whether the correct IIS or .NET Framework version is installed.
Before you can check the system requirements, the update packages must be distributed with the new files. The update packages are downloaded to the Management Point’s Repository cache for checking. Click Check System Requirements to begin. This check is executed across a distributed environment.
Depot Access Check
Here, the Write access to all depots is checked. Click Start Depot Access Check to begin. This check is executed across a distributed environment.
The Management Points that are in charge of the Work-Install distribution of the depots must have Write access to the depot with their Distribution account. Use this check to ensure that no DSMC.exe or any other programs will be executed from the depot during the update.
Remove BLS from production
Once the checks are completed, the update of the depots and Management Points is ready to start. The BLS must be set to installation mode. From this point on, clients can no longer synchronize with the BLS and the database cannot be changed during the update phase. Click Set Installation Modek to begin. This task is executed across a distributed environment.
Update Depots
This page indicates that all of the depots in the environment are ready to be updated. Click Start Depot Update for the Management Points to begin updating their depots. This task is executed across a distributed environment.
Migrate ICDB
Use this dialog if the update calls for changes to the ICDB. Click Start ICDB Migration to begin. The changes to the ICDB are performed directly on the ORG Master Share.
Distribute ICDB
The Distribution Services will distribute the new ICDB to all depots as fast as possible. Click Start ICDB Distribution to begin. This task is executed across a distributed environment.
Prepare Client Binaries
In order for the clients to be updated, the respective packages must be prepared on all depots. Click Prepare Client Binaries to begin creating the packages. Note that the packages are only needed for the client update. This task is executed across a distributed environment.
Update Primary BLS
Use this page to update the primary BLS. The Update Manager displays the update progress. If the Update Manager was not started on the primary BLS, you may not be able to continue. In this instance you need to exit the Update Manager and restart the process on the primary BLS. Click Start Update to begin.
Update Auxiliary Service
This page is displayed only if the Auxiliary Service is running separately from the BLS. The Management Point with the Auxiliary Service will be updated at this point. If the Update Manager is not started on the Management Point with the Auxiliary Service, you will be prompted to update the Management Point with the Auxiliary Service manually.
Update Management Points
Once the Primary BLS and the Auxiliary Service have been updated, the Update Manager will begin to update all other Management Points within the environment. Click Update Management Points to begin. This task is executed across a distributed environment.
Change of the encryption method (for the update to DSM 2015.1 only)
When updating to DSM 2015.1, the method for the encryption of passwords is changed once. As a prerequisite, the configuration database (ICDB) needs to be successfully distributed to all depots. If not all of the depots have the current configuration at this stage of the update process, the steps to change the encryption method will be skipped. An appropriate information is shown how to proceed in this case.
Otherwise the following three steps are executed subsequently to change the encryption method:
•Prepare change of encryption
The depots are prepared to encrypt the passwords which are used by the Management Points. To do this, a protected directory is created for storing the Private Key.
• Change encryption
The Private Key for the encryption of passwords is created and then stored in the protected directory of the depot. The access is restricted to the Distribution Service account and the system account. After that, all passwords which are used by the Management Points are re-encrypted (e.g. the password of the Distribution Service account or the SIS account).
• Start ICDB distribution
The updated configuration database (ICDB) is now distributed to the depots. The protected directory is also distributed with the private key and the correspondingly limited access.
Depots that communicate only via HTTP must be changed to this new encryption method manually.
See: Protecting HTTP Depots
Enable Productive Environment
Once update of the depots and Management Points is completed, enable Productive Mode for the BLS if applicable. Click Set Productive Mode to begin. This task is executed across a distributed environment.