Motorola MSP3-CNTRL-SW-1 - Mobility Services Platform Control Edition, Mobility Services Platform 3.2.1 Installation Manual

Mobility Services Platform 3.2.1 Software
Installation Guide

Mobility Services Platform 3.2.1 Software Installation Guide

72E-100159-08

Revision A

March 2009

© 2009 by Motorola, Inc. All rights reserved.
No part of this publication may be reproduced or used in any form, or by any electrical or

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:/motorola.com/enterprisemobility

Table of Contents

Before You Begin................................................................................................1

Read This First .........................................................................................................................................1

About the Guide........................................................................................................................................ 1

Related Documents.......................................................................................................................... 1

Service Information...........................................................................................................................2

Chapter 1 - Introduction.....................................................................................3

Deciding Your Installation Scenario........................................................................................................... 4

Common Installation Scenarios.........................................................................................................4

Typical Setup.................................................................................................................................... 5

Custom Setup................................................................................................................................... 6

Things to Consider Before Installing .......................................................................................................... 6

MSP 3.2.1 Delivery Methods..................................................................................................................... 7

Downloading from Motorola............................................................................................................... 7

Chapter 2 – MSP Server Requirements.............................................................9

Minimum Software and Hardware Requirements........................................................................................ 9

SQL Server 2005 Requirements.............................................................................................................. 11

Suggested Microsoft SQL Sever 2005 Standard or Enterprise Edition Settings......................................... 12

Required to be installed.................................................................................................................. 12

Required Configuration................................................................................................................... 12

Authentication................................................................................................................................. 12

Chapter 3 – Installing Pre-Requisite Software................................................13

Installing Microsoft IIS............................................................................................................................. 13

Repairing IIS Mapping After Reinstalling IIS..................................................................................... 13

Installing .NET Framework 2.0................................................................................................................. 14

Installing .NET Framework 2.0 from the Downloaded Version........................................................... 14

Installing Microsoft SQL Server 2005 Standard or Enterprise Editions....................................................... 14

Installing Microsoft SQL Server 2005 Express.......................................................................................... 15

iv Mobility Services Platform 3.2.1 Software Installation Guide

Installing SQL Server 2005 Express with a Command line................................................................ 15

Chapter 4 – Uninstalling Earlier Versions of MSP as Preparation for an

Upgrade.............................................................................................................17

Installing MSP Server 3.2.1 with an Existing Version of MSP Server 3.1 and Above.................................. 17

Uninstalling MSP 3.2 or 3.2.1.......................................................................................................... 18

Uninstalling MSP 3.1 or 3.1.1.......................................................................................................... 18

Migrating the User Data Files Shared Folder............................................................................................ 21

Chapter 5 – Installing MSP 3.2.1 with the Typical Setup Type......................23

Installing MSP Server 3.2.1 with the Typical Setup Type Option in a New Installation................................ 23

Chapter 6 – Architecture Overview and Custom Installation Planning........33

Architectural Overview............................................................................................................................ 33

Major Components of a Complete MSP System Installation............................................................. 33

Prerequisite Components Involved..................................................................................... 33

MSP Components Involved............................................................................................... 34

Major Installation Differences between MSP 3.2.0 and MSP 3.2.1 ...................................... 37

Additional Installation Recommendations........................................................................... 37

Questions for Consideration:............................................................................................. 38

MSP 3.2.1Facts: ............................................................................................................... 39

High Availability and Distributed System Configurations..................................................... 39

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom

Configuration ....................................................................................................41

Advanced Users Recommended ............................................................................................................. 41

About this Chapter.................................................................................................................................. 41

Before You Begin............................................................................................................................ 41

Requirements................................................................................................................... 41

Example Custom Installation Scenario..................................................................................................... 42

Custom Setup Overview.................................................................................................... 44

Installing MSP on a Database Server....................................................................................................... 44

Installing MSP on an Application Server................................................................................................... 51

Chapter 8 – Upgrading a Database Server to SQL Server 2005 Standard or

Enterprise Edition.............................................................................................59

Introduction............................................................................................................................................. 59

General Process..................................................................................................................................... 59

Upgrading the Database Server............................................................................................................... 60

Before You Begin

Read This First

Motorola recommends that you read this entire document before you begin installing MSP 3.2.1.
If you skip to Chapters 5 or 6 without reading Chapters 1, 2, 3, and 4, your installation experience
may not go smoothly.

MSP 3.2.1 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.1 Control
Edition with Data Collection but WITHOUT Analysis functionality, you will not 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.1 software, you must go to Chapter 6
after reading Chapters 1, 2, 3, and 4. Chapter 5 discusses the specifics of installing MSP with the
Typical Setup Type. 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.1

About the Guide

The MSP 3.2.1 Software Installation Guide provides general instructions for installing the MSP

3.2.1 software product. Newer versions of this document may be available at

http://support.symbol.com/support/product/softwaredownloads.do.

Related Documents

• MSP 3.2.1 User’s Guide, p/n 72E-100158

• MSP 3.2.1 Release Notes, p/n 72E-100160

• AirBEAM Package Builder Product Reference Guide, p/n 72E-55769

• AirBEAM Package Builder Version 2.x Addendum

2 Before You Begin

Service Information

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.

Chapter 1 - Introduction

Mobility Services Platform version 3.2.1 is available in several Editions that allow you to choose
to purchase and install just the functionality you need. MSP Stage Edition provides support only
for initial deployment of devices. MSP Provision Edition provides all the features of MSP Stage
Edition plus the ability to use Provisioning to keep your devices continuously up to date. MSP
Control Edition provides all the features of MSP Provision Edition plus the ability to perform Data
Collection and optionally Collection Analysis and the ability to perform Actions on selected
devices. Depending on the MSP Edition you choose to install, the functionality you elect to use,
and the complexity of the enterprise you need to manage, the installation of MSP will vary in
complexity.

Installing MSP 3.2.1 Stage or MSP 3.2.1 Provision Edition will typically be the least demanding.
You may choose to use either Microsoft SQL Server Express 2005 or Microsoft SQL Server 2005
Standard or Enterprise edition to host your MSP database. Microsoft SQL Server Express 2005
is license-free, and hence Microsoft offers no support. In addition, Microsoft SQL Server Express
2005 has limitations on maximum database size and generally is not considered an enterprise­class solution. Depending on your situation, you may want to use Microsoft SQL Server 2005
Standard or Enterprise editions even though they require the purchase of licenses from
Microsoft. By paying for licenses, you get an enterprise-class solution and support from
Microsoft.

Installing MSP 3.2.1 Control Edition without Data Collection is comparable in complexity to
installing MSP 3.2.1 Stage Edition or MSP 3.2.1 Provision Edition. You may choose to use either
Microsoft SQL Server Express 2005 or Microsoft SQL Server 2005 Standard or Enterprise
editions to host your MSP database. For the same reasons stated above, it is often advisable to
use Microsoft SQL Server 2005 Standard or Enterprise editions to ensure that you have an
enterprise-class scalable and supported solution.

Installing MSP 3.2.1 Control Edition with Data Collection always requires the use of Microsoft
SQL Server 2005 Standard or Enterprise editions to host your MSP database. In addition, if you
wish to use Collection Analysis, you will need to install the optional Analysis Services feature of
Microsoft SQL Server 2005 Standard or Enterprise editions.

