|
|
|
|
Upgrading MSP Center Plus Prerequisites for applying the PPM Upgrade
- Download the PPM.
- The build number of
MSP Center Plus/OpManager MSP
installed should be 7000, 6005, 6004, 6003, 6002, 6001 or 6000. To find
the current build number of your installation, login to the central
client and click the About link in the top pane. You will find the
build number mentioned here.
- The
upgrade will take a backup of your whole central/probe folder. Hence make
sure that you have enough free disk space in your central and probe
machines. Note: If you have the daily backups scheduled and saved under
the product installation directory, move them to a different
folder so that they will be excluded from being copied.
- The whole
upgrade process may take a few hours depending on your installation
data size and the internet connectivity between the Central and
Probe. Plan accordingly during off hours.
Instructions for applying the
PPM Upgrade
- Shutdown the central
server. Note: Install
the PPM only in the central. Probes will automatically download the
pack from Central Server and upgrade themselves. The Probes restart on
their own, post upgrade.
- Make sure all the
processes are killed. Open "taskmanager" and check there are no
java, mysql, apache process running. Also terminate if any anti-virus software is running.
- Execute
UpdateManager.bat file present under <Central-Home>/bin folder.
- Click on Browse to locate and
select the PPM file that you have downloaded.
- Click on Install to
install the upgrade pack. Note: This may take some time depending on the data
size. Wait till the upgrade
is fully installed. Don't abrupt the process in the middle.
- Click on Close to exit
the UpdateManager once the upgrade is completed successfully.
- Start the Central
Server.
- Connect to the Central
WebClient and check if your upgrade is successfull. Click on the About
link and check if the build number is "7001" or "7002". Note: Build Numbers 7001 and 7002 are same with features there is no difference in builds except the number(buildNumber).So there is no need to worry about upgrading to 7002 when you are in 7001.
- The probes will automatically get upgraded and will restart.
In case of any FAILURE in the UPGRADE PROCESS follow the below steps.
- The upgrade process
takes a complete backup of your old installation, so if there is any
failure you can bring up the old setup within minutes and report the
issue immediately to support@mspcenterplus.com.
- If your central
upgrade reports any failure or if you find any serious issue after the
upgrade:
- Stop the Central
Server.
- There will be a
backup directory named as "Central_Backup_<date_time of upgrade>"
under your installation directory. For eg. if you have installed central
under "C:\AdventNetMSP" there will be a
"Central_Backup_06_Aug_2008_16_07" directory under "C:\AdventNetMSP". This is the total backup of your old
installation.
- Now go to the bin directory in command prompt and execute "OpManagerService.bat -r " . This will remove the installed services during the failed upgrade.
- Rename your current "C:\AdventNetMSP\Central" directory to
"C:\AdventNetMSP\CentralNew" and your
backup directory("Central_Backup_<date_time of upgrade>") to "C:\AdventNetMSP\Central".
- Now go to this "C:\AdventNetMSP\Central\bin" directory in command prompt and execute "OpManagerService.bat -i " . This will install the old services(and its dependents).
- Now start the
Central Server. This will restore your old installation.
- If your probe upgrade
reports any failure or if you find any serious issue after the upgrade:
- If none of your probes have upgraded,revert the central first as per the steps above
- Stop the Probe Server.
- There will be
similar backup directory named as "Probe_Backup_<date_time
of upgrade>" for the probe. Follow the steps 2 to 5(above) that is provided for the central server
and revert the probe to the previous version.
- Start Probe Server
and check if the probe communicates successfully with the Central.
- If some of your
probes have upgraded, then please report the issue to
support@mspcenterplus.com .We will revert immediately to fix the
problematic probes.
- In case of any other upgrade
failures send the zip of "Central/logs" and "Probe/logs" directory to
support@mspcenterplus.com.
TroubleShooting Tips:
- Probe - Central Communication fails after upgrade, If you have a third party SSL Certificate installed,then this issue might arise.Follow the below steps to overcome this problem.
- Shutdown the probe
- Copy the https.truststore from <Central-Home>/conf directory to <Probe-Home>/conf directory
- Go to <Probe-Home>/bin directory and execute the command "sslgen.bat -f"
2. Tabs are not properly visible in the Central webclient after upgrade
- Shutdown Central
- Go to <Central-Home>/bin directory and execute the "DBXmlTool.bat"
3. When the Central/Probe service is removed and not able to start as windows service while upgrading(this happens when the upgrade tool shows "Failed to backup central/probe directory.Not enough free disk space.")
- For this problem, open a new command prompt window and go to central\bin> folder.
- Execute "OpManagerService.bat -i" . (without quotes).
- this will install the central/probe service and now one can start central/probe as a normal win-service.
Known
Issues:
- Rebranding changes
will be lost after the upgrade. You can do the rebranding by connecting
to the Central Webclient->Admin->Rebranding MSP after the successfully completing the upgrade
process.
- For the existing user
logins other than admin and the default customer login, the new Desktop Management tab will not be accessible.
|
Document Saved Successfully
|
|
|
|
|
|
|