Upgrading to the Cloud Extender version 3.x installer, configuration tool, and modules
Information about upgrading the Cloud Extender® installer (core
agent), Base module, Cloud Extender
Configuration Tool,
Certificate Integration module, and the Email Notification module
to Cloud
Extender version
3.x.
Prerequisites to upgrading to Cloud Extender version 3.x
-
Cloud Extender installer
Requires Windows Server 2016 or later to upgrade to version 3.x.
-
Base module, Cloud Extender Configuration Tool, Certificate Integration module, and Email Notification moduleNo prerequisites required to upgrade to version 3.x.
-
Cloud Extender Configuration Tool
The old version of the Cloud Extender Configuration Tool (ASConfig.exe) is deprecated.
Effective with Cloud Extender version 3.x, you must use the new version of the Cloud Extender Configuration Tool (ConfigTool.exe) to configure the Cloud Extender modules and to monitor the status of the Cloud Extender. The new Cloud Extender Configuration Tool (ConfigTool.exe) is located in the directory where you installed Cloud Extender (typically, C:\Program Files (x86)\MaaS360\Cloud Extender\ConfigTool.exe).
To confirm that you are running the new Cloud Extender Configuration Tool:- From the Cloud Extender Configuration Tool Landing page, click . The Cloud Extender Configuration Tool version number displays 3.x.
For more information about the new user interface and features of the tool, see Using the Cloud Extender Configuration Tool.Note: To use Cloud Extender version 3.x, youmustupgrade the installer (core agent), Base module, and the Cloud Extender Configuration Tool to version 3.x. However, for theCertificate Integrationmodule and theEmail Notificationmodule, you can upgrade those modules to version 3.x depending on your Cloud Extender configuration. -
Cloud Extender configuration files
- Back up your current Cloud
Extender configuration using
the Export option in the Cloud Extender
Configuration Tool. By default, the
Cloud
Extender
configuration files are saved at C:\ProgramData\MaaS360\Cloud Extender\Downloaded
Configuration. Important: Back up the Cloud Extender configuration files to another directory apart from the Cloud Extender directory (for example, in a new folder named C:\CloudExtenderBackup).
Procedure: Exporting the Cloud Extender configuration files and importing those files to another Cloud Extender
- Start the Cloud Extender Configuration Tool from the Windows Server Start menu or access the tool directly from %Program Files(x86)%\MaaS360\Cloud Extender\ConfigTool.exe.
- Click Export to export the configuration
files.
When the configuration files have finished exporting, a
Configuration export successfully completedmessage window is displayed. Click OK. - Save the configuration files and copy those files to another Cloud Extender. By default, the files are saved at C:\ProgramData\MaaS360\Cloud Extender\Downloaded Configuration.
- On the Export message window, select the Click here to view
these files link to open the location of the configuration files that you want to copy
and to import those files to another Cloud
Extender.Example of the Cloud Extender configuration file names.
- Cloud
Extender
configuration file: CEConfiguration_xxxxxxxxxxx_XXX-XXXXXXXX
(DateTime_ServerName) Note: Each time that you export the Cloud Extender configuration file, you create a new CEConfiguration file. Make sure that you copy and import the latest exported configuration file that you created.
- Encryption key file: ConfigPrivKey.key
- Cloud
Extender
configuration file: CEConfiguration_xxxxxxxxxxx_XXX-XXXXXXXX
(DateTime_ServerName)
- For the Cloud
Extender server that is receiving the imported data, do the following.
- Download the Cloud Extender Configuration Tool and license key. For steps on downloading the Cloud Extender Configuration Tool and license key, see Downloading the license key and the Cloud Extender software.
- Install the Cloud Extender software. For steps on installing the Cloud Extender software, see Installing the Cloud Extender software.
- Review the minimum system requirements for Cloud Extender. For more information about Cloud Extender system requirements, see Cloud Extender and Mobile Enterprise Gateway (MEG) module system requirements.
- Start the Cloud Extender Configuration Tool, and click Import. The Import window is displayed.
- Copy the configuration file and the encryption key file to the Cloud
Extender server, and click
OK.
When the files have finished importing, a
Configuration import successfully completedmessage window is displayed. - Click OK.
- Back up your current Cloud
Extender configuration using
the Export option in the Cloud Extender
Configuration Tool. By default, the
Cloud
Extender
configuration files are saved at C:\ProgramData\MaaS360\Cloud Extender\Downloaded
Configuration.
Checking the Cloud Extender installer and module versions after upgrading to Cloud Extender version 3.x
- From the Cloud Extender Configuration Tool, select . The Status window displays the version numbers if you successfully upgraded the Cloud Extender installer and modules to version 3.x.
Troubleshooting issues with the upgrade to Cloud Extender version 3.x
- Installer upgrade error - module version not compatible with installer version
If you upgrade the Cloud Extender installer to version 3.x before you upgrade the impacted modules (Base module, the Cloud Extender Configuration Tool, the Certificate Integration module, or the Email Notification module) to version 3.x, an error message is displayed stating that the current Email Notification module version is not compatible with this installer along with the minimum expected version.
Remedy: Upgrade the impacted modules to version 3.x.
- Installer upgrade error - Windows Server OS version
not supported by installer version
If you upgrade to Cloud Extender version 3.x on Windows Server 2012 or earlier, an error message is displayed stating that the CE installer is not compatible with the current OS and the user must upgrade.
Remedy: Upgrade to Windows Server 2016 or later, and then retry the installer upgrade to Cloud Extender version 3.x.