If you need a higher scalability solution and/or or a higher availability solution that provides for
redundancy in the event of a catastrophic failure, you will need to use Microsoft SQL Server 2005
Standard or Enterprise editions to host your MSP database. Further, you will generally need to
host SQL Server 2005 on a separate dedicated server or server cluster. Such installations will be

4 Mobility Services Platform 3.2.1 Software Installation Guide

more complex and generally would be best performed by individuals skilled in the installation and
management of Microsoft SQL Server 2005 servers and/or clusters.

Deciding Your Installation Scenario

MSP installations can vary in complexity from straightforward to very complex.

• The simplest installation can provide full functionality and keep all of the MSP
Components on one server along with SQL Server. This can be achieved via the typical
setup type option.

• Depending upon your installation requirements, IT policies and the number of devices
that will be supported, the MSP components may need to be spread across multiple
servers.

The arrangement of the following MSP components needs to be considered when planning an
MSP installation:

• MSP Core Database {hosted by SQL Server 2005 Database Engine}

• MSP Analysis Database {hosted by SQL Server 2005 Analysis Services (SSAS)}

• MSP Web {hosted by Internet Information Services (IIS)}

• MSP Services {Windows Services}

Common Installation Scenarios

Scenario Setup Type

• New installation on one server with or without Data
Collection and Analysis

• Upgrade from 3.1/3.1.1 on one server with or without
Data Collection and Analysis

• New installation without Analysis 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
Analysis 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
Analysis where the instance of Microsoft SQL Server
2005 is on a second, separate server

Typical

Typical

Custom

Chapter 1 - Introduction 5

Scenario Setup Type

• *Distributing MSP Components across multiple servers
and *Installing MSP in a High Availability Configuration
(HA).

*Specific details for these scenarios are not covered in this
document.

Custom

Typical Setup

The most straightforward installation configurations can be installed using the typical setup type
option (Figure 1) when installing MSP.

Figure 1

These configurations meet the following requirements:

• All MSP Components are installed on the same server. This includes SQL Server 2005
and IIS.

• SQL Authentication is to be used for runtime connections to the SQL database.

• One of three supported editions of SQL Server 2005 is to be used (Express, Standard or

Enterprise).

• Default values are acceptable for the following:

o SQL Catalog (database) name: MSP
o Runtime SQL User Credentials: msp_user (with default password)
o Windows account: MspServiceAccount (with default password)

Note:

The Analysis Database will only be installed if Analysis Services is installed as part of the SQL
Server 2005 Standard or Enterprise instance that will be used. This is required for analysis to be
available if a Control license is applied.

6 Mobility Services Platform 3.2.1 Software Installation Guide

There is one exception to the above list of configuration requirements that is still supported by the
typical setup type option.

• The MSP Core Database (SQL database) can be remotely installed to an instance of
SQL Server 2005 that is installed on a separate server. The runtime connection must be
able to use SQL Authentication and SQL Server Analysis Services are not installed as
part of that instance.This configuration will not install the Analysis Database component
and therefore will not support integrated analysis.

Custom Setup

If the desired installation configuration does not meet the above requirements, the custom setup
type option must be used when installing MSP. This includes the following requirements:

• Windows Authentication is required for runtime connections.

• SQL Server Analysis Services is on a separate server than the MSP Server components.

The custom setup type option allows configuration of the following:

• Configuration of MSP Web Application and MSP Services to run as a domain user to
allow Windows Authentication to SQL Server 2005.

• Specifying a different name to use for the MSP catalog.

• Creating a non-default SQL Authentication user if Windows authentication is not being

used.

• Specify a different SQL Server instance to use for the Analysis Database.

• Installing a redundant MSP Server for high availability configurations.

• Distributing MSP Server components across on multiple servers.

Things to Consider Before Installing

• In MSP 3.2.1 the package files and plug-in definition documents are now stored in the
database. (For more details see Chapter 6 – Architecture Overview and Installation
Planning)

• If multiple servers are being used, then they must be members of the same domain or
trusted domains.

• The file system permissions, usernames and passwords used by MSP, database
connection string properties, and any other configuration property set during install
should NOT be changed after the MSP installation completes.

• SQL Server 2005 Express is not supported for use with MSP if Data Collection is
required. You will need SQL Server 2005 Standard or Enterprise if you ever plan to use
Data Collection or Data Collection WITH integrated Analysis.

• MSP configuration items and permissions set during install can easily be changed by
uninstalling MSP and reinstalling. When you uninstall and choose to not delete user
data, the key information is not lost. You can simply reinstall and alter the configuration
options as needed.

Chapter 1 - Introduction 7

Note:

If MSP is originally installed with Windows authentication for the runtime connection to the
database, you have to manually create a SQL user before switching to SQL authentication.

MSP 3.2.1 Delivery Methods

MSP 3.2.1 is available 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

Note:

No prerequisite software will be included in the Motorola download file.

If your enterprise plans to use the Data Collection feature of MSP 3.2.1 you must have Microsoft
SQL Server 2005 Standard or Enterprise editions installed (See Installing Microsoft SQL Server
2005 Standard or Enterprise Editions on Page 14). 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:

http://www.microsoft.com/downloads/details.aspx?familyid=31711D5D-725C-4AFA-9D65­E4465CDFF1E7&displaylang=en.

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.

8 Mobility Services Platform 3.2.1 Software Installation Guide

Chapter 2 – MSP Server Requirements

Minimum Software and Hardware Requirements

Servers on which you plan to install MSP 3.2.1 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.1 is not supported on
Windows Server systems that are Domain Controllers.

10 Mobility Services Platform 3.2.1 Software Installation Guide

Category Requirements

§ Microsoft Internet Information Services 6 – See Page 13 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 Suggested Microsoft SQL Sever

2005 Standard or Enterprise Edition Settings on Page 12)

These are recommended minimum specifications for the computer on
which you will run these editions of MSP. 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

§ 2 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.1 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 these editions of MSP.

§ 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.1 User’s Guide for more information on factors
that can affect MSP performance.

Chapter 2 – MSP Server Requirements 11

SQL Server 2005 Requirements

The edition of Microsoft SQL Server 2005 you must use is determined by how the installation of
MSP 3.2.1 will be used. The following table delineates which edition you must use:

Table 2 – SQL Server 2005 Version Requirements

If MSP 3.2.1 will be used for a… SQL Server 2005 Version Requirements

Microsoft SQL Server 2005 Express or SQL

• New installation

• On a single server

• Without Data Collection

• New installation

• On a single server

• With Data Collection

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.

• Upgrade from 3.1/3.1.1

• On a single server

• Without Data Collection

• Upgrade from 3.1/3.1.1

• On a single server

• Without Data Collection

• Upgrade from 3.1/3.1.1

• On a single server

• With 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.

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.

If you are going to upgrade the database from
SQL Server2005 Express, see Chapter 6 for
more information.

12 Mobility Services Platform 3.2.1 Software Installation Guide

If MSP 3.2.1 will be used for a… SQL Server 2005 Version Requirements

Microsoft SQL Server 2005 Express or SQL

• Upgrade from 3.1/3.1.1

• The instance of Microsoft SQL server

is on a second, separate server

• Without Data Collection

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.1 will

require Internet Information Services 6 and .NET Framework 2.0.

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.

