There is no direct migration
path from LCS 2003 or 2005 to Lync Server 2010. An intermediate step of
migrating to OCS 2007 R2 is required. Although the focus in this book
is on Lync, it would be remiss to disregard this step completely, so
this section reviews the OCS 2007 R2 process at a high level. A key
issue is that the administrator must install the OCS 2007 R2 schema and
server(s) before installing the Lync Server schema.
Although there are a few client-side issues for
coexistence, assume this is a short-term intermediate step on the way
to Lync and that the Lync client is rolled out before going live. On
the server-side, administrators want to make sure they are on at least
LCS 2005 Service Pack 1. Also, if any coexistence is required, an MTLS
certificate is required on the LCS server to communicate with OCS, and
users should not be enabled for enhanced presence until the
Communicator 2007 client or later is deployed.
These preparation steps use LCSCmd, which can be
found on the OCS 2007 R2 installation media at the following path:
Setup\amd64. The first step is to extend the schema. Next, ensure the
user is a member of the Schema Admins group and the commands are either
run on the Schema Master or that Remote RPC is enabled on the Schema
Master server. Then, run the following command:
LCSCmd /Forest /Action:SchemaPrep
After that command finishes, wait until the changes
replicate throughout the Active Directory forest. A different
permutation of the LCSCmd can be used to determine the overall state of
the schema preparation. To see the schema prep state, run the following
command:
LCSCmd /Forest /Action:CheckSchemaPrepState
The next step is to prepare the Active Directory
forest. This command requires being a member of the Enterprise Admins
group. To prepare the forest, run the following command:
LCSCmd /Forest /Action:ForestPrep
Be sure to wait until the effect has replicated to
all domain controllers in the forest. To check the state, run the
following command:
LCSCmd /Forest /Action:CheckForestPrepState
The final preparation step is to prepare the domain.
You need to run this step for each domain where you currently have LCS
or plan to deploy OCS or Lync. To prepare the domain, run the following
command:
LCSCmd /Domain[:<domain FQDN>] /Action:DomainPrep
Wait until the changes have propagated to all domain
controllers in the domain before continuing. The state can be checked
by running the following command:
LCSCmd /Domain[:<domain FQDN>] /Action:CheckDomainPrepState
The final step is to delegate installation
permissions using the least necessary permissions model. This is
important because many unified communications administrators are not
also domain administrators. This process delegates the necessary
permissions to install OCS 2007 R2.
To continue the installation process, perform the following steps:
1. | From the Deployment Wizard, click Delegate Setup and Administration under Step 7.
|
2. | Click the Run button under Delegate Setup Tasks.
|
3. | At the Setup Delegation Wizard welcome dialog box, click Next to continue.
|
4. | At
the Authorize Group dialog box, choose the Trustee domain and enter a
name of an existing Universal Security group. Members of that group
receive permissions to activate the server. Click Next to continue.
Note
The group chosen must be a Universal Security group or installation fails.
|
5. | At
the OU Location dialog box, enter the full distinguished name (DN) of
the organizational unit (OU) where the OCS Server computer accounts are
located. For example, OU=OCS, OU=Servers, CN=Computers, DC=companyabc,
DC=com.
|
6. | After entering the DN of the server’s OU, click Next to continue.
|
7. | Enter
the name of service accounts used for the session initiation protocol
(SIP) and components services. These accounts should be created in
advance in Active Directory.
|
8. | Review the information in the subsequent dialog box, and then click Next to begin setup.
|
9. | Click Finish.
|
Install Office Communications Server 2007 R2
After the preparation steps are complete, it’s time to move on to installing OCS 2007 R2.
Note
Because the context is to provide only a short-term
interim step to Lync Server 2010. That is all that is necessary for most deployments.
First, the administrator must install the
prerequisites. This can be easily scripted for Windows Server 2008 x64
or Windows Server 2008 R2 using the following commands:
Servermanagercmd -i web-server
Servermanagercmd -i web-webserver
Servermanagercmd -i web-common-http
Servermanagercmd -i web-static-content
Servermanagercmd -i web-dir-browsing
Servermanagercmd -i web-http-errors
Servermanagercmd -i web-http-redirect
Servermanagercmd -i web-health
Servermanagercmd -i web-http-logging
Servermanagercmd -i web-request-monitor
Servermanagercmd -i web-security
Servermanagercmd -i web-basic-auth
Servermanagercmd -i web-windows-auth
Servermanagercmd -i web-digest-auth
Servermanagercmd -i web-filtering
Servermanagercmd -i web-performance
Servermanagercmd -i web-stat-compression
Servermanagercmd -i web-mgmt-tools
Servermanagercmd -i web-mgmt-console
Servermanagercmd -i web-mgmt-compat
Servermanagercmd -i web-metabase
Servermanagercmd -i web-wmi
Servermanagercmd -i web-lgcy-scripting
Servermanagercmd -i web-lgcy-mgmt-console
Servermanagercmd -i rsat
Servermanagercmd -i rsat-addc
Servermanagercmd -i rsat-role-tools
Servermanagercmd -i rsat-web-server
Servermanagercmd -i was
Servermanagercmd -i was-process-model
After
all the prerequisites have been satisfied and the Active Directory
schema has been extended, the process for installing an OCS 2007 R2
server can begin. To begin this process, perform the following steps:
1. | From the Deployment Wizard, click Deploy Standard Edition Server.
|
2. | Under Step 2, click Run.
|
3. | Click Deploy Server at the screen that appears and click Next on the first screen. Leave the installation folder at the default, and then click Next to continue.
|
4. | Select the appropriate Application Configuration. The default is all services selected.
|
5. | At the account information field, select Use an Existing Account, and enter the service account information entered in the previous steps for delegation.
|
6. | At the Component Service Account dialog box, choose Use an Existing Account, and then enter the second service account created during the delegation steps and its password. Click Next to continue.
|
7. | In the Web Farm FQDNs dialog box, enter the internal and external FQDNs of the farm. Click Next to continue.
|
8. | Enter the database and log information into the fields in the Database File dialog box. Click Next to continue.
|
9. | Click Next at the Ready to Deploy dialog box.
|
10. | Click Finish.
|
Some basic configuration is required;
however, it is minimal because OCS 2007 R2 is used only to bridge LCS
and Lync. With OCS 2007 R2 now in place, the administrator can move all
the users from the legacy LCS pool to the OCS pool. After the users are
moved to the OCS pool, follow the instructions in the next section to
migrate users and configure the Lync pool.
