mechanical means, without permission in writing from Motorola. This includes electronic or
mechanical means, such as photocopying, recording, or information storage and retrieval
systems. The material in this manual is subject to change without notice.
The software is provided strictly on an “as is” basis. All software, including firmware, furnished to
the user is on a licensed basis. Motorola grants to the user a non-transferable and non-exclusive
license to use each software or firmware program delivered hereunder (licensed program).
Except as noted below, such license may not be assigned, sublicensed, or otherwise transferred
by the user without prior written consent of Motorola. No right to copy a licensed program in
whole or in part is granted, except as permitted under copyright law. The user shall not modify,
merge, or incorporate any form or portion of a licensed program with other program material,
create a derivative work from a licensed program, or use a licensed program in a network without
written permission from Motorola. The user agrees to maintain Motorola’s copyright notice on the
licensed programs delivered hereunder, and to include the same on any authorized copies it
makes, in whole or in part. The user agrees not to decompile, disassemble, decode, or reverse
engineer any licensed program delivered to the user or any portion thereof.
Motorola reserves the right to make changes to any software or product to improve reliability,
function, or design.
Motorola does not assume any product liability arising out of, or in connection with, the
application or use of any product, circuit, or application described herein.
No license is granted, either expressly or by implication, estoppel, or otherwise under any
Motorola, Inc., intellectual property rights. An implied license only exists for equipment, circuits,
and subsystems contained in Motorola products.
MOTOROLA and the Stylized M Logo and Symbol and the Symbol logo are registered in the US
Patent & Trademark Office. All other product or service names are the property of their respective
owners.
Motorola, Inc
One Motorola Plaza
Holtsville, New York 11742-1300
http://www.symbol.com
Page 5
Table of Contents
Before You Begin................................................................................................1
Read This First .........................................................................................................................................1
About the Guide........................................................................................................................................ 1
Related Documents.......................................................................................................................... 1
Service Information...........................................................................................................................2
Installing Microsoft IIS............................................................................................................................. 11
Repairing IIS Mapping After Reinstalling IIS..................................................................................... 11
About this Chapter.................................................................................................................................. 31
Before You Begin............................................................................................................................ 31
Installing a Database Server with Download from Motorola.............................................................. 34
Installing a Database Server with the Installation CD........................................................................ 34
Completing the Installation of a Database Server............................................................................. 35
Installing MSP Services and MSP Web Server......................................................................................... 43
Installing the MSP Services and MSP Web Server with Download from Motorola.............................. 43
Installing MSP Services and MSP Web Server with the Installation CD............................................. 43
Completing Installation of an MSP Web Server................................................................................ 44
Possible Post-Installation Steps............................................................................................................... 51
Chapter 6 – Installing the High Availability (HA) Configuration....................53
Before you Begin.................................................................................................................................... 53
About High Availability and Distributed Setups......................................................................................... 53
HA Configuration............................................................................................................................ 53
General Process..................................................................................................................................... 57
Upgrading the Database Server............................................................................................................... 58
Page 7
Before You Begin
Read This First
Motorola recommends that you read this entire document before you begin installing MSP 3.2. If
you skip to Chapters 4 or 5 without reading Chapters 1, 2, and 3, your installation experience may
not go smoothly.
MSP 3.2 Stage and Provision Editions, as well as Control Edition (without Data Collection and
Analysis) offer the most straight-forward installations. If you choose to use MSP 3.2 Control
Edition with Data Collection and Analysis functionality, you will have to install Analysis Services.
If you plan to install Microsoft SQL Server 2005 Standard or Enterprise editions with Analysis
Services on a separate server from the rest of the MSP 3.2 software, you must go to Chapter 5
after reading Chapters 1, 2, and 3. Chapter 5 discusses the specifics of installing MSP with Data
Collection where SQL 2005 Standard or Enterprise edition is installed on a separate server. If you
have other custom setup type scenarios not covered in this document, referencing Chapter 5
might offer additional help.
Chapter 6 discusses a High Availability (HA) Configuration installation.
Chapter 7 focuses on the specifics of upgrading your database server to SQL Server 2005
Standard or Enterprise editions for use with MSP 3.2.
About the Guide
The MSP 3.2 Software Installation Guide provides general instructions for installing the MSP 3.2
software product. Newer versions of this document may be available at
If you have a problem with your software, contact Motorola Enterprise Mobility support for your
region. Contact information is available at: http://www.symbol.com/contactsupport.
When contacting Enterprise Mobility support, please have the following information available:
• Serial number of the software
• Model number or product name
• Software type and version number
• Software license information
Motorola responds to calls by email, telephone or fax within the time limits set forth in support
agreements.
If you purchased your Enterprise Mobility business product from a Motorola business partner,
contact that business partner for support.
Page 9
Chapter 1 - Introduction
Mobility Services Platform version 3.2 enables you to choose to better manage your mobile
assets with the addition of a Data Collection module that gives you the flexibility of collecting and
analyzing data down to the individual device level.
MSP 3.2 Control Edition can be installed for use with or without Data Collection and Analysis. In
previous versions of MSP, you could use Microsoft SQL Server Express 2005 or Microsoft SQL
Server 2005 Standard or Enterprise editions as your database. In MSP 3.2, you can still use
either as your database for Stage Edition, Provision Edition, or Control Edition without Data
Collection and Analysis. However, in MSP 3.2 Control Edition, you must use Microsoft SQL
Server 2005 Standard or Enterprise editions if you plan to use Data Collection and Analysis.
This change means MSP users must determine which installation scheme best suits their
enterprise.
Typical Setup Option or Custom Setup Option
At an early point in the installation of MSP 3.2, you will see the screen in Figure 1. Your decision
about the setup type needs to be made before you see this screen.
Figure 1
Page 10
4 Chapter 1 - Introduction
Common Installation Scenarios
Scenario Type
•New installation on one server with or without Data
Collection
•Upgrade from 3.1/3.1.1 on one server with or without
Data Collection
•New installation without Data Collection where the
instance of Microsoft SQL Server 2005 is on a
second, separate server
•Upgrade from 3.1/3.1.1 on one server without Data
Collection where the instance of Microsoft SQL Server
2005 is on a second, separate server
•Using Windows authentication to the Microsoft SQL
Server 2005 database
•New installation or upgrade from 3.1 or 3.1.1 with
Data Collection where the instance of Microsoft SQL
Server 2005 is on a second, separate server
• *Distributing MSP Components across multiple servers
• *Installing MSP in a High Availability Configuration
(HAC); see Chapter 5 for an overview
Typical
Typical
Custom
Custom
*Specific details for these scenarios are not covered in this
document.
MSP 3.2 Delivery Methods
MSP 3.2 is available on an installation CD and by download from Motorola at:
http://support.symbol.com/support/product/softwaredownloads.do. There are differences in the
delivery methods.
Downloading from Motorola
The following files are available for download:
• MSP32_InstallGuide.pdf
• MSP32_UserGuide.pdf
• MSP32_ReleaseNotes.pdf
• MSP32_InstallServer32.msi
• MSP32_InstallServer64.msi
• MSP32_InstallWorkstation.msi
Page 11
Chapter 1 - Introduction5
5
Note:
No prerequisite software will be included.
If your enterprise plans to use the Data Collection feature of MSP 3.2 you must have Microsoft
SQL Server 2005 Standard or Enterprise editions installed. Otherwise, users can download SQL
Server Express 2005 SP2 (both 32 and 64 bit versions) and installation instructions for free from
the Microsoft Download Center at:
Users can also download the latest version of Microsoft .Net Framework 2.0 (both 32 and 64 bit
versions) from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=55731
.
Installation CD
Users will launch the installation CD which will guide them through the installation process. All
manuals, all pre-requisite software, all applications, and SQL Server 2005 Express are included
on the CD.
Page 12
6 Chapter 1 - Introduction
Page 13
Chapter 2 – MSP Server Requirements
Minimum Software and Hardware Requirements
Servers on which you plan to install MSP 3.2 must meet the minimum software and hardware
requirements listed in Table 1.
Table 1 – Minimum Software and Hardware Requirements
Category Requirements
§ Windows Server 2003 Standard edition with SP2 or higher
§ Windows Server 2003 Enterprise edition with SP2 or higher
§ Windows Server 2003 Web edition with SP2 or higher
§ Windows Server 2003 R2 Standard edition with SP2 or higher
§ Windows Server 2003 R2 Enterprise edition with SP2 or higher
Windows Operating
Systems
§ Windows Server 2003 R2 Web edition with SP2 or higher
§ Windows Server 2003 R2 Standard x64 edition with SP2 or higher
§ Windows Server 2003 R2 Enterprise x64 edition with SP2 or
higher
Important:
Windows XP is not supported. MSP 3.2 is not supported on Windows
Server systems that are Domain Controllers.
Page 14
8 Chapter 2 – MSP Server Requirements
Category Requirements
§ Microsoft Internet Information Services 6 – See Page 11 for
installation instructions and for a repair if known mapping problems
occur when reinstalling IIS.
Additional Software
Hardware for Stage,
Provision, or Control
Editions without Data
Collection
§ Microsoft .NET Framework 2.0
§ Microsoft SQL Server 2005 (see Table 2 – SQL Server 2005
Version Requirements)
These are recommended minimum specifications for the computer on
which you will run the above versions of MSP Server. These are only
recommendations and you may obtain satisfactory performance on
computers with a configuration that differs from these specifications.
The High Availability Configuration of MSP will require at least four
computers (this does not mean you will need 4 additional servers) with
the following minimum specifications.
§ 3 GHz processor
§ 1 GB of memory
§ 40 GB hard drive
Note:
The perceived performance of MSP Server is affected by many
parameters other than the configuration of the computer on which it
runs. See the MSP 3.2 User’s Guide for more information on factors
that can affect MSP performance.
Hardware for Control
Edition with Data
Collection
These are recommended minimum specifications for the computer on
which you will run the above version of MSP Server. The High
Availability Configuration of MSP will require at least four computers
(this does not mean you will need 4 additional servers) with the
following minimum specifications.
§ Dual 2.33 GHz dual-core Xenon 5140 processors
§ 4 GB of memory
§ 40 GB space available on hard drive
Note:
The perceived performance of MSP Server is affected by many
parameters other than the configuration of the computer on which it
runs. See the MSP 3.2 User’s Guide for more information on factors
that can affect MSP performance.
Page 15
Chapter 2 – MSP Server Requirements9
9
SQL Server 2005 Requirements
The edition of Microsoft SQL Server 2005 you must use is determined by how the installation of
MSP 3.2 will be used. The following table delineates which edition you must use
Table 2 – SQL Server 2005 Version Requirements
If MSP 3.2 will be used for a… SQL Server 2005 Version Requirements
§ New installation
§ On a single server
§ Without Data Collection
§ New installation
§ On a single server
§ With Data Collection
§ New installation
§ The instance of Microsoft SQL
server is on a second, separate
server
§ Without Data Collection
§ Upgrade from 3.1/3.1.1
§ On a single server
§ Without Data Collection
Microsoft SQL Server 2005 Express or SQL Server 2005
Standard or Enterprise without SSAS enabled, as well as
the other software and hardware requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
SQL Server 2005 Standard or Enterprise with SSAS
enabled, as well as the other software and hardware
requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
Microsoft SQL Server 2005 Express or SQL Server 2005
Standard or Enterprise without SSAS enabled, as well as
the other software and hardware requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
Microsoft SQL Server 2005 Express or SQL Server 2005
Standard or Enterprise without SSAS enabled, as well as
the other software and hardware requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
§ Upgrade from 3.1/3.1.1
§ On a single server
§ With Data Collection
§ Upgrade from 3.1/3.1.1
§ The instance of Microsoft SQL
server is on a second, separate
server
§ Without Data Collection
SQL Server 2005 Standard or Enterprise with SSAS
enabled, as well as the other software and hardware
requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
If you are going to upgrade the database from SQL
Server2005 Express, see Chapter 6 for more information.
Microsoft SQL Server 2005 Express or SQL Server 2005
Standard or Enterprise without SSAS enabled, as well as
the other software and hardware requirements listed in
Table 1 – Minimum Software and Hardware
Requirements.
Page 16
10 Chapter 2 – MSP Server Requirements
Exceptions:
If a server will be a Database Server only, SQL Server 2005 Express, Standard, or Enterprise will
be required, but the installer will not require Internet Information Services 6 or .NET Framework
2.0.
If a server will be a Web Server only, SQL Server 2005 will NOT be required, but MSP 3.2 will
require Internet Information Services 6 and .NET Framework 2.0.
Suggested Microsoft SQL Sever 2005 Standard or
Enterprise Edition Settings
Required to be installed
• SQL Server Database Engine
• Analysis Services Engine (if MSP 3.2 Control Edition with Data Collection and Analysis
will be used)
Required Configuration
• TCP/IP enabled under SQL Server 2005 Network Configuration
Authentication
• SQL Authentication must be enabled to use the Typical Setup Type Option
• Windows Authentication will require the use of the Custom Setup Type Option
Page 17
Chapter 3 – Installing Pre-Requisite Software
Installing Microsoft IIS
Use the following steps to install IIS:
1. From the Start menu, go to Control Panel > Add or Remove Programs.
2. Click the Add/Remove Windows Components tab in the left pane.
3. In the list of Windows Components, select Application Server and click Details.
4. In the list of Application Server subcomponents, select Internet Information Services (IIS) and click the Details.
5. In the list of IIS subcomponents, select World Wide Web Service and click Details.
6. In the World Wide Web Service list, select World Wide Web Service and click OK.
7. In the Application Server dialog box, click OK.
8. In the Windows Components dialog box, click Next. The installation program will
prompt you for the Windows CD that was used to install the operating system. Follow the
prompts to complete the installation of IIS.
9. To verify that IIS has been installed correctly–
a. From the Start menu, go to Administrative Tools.
b. Verify that Internet Information Services (IIS) Manager is listed as one of the
Administrative tools.
Repairing IIS Mapping After Reinstalling IIS
Because of a known problem with the Microsoft IIS Framework, the following error message may
display if you reinstall Microsoft IIS:
Page 18
12 Chapter 3 – Installing Pre-Requisite Software
Server Error in '/MSP.Web' Application
The following Microsoft article describes the problem and how to correct it: How to repair IIS
mapping after you remove and reinstall IIS located at
Installing .NET Framework 2.0 from the Downloaded Version
If you downloaded .NET Framework 2.0 from http://go.microsoft.com/fwlink/?LinkId=55731, use
the installation instructions that come with it to install the software.
Installing .NET Framework 2.0 from the Installation CD
To install .NET Framework 2.0:
1. Place the Installation CD in the appropriate drive to display the Welcome to the MSP 3.2 CD Launcher dialog box (Figure 3)
2. Click Install .NET Framework 2.0.
Note:
You should have minimal interaction with this installation. A series of dialog
boxes will appear and disappear as they complete their functions. When the
final product is installed, you will be told the installation was successful.
Installing Microsoft SQL Server 2005 Standard or
Enterprise Editions
Important:
Motorola provides a batch file that can perform the following task. The file is
named SetupSQLStd.bat.
If you intend to use the Motorola-provided batch file, copy it from the MSP
Installation CD (Prerequisite\SQLBatchFiles\SetupSQLExpress.bat) to a
folder on the local hard drive (for example; C:\BatchFiles) before completing
the following steps.
1. Place the Microsoft SQL Server 2005 installation CD in the appropriate CD drive.
3. From the Command Prompt, navigate to the appropriate CD drive.
Page 19
Chapter 3 – Installing Pre-Requisite Software13
13
Important:
In the following steps, the examples provided assume 1) the batch file referred to
was placed in a folder on your hard drive named C:\BatchFiles, and 2) the drive
letter of your CD drive is D:. Your drive letters and folder names may be different;
please make the appropriate adjustments.
4. From the command line while in the SQL Server Standard CD root directory, either:
o Invoke the batch file (with a Product Key Argument) as follows: D:\>
C:\BatchFiles\SetupSQLStd.bat ABCDE12345FGHIJ67890KLMNO
OR
o Type: start /wait setup.exe /qb INSTANCENAME=MSP
You will need to substitute the product key from your SQL Server 2005 Standard or
Enterprise edition for the sample value shown for the PIDKEY option.
If you are not installing on an English localization on Windows, the "NT
AUTHORITY\SYSTEM" values may have to be changed.
Installing Microsoft SQL Server 2005 Express
There are two quick ways to install SQL Server 2005 Express so it will be pre-configured for use
with MSP 3.2. It can be downloaded from Microsoft and installed with the use of a command line,
or you can use the Installation CD to install the software.
Note:
Microsoft .NET Framework 2.0 must be on the server before installing SQL Server 2005 Express.
Installing SQL Server 2005 Express with a Command line
Important:
Motorola provides a batch file that can perform the following task. The file is
named SetupSQLExpress.bat.
If you intend to use the Motorola-provided batch file, copy it from the MSP
Installation CD (Prerequisite\SQLBatchFiles\SetupSQLExpress.bat) to a
folder on the local hard drive (for example; C:\BatchFiles) before completing
the following steps.
Page 20
14 Chapter 3 – Installing Pre-Requisite Software
To install SQL Server 2005 Express:
1. Download SQL Server 2005 Express from the Microsoft Download Center at:
3. From the Command Prompt, navigate to the location of the downloaded installation file.
Important:
In the following steps, the examples provided assume the batch file referred to was
placed in a folder on your hard drive named C:\BatchFiles. Your drive letters and
folder names may be different; please make the appropriate adjustments.
1. From the command line while at the location of the downloaded installation file, either:
o Invoke the batch file (with a Product Key Argument) as follows:
C:\BatchFiles\SetupSQLExpress.bat
OR
o Invoke: SQLEXPR.EXE q /norebootchk /qb reboot=ReallySuppress addlocal=all
You should have minimal interaction with this installation. A series of dialog
boxes will appear and disappear as they complete their functions. The Setup
Progress dialog box (Figure 2) alerts you to the status of the install. When the
final product is installed, the dialog box will close automatically.
Figure 2
Page 21
Chapter 3 – Installing Pre-Requisite Software15
15
Installing SQL Server 2005 Express with the Installation CD
To install SQL Server 2005 Express:
1. Place the Installation CD in the appropriate drive to display the Welcome to the MSP 3.2 CD Launcher dialog box (Figure 3)
,
Figure 3
2. Click Install Microsoft SQL Server 2005 Express Edition.
Note:
You should have minimal interaction with this installation. A series of dialog
boxes will appear and disappear as they complete their functions. The Setup
Progress dialog box (Figure 4) alerts you to the status of the install. When the
final product is installed, the dialog box will close automatically.
Figure 4
Page 22
16 Chapter 3 – Installing Pre-Requisite Software
Page 23
Chapter 4 – Installing MSP 3.2 with the Typical
Setup Type
Installing MSP Server 3.2 with the Typical Setup Type
Option in a New Installation
IMPORTANT:
If you downloaded the Installation Package, go to Installing MSP 3.2 with Download from
Motorola.
If you are using the Installation CD, go to Installing with the Installation CD on Page 18.
Installing MSP 3.2 with the Typical Setup Type Option and Files
Downloaded from Motorola
To install MSP 3.2:
1. Download the following installation files from Motorola at
http://support.symbol.com/support/product/softwaredownloads.do:
o MSP32_InstallServer32.msi
OR
o MSP32_InstallServer64.msi
2. Browse to the location to which you downloaded the Installation Package and doubleclick either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the Welcome dialog box.
3. Go to Completing Installation of MSP 3.2 with the Typical Setup Type Option on Page 19
to continue.
Page 24
18 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Installing MSP 3.2 with the Typical Setup Type Option using the
Installation CD
To install MSP 3.2 with the Installation CD:
1. Place the Installation CD in the appropriate drive. The Welcome to the MSP 3.2 CD
Launcher dialog box (Figure 5) will display. (This may take a few seconds.)
Figure 5
2. Check the list of MSP Server Prerequisites. If you:
§HAVE the prerequisites, click Install MSP 3.2 Server. To display the
Welcome dialog box.
Note:
The installer will display a button to install either the 32 bit or 64 bit version
depending on which version of Windows it detects.
§DO NOT HAVE some or all of the prerequisites, click Cancel and install the
prerequisite software before restarting the installation.
Important:
The installer will begin the install process if prerequisite software is not
detected, but discontinue the installation at a certain point if prerequisite
software is not detected.
If a server will be a Database Server only, SQL Server 2005 Standard or
Enterprise will be required, but MSP 3.2 will not require Internet Information
Page 25
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type19
19
Services 6 or .NET Framework 2.0.
If a server will be a Web Server only, SQL Server 2005 will NOT be required,
but MSP 3.2 will require Internet Information Services 6 and .NET Framework
2.0.
3. Go to Completing Installation of MSP 3.2 with the Typical Setup Type Option to continue.
Completing Installation of MSP 3.2 with the Typical Setup Type
Option
To finish a New, Typical installation:
1. On the Welcome dialog box (Figure 6), click Next, and a list of prerequisites will display
(Figure 7).
Figure 6
Page 26
20 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Figure 7
2. Check the list of prerequisites. If you:
§ HAVE the prerequisites, click Next.
§ DO NOT HAVE some or all of the prerequisites, click Cancel and install the
prerequisite software before restarting the installation.
§ARE UNCERTAIN if you have the prerequisites, click Next to continue with
the installation.
Important:
The installer will begin the install process if prerequisite software is not
detected, but discontinue the installation at a certain point if prerequisite
software is not detected.
If a server will be a Database Server only, SQL Server 2005 Standard or
Enterprise will be required, but MSP 3.2 will not require Internet Information
Services 6 or .NET Framework 2.0.
If a server will be a Web Server only, SQL Server 2005 will NOT be required,
but MSP 3.2 will require Internet Information Services 6 and .NET Framework
2.0.
3. On the License Agreement dialog box (Figure 8), accept the license agreement and
click Next.
Page 27
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type21
21
Figure 8
4. When the Setup Type dialog box (Figure 9) appears, select Typical and click Next.
Important:
For a “Typical” install, you must have Mixed Mode authentication enabled in
SQL Server.
5. If the installer detects that Internet Information Services (IIS) is:
§ Installed, go to Step 6 to continue.
§ Not installed, you will be prompted that the software is not installed (Figure
10). Click OK and the Installer Completed dialog box will display (Figure
11). Click Finish to exit the installer.
Figure 9
Page 28
22 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Figure 10
Note:
You can install IIS 6 from the original Windows installation CDs. Go to Page
11 for instructions on installing Microsoft IIS 6.
6. If the installer detects that .NET 2.0 is:
§ Installed, go to Step 7 to continue.
§ Not installed, you will be prompted that the software is not installed. Click
OK and the Installer Completed dialog box will display. Click Finish to exit
the installer.
Note:
The .NET 2.0 installer is included on the MSP 3.2 installation CD. Users can
also download the latest version of Microsoft .Net Framework 2.0 (both 32
and 64 bit versions) from the Microsoft Download Center at
http://go.microsoft.com/fwlink/?LinkId=55731. Go to Page 12 for instructions
on how to install .Net Framework 2.0.
Figure 11
7. On the Destination Folder dialog box (Figure 12), accept the destination folder or click
Change to change the destination.
Page 29
23
8. Click Next.
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type 23
Figure 12
Important:
At this point the installer has made note of any instances of Microsoft SQL Server on the
computer on which the installation is being run. The exact sequence of the next few steps
depends on what, if any, SQL Server instances are discovered and the installer’s success in
contacting the SQL Server instances.
You may receive one or more error and/or success messages during this part of the installation.
Keep clicking OK to continue.
If the installer successfully connects with a SQL Server instance, you will end up at Step 11.
If the installer CAN NOT connect with a SQL Server instance, you will end up at Step 9.
9. Use the information in the following table to complete the fields on the Database Installation Connection dialog box (Figure 13):
Page 30
24 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Figure 13
Table 3 – Database Installation Connection Dialog Box Information
In Field… What you need to do and know…
• You can leave the default value if it is correct.
• You can type in the correct name and path to the SQL
instance you will use (Examples:
(local)\<YourInstanceName>, ServerName\MSP,
ServerName\<YourInstanceName>)
•If you want to search for SQL instances, click Browse
Database server that you are
installing to
and the installer will look for SQL instances on the
computer on which you are installing MSP 3.2 and on the
computers networked to the install computer. Select the
appropriate SQL instance and click OK.
•Motorola recommends clicking the dropdown arrow to
see the running SQL instances on the computer on which
you are installing MSP 3.2 if you are installing MSP 3.2
on the same server on which your SQL database is
installed. Select the appropriate SQL instance.
•If you are installing the MSP Database on another server,
you must use SQL authentication.
Connect to install using
•If you choose Windows authentication, the Login ID and
Password fields will be grayed out.
Login ID Use the sa ID or the ID of a user with sysadmin permissions.
Password
Name of database catalog
Motorola recommends using the default value, 11!Noxlet.
Select a name for the database that will be installed. MSP is the
default value.
Page 31
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type25
25
10. Click Next.
11. On the Ready to Install dialog box (Figure 14) click Install.
Figure 14
12. When the Installer Completed dialog box displays (Figure 15), click Finish.
Note:
In some instances, you may be prompted to restart the system. If prompted,
do the restart.
Figure 15
Page 32
26 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Installing MSP Server 3.2 with an Existing Version of
MSP Server 3.0
Important:
You cannot install MSP Server 3.2 over an existing version of MSP Server 3.0.
Uninstalling MSP 3.0
To uninstall MSP 3.0:
1. Click Start > Control Panel > Add or Remove Programs.
2. Select MSP 3.0 and click Remove.
Important:
Make sure you select the check box that indicates you want to keep all data
associated with MSP.
Installing MSP 3.1.1
By installing 3.1.1, you convert the 3.0 version database to a 3.1.1 database. If you attempt to
install MSP 3.2 before converting the database, the installer displays the screen in Figure 16.
Figure 16
The MSP 3.1.1 Software Installation Guide provides general instructions for installing the MSP
3.1.1 software product. Newer versions of this document may be available at
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type27
27
Installing MSP Server 3.2 with an Existing Version of
MSP Server 3.1 or 3.1.1
In order to Install MSP Server 3.2 on a server with an existing version of MSP Server 3.1 or 3.1.1,
you must first remove the existing version.
Note:
If you do not remove the existing MSP version, the installer will cancel the
installation.
If you want Data Collection you may need to upgrade the database from SQL Server
2005 Express, see Chapter 6 for more information.
Uninstalling MSP 3.1 or 3.1.1
To uninstall MSP 3.1 or 3.1.1:
1. Click Start > Control Panel > Add or Remove Programs.
2. Select appropriate MSP version and click Change to display the InstallShield Wizard
(Figure 17).
Figure 17
3. Click Next to display the Program Maintenance dialog box (Figure 18).
Page 34
28 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Figure 18
4. Select the Remove radio button and click Next to display the Remove Program dialog
box (Figure 19).
5. Select the Keep all data associated with MSP check box.
Warning:
Failure to select the Keep all data associated with MSP check box will result in the
loss of your database.
6. Click Remove.
7. When the InstallShield Wizard Completed dialog box displays (Figure 20), click Finish.
Figure 19
Page 35
29
8. To perform a:
Chapter 4 – Installing MSP 3.2 with the Typical Setup Type 29
Figure 20
§Typical Installation, go to Installing MSP Server 3.2 with the Typical Setup
Type Option in a New Installation on Page 17 to continue.
§Custom Installation, go to Custom Setup Type Installation Scenarios for
more information.
Page 36
30 Chapter 4 – Installing MSP 3.2 with the Typical Setup Type
Page 37
Chapter 5 – Installing MSP 3.2 Server with the
Most Common Custom Configuration
Advanced Users Recommended
The Custom Setup Type Option requires the most interaction with the installation process and
most familiarity with SQL Server and file sharing configuration. It is recommended for advanced
users.
About this Chapter
You should have read Chapters 1, 2, and 3 before beginning with this installation. This chapter
concentrates on installing MSP 3.2 Control Edition with Data Collection and Analysis functionality
where the SQL database, Analysis Services, and a shared folder for the User Data Files are all
on the same server and separate from the server on which the rest of the MSP 3.2 components
are installed. SQL authentication must be used in all areas.
Important:
Analysis Services and the shared folder for User Data Files must be installed on the same server
as the SQL database in this installation scenario. Any other configuration is not covered.
While this is the most-common Custom Setup Type Option installation, there are many others. If
your particular installation scenario is different from those in this guide, you may need to contact
Motorola support.
Before You Begin
Requirements
•Read Chapters 1, 2, and 3 and make sure all software and hardware requirements have
been met.
Page 38
32 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
•Make sure Microsoft SQL Server 2005 Enterprise or Standard edition is installed on the
database server. (Chapter 6 describes how to upgrade from SQL Server 2005 Express to
SQL Server 2005 Enterprise or Standard edition.)
• All servers must be part of the same Domain.
• A SQL login with ‘sysadmin’ rights must be created in SQL prior to installation. This login
can be removed when installation is complete.
• A Domain user must already exist to be used for authentication.
• Create or select an existing Domain user for use with MSP. The Domain user does not
need to be the member of any special Domain groups.
Overview
These are the general steps for this installation scenario. If detailed instructions on how to
perform the general steps exists in this guide, you will be directed to them.
A.
Create a shared folder on the database server in which the User Data Files will be installed. Go to
Creating and Configuring a Shared Folder on Page 33 for instructions.
B.
Install the MSP database on the database server. If you are installing via:
•Download from Motorola, go to Installing a Database Server with Download from
Motorola on Page 34.
•Installation CD, go to Installing a Database Server with the Installation CD on Page 34.
Note:
You first must run the installer on the server on which the SQL database will be
resident.
The default Runtime SQL Authentication user is msp_user. If you accept this user, it
will be presented as the default SQL Authentication user. If you change the user
name and password, you will need to make note of the change and use that user as
the Runtime SQL Authentication user.
Important:
This installation scenario includes the installation of Analysis Services and User
Data Files within the instructions for installing the database server.
Analysis Services and the User Data Files must be installed on the same server as
the SQL database in this installation scenario. Any other configuration will not be
covered in this document.
Page 39
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration33
33
C.
Install the MSP Services and MSP Web Site on the appropriate servers. If you are installing via:
•Download from Motorola, go to Installing the MSP Services and MSP Web Server with
Download from Motorola on Page 43.
•Installation CD, go to Installing MSP Services and MSP Web Server with the Installation
CD on Page 43.
A.
Creating and Configuring a Shared Folder
1. Open My Computer on the desktop or through the Start menu.
2. In the root directory (C:\), create a folder with a meaningful name. (For example, FSshare
for File Server share.)
3. Right-click the folder you created and click Properties.
4. On the Sharing tab, select Share this folder.
5. On the Security tab, click Add to display the Select Users, Computers, or Groups
dialog box.
6. In the Enter the object names to select field, type MspServiceGroup.
7. Click Location and click Cancel when prompted to enter network password.
8. Select the local computer and click OK.
9. Click OK again to add the group.
10. On the Security tab of the Properties dialog box, in the Group or user names area,
select MspServiceGroup.
11. Select the Allow Full Control check box, and then click OK.
Page 40
34 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
B.
Installing MSP Database
Installing a Database Server with Download from Motorola
Note:
On a Database Server, MSP does not require that Microsoft IIS 6 or .NET Framework 2.0 be
installed.
To install a Database Server:
1. Download the following installation files from Motorola at
http://support.symbol.com/support/product/softwaredownloads.do:
o MSP32_InstallServer32.msi (32-bit OS)
OR
o MSP32_InstallServer64.msi (64-bit OS)
2. Browse to the location to which you downloaded the Installation Package and doubleclick either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the Welcome dialog box.
3. Go to Completing Installation of a Database Server on Page 35 to continue.
Installing a Database Server with the Installation CD
To install a Database Server:
1. Place the Installation CD in the appropriate drive. The Welcome to the MSP 3.2 CD Launcher dialog box (Figure 21) will display. (This may take a few seconds.).
Figure 21
Page 41
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration35
35
2. On the list of MSP Server Prerequisites, you can ignore Microsoft IIS 6 and .NET
Framework 2.0 because you are installing a Database Server.
Important:
MSP 3.2 still requires a SQL Sever instance, and the installer will discontinue
the install process during a Typical install if a SQL Instance is not detected.
3. Click Install MSP Server to display the Welcome dialog box.
Note:
The installer will display a button to install either the 32 bit or 64 bit version
depending on which version of Windows it detects.
4. Go to Completing Installation of a Database Server to continue.
Completing the Installation of a Database Server
To complete the installation of a Database Server:
1. On the Welcome dialog box (Figure 22), click Next, and a list of prerequisites will display
(Figure 23).
Figure 22
Page 42
36 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Figure 23
2. On the list of MSP Server Prerequisites, you can ignore Microsoft IIS 6 and .NET
Framework 2.0 because you are installing a Database Server. Click Next.
Important:
MSP 3.2 still requires a SQL Sever instance, and the installer will discontinue
the install process during a Typical install if a SQL Instance is not detected.
3. On the License Agreement dialog box (Figure 24), accept the license agreement and
click Next.
Figure 24
4. When the Setup Type dialog box (Figure 25) appears, select Custom and click Next.
Page 43
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration37
37
Figure 25
5. When the Custom Setup dialog box displays, deselect everything except MSP User
Data and MSP Databases (Figure 26).
Note:
If you expand MSP Databases (Figure 27), you can see that the MSP Core
Database and the MSP Analysis Database (Analysis Services) are included.
Figure 26
Page 44
38 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Figure 27
6. Click Change to switch the installation of the MSP User Data to the shared folder you
previously created on the database server. Choose the appropriate folder (Figure 28) and
click OK.
Note:
The shared folder for User Data Files already should have been created.
Figure 28
7. When you return to the Custom Setup dialog box, click Next to display the SQL
Database Installation Connection dialog box (Figure 29).
Important:
If you use SQL authentication, you must provide an SQL login with ‘sysadmin’ rights
to complete the install.
Page 45
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration39
39
Figure 29
8. On the SQL Database Installation Connection dialog box, specify the database server,
the authentication method, and the database name that you will be installing. The
database Name default is MSP, but you can set it to anything you want. Select SQL
Server Authentication and enter the correct Login ID and password.
Note:
If you are installing directly on the database server, you can use Windows
authentication.
9. Click Next to display the MSP Database Runtime Connection dialog box (Figure 30).
Figure 30
Page 46
40 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
selection
10. On the MSP Database Runtime Connection dialog box, select the appropriate runtime
authentication. Select SQL Server authentication and enter the appropriate Login ID and
Password. This will be the user login that MSP will use to connect to the database after
the installation process.
Important:
You must use SQL authentication to complete the installation. After MSP is installed,
the runtime connection string can be changed to use the Domain user that was
selected or created for this purpose.
11. Click Next to display the Analysis Services Database Connection dialog box (Figure
31). Select which Windows authentication credentials to use.
Motorola suggests
using the Browse
button to make this
Figure 31
12. Click Next to display the MSP User Selection (Required) dialog box (Figure 32).
Page 47
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration41
41
selection
Figure 32
13. On the MSP User Selection (Required) dialog box, you MUST select the Select local or
domain user account for MSP Web and services to run as radio button.
14. Click Next to display the Logon Information dialog box (Figure 33). Go to Step 15 to
continue.
Motorola suggests
using the Browse
button to make this
Figure 33
15. On the Logon Information dialog box, enter the correct user account information for the
Domain User you selected or created previously. The user account must be in the
DOMAIN\Username format. Click OK when finished, and click Next to display the Ready to Install Program dialog box (Figure 34).
16. On the Ready to Install Program dialog box, click Install.
Page 48
42 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Figure 34
17. When the Installer Completed dialog box displays (Figure 35), click Finish.
Figure 35
Page 49
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration43
43
C.
Installing MSP Services and MSP Web Server
Installing the MSP Services and MSP Web Server with Download
from Motorola
Note:
On a Web Server, MSP requires that Microsoft IIS 6 or .NET Framework 2.0 be installed, but you
do NOT need a SQL Server Instance.
To install a Web Server:
1. Download the installation files from Motorola at
http://support.symbol.com/support/product/softwaredownloads.do:
o MSP32_InstallServer32.msi (32-bit OS)
OR
o MSP32_InstallServer64.msi (64-bit OS)
2. Browse to the location to which you downloaded the Installation Package and doubleclick either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the Welcome dialog box.
3. Go to Completing the Installation of a Web Server on Page 44 to continue.
Installing MSP Services and MSP Web Server with the
Installation CD
To install a Database Server:
1. Place the Installation CD in the appropriate drive. The Welcome to the MSP 3.2 CD Launcher dialog box (Figure 36) will display. (This may take a few seconds.).
Page 50
44 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Figure 36
Important:
MSP 3.2 does not require a SQL Sever instance for a Web Server, but
Microsoft IIS 6.0 and .NET Framework 2.0 must be installed. The installer will
fail if these requirements are not installed.
2. Click Install MSP Server to display the Welcome dialog box.
Note:
The installer will display a button to install either the 32 bit or 64 bit version
depending on which version of Windows it detects.
3. Go to Completing Installation of an MSP Web Server to continue.
Completing Installation of an MSP Web Server
To complete the Installation of a Web Server:
1. On the Welcome dialog box (Figure 37), click Next, and a list of prerequisites will display
(Figure 38).
Page 51
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration45
45
Figure 37
Figure 38
2. On the list of MSP Server Prerequisites, you must have Microsoft IIS 6 and .NET
Framework 2.0 installed, because you are installing a Web Server. Click Next.
Important:
A Web server does NOT require a SQL Sever instance.
Page 52
46 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
3. On the License Agreement dialog box (Figure 39), accept the license agreement and
click Next.
Figure 39
4. When the Setup Type dialog box (Figure 40) appears, select Custom and click Next.
Figure 40
5. On the Custom Setup dialog box (Figure 41), deselect MSP User Data and MSP
Databases.
Page 53
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration47
47
Note:
These components should have been previously installed on the database
server.
Figure 41
6. Click Next to display the Database Runtime Connection dialog box (Figure 42).
Motorola suggests
using the Browse
button to select the
remote server on
which the MSP
database is installed.
Figure 42
Page 54
48 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Important:
You must select the same database catalog as defined in Figure 29. You also must
use SQL authentication and the user that was selected in Figure 30 to complete the
installation. If you want to use Windows authentication, you can change the runtime
connection string to the desired user as described in Possible Post-Installation Steps
on Page 51.
7. On the Database Runtime Connection dialog box, specify the server where the
database resides, the authentication method you are using, and the name of the
Database. Select SQL Server authentication and enter the Login ID and the Password.
8. Click Next to display the Use a remote instance of Analysis Services Database dialog
box (Figure 43).
9. On the Use a remote instance of Analysis Services Database dialog box, specify the
remote Analysis Services database as required.
10. Click Next to display the MSP User Selection (Required) dialog box (Figure 44).
Figure 43
Page 55
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration49
49
Figure 44
11. On the MSP User Selection (Required) dialog box, you MUST select the Select local
or domain user account for MSP Web and services to run as radio button and click
Next to display the Logon Information dialog box (Figure 45).
12. On the Logon Information dialog box, enter the correct user account information for the
Domain User you selected or created for this purpose. The user account must be in the
DOMAIN\Username format.
Figure 45
13. Click OK when finished, and click Next to display the Select Remote User Data folder
dialog box (Figure 46).
Page 56
50 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Figure 46
14. On the Select Remote User Data folder dialog box, click Change to specify the remote
directory where the User Data resides. The User Data already must be installed in the
shared folder that was created on the database server.
Important:
The Remote User data folder must be specified using the Universal Naming
Convention [\\PCname\sharedfolder] rather than a mapped drive.
To be able to change the User Data File to a remote shared folder, you must be
logged in as a user that has Read permissions to that shared directory.
15. Click Next to display the Ready to Install the Program dialog box (Figure 47).
16. Click Install.
Figure 47
Page 57
Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration51
51
17. When the Installer Completed dialog box displays (Figure 48), click Finish.
Figure 48
Possible Post-Installation Steps
These are some possible post-installation steps that you may or may not need to complete.
Motorola recommends that you read all of them to see if they apply to your enterprise.
•If you intend to use the Domain user instead of the SQL authentication user on the MSP
Services server, you will need to change the SQL connection string in both
WebConnectionStrings.config and CommonConnectionStrings.config. You will need a
Motorola provided tool to do this.
If you want complete use of Windows authentication, you also must change the
connection string used by the Motorola MSP Cube stored in the Analysis databases. To
do this, use SQL Server Management Studio to connect to Analysis Services; go to
Databases > Motorola MSP Cube > Data Sources. Select Properties on the MSP Data
component, and the Properties dialog box is displayed. Change the connection string
details to logon using Windows authentication and click OK. This step is only required if
you want the MSP Cube to connect to the Database Service using only Windows
authentication.
Important:
The Domain user needs to be granted logon permissions to the SQL instance and mapped to the
msp_role of the MSP database.
•If SQL Server has never been installed on the MSP Services server, you may not have
all the necessary SQL assemblies required for correct operation. There is a patch
available; ask your MSP support contact for this patch.
•After installation and before use, verify the functionality of your MSP installation
Page 58
52 Chapter 5 – Installing MSP 3.2 Server with the Most Common Custom Configuration
Page 59
Chapter 6 – Installing the High Availability (HA)
Configuration
Before you Begin
Motorola recommends that you read Chapter 1, 2, and 3 before you attempt the process
described in this Chapter. Step-by-step instructions and screen shots for the installation
processes described here can be found in Chapter 5. References and internal document links are
provided.
About High Availability and Distributed Setups
HA Configuration
In a High Availability (HA) configuration, you create a primary application server and at least one
secondary application server you can switch to manually in case of a primary server failure. Such
secondary application servers are installed and configured exactly like the primary application
server, except, all MSP-related services on the secondary server(s) are inactive.
The HA configuration assumes that the MSP Database Server and the shared folder for User
Data Files are in a failsafe, backed-up environment. The end user is responsible for implementing
the backup and failover procedures that best suit their needs. In most cases, the HA installation is
very similar to the most-common custom installation scenario (Chapter 5) with a few additional
steps.
Note:
There is no limit to the number of secondary application servers that can be installed, however,
only 1 can be allowed to run at any given time.
Distributed System
The Distributed System is another type of custom setup scenario. Motorola does not cover this in
Page 60
54 Chapter 6 – Installing the High Availability (HA) Configuration
any detail, but the various components of MSP Server can be distributed over several servers.
Space prohibits even an attempt to describe every possible or existing system configuration,
therefore, describing exact installation scenarios is impractical. It will have to suffice that such a
method exists and that extensive knowledge of the installation environment and each component
would be required for such an installation.
High Availability Installation Process
1. Install the shared folder for User Data Files and the MSP Database server. Refer to
Creating and Configuring a Shared Folder on Page 33 and Installing MSP Database on
Page 34.
2. Identify your primary server and secondary server(s).
3. Install the SECONDARY server, using the process entitled Installing MSP Services and
MSP Web Server on Page 43.
4. Go to Start > MSP Admin.
5. On the MSP Administration Program dialog box, click Services to display all MSP
services (Figure 49).
6. Click Stop All; when all services report they are stopped, exit the MSP Administration
Program.
7. For all additional secondary servers, repeat Steps 2 through 5 exactly as you did for the
previous secondary server(s).
8. Install the PRIMARY server exactly as you did the secondary server(s), using the process
entitled Installing MSP Services and MSP Web Server on Page 43. Do not stop the
services on the primary server.
9. Once the primary server installation is complete, you should test your MSP Server HA
configuration for basic functionality.
Figure 49
Page 61
Chapter 6 – Installing the High Availability (HA) Configuration55
55
Important:
Make sure that only one Application Server (Primary or Secondary) is operational at any time. If
any of the corresponding services are active on more than one Application Server, the duplication
will interfere with the correct operation of MSP.
If and when the need arises, the secondary server must be brought online manually to resume
the functionality of the MSP server and to use the web-based Console UI to create and send any
new content to Devices.
Important Notes When Switching between Application
PCs in HA Configuration
The one additional manual change that may be needed when bringing the secondary application
PC online is dependent upon whether Data Collection and Analysis is being used. If it is used,
each of the Relay Servers defined in the MSP system must be edited to use the unique GUID of
the Control Collection Service on the secondary PC (Figure 50). Until this value is changed no
data will be collected from those Relay Servers.
There is NO means provided to automate the switchover between the primary and secondary
applications servers. There also is no built-in facility for the secondary application server to detect
that the primary has gone down. Motorola does not directly support any attempts to externally
implement such a mechanism.
Figure 50
Page 62
56 Chapter 6 – Installing the High Availability (HA) Configuration
Page 63
Chapter 7 – Upgrading a Database Server to
SQL Server 2005 Standard or Enterprise Edition
Introduction
The MSP 3.2 Server installer does not provide support to upgrade from using a SQL Server 2005
Express Edition to using either SQL Server 2005 Standard or Enterprise editions. This upgrade
must be performed separately from the MSP 3.2 server install/upgrade.
Q: Why would I need to upgrade from SQL Server Express edition to either the Standard or
Enterprise edition?
A: If you wish to use data collection your installation must use SQL Server 2005 Standard or
Enterprise edition with Analysis Services.
Q: I have an existing MSP server installation (3.1.x or 3.2) that is using SQL Server 2005
Express. How do I keep my data and upgrade to MSP 3.2 and be able to use data collection?
A: You must upgrade your existing SQL Server 2005 Express instance to SQL Server 2005
Standard or Enterprise with Analysis Services.
Q: I have an existing MSP server installation that is using SQL Server 2005 Express, I have
decided that I want to run SQL Server 2005 Standard or Enterprise. How can I keep my data?
A: You can upgrade your existing SQL Server 2005 Express instance to SQL Server 2005
Standard or Enterprise.
General Process
The general process is as follows:
1. Stop MSP.
Page 64
58 Chapter 7 – Upgrading a Database Server to SQL Server 2005 Standard or Enterprise
Edition
2. Upgrade your SQL Server instance from SQL Server 2005 Express to SQL Server 2005
Standard or Enterprise
3. If data collection is desired, add Analysis Services to the upgraded SQL Server instance.
4. Upgrade your MSP install if needed, for example:
o Upgrading from MSP 3.1.x to MSP 3.2
o Installing the MSP Analysis Database
Upgrading the Database Server
Important:
Motorola provides batch files that can perform the following tasks. If you are
upgrading from 3.1.x, you can use
UpgradeSQLEXPRESSInstanceToSQLStd.bat. If you are upgrading from 3.2,
you can use UpgradeMSPInstanceToSQLStd.bat.
If you intend to use the Motorola-provided batch file to upgrade your
database, copy the appropriate file from the MSP Installation CD
(Prerequisite\SQLBatchFiles\ [appropriate file]) to a folder on the local hard
drive (for example; C:\BatchFiles) before completing the following steps.
If you are installing on a VMWare image, you may need to refresh the CD
drive after ejecting the MSP Installation CD in order to see the contents of the
SQL CD when it is placed in the CD drive. One possible check is to perform a
dir command on the CD drive before running the batch file.
5. Use the MSP Admin Tool (Figure 51) to stop all of the MSP Services.
6.
Figure 51
Page 65
Chapter 7 – Upgrading a Database Server to SQL Server 2005 Standard or Enterprise Edition
59
59
7. If the SQL Sever Management Studio Express is installed, Use the Windows
Add/Remove Program to remove it.
Important:
In the following steps, the examples provided assume 1) the batch files referred to
were placed in a folder on your hard drive named C:\BatchFiles, and 2) the drive
letter of your CD drive is D:. Your drive letters and folder names may be different;
please make the appropriate adjustments.
8. Put the SQL Server Standard CD in the appropriate server CD drive.
9. When the CD auto starts, click Exit.
10. Go to Start > All Programs > Accessories > Command Prompt and browse to the
SQL Server Standard CD root directory.
11. If you are upgrading from—
3.1.x, from the command line while in the SQL Server Standard CD root directory,
o
either:
o Invoke the batch file (with a Product Key Argument) as follows: D:\>
You will need to substitute the product key from your SQL Server 2005 Standard or
Enterprise edition for the sample value shown for the PIDKEY option.
Page 66
60 Chapter 7 – Upgrading a Database Server to SQL Server 2005 Standard or Enterprise
Edition
Important:
Motorola provides batch files that can perform the following tasks. If you are
upgrading from 3.1.x, you can use
AddSsasToSQLEXPRESSInstanceOfSQLStd.bat. If you are upgrading from 3.2,
you can use AddSsasToMSPInstanceOfSQLStd.bat.
If you intend to use the Motorola-provided batch file to upgrade your database, copy
the appropriate file from the MSP Installation CD (Prerequisite\SQLBatchFiles\
[appropriate file]) to a folder on the local hard drive (for example; C:\BatchFiles)
before completing the following steps.
If you are installing on a VMWare image, you may need to refresh the CD drive after
ejecting the MSP Installation CD in order to see the contents of the SQL CD when it
is placed in the CD drive. One possible check is to perform a dir command on the
CD drive before running the batch file.
12. Either command prompt (or batch file) installs SQL Server Management Studio and
upgrades the SQL Server Express installation to SQL Server Standard.
Important:
In the following steps, the examples provided assume 1) the batch files referred to
were placed in a folder on your hard drive named C:\BatchFiles, and 2) the drive
letter of your CD drive is D:. Your drive letters and folder names may be different;
please make the appropriate adjustments.
13. After the installation completes if you want Analysis Services installed and you are
upgrading from—
3.1.x
o
, from the command line while in the SQL Server Standard CD root directory,
either:
o Invoke the batch file (with a Product Key Argument) as follows: D:\>