Suggested Microsoft SQL Sever 2005 Standard or
Enterprise Edition Settings

Required to be installed

• SQL Server Database Engine

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

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:

14 Mobility Services Platform 3.2.1 Software Installation Guide

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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306005&GSSNB=1

Installing .NET Framework 2.0

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 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. This batch file was provided on the MSP 3.2.0 Installation CD. If you don’t
have access to the CD or the ISO from the support site, contact Motorola support.

If you intend to use the Motorola-provided batch file, copy it from the MSP 3.2.0 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.

2. Click Start > All Programs > Accessories > Command Prompt.

3. From the Command Prompt, navigate to the appropriate CD drive.

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

Chapter 3 – Installing Pre-Requisite Software 15

o Type: start /wait setup.exe /qb INSTANCENAME=MSP

ADDLOCAL=SQL_Engine,SQL_Tools90,Analysis_Server,AnalysisDataFiles
SECURITYMODE=SQL SAPWD=11!Noxlet SQLACCOUNT="NT
AUTHORITY\SYSTEM" SQLAUTOSTART=1 SQLBROWSERACCOUNT="NT
AUTHORITY\SYSTEM" SQLBROWSERAUTOSTART=1 AGTACCOUNT="NT
AUTHORITY\SYSTEM" AGTAUTOSTART=0 ASACCOUNT="NT
AUTHORITY\SYSTEM" ASAUTOSTART=1 DISABLENETWORKPROTOCOLS=2
PIDKEY=ABCDE12345FGHIJ67890KLMNO

Notes:

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.1. It can be downloaded from Microsoft and installed with the use of a command
line.

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. This batch file was provided on the MSP 3.2.0
Installation CD. If you don’t have access to the CD or the ISO from the
support site, contact Motorola support.

If you intend to use the Motorola-provided batch file, copy it from the MSP

3.2.0 Installation CD (Prerequisite\SQLBatchFiles\SetupSQLExpress.bat) to a
folder on the local hard drive (for example; C:\BatchFiles) before completing
the following steps.

To install SQL Server 2005 Express:

1. Download SQL Server 2005 Express from the Microsoft Download Center at:

http://www.microsoft.com/downloads/details.aspx?familyid=31711D5D-725C-4AFA­9D65-E4465CDFF1E7&displaylang=en.

2. Click Start > All Programs > Accessories > Command Prompt.

3. From the Command Prompt, navigate to the location of the downloaded installation file.

16 Mobility Services Platform 3.2.1 Software Installation Guide

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.

4. 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

instancename=MSP SQLAUTOSTART=1 SQLBROWSERAUTOSTART=1
SECURITYMODE=SQL SAPWD=11!Noxlet DISABLENETWORKPROTOCOLS=0

5. Press Enter.

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 2) alerts you to the status of the install. When the
final product is installed, the dialog box will close automatically.

Figure 2

Chapter 4 – Uninstalling Earlier Versions of MSP
as Preparation for an Upgrade

WARNING:

If you have an installation of MSP 3.2.0 with the Package Builder 1.0 add-on installed, you MUST

uninstall Package Builder BEFORE you uninstall MSP 3.2.0. If you do not remove this

software in this order, you may not be able to uninstall Package Builder. There is no fix for this.

Installing MSP Server 3.2.1 with an Existing
Version of MSP Server 3.1 and Above

To upgrade an existing install of MSP 3.1, 3.1.1, 3.2, or 3.2.1 use the following process:

Important:

Motorola strongly recommends backing up and/or exporting your existing database before
proceeding!

1. Backup and/or Export your existing data.

Note:

If a backup is saved from your previous version of MSP, it can NOT be applied after
you have upgraded to a newer version of MSP. A backup of a particular version of
MSP is compatible ONLY with that same version of MSP (i.e., you can not restore a

3.2.0 backup to a 3.2.1 system). Motorola recommends the backup so that, if all else
fails, you can revert back to your initial versioned installation and restore your data.
Refer to Understanding and Using MSP 3.2.1 (the user guide) for more information.

To export your MSP Objects, use the XML Export function and save the resulting
XML file to a safe place. Refer to Understanding and Using MSP 3.2.1 for more
information on the XML Export function.

18 Mobility Services Platform 3.2.1 Software Installation Guide

2. Uninstall the existing version of MSP keeping existing data. Failure to select the check
box to keep your data will result in a loss of your database.

3. Migrate the User Data Files shared folder, if applicable.

4. Install the new version of MSP specifying the same database and runtime connection.

Important:

You cannot install MSP Server 3.2.1 over an existing version of MSP Server without removing the
existing MSP Server first. You do have the ability to save the exported objects from your existing
installation for use with your new installation.

Uninstalling MSP 3.2 or 3.2.1

To uninstall MSP Server:

1. Click Start > Control Panel > Add or Remove Programs.

2. If Package Builder is installed, it must be removed first.

a. Select MSP Package Builder and click Change.
b. Wait for it to finish uninstalling and then proceed.

Note:

If uninstalling MSP 3.2.1, MSP Package Builder 3.2.1 will need to be removed
before removing MSP Server.

3. Select MSP Server and click Change.

Important:

Make sure you select the check box that indicates you want to keep all data
associated with MSP.

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.

Chapter 4 – Uninstalling Earlier Versions of MSP as Preparation for an Upgrade 19

2. Select appropriate MSP 3.1.1 version and click Change to display the InstallShield

Wizard (Figure 3).

Figure 3

3. Click Next to display the Program Maintenance dialog box (Figure 4).

Figure 4

4. Select the Remove radio button and click Next to display the Remove Program dialog
box (Figure 5).

20 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 5

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 6), click Finish.

Figure 6

Chapter 4 – Uninstalling Earlier Versions of MSP as Preparation for an Upgrade 21

Note:

When MSP is removed, the folder \MotorolaMSP\Archives is not removed. This is for the user’s
benefit. It is a folder created by MSP that stores a copy of each of the Packages which you can
go back and retrieve if necessary. However, if you want this folder removed completely after an
uninstall, you must remove it manually.

Migrating the User Data Files Shared Folder

Note:

This step does not apply to all setup types. If you are unsure if this applies to your specific setup,
please read Chapter 6 – Architecture Overview and Installation Planning in this document.

After the removal of the previous installation of 3.1 or 3.2.0 is complete, depending on your setup
configuration you may need to migrate your User Data Files from its remote shared folder to the
default install location on your MSP Application Server. As described in Chapter 1, this shared
folder is no longer needed beginning with MSP version 3.2.1.

If your previous installation was configured using the Custom Setup Type option where the User
Data Files were located on a shared folder anywhere other than the default install directory on the
MSP Application Server (i.e., C:\ProgramFiles\MotorolaMSP\), you must manually copy the entire
“\library” folder from the remote share folder and paste it into the location of your \MotorolaMSP
folder on the MSP Application Server.

If you have NOT read Chapter 6 – Architecture Overview and Installation Planning thoroughly,
you should do so now. You are ready to begin installation of MSP 3.2.1.

22 Mobility Services Platform 3.2.1 Software Installation Guide

Chapter 5 – Installing MSP 3.2.1 with the Typical
Setup Type

Installing MSP Server 3.2.1 with the Typical Setup
Type Option in a New Installation

To install MSP 3.2.1:

