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

Domain User for Runtime Access, Domain User for Installation

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

Page 16 highlights

10 -- Mobility Services Platform 3.3.1 Software Installation Guide If you answer Yes, it will continue with the upgrade carrying along most configuration options set via the Administration Program (see Administering MSP 3.3.1). If you answer No, you will have to perform a fresh MSP 3.3.1 installation. You will not be able to continue the current installation and will have to cancel it. To do a fresh installation, you will need to manually uninstall your previous MSP installation, before beginning the MSP 3.3.1 installation again. 5. After the Install Point installer completes and you click Finish (Step 8), it will uninstall your previous version of MSP. Note: If upgrading from MSP 3.3, the Install Runner will not automatically dismiss and you will have to click the close button to dismiss it manually for the install to continue. 6. When the Install Interviewer indicates that the database already exists (step 14), you will want to select the option to keep the data. Domain User for Runtime Access This domain user must be created before starting the MSP installation and since it is used as a service account, it must remain UNCHANGED for the entire length of time that MSP remains installed. This means you must ensure there is no policy in place that will cause the password to change, expire, or be otherwise affected by an external event. This user does not need special domain permissions and does not need any special permissions granted before installing MSP 3.3.1. This domain user only needs to be a member of the "domain users" group. Important: The Domain User for Runtime Access and the Domain User for Installation should never be the same user. Domain User for Installation This domain user must be created before starting the MSP installation and is only required for the installation itself. After completing the installation this user is no longer used and may be demoted or removed altogether. Domain Users for Installation REQUIRE the following permissions: Must be a member of the local Administrators group on the server where MSP components will be installed. It is NOT sufficient for the user to be assigned by domain group association which is a member of the local Administrators group; the user itself must be directly assigned. Must have sysadmin permissions to the SQL Server instance. Must be assigned as a Server Administrator in Analysis Services due to the fact that windows authentication is the only option for connecting to Analysis Services. (This may or may not be required, depending on the features you plan to install. Refer to the SQL Requirements table in Ch. 1 for details.) This domain user does NOT need any special permissions at the domain level (for example it does not need to be a domain administrator).

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
10 -- Mobility Services Platform 3.3.1 Software Installation Guide
If you answer
Yes
, it will continue with the upgrade carrying along most configuration
options set via the Administration Program (see Administering MSP 3.3.1).
If you answer
No
, you will have to perform a fresh MSP 3.3.1 installation.
You will
not be able to continue the current installation and will have to cancel it.
To do a
fresh installation, you will need to manually uninstall your previous MSP installation,
before beginning the MSP 3.3.1 installation again.
5.
After the Install Point installer completes and you click
Finish
(Step 8), it will uninstall
your previous version of MSP.
Note:
If upgrading from MSP 3.3, the Install Runner will not automatically dismiss and you
will have to click the close button to dismiss it manually for the install to continue.
6.
When the Install Interviewer indicates that the database already exists (step 14), you will
want to select the option to keep the data.
Domain User for Runtime Access
This domain user must be created before starting the MSP installation and since it is used as a
service account, it must remain UNCHANGED for the entire length of time that MSP remains
installed. This means you must ensure there is no policy in place that will cause the password to
change, expire, or be otherwise affected by an external event. This user does not need special
domain permissions and does not need any special permissions granted before installing MSP
3.3.1
.
This domain user only needs to be a member of the “domain users” group.
Important:
The Domain User for Runtime Access and the Domain User for Installation should never be the
same user.
Domain User for Installation
This domain user must be created before starting the MSP installation and is only required for the
installation itself. After completing the installation this user is no longer used and may be demoted
or removed altogether.
Domain Users for Installation REQUIRE the following permissions:
Must be a member of the local Administrators group on the server where MSP components
will be installed. It is NOT sufficient for the user to be assigned by domain group association
which is a member of the local Administrators group; the user itself must be directly assigned.
Must have sysadmin permissions to the SQL Server instance.
Must be assigned as a Server Administrator in Analysis Services due to the fact that windows
authentication is the only option for connecting to Analysis Services. (This may or may not be
required, depending on the features you plan to install. Refer to the SQL Requirements table
in Ch. 1 for details.)
This domain user does NOT need any special permissions at the domain level (for example it
does not need to be a domain administrator).