Reconfiguring Factory Shipped CMS

White paper | Reconfiguring Factory Shipped CMS
3 | April 16, 2013
CMS reconfiguration scripts: Overview
This document describes the CMS (central management server) reconfiguration scripts that are
used to reconfigure the factory shipped CMS. It describes the goal, scope, pre-requisites, usage,
and CMS reconfiguration steps.
Goal
The goal of the scripts is to take an initial standard, self-contained (local RDP and SQL server)
server installation and to customize the CMS for its ultimate environment.
The scripts cover the reconfiguration use cases and use case combinations. The use case
combinations should be executed in the following order:
1. Change the hostname/IP addresses
2. Change the local service account (user name and password)
3. Change the local service account password
4. Change the hostname/IP – Change the local service account password
5. Change the hostname/IP – Change the local service account (user name and password)
6. Change the hostname/IP – Change to a domain service account
7. Change the hostname/IP – Move the databases to remote SQL server (this
includes/requires changing to a domain service account)
CMS-Reconfig.ps1
Scope
The CMS-Reconfig.ps1 script is the main wrapper script for executing the CMS reconfiguration use
cases addressed in the other scripts.
Pre-requisites
Ensure that the local or domain username/hostname does not contain the character $.
Automated Steps
1. Ensures that all reconfiguration scripts are present in the directory
2. Backs up all existing configuration files
3. Presents a menu of reconfiguration choices to the user
4. Executes the appropriate reconfiguration script based on the user’s choice
Manual Steps Needed
None
HostName-IP-Change.ps1
Scope
The HostName-IP-Change.ps1 script is used only for the initial reconfiguration, as it depends on
the values in the software-settings.xml file.
Pre-requisites
 New CMS host name must be manually set
 New IPs must be configured
o Primary Management interface IP address
o RDP interface IP address
 If applicable, the CMS must be joined to the domain
 User must be logged in as initial installation account
 Federated mode must be disabled for non-domain installation.
 The local or domain username/hostname must not contain the character $
Note
The scripts are written specific to achieve
the goal and therefore must not be
executed on an in-production CMS. These
scripts must not be executed more than
once on a CMS, where you perform the
reconfi
g
uration.
Note
The CMS-Reconfig.ps1 is the only script
that must be executed b
y
the user.