1. Download the following installation files from Motorola at
http://support.symbol.com/support/product/softwaredownloads.do:

§ MSP321_InstallServer32.msi

OR

§ MSP321_InstallServer64.msi

2. Browse to the location to which you downloaded the Installation Package and double­click either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the
Welcome dialog box.

3. On the Welcome dialog box (Figure 7), click Next, and a list of prerequisites will display
(Figure 8).

24 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 7

4. 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.1 will not require Internet Information

Figure 8

Chapter 5 – Installing MSP 3.2.1 with the Typical Setup Type 25

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.1 will require Internet Information Services 6 and .NET
Framework 2.0.

5. On the License Agreement dialog box (Figure 9), accept the license agreement and
click Next.

Figure 9

6. When the Setup Type dialog box (Figure 10) appears, select Typical and click Next.

Figure 10

Important:

For a “Typical” install, you must have Mixed Mode authentication enabled in
SQL Server.

7. If the installer detects that Internet Information Services (IIS) is:

26 Mobility Services Platform 3.2.1 Software Installation Guide

§ Installed, go to Step 9 to continue.

§ Not installed, you will be prompted that the software is not installed (Figure

11). Click OK and the Installer Completed dialog box will display (Figure

12). Click Finish to exit the installer.

Figure 11

Note:

You can install IIS 6 from the original Windows installation CDs. Go to Page
13 for instructions on installing Microsoft IIS 6.

8. If the installer detects that .NET 2.0 is:

§ Installed, go to Step 9 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:

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

Figure 12

Chapter 5 – Installing MSP 3.2.1 with the Typical Setup Type 27

http://go.microsoft.com/fwlink/?LinkId=55731. Go to Page 14 for instructions

on how to install .Net Framework 2.0.

9. On the Destination Folder dialog box (Figure 13), accept the destination folder or click

Change to change the destination.

Figure 13

10. Click Next.

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 13.

If the installer CAN NOT connect with a SQL Server instance, you will end up at Step 11.

11. Use the information in the following table to complete the fields on the Database
Installation Connection dialog box (Figure 14):

28 Mobility Services Platform 3.2.1 Software Installation Guide

Note:

You can use the Database Installation Connection dialog box to install the database
to a remote SQL Server. If this is the case, you must type the server name and
instance of the remote SQL server instead of using the (local) name. For remote
SQL installations you must use SQL Authentication and the “Browse” button cannot
be used.

Figure 14

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.1 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.1 if you are installing MSP

3.2.1 on the same server on which your SQL database is
installed. Select the appropriate SQL instance.

Connect to install using

• If you are installing the MSP Database on another server,

you must use SQL authentication.

• If you choose Windows authentication, the Login ID and

Password fields will be grayed out.

Chapter 5 – Installing MSP 3.2.1 with the Typical Setup Type 29

In Field… What you need to do and know…

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.

12. Click Next.

13. On the Ready to Install dialog box (Figure 15) click Install.

Figure 15

14. When the Installer Completed dialog box displays (Figure 16), click Finish.

30 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 16

15. In the final step of the installation process, a Command Prompt window will open (Figure

17). You will be prompted as to what is being done to your system; You will be prompted
when the final step is complete (Figure 18).

Figure 17

Chapter 5 – Installing MSP 3.2.1 with the Typical Setup Type 31

16. Click OK.

Figure 18

32 Mobility Services Platform 3.2.1 Software Installation Guide

Chapter 6 – Architecture Overview and Custom
Installation Planning

Architectural Overview

The MSP Server system consists of several components, each serving a different purpose in the
overall operation. It is important to understand each component’s purpose and the installation
requirements for each. There are many different configuration options for any MSP system and
various factors dictate your installation decisions including your enterprise needs, IT policies,
current database and network configuration and others. This section describes the overall
architecture as it pertains to the installation and the how the individual pieces fit together.

Major Components of a Complete MSP System
Installation

Prerequisite Components Involved

The prerequisite components are used to refer to the Microsoft Windows and SQL Server
applications required for any MSP installation. Chapters 2 and 3 cover the requirements and the
installation of the prerequisites respectively, however it’s important to know why they are required
and which parts of MSP use them.

The server machine that is running SQL Server 2005 is referred to as the Database Server in our
scenario descriptions. SQL Server 2005 is used to contain and manage the core database used
by MSP to store all application data. It is also used to store the analysis database used by MSP if
the data analysis feature is used. Other important components required by MSP are IIS and
Microsoft .NET 2.0. The server machine that has IIS and .NET installed is referred to as the
Application Server. In simple setup scenarios these components may all be located on the same
physical machine. The connection details that are used by these individual components to
communicate with each other vary depending on the type and complexity of setup used. The
required connection protocols, user permissions and supported authentication types are
described in greater detail in following sections.

34 Mobility Services Platform 3.2.1 Software Installation Guide

MSP Components Involved

The MSP components refer to the individual parts of MSP that are installed on the corresponding
prerequisite components described above. The breakdown of MSP into its components also
appears in the Installer Feature tree within the actual MSP installation application. Hence, we
have tried to use the same naming conventions. It is important to understand how each of the
required MSP components fit into the overall system. The details and placement may vary
depending on your setup, but each of them must be present for all setup types. Use the diagram
provided below to see how each of the components fit together to form the complete system.

The MSP Web Application is an ASP.NET web application which runs on the IIS6 web service
and requires the .NET Framework 2.0. The MSP application uses the windows file system on the
server that it is installed on to store necessary program files and folders used for temporary file
storage. The MSP Server application also has seven Windows Services that perform various
tasks during normal operation. These are created by the installation program.

Both the MSP Web Application and the MSP Services require a connection to a SQL Server 2005
Database Engine to store the core data. Your MSP installation may or may not also require a
SQL Server 2005 Analysis Service connection depending on the MSP feature set you intend to
use. The following sections provide assistance in deciding the proper setup type based on your
specific enterprise needs. You must carefully consider the install options you have for each
component which in turn requires an understanding of how they all work together. Figure 19 and
Figure 20 illustrate the purpose of each component and the connections that must be made
between them.

Figure 19

Chapter 6 – Architecture Overview and Custom Installation Planning 35

Figure 20

In Figure 20 each of the major components of MSP are represented by a circular region. This is
intended to be a component-wise overview that is independent of the particular server machine
on which each is actually installed. Installation scenarios range from the simplest case where all
components are installed on the same server to more complex scenarios where each is on a
different server. The point is that as long as the necessary components exist and the integrity of
the connections between them remains constant, the system will function correctly as a whole.

The arrowed lines indicate the usage connection between two component modules. In other
words, the first module “connects to” the second module and uses the information obtained from
it to do work. It also can be thought of in terms of the first one depending on the second one for
some information. The Console UI component, for example, connects to the MSP Web
Application service using an http or https protocol to retrieve the information for a particular page
to display (see connection 1 in Figure 20). While the Console UI is dependent upon the MSP Web
Application for this information, at the same time the Web Application is dependent upon the MSP
Core database for its information. From Figure 20, you can start to see how the components
interact to exchange information. You can also start to get an idea of what connection properties
and user permissions might be required for each connection.

The MSP Web Application requires several important connections starting with the MSP Files
(see connection 2 in Figure 20). The MSP Files component consists of both application program
“bin” files and temporary file folders used by the MSP Application They also contain a special
Archives folder which holds a backup of all Packages stored in your MSP database. None of
these folders contain irreplaceable data but the folder structure must remain in tact. In most
scenarios, these MSP Files reside in the \Motorola MSP directory on the same machine as the
MSP Web Application.

The second important connection the MSP Web Application requires is to the MSP Core
Database (see connection 3 in Figure 20). This connection is imperative to the submission and
retrieval of data from the MSP Web Application to the MSP database in SQL. This actually uses
two possibly different connections. One must be used during the installation process to install the
database and the other is used as the runtime connection once MSP has completed installation
and is running. Chapter 6 illustrates the difference between these two connections. The
supported authentication types for this connection are SQL Authentication or Windows
Authentication.

The third connection the MSP Web Application uses is conditional. This connection is ONLY

36 Mobility Services Platform 3.2.1 Software Installation Guide

required if the MSP Analysis database is used (see connection 6 in Figure 20). This database
would be required only if the integrated Analysis feature of MSP is needed. If this feature is not
needed, then SQL Server Analysis Services is not needed and the Analysis database will
obviously not be used. However, if the integrated Analysis feature is required, the Web
Application must connect to the MSP Analysis Database and the only supported connection
authentication type is Windows Authentication. This means that if these two components do not
reside on the same physical machine, a common domain user must be used to authenticate over
this connection. This requires them both to be members of the same domain. Chapter 6
describes an example of this.

The MSP Services also require a few important connections to the components shown in Figure

20. Like the MSP Web Application, each of the seven MSP Services also must have file system
access to the MSP Files (see connection 4 in Figure 20). In most installations this is not a
problem due to the fact that the MSP Services are commonly installed on the same server as
these files.

The second important connection the MSP Services require is to the MSP Core Database (see
connection 5 in Figure 20). This connection is imperative to the submission and retrieval of data
from the MSP Web Application to the MSP database in SQL. This actually uses two possibly
different connections. One must be used during the installation process to install the database
and the other is used as the runtime connection once MSP has completed installation and is
running. Chapter 6 describes the difference between these two connections. The supported
authentication types for this connection are SQL Authentication or Windows Authentication.

The third connection the MSP Services use is a conditional one. This connection is required
ONLY if the MSP Analysis database is used (see connection 7 in Figure 20). This database
would only be required if the integrated Analysis feature of MSP is needed. If this feature is not
needed then SQL Server Analysis Services is not needed and the Analysis database will
obviously not be used. However, if the integrated Analysis feature is required, the Services must
connect to the MSP Analysis Database and the only supported connection authentication type is
Windows Authentication. This means that if these two components do not reside on the same
physical machine, a common domain user must be used to authenticate over this connection.
This requires them both to be members of the same domain. Chapter 6 describes an example of
this.

The MSP Services must also be able to connect via FTP to the FTP Servers that will be used to
deliver and collect information to Relay Servers for devices. This does not require any special
configuration consideration during installation but is worth mentioning in the discussion of the
overall architecture of the system.

Finally, the last possible connection that will be needed involves the connection between the MSP
Analysis Database (including the MSP Cube) and the MSP Core Database (see connection 8 in
Figure 20). Once again, this connection is a conditional one and would only be needed if the
Analysis database is needed for the integrated analysis. This is the same runtime connection
string that the MSP Web Application and MSP Services use to connect to the MSP Core
Database. If SQL authentication is used, no special consideration is required. However if
Windows Authentication is used, the Analysis Database, needs to be configured to impersonate
the domain user for the connection.

As you may conclude from looking at Figure 19 and Figure 20, it is possible to create complex
distributed systems out of the MSP components which involve several interconnected machines.
The benefits of these complex types of setup are described later on. Experienced users may
even be able to derive the knowledge needed to successfully create and use such systems.
However, due to the fact that these are not common scenarios we do not cover the details of
installing such systems in this document.

Chapter 6 – Architecture Overview and Custom Installation Planning 37

Major Installation Differences between MSP 3.2.0 and MSP 3.2.1

The first important difference in MSP 3.2.1 is that the actual package files and the plug-in
definition documents are now stored in the database. Previously, in MSP 3.2.0 these were stored
as files in a special directory which the Web Application and the Services required access to. In
custom distributed scenarios, a specific shared directory had to be created for this shared user
data folder. There are several benefits to making this change. The primary benefit is that you no
longer have to backup the contents of the shared user data folder along with the MSP database
backups. Because the packages and all necessary data are stored entirely in the core database,
it is sufficient to only ensure an effective routine database backup procedure. There are no
needed files stored in any file system directory. The MSP folders are simply used as temporary
storage, the contents of which are repopulated as needed if they are lost. It’s important to note
however, that the user data folders play an important role in the 3.2.1 installation process. The
temporary folders do contain the default packages and plug-in definition documents initially; they
are placed there during the Application Server installation. At the completion of the installation on
the Application Server, scripts are run which will upload all the default packages and definition
documents into the MSP database where they will be stored during the life of the MSP system
unless and until they are deleted. This means, however, that if you are installing MSP 3.2.1 as
part of an upgrade there may be an additional step required after you have uninstalled the
previous version. This would only be required for custom installations where the User Data Files
are stored on a remote shared folder. For detailed steps on this procedure, if required, see
Chapter 6.

The second major difference in MSP 3.2.1 is that it is now possible to use the data collection
feature without installing the integrated data analysis feature provided. This means that if no data
analysis is desired, the SQL Server Analysis Services (SSAS) is not a requirement. If your
specific enterprise setup calls for data collection without data analysis, you now have this option.
The following section which describes installation scenarios provides more details as well as
Chapter 2.

The third important difference in the MSP 3.2.1 installer is that the MSP Package Builder is
installed by default along with the MSP Web Application. In MSP 3.2.0 this was delivered as a
separate add-on installer. In MSP 3.2.1 the Package Builder will again appear as a tab section in
the Console User Interface.

Additional Installation Recommendations

This section describes several recommended steps that may be mandatory or optional depending
on you specific installation needs. Please review them all and consider the implications they may
have on your MSP setup scenario. Failure to observe recommended steps may result in an
unsuccessful installation experience.

The first recommendation is due to the changes made in MSP 3.2.1 with respect to the storage
location of packages and definition documents. If you are upgrading from an earlier version of
MSP, you should be aware that the previously used User Data Files shared folder will need to be
moved to a location where the 3.2.1 installer will recognize and pick up the files if they were
installed on a server separate from the MSP Application Server. The easiest way to ensure this
happens is to follow the recommended procedure at the end of Chapter 5. If the Custom Type
install was not used for your previous installation and the remote shared folder was never created
for this purpose, no action is required because the package files will reside in the default
\Motorola MSP directory as expected by the MSP 3.2.1 installer.

The second recommendation is dependent upon the feature set required from your MSP
installation. Beginning in MSP 3.2.1, you have greater flexibility in component requirements.
Previously, MSP 3.2.0 required the SQL Server 2005 WITH Analysis Services (SSAS) to use
Data Collection and Analysis and there was no middle road. You had to decide between having

38 Mobility Services Platform 3.2.1 Software Installation Guide

the data collection feature including analysis or neither of them. However, a major difference in
MSP 3.2.1 is that you can now choose to utilize the data collection feature without using the
analysis feature. This is a significant change and has important implications on your setup
scenario decisions. It is now the case that you need NOT have SSAS installed on your SQL
Server instance if you only want Data Collection without analysis. However, note that the SQL
Server Express edition is still not supported for Data Collection in MSP 3.2.1.

The third recommendation applies only if you have installed the MSP Package Builder 1.0 add-on
for your previous MSP 3.2.0 installation. You must always make sure to uninstall the Package
Builder application first and then uninstall the MSP application only after you have removed
Package Builder. Beginning with MSP 3.2.1, if you attempt to remove MSP before Package
Builder, it will not complete and will give a message indicating that you must remove Package
Builder first.

Motorola also strongly recommends that you plan your system so that it does not need to be
modified in the future. While there will frequently be unknowns that cannot be avoided you should
make every effort to account for future naming conventions of authentication users, connection
strings, machine names, and the like. The MSP installer assumes that things like the connection
users and computer names will NOT change some time in the future after MSP has been
installed. This includes migrating the database. Once the MSP database has been installed it
cannot be moved to another server or SQL instance. Modifying user permissions or other aspects
of MSP that were configured during time of install will significantly increase the chances of
negatively affecting the correct functionality of your MSP system.

The final recommendation is that you should plan a regular backup procedure for you system
once it is installed. Backup and failsafe preparations depend on your individual enterprise policies
but should be comprehensive. Consider the vulnerability of each component involved and ensure
regular backups or other failsafe precautions are in place.

The following questions and fact statements will help you further understand your setup scenario
needs. These are presented to introduce certain requirement criteria that affect your installation
decisions. If you don’t fully understand the significance of these questions and statements, they
will be discussed in greater detail throughout this introductory chapter and in following chapters.
For further clarification, you should consider these questions as you plan your specific installation
scenario.

Questions for Consideration:

• Do you plan to use the Control Edition features of MSP 3.2.1?

• Will you require the Data Collection feature?

• Will you require the integrated Collection Analysis feature?

• Will your MSP Web Application reside on the same machine as your SQL Server

installation?

• How many different servers will be used in your installation scenario?

• Do you plan to use an existing SQL Server installation?

• Do you currently use a dedicated machine or cluster for the SQL Server, or will you be

installing SQL specifically for MSP to use?

• Does your SQL Server installation currently have SQL Server Analysis Services (SSAS)
installed?

• If you require SSAS, will it be installed on the same machine as your SQL Database
Engine?

Chapter 6 – Architecture Overview and Custom Installation Planning 39

• Will all of the machines involved in your MSP system reside on the same Active Directory
domain?

• Do you intend to use SQL Authentication or Windows Authentication for your installation
connection to the Database Engine?

• Do you intend to use SQL Authentication or Windows Authentication for your runtime
connection to the Database Engine?

• Will the server acting as the MSP Application server be a dedicated machine, or will it be
running other applications as well?

MSP 3.2.1Facts:

• Once MSP has been installed, the database cannot be migrated to another server
without re-installation. Also, the file system permissions, usernames and passwords used
by MSP, database connection string properties, and any other configuration property set
during install should NOT be change after the MSP installation completes.

• SQL Server 2005 Express is not supported for use with MSP if Data Collection is
required. You will need SQL Server 2005 Standard or Enterprise if you ever plan to use
Data Collection or Data Collection WITH integrated Analysis.

• SQL Server 2005 Analysis Services (SSAS) IS required if you ever plan to use integrated
Collection Analysis. Alternatively, if you will never need the integrated Analysis feature
provided by MSP, SSAS is not required. If you choose not to use SSAS and Analysis but
later change your mind and decide you will, you will have to reinstall MSP.

• If you will be using the Analysis Services component and it will be installed on a different
server than the MSP Web App component, you must use Windows Authentication which
requires both machines to be on the same domain.

• If you require both data collection and analysis, and your SSAS instance resides on a
different server than your SQL Database Engine instance, the two servers will need to be
on the same domain. This will also require a special custom setup that is not explicitly
described in this document.

• If your installation scenario involves more than one server, you will need to run the
installer on each separate server. The one exception to this is if you are installing to a
remote SQL Database Engine and you are NOT using Analysis.

The Common Installation Scenarios section that follows discusses different potential installation
scenarios. While there are many possible variations, a few of the most common types are
highlighted. It’s critical that you decide upon the required MSP components needed for the
features you intend to use and that you have a clear understanding of the installation scenario
you plan to use. To help facilitate the setup process that takes place as the installer application is
run, we have split the common setup scenarios into two types, the Typical (or Simple) setup type
and the Custom (or Complex) setup type. It is imperative that the decision on setup type that you
intend to use is made long before the installation program is run.

High Availability and Distributed System Configurations

It is also important to mention that MSP provides the ability to create systems configured in High
Availability (H.A.) type setup and other complex Distributed installations. The setup and
configuration details of these types of systems are not covered by this document but it is worth
noting the reasons and benefits for creating such systems. It will have to suffice that such
methods exist and that extensive knowledge of the installation environment and each component
would be required to attempt such an installation.

40 Mobility Services Platform 3.2.1 Software Installation Guide

In a High Availability configuration, you create a primary application server and at least one
secondary application server that you can switch to manually in case of a primary server failure.
There is no limit to the number of secondary application servers that can be installed, however,
only one can be allowed to run at any given time. Such secondary application server(s) 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
Database Server exists 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 with a few
additional steps. The process of switching from the primary to any secondary server is a manual
one; there is currently no way to have MSP switch over automatically if and when the primary
server fails. There are a couple important manual steps that would have to be taken to
successfully switch over. These are out of the scope of this document.

The Distributed System is another type of custom setup scenario. This is also not covered in any
significant detail, but should be mentioned that the various components of MSP Server can be
distributed over several servers. Distributed systems provide the most benefit when used in very
large-scale enterprise deployments with a well-defined IT policy need. One could, for example,
dedicate one server to simply run the MSP web application, while the additional seven MSP
services could be spread out over two or more additional servers. Another prime example of a
distributed system occurs when the SQL Server running the Database Engine resides on a
different server than the SQL Server instance running the Analysis Services. Also, the SQL
instances may or may not be the same. While these types of installations are not common
installation scenarios, MSP is capable of utilizing such configurations and the powerful flexibility
they provide.

One of the standard benefits of using MSP is that it provides a relatively high degree of scalability
using only the minimum published hardware and software requirements. MSP achieves this from
a single management server by leveraging the multi-tiered architecture where Relay Servers are
used to transfer information to and from devices. Information about the scalability numbers are
published in Chapter 1 of the MSP 3.2.1 Users Guide. However, for very large deployments it is
also possible to further extend your enterprise scalability using a distributed system described
above. It is recommended that you contact Motorola Support in advance if you plan to implement
such systems.

Chapter 7 – Installing MSP 3.2.1 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, 3, and 6 before beginning this installation. This chapter
concentrates on installing MSP 3.2.1 Control Edition with Data Collection and Analysis
functionality where the SQL database is on a server separate from the server on which the rest of
the MSP 3.2.1 components are installed.

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

Important:

If you have not yet read Chapter 6 – Architecture Overview and Installation Planning go back and
do it now.

Requirements

• Read Chapters 1, 2, 3, and 6 and make sure all software and hardware requirements
have been met and that you understand the Architecture Overview and Installation
Planning information.

