Motorola MSP3-CNTRL-SW-1 Software Setup Guide - Page 15

Installing MSP 3.3.1

Get Motorola MSP3-CNTRL-SW-1 - Mobility Services Platform Control Edition PDF manuals and user guides View all Motorola MSP3-CNTRL-SW-1 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

Chapter 2 - Installing MSP 3.3.1 Before Installing MSP 3.3.1 If you are planning to install the MSP Core Database on a SQL Server instance that is running on a different box than the rest of the MSP components will be, then you should have two domain users available before beginning the installation of MSP 3.3.1. One domain user is required for installation and a separate domain user is required for runtime. Otherwise, for an installation with everything on one box, then a local service account will be created by the installer. Note: The only exception to this is if you are not using Long Term Analysis and can use SQL Authentication to install the Core Database and access it at runtime. Upgrading from Previous MSP Versions Notes: Beginning with MSP 3.3.1, you no longer need to remove MSP before performing an upgrade. Use the steps below to perform the upgrade. Following an upgrade, the Relay Servers in your Enterprise will have to be Activated manually from the MSP Console UI. The Relay Servers are Deactivated during an upgrade so that network traffic following the upgrade can resume at a measured pace. 1. Upgrades to MSP 3.3.1 are supported only from MSP versions 3.2.1 or 3.3. 2. Motorola recommends exporting all Objects before continuing; see Using MSP 3.3.1 - Understanding Objects for more detail. Motorola also recommends saving at least one SQL backup of your current install. This is a precautionary step in case something goes wrong with the upgrade. 3. Proceed with installing MSP 3.3.1 (see below). 4. After accepting the license agreement (Step 5), the installer will indicate that it has detected an existing MSP installation and ask if you wish to upgrade it.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
Chapter 2
–
Installing MSP 3.3.1
Before Installing MSP 3.3.1
If you are planning to install the MSP Core Database on a SQL Server instance that is running on
a different box than the rest of the MSP components will be, then you should have two domain
users available before beginning the installation of MSP 3.3.1.
One domain user is required for
installation and a separate domain user is required for runtime.
Otherwise, for an installation with
everything on one box, then a local service account will be created by the installer.
Note:
The only exception to this is if you are not using Long Term Analysis and can use SQL
Authentication to install the Core Database and access it at runtime.
Upgrading from Previous MSP Versions
Notes:
Beginning with MSP 3.3.1, you no longer need to remove MSP before performing an upgrade.
Use the steps below to perform the upgrade.
Following an upgrade, the Relay Servers in your Enterprise will have to be Activated manually
from the MSP Console UI. The Relay Servers are Deactivated during an upgrade so that network
traffic following the upgrade can resume at a measured pace.
1.
Upgrades to MSP 3.3.1 are supported only from MSP versions 3.2.1 or 3.3.
2.
Motorola recommends exporting all Objects before continuing; see Using MSP 3.3.1
–
Understanding Objects for more detail. Motorola also recommends saving at least one
SQL backup of your current install. This is a precautionary step in case something goes
wrong with the upgrade.
3.
Proceed with installing MSP 3.3.1 (see below).
4.
After accepting the license agreement (Step 5), the installer will indicate that it has
detected an existing MSP installation and ask if you wish to upgrade it.