42 Mobility Services Platform 3.2.1 Software Installation Guide

• Make sure Microsoft SQL Server 2005 Enterprise or Standard edition is installed on the
database server. (Chapter 7 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 Server login with ‘sysadmin’ rights must be present in SQL prior to installation.

This login can use either SQL Authentication or Windows Authentication. This login can
be removed when installation is complete.

• 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. This user will be the MSP runtime
user that is used for authentication.

Example Custom Installation Scenario

Figure 21 depicts an example custom installation scenario. This depiction is the specific scenario
covered by this chapter. The figure shows the two separate machines involved, the pre-requisite
components and the MSP components that correspond with them. The Installer Features column
on the right provides the name of the MSP component associated with each as it appears in the
MSP Installer feature tree itself. The diagram below also uses several example names that will be
referenced by many of the figures throughout this chapter. If at any point during the process of
the install you are unsure as to the meaning of the names used in any screen capture given, you
can refer back to this diagram to understand which SQL or Application Server component is being
referenced.

The PC serving as the Database Server has SQL Server 2005 Standard or Enterprise installed
and for the purposes of this scenario includes both the Database Engine and the Analysis
Services (SSAS). The SQL Server installation contains a single SQL Server instance, named
RemoteInstanceName in which both the Database Service and the SSAS are installed. If the
SSAS component is not required for your installation based on the criteria provided earlier, your
install experience will be slightly different from the one described here. The example name used
to indicate this server is RemoteSQLServer.

The PC serving as the Application Server has IIS and .NET 2.0 installed and for this scenario
assumes that all of the MSP services and User Data files reside on this server as well. Again, if
your setup requirements involve deviations from this, your installation experience will be different
from the steps described here. The example name used to indicate this server is MSPAppPC.

Table 4 – SQL Users and Table 5 – Domain Users list the user accounts referenced throughout
the rest of this chapter. These users are only examples or default names. If your setup requires
different user names, you must make sure they are correctly substituted for these and they have
the correct permissions. If using Windows Authentication for either the installation connection or
the runtime connection, the corresponding SQL user from Table 4 will not be needed. When
running the install on the Application Server you should be logged in as the domain user created
for the install. Both domain users listed in Table 5 must be created prior to beginning the
installation process.

Any installation scenario that involves more than one server machine will require running the
installation on each machine involved. Steps A and B in the Custom Setup Overview demonstrate
this.

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 43

Table 4 – SQL Users

SQL Users Description

sa

SQL Administrator, must have ‘sysadmin’ rights. Only required during
installation.

msp_sql_user

MSP runtime user that will be created during install. This user should
remain unchanged while the MSP App remains installed. This user
gets created and mapped to the msp_role on the MSP Database.

Table 5 – Domain Users

Domain Users Description

Domain user used for installation, no specific domain permissions

domaininstalluser

required but user must be assigned to the local Administrators Group
on the PC on which MSP is being installed. This is a user on the
domain, “YourDomain.”

MSP runtime domain user, no specific permissions required. This user

mspdomainuser

should remain unchanged while the MSP App remains installed. This
user gets assigned as a member of the group named
MspServiceGroup. This is a user on the domain, “YourDomain.”

Figure 21

44 Mobility Services Platform 3.2.1 Software Installation Guide

Custom Setup 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.

• Install the MSP Database on the database server. Go to Installing MSP on a Database
Server on Page 44.

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.

B.

Install the MSP Services, User Data, and MSP Web Site on the appropriate servers. If you are
installing via:

• Download from Motorola, go to Installing MSP on an Application Server on Page 51.

A.

Installing MSP on a Database Server

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 double-

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 45

click either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the
Welcome dialog box.

3. On the Welcome dialog box (Figure 22), click Next, and a list of prerequisites will display
(Figure 23).

Figure 22

Figure 23

4. 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.

5. On the License Agreement dialog box (Figure 24), accept the license agreement and
click Next.

46 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 24

6. When the Setup Type dialog box (Figure 25) appears, select Custom and click Next.

7. When the Custom Setup dialog box displays, deselect everything except 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 25

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 47

Figure 26

Figure 27

8. Click Next to display the SQL Database Installation Connection dialog box (Figure 28).

Important:

If you use SQL authentication, you must provide an SQL login with ‘sysadmin’ rights
to complete the install. If you use Windows authentication, you must be logged in as
a user (domaininstalluser) that has SQL ‘sysadmin’ rights to complete the install.

48 Mobility Services Platform 3.2.1 Software Installation Guide

selection

Motorola suggests
using the Browse
button to make this

Figure 28

9. 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:

The SQL administrative account “sa” is used in Figure 28, however, any SQL login
that has “sysadmin” rights can be used here as well. If you are installing directly on
the database server, you can use Windows authentication.

10. Click Next to display the MSP Database Runtime Connection dialog box (Figure 29).

11. On the MSP Database Runtime Connection dialog box, select the appropriate runtime
authentication. Select SQL Server authentication and enter the appropriate Login ID and

Figure 29

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 49

selection

Password. This will be the user login that MSP will use to connect to the database after
the installation process.

Important:

If the option to use Windows authentication is selected, later in the install process
the installer will prompt to enter the Domain user (mspdomainuser) that was
selected or created for this purpose.

12. Click Next to display the Analysis Services Database Connection dialog box (Figure

30). Select which Windows authentication credentials to use.

Motorola suggests
using the Browse
button to make this

Figure 30

13. Click Next to display the MSP User Selection (Required) dialog box (Figure 31).

Figure 31

14. 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.

50 Mobility Services Platform 3.2.1 Software Installation Guide

selection

15. Click Next to display the Logon Information dialog box (Figure 32). Go to Step 15 to
continue.

Motorola suggests
using the Browse
button to make this

Figure 32

16. 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 33).

17. Click Install.

18. When the Installer Completed dialog box displays (Figure 34), click Finish.

Figure 33

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 51

Figure 34

19. If SQL authentication has been selected for the MSP Database Runtime Connection then
the database server setup is complete. Otherwise, if Windows authentication has been
selected, then the Domain User must be configured in SQL server.

20. Create a login account for the Domain User (mspdomainuser) in the SQL Server
Database engine. Map the Domain User to the msp_role in the MSP database.

21. Under Analysis Services configure the Data Source Impersonation Info for the Motorola
MSP Cube to use the Domain User (mspdomainuser) when connecting to the data
source.

B.

Installing MSP on an Application Server

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:

§ MSP321_InstallServer32.msi (32-bit OS)

OR

§ MSP321_InstallServer64.msi (64-bit OS)

2. Browse to the location to which you downloaded the Installation Package and double­click either MSP32_InstallServer32.msi or MSP32_InstallServer64.msi to display the
Welcome dialog box.

52 Mobility Services Platform 3.2.1 Software Installation Guide

Note:

The installer should be run while logged in as the Domain Install User
(domaininstalluser).

3. On the Welcome dialog box (Figure 35), click Next, and a list of prerequisites will display
(Figure 36).

Figure 35

Figure 36

4. 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.

5. On the License Agreement dialog box (Figure 37), accept the license agreement and
click Next.

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 53

Figure 37

6. When the Setup Type dialog box (Figure 38) appears, select Custom and click Next.

7. On the Custom Setup dialog box (Figure 39), deselect MSP Databases. These
components should have been previously installed on the database server.

Figure 38

54 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 39

8. Click Next to display the Database Runtime Connection dialog box (Figure 40).

Motorola suggests
using the Browse
button to select the
remote server on
which the MSP
database is installed.

Figure 40

Important

You must select the same database catalog as defined in Figure 28. You also must
use specify the same authentication method that was selected in Figure 29 to
complete the installation. If SQL authentication is being used, then the same SQL
user and password must also be specified. If Windows authentication is being used,
then the Domain User specified when installing the MSP database will also need to
be specified later in Step 14.

9. 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. If SQL authentication is being used, enter the Login ID and the Password.

10. Click Next to display the Use a remote instance of Analysis Services Database dialog
box (Figure 41).

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 55

Figure 41

11. On the Use a remote instance of Analysis Services Database dialog box, specify the
remote Analysis Services database as required.

12. Click Next to display the MSP User Selection (Required) dialog box (Figure 42).

Figure 42

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 and click
Next to display the Logon Information dialog box (Figure 43).

14. On the Logon Information dialog box, enter the correct user account information for the
Domain User (mspdomainuser) you selected or created for this purpose. The user
account must be in the DOMAIN\Username format.

56 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 43

15. Click Next to display the Ready to Install the Program dialog box (Figure 44).

Figure 44

16. Click Install.

17. When the Installer Completed dialog box displays (Figure 45), click Finish.

Chapter 7 – Installing MSP 3.2.1 Server with the Most Common Custom Configuration 57

Figure 45

18. In the final step of the installation process, a Command Prompt window will open (Figure

46).You will be prompted as to what is being done to your system; You will be prompted
when the final step is complete (Figure 18).

Figure 46

58 Mobility Services Platform 3.2.1 Software Installation Guide

Figure 47

19. Click OK.

Note

The Domain user (mspdomainuser) needs to be granted logon permissions to the SQL instance
and mapped to the msp_role of the MSP database.

20. After installation and before use, verify the functionality of your MSP installation.

Chapter 8 – Upgrading a Database Server to
SQL Server 2005 Standard or Enterprise Edition

Introduction

The MSP 3.2.1 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.1 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.1 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.

60 Mobility Services Platform 3.2.1 Software Installation Guide

2. Upgrade your SQL Server instance from SQL Server 2005 Express to SQL Server 2005
Standard or Enterprise

3. Upgrade your MSP install if needed, for example:

o Upgrading from MSP 3.x.x to MSP 3.2.1
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. These batch files were provided on the MSP 3.2.0
Installation CD. If you don’t have access to the CD or the ISO from the support site, contact
Motorola support.

If you intend to use the Motorola-provided batch file to upgrade your database, copy the
appropriate file from the MSP 3.2.0 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.

1. Use the MSP Admin Tool (Figure 48) to stop all of the MSP Services.

Figure 48

2. If the SQL Sever Management Studio Express is installed, go to Start > Control Panel >
Add/Remove Program to remove it.

Chapter 8 – Upgrading a Database Server to SQL Server 2005 Standard or Enterprise Edition 61

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.

3. Put the SQL Server Standard CD in the appropriate server CD drive.

4. When the CD auto starts, click Exit.

5. Go to Start > All Programs > Accessories > Command Prompt and browse to the
SQL Server Standard CD root directory.

6. If you are upgrading from—

, from the command line while in the SQL Server Standard CD root directory,

3.1.x

o

either:

§ Invoke the batch file (with a Product Key Argument) as follows: D:\>
C:\BatchFiles\UpgradeSQLEXPRESSInstanceToSQLStd.bat
ABCDE12345FGHIJ67890KLMNO

OR

§ Type: Start /wait setup.exe /qb INSTANCENAME=SQLEXPRESS
ADDLOCAL=SQL_Engine,SQL_Tools90,Connectivity,SDK
UPGRADE=SQL_Engine,Client_Components,Connectivity,SDK
SKUUPGRADE=1 PIDKEY=ABCDE12345FGHIJ67890KLMNO

Note:

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.

o

, from the command line while in the SQL Server Standard CD root directory,

3.2

either:

§ Invoke the batch file (with a Product Key Argument) as follows: D:\>
C:\BatchFiles\UpgradeMSPInstanceToSQLStd.bat
ABCDE12345FGHIJ67890KLMNO

OR

§ Type: Start /wait setup.exe /qb INSTANCENAME=MSP
ADDLOCAL=SQL_Engine,SQL_Tools90,Connectivity,SDK
UPGRADE=SQL_Engine,Client_Components,Connectivity,SDK
SKUUPGRADE=1 PIDKEY=ABCDE12345FGHIJ67890KLMNO

Note:

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.

62 Mobility Services Platform 3.2.1 Software Installation Guide

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. These batch files were
provided on the MSP 3.2.0 Installation CD. If you don’t have access to the CD or
the ISO from the support site, contact Motorola support.

If you intend to use the Motorola-provided batch file to upgrade your database, copy
the appropriate file from the MSP 3.2.0 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.

7. 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.

8. After the installation completes if you want Analysis Services installed and you are
upgrading from—

, from the command line while in the SQL Server Standard CD root directory,

3.1.x

o

either:

§ Invoke the batch file (with a Product Key Argument) as follows: D:\>
C:\BatchFiles\AddSsasToSQLEXPRESSInstanceOfSQLStd.bat
ABCDE12345FGHIJ67890KLMNO

OR

§ Type: Start /wait setup.exe /qb INSTANCENAME=SQLEXPRESS
ADDLOCAL=Analysis_Server,AnalysisDataFiles SKUUPGRADE=1
ASACCOUNT="NT AUTHORITY\SYSTEM" ASAUTOSTART=1
PIDKEY=ABCDE12345FGHIJ67890KLMNO

Chapter 8 – Upgrading a Database Server to SQL Server 2005 Standard or Enterprise Edition 63

Notes:

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.

3.2

o

, from the command line while in the SQL Server Standard CD root directory,

either:

§ Invoke the batch file (with a Product Key Argument) as follows: D:\>
C:\BatchFiles\AddSsasToMSPInstanceOfSQLStd.bat
ABCDE12345FGHIJ67890KLMNO

OR

§ Type: Start /wait setup.exe /qb INSTANCENAME=MSP
ADDLOCAL=Analysis_Server,AnalysisDataFiles SKUUPGRADE=1
ASACCOUNT="NT AUTHORITY\SYSTEM" ASAUTOSTART=1
PIDKEY=ABCDE12345FGHIJ67890KLMNO

Notes:

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.

9. Either command prompt (or batch file) installs the Analysis Services. After the installation
completes:

10. Start SQL Configuration Manager.

11. Bring up the SQL Server Browser properties under SQL Server 2005 Services

12. Under the Log On tab, change the setting for Log on as from Network Service to Local
System. Click OK to commit the change.

13. When you are told that the SQL Browser service must be restarted, click Yes.

64 Mobility Services Platform 3.2.1 Software Installation Guide

Motorola, Inc.
One Motorola Plaza
Holtsville, New York 11742, USA
1-800-927-9626
http:/motorola.com/enterprisemobility
MOTOROLA and the Stylized M Logo and Symbol and the Symbol logo are registered in

the U.S. Patent and Trademark Office. All other product or service names are the
property of their registered owners.

© MOTOROLA, Inc. 2009

72E-100159-08