Migrating from Beta

3 to Office
Communications
Server 2007 Public
Beta
Published: March 2007
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This
document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use
or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names,
e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization,
product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright
laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or
introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or
for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

 Contents
Contents........................................................................................................................................................1
Introduction...................................................................................................................................................1
Recommended Migration Path.................................................................................................................1
How to Use This Guide............................................................................................................................1
Planning for Beta 3 to Public Beta Migration..............................................................................................2
Step 1 Deploying Edge Servers....................................................................................................................3
Step 2 Prepare the Active Directory Forest..................................................................................................3
Step 3 Deploying a Director.........................................................................................................................3
Step 4 Migrating from a Beta 3 Standard Edition Server or Pool................................................................5
Step 4.1. Export User Data from Your Beta 3 Standard Edition Server or Pool......................................6
Step 4.2 Remove User Data from Your Beta 3 Standard Edition Server or Pool.....................................7
Step 4.3 Remove Your Standard Edition Server or Enterprise Pool.........................................................7
Step 4.4 Deploy a Public Beta Release of Standard Edition Server or Pool..........................................12
Step 4.5 Verify the User Replicator Has Completed..............................................................................13
Step 4.6 Reassign Users to Public Beta Release of Standard Edition Server or Enterprise Pool...........14
Step 4.7 Enable IP Video on Global Properties (optional).....................................................................15
Step 4.8 Import User Data Back into the Public Beta Release of Standard Edition Server or Enterprise Pool
................................................................................................................................................................15
Step 5 Deploying a Archiving and CDR Server Public Beta......................................................................16
Step 6 Migrating Your Voice Settings.........................................................................................................16
Introduction
This document guides you through the process of migrating from a Microsoft® Office
Communications Server 2007 (Beta 3) deployment to a Microsoft Office Communications Server
2007 Public Beta deployment. No in-place upgrade exists for beta 3 to the public beta release.
You must uninstall and reinstall all server roles. For your internal Standard Edition Servers and
Enterprise pools, use the procedures explained in this document to ensure your users and their
data are migrated correctly.

Recommended Migration Path

When migrating your servers, you should deploy Office Communications Server 2007 servers
using an “outside-in” approach. This means that you first deploy the edge servers you need to
support your new Office Communications Server 2007 environment and then deploy internal
servers. This migration process requires the following:
• Deploying edge servers, if you need to support external users.
• Deploying a Director, if you want to use a Director to authenticate inbound traffic for edge
servers.
• Migrating to the public beta version of Office Communication 2007 Standard Edition or
Enterprise pool server or Enterprise pool, which includes deploying servers, moving users to
the new servers, and then uninstalling Office Communications Server 2007 (Beta 3).
• Deploying public beta versions of Archiving and CDR Servers, if required.
• Deploying public beta versions of Mediation Server, if you have deployed Enterprise Voice
for beta 3.

How to Use This Guide

This guide provides information specific to upgrading your existing beta 3 deployment, but does
not duplicate the detailed planning and deployment information and procedures that are provided
in other Office Communications Server 2007 documentation. The migration process requires that
you perform some tasks that are described in detail in other documents, as noted in specific
sections of this document. Table 1 summarizes the dependencies of the primary migration tasks
on these other documents.
Table 1. Documentation Dependencies
Section Document Required
Deploying Edge Servers The planning information, including information
about side-by-side migration, provided in the
Microsoft Office Communications Server 2007
Planning Guide.
2 Migrating from Beta 3 to Office Communications Server 2007 Public Beta

The edge server deployment procedures in the

Deploying a Director
Migrating a Server or
Enterprise Pool
Deploying an Archiving
and CDR Server
Microsoft Office Communications Server 2007 Edge
Server Deployment Guide.
The planning information provided in the Microsoft
Office Communications Server 2007 Planning Guide.
The Director deployment procedures in the
Microsoft Office Communications Server 2007 Edge
Server Deployment Guide.
The planning information provided in the Microsoft
Office Communications Server 2007 Planning Guide.
The information about preparing the Active
Directory® Domain Services provided in the
Microsoft Office Communications Server 2007
Active Directory Preparation Guide.
The Standard Edition or Enterprise Edition server
deployment information provided in the Microsoft
Office Communications Server 2007 Standard
Edition Deployment Guide or the Microsoft Office
Communications Server 2007 Enterprise Edition
Deployment Guide.
The beta 3 version of the dbbackup-readme.htm.
The planning information provided in the Office
Communications Server 2007 Planning Guide.
The Archiving and CDR deployment information
provided in the Office Communications Server 2007
Archiving and CDR Deployment Guide.

Deploying a Mediation The information provided in the Office

Server Communications Server 2007 Enterprise Voice
Guide.

Planning for Beta 3 to Public Beta

Migration
In this scenario, first you deploy any new Communications Server 2007 Edge Servers and
Directors if your organization uses them. Next, you deploy a new Office Communications Server
2007 Enterprise pool or Standard Edition Server on separate hardware alongside your existing
Beta 3, and then move users and their data from their current home servers or pools to the new
Office Communications Server home servers or pools.

To deploy in an existing beta 3 topology, use the following steps:

• Deploy your Office Communications Server 2007 Edge Servers before any internal servers.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 3
• Configure an HTTP reverse proxy for use with the Web Conferencing Edge Server.
• Rerun Forest Prep.
• Install and configure a public beta version of Office Communications Server 2007 Director
so that it communicates with your new public beta version of the Edge Server. Although a
Director is not required, it is recommended.
• Deploy your public beta version of Office Communications Server 2007 Standard Edition
Server or Enterprise Pool and migrate your users.
• If archiving is required for your new server or pool, install and configure the public version
of Office Communications Server 2007 Archiving and CDR Server. Your existing beta 3
Archiving and CDR Server will not work with your new public beta version of the server or
pool.

Step 1 Deploying Edge Servers

If you want to upgrade your beta 3 edge topology, you must deploy the new edge topology before
migrating your server or pool. To deploy edge servers, do the following:
• Take the existing beta 3 edge servers offline.
• Deploy each Office Communications Server 2007 (Public Beta) Edge Server required in
your perimeter network, configuring each edge server with the same settings as those for
your beta 3 edge servers. Use the procedures provided in the Microsoft Office
Communications Server 2007 Edge Server Deployment Guide to deploy your edge servers.
• If the edge servers use different IP addresses than the beta 3 edge servers, update the DNS
records required.

Step 2 Prepare the Active Directory

Forest
Before you deploy a Director or any internal servers, you must prepare the Active Directory®
Domain Services for the Office Communications Servers Public Beta by re-running Forest
Preparation. You do not need to run the steps to prepare the schema or prepare domains again
because no changes have been made to the schema or the domain preparation process from beta
3.

Step 3 Deploying a Director

If you deploy Office Communications Server 2007 edge servers in your organization, you should
also deploy an Office Communications Server 2007 Director. A Director does not home users but
does authenticate inbound traffic for edge servers. It resides inside the corporate firewall but
outside pool boundaries. A Director is not required, but it is strongly recommended. For an in-
4 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
depth discussion of the planning considerations for deploying Directors, see the Microsoft Office
Communications Server 2007 Planning Guide.
To migrate a Director, do the following:
1. Deploy an Office Communications Server 2007 (Public Beta), Standard Edition Server or
Enterprise pool as a Director (or you can use an array of Directors) and configure the
Director with the same settings that were configured on your beta 3 Director, configuring the
server as the “next hop” server for the Access Edge Server. Use the Director deployment
procedures in the Microsoft Office Communications Server 2007 Edge Server Deployment
Guide to deploy a Director.
2. Take your Beta 3 Director offline.
3. Wait for User Replicator to complete.

Verifying that User Replicator Has Completed

After you deploy a new Office Communications Server 2007 Director, User Replicator must
complete in order to synchronize the latest user data so that the Director can route
communications to the appropriate server or pool where users are hosted.
Verify that User Replicator has completed the first replication cycle on Office Communications
Server 2007 for all the domains in your environment.
In an Enterprise pool, only one server in the pool is assigned the role of User Replicator. To
determine which server in the pool runs User Replicator, use the Dbanalyze tool as described
later in this section. This tool is available in the Office Communications Server 2007 Resource
Kit, which you can install by using the Office Communications Server 2007 Deployment Wizard.
To verify that User Replicator completed on an Office Communications
Server 2007 Standard Edition Server Director
4. Log on to the server as a member of the Administrators group.
5. Open Event Viewer: Click Start, point to All Programs, point to Administrative Tools, and
then click Event Viewer.
6. In the console tree, click Office Communications Server.
7. In the details pane, look for an event with OCS User Replicator as the source and the event
ID 30024. The event should display the following text:
User Replicator has completed initial synchronization of domain <domain
name> (DN: <distinguished name>) and the database. Future synchronization
for this domain will occur as changes are made in Active Directory.
Check this event for all the domains that have users enabled for Office Communications
Server 2007. If you do not find event ID 30024, check for error events that have Office
Communications Server User Replicator as the source to help identify any failure to
synchronize the users in the domain in which Office Communications Server is deployed.
To verify that User Replicator completed in an Office Communications
Server Enterprise Pool Director
8. Log on to Office Communications Server 2007 Back-End Database as a member of the
System Administrators group for the Office Communications Server Back-End Database.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 5
9. Use the Dbanalyze tool from the Office Communications Server 2007 Resource Kit to
determine which server in the pool is assigned as the User Replicator: Click Start, and then
click Run. In the Open box, type cmd, and then click OK. At the command prompt, type the
following:
Dbanalyze.exe /report:diag /poolfqdn:<pool fqdn for the pool>.
The report that is generated shows which server within the pool is assigned as the User
Replicator. In the following example report, server03 is assigned the user replication task:
TaskName Fqdn
----------------- -------
Endpoint Expiration server01.contoso.com

Subscription Expiration server02.contoso.com

User Replication server03.contoso.com

Nightly Maintenance server04.contoso.com

10. Log on to the server that is assigned as the User Replicator as a member of the
Administrators group.
11. Open Event Viewer. Click Start, point to All Programs, point to Administrative Tools, and
then click Event Viewer.
12. In the console tree, click Office Communications Server.
13. In the details pane, look for an event with OCS User Replicator as the source and the event
ID 30024. The event should display the following text:
User Replicator has completed initial synchronization of domain <domain
name> (DN: <distinguished name>) and the database. Future synchronization
for this domain will occur as changes are made in Active Directory.
14. Verify that this event is logged for all the domains that have users enabled for Office
Communications Server 2007. If you do not find event ID 30024, check for error events that
have OCS User Replicator as the source to help identify any failure to synchronize the users
in the domain in which Office Communications Server is deployed. If User Replicator fails,
an event will be posted to the log.

Step 4 Migrating from a Beta 3

Standard Edition Server or Pool
The following section explains how to migrate from a beta 3 Standard Edition Server or
Enterprise pool.
6 Migrating from Beta 3 to Office Communications Server 2007 Public Beta

Step 4.1. Export User Data from Your Beta 3

Standard Edition Server or Pool
To preserve the latest user data including contacts, groups, and ACEs for each user, use the Office
Communications Server 2007 Dbimpexp.exe tool to save a copy of all the Office
Communications Server 2007 user data. This process preserves contacts, groups, and ACEs,
conferences that organizers have created and any static publications, such as out of the office
notes that appear in Communicator.

Notes
The public beta release of Office Communications Server 2007
Dbimpexp.exe tool is required for this operation. Do not use
the beta 3 release of this tool. The Dbimpexp.exe tool must be
run on the computer from which you are exporting the data.
The Office Communications Server 2007 User Services
database (the RTC database) must be available when you
perform this procedure.

To export user data from Office Communications Server 2007

1. Log on to the appropriate server:
• For Standard Edition server, log on to the server that is running Office Communications
Server 2007 as a member of the Administrators group.
• For an Enterprise pool, log on to the Office Communications Server 2007 Back-End
Database using an account that has read-only access to the database.
2. Insert the Office Communications Server 2007 CD.
3. Open the Command Prompt window: Click Start, and then click Run. In the Open box, type
cmd, and then click OK.
4. At the command prompt, go to the <drive letter>:\Support folder, and then run
DBimpexp.exe using the following command:
Dbimpexp.exe /hrxmlfile:”<XML file path for the exported user data>”
If you want to export data for only a specific user, add the /user:Username parameter to the
command line. Username is fully qualified SIP address.
For example, to move all users:
Dbimpexp.exe /hrxmlfile:“c:\SavedUserData.xml”
For example, to move a single user:
Dbimpexp.exe /hrxmlfile:“c:\SavedUserData.xml” /user:johna@contoso.com
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 7

Note
If the users are currently homed on multiple Office
Communications Server 2007 pools or servers, you must
export the user data that is stored on each Enterprise pool or
Standard Edition server. To do this, repeat steps 1 through 4
on each server or pool on which users are homed.

Step 4.2 Remove User Data from Your Beta 3

Standard Edition Server or Pool
To be rehomed, the user accounts on the beta 3 release of Enterprise pools or Standard Edition
Servers must be removed them from the beta 3 Office Communications Server 2007 User
Services database (the RTC database).
To remove user data from Office Communications Server 2007 RTC
database
1. Log on as a member of the RTCUniversalUserAdmins group to a server that has the Office
Communications Server 2007 administrative snap-in.
2. Open Office Communications Server 2007. Click Start, point to All Programs, point to
Administrative Tools, and then click Office Communications Server 2007.
3. In the console tree, do one of the following:
• For a Standard Edition deployment, expand Communications Standard Edition
Servers.
• Expand Communications Enterprise Edition Pools, and then click the pool
whose properties you want to view or change.
4. Expand the server or pool where the user accounts are currently homed, and then click
Users.
5. In the details pane, select the user accounts that you want to remove, right-click the selection,
and then click Delete users.
6. In the wizard, click Next on the Welcome to the Delete Users page.
7. Read the warning on the next page, and then click Next to delete the user information.
8. On the Delete Operation Status page, verify that the operation succeeded, and then click
Export to export and save the log.
9. In the Save As dialog box, type a file name and path for the log file (or browse to the file),
click Save, and then click Finish.

Step 4.3 Remove Your Standard Edition Server or

Enterprise Pool
Use the following procedures to remove your beta 3 Standard Edition Server or Enterprise pool.
8 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
Removing a Pool
Use the following procedures to remove an Enterprise pool.
Deactivating Servers on the Pool
Use the following procedure to deactivate the each server role in the pool.
To deactivate each server in the pool
1. Log on to a computer as a user with DomainAdmins credentials for the domain where the
pool is deployed. If the domain is a child domain, the user will also need to have
RTCUniversalServerAdmins credentials. The computer can be anywhere in the enterprise
as long as it is joined to a domain and the user has relevant credentials.
2. Open administrative snap-in: Click Start, point to Programs, point to Administrative
Tools, and then click Office Communications Server 2007.
3. In the console, expand Communications Server Enterprise Edition Pools.
4. Expand the beta 3 pool you want to remove.
5. Expand Web Components.
6. Right-click the FQDN of the server, and then click Deactivate and complete the wizard.
7. Expand A/V Conferencing.
8. Right-click the FQDN of the server, and then click Deactivate and complete the wizard.
9. Expand Web Conferencing.
10. Right-click the FQDN of the server, and then click Deactivate and complete the wizard.
11. Expand Front Ends.
12. Right-click the FQDN of the server, and then click Deactivate and complete the wizard.
Uninstalling Files on Enterprise Edition Servers
For Enterprise Edition Servers in a Consolidated Pool Configuration Use
the following procedure to uninstall the beta 3 files on the each server in the pool. For an
Enterprise pool in the consolidated configuration, all server roles will be installed on each
Enterprise Edition Server. Use the following procedure to uninstall the files.
To uninstall the files an Enterprise Edition Server in the Consolidated
Configuration
1. Log on to the Office Communications Server by using local administrator credentials.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Web Components, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
6. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Audio/Video Conferencing Server, and then click Change.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 9
7. On the Confirm Uninstallation page, click Next.
8. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
9. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Web Conferencing Server, and then click Change.
10. On the Confirm Uninstallation page, click Next.
11. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
12. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Front End Server, and then click Change.
13. On the Confirm Uninstallation page, click Next.
14. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
For Enterprise Edition Servers in an Expanded Pool Configuration Use the
following procedure to uninstall beta 3 files on the each server in the pool. For an Enterprise pool
in the expanded configuration, all server roles are installed on dedicated computers.
To uninstall the files an Web Component Server in the Expanded
Configuration
1. Log on to the Office Communications Server by using local administrator credentials.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Web Components, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
To uninstall the files an Audio/Video Conferencing Server in the
Expanded Configuration
1. Log on to the Office Communications Server as a member of the Administrators group.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Audio/Video Conferencing Server, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
To uninstall the files a Web Conferencing Server in the Expanded
Configuration
1. Log on to the Office Communications Server by using local administrator credentials.
10 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
To uninstall the files on a Front-End Server in the Expanded
Configuration
1. Log on to the Office Communications Server as a member of the Administrators group.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Front End Server, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
Removing an Enterprise Pool
This is the last procedure you can run only after deactivating and uninstalling files for all but the
last server within the pool.

Important
Do not remove a pool unless you are certain that the pool is
no longer used by any servers or users. After removing this
pool, you must delete its configuration from the load balancer.

To remove a pool
1. Log on to a computer as a member of the RTCUniversalServerAdmins group. The
computer can be anywhere in the enterprise as long as it is joined to a domain and the user
has relevant credentials.
2. In the console, expand Communications Server Enterprise Edition Pools.
3. Right-click your Beta 3 pool, and then click Remove Pool.
4. On the Welcome page, click Next.
5. On the Pool Removal Options page, clear the Keep user database check box, and then
click Next.
6. On the Ready to Remove Enterprise Pool page, click Next.
7. Click Finish.
Remove the Service Account Used by the Pool
The above procedures (deactivating and uninstalling and removing the pool) do not remove the
service account, because these procedures cannot determine whether the existing account was
created prior to the pool creation. If you allowed activation to create a new service account, and
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 11
you do not plan to recreate the pool, you should remove the service account to avoid the
possibility that it might be accessed by an unauthorized user.
If you used an existing account during activation, then you must decide if this service account
should be retained after the pool is removed. If not, then delete the service account after you have
removes the pool.

Removing a Standard Edition Server

Use the following procedure to remove a Standard Edition Server.
Deactivating Server Roles on the Standard Edition Server
Use the following procedure to deactivate the each server role on the Standard Edition Server.
To deactivate each server role on the Standard Edition Server
1. Log on to a computer as a user with Domain Admins credentials for the domain where the
pool is deployed. If the domain is a child domain, the user will also need to have
RTCUniversalServerAdmins credentials. The computer can be anywhere in the enterprise as
long as it is joined to a domain and the user has relevant credentials.
2. Open the Office Communications Server 2007 administrative snap-in: Click Start, point to
Programs, point to Administrative Tools, and then click Office Communications Server
2007.
3. In the console, expand Communications Standard Edition Servers.
4. Expand the Standard Edition Server that you want to remove.
5. Right-click the FQDN of the server point to Deactivate, and then click Web Conferencing.
6. Complete the wizard.
7. Right-click the FQDN of the server, point to Deactivate, and then click Web Components.
8. Complete the wizard.
9. Right-click the FQDN of the server, point to Deactivate, and then click A/V Conferencing.
10. Complete the wizard.
11. Right-click the FQDN of the server, point to Deactivate, and then click Front End.
12. Select the Force deactivation of Standard Edition Server check box.
13. Complete the wizard.
Uninstalling Files Standard Edition Servers
Use the following procedure to deactivate the each server role in the pool. For an Enterprise pool
in the consolidated configuration, all server roles will be installed on each Enterprise Edition
Server. Use the following procedure to uninstall the files.
To uninstall the files on the Standard Edition Server
1. Log on to the Office Communications Server by using local administrator credentials.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
12 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Web Components, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
6. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Audio/Video Conferencing Server, and then click Change.
7. On the Confirm Uninstallation page, click Next.
8. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
9. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Web Conferencing Server, and then click Change.
10. On the Confirm Uninstallation page, click Next.
11. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
12. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Front End Server, and then click Change.
13. On the Confirm Uninstallation page, click Next.
14. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.
15. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Standard Edition, and then click Change.
16. On the Confirm Uninstallation page, clear the Keep the user database check box, and then
click Next.
17. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.

Step 4.4 Deploy a Public Beta Release of Standard

Edition Server or Pool
After you have removed your beta 3 Standard Edition Server or Enterprise pool, deploy public
beta releases of Enterprise pool or Standard Edition Server.
Refer to the Office Communications Server 2007 Active Directory Guide, the Office
Communications Server 2007 Standard Edition Server Guide and Office Communications Server
2007 Enterprise Edition Server Guide for step-by-step instructions.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 13

Step 4.5 Verify the User Replicator Has Completed

Before you assign users to the new pools or Standard Edition Servers, verify that User Replicator,
has completed its replication cycle on Office Communications Server 2007 for all the domains in
your environment.
In an Enterprise pool, only one server in the pool is assigned the role of User Replicator. To
determine which server in the pool runs User Replicator, use the Dbanalyze tool, as described
later in this section. This tool is available in the Office Communications Server 2007 Resource
Kit, which you can install using the Office Communications Server 2007 Deployment Wizard.
To verify that User Replicator completed on an Office Communications
Server 2007 Standard Edition Server
1. Log on to the server as a member of the Administrators group on the local computer.
2. Open Event Viewer. Click Start, point to All Programs, point to Administrative Tools, and
then click Event Viewer.
3. In the console tree, click Office Communications Server.
4. In the details pane, look for an event with OCS User Replicator as the source and the event
ID 30024. The event should display the following text:
User Replicator has completed initial synchronization of domain <domain
name> (DN: <distinguished name>) and the database. Future synchronization
for this domain will occur as changes are made in Active Directory.
Check this event for all the domains that have users enabled for Office Communications
Server 2007. If you do not find event ID 30024, check for error events that have Office
Communications Server User Replicator as the source to help identify any failure to
synchronize the users in the domain in which Office Communications Server is deployed.
To verify that User Replicator completed in an Office Communications
Server Enterprise Pool
1. Log on to Office Communications Server 2007 Back-End Database as a member of the
System Administrators group for the Office Communications Server Back-End Database.
2. Use the Dbanalyze tool from the Office Communications Server 2007 Resource Kit to
determine which server in the pool is assigned as the User Replicator: Click Start, and then
click Run. In the Open box, type cmd, and then click OK. At the command prompt, type the
following:
Dbanalyze.exe /report:diag /poolfqdn:<pool fqdn for the pool>.
The report that is generated shows which server within the pool is assigned as the User
Replicator. In the following example report, server03 is assigned the user replication task:
TaskName Fqdn
----------------- -------
Endpoint Expiration server01.contoso.com

Subscription Expiration server02.contoso.com

14 Migrating from Beta 3 to Office Communications Server 2007 Public Beta

User Replication server03.contoso.com

Nightly Maintenance server04.contoso.com

3. Log on to the server that is assigned as the User Replicator as a member of the
Administrators group.
4. Open Event Viewer: Click Start, point to All Programs, point to Administrative Tools, and
then click Event Viewer.
5. In the console tree, click Office Communications Server.
6. In the details pane, look for an event with OCS User Replicator as the source and the event
ID 30024. The event should display the following text:
User Replicator has completed initial synchronization of domain <domain
name> (DN: <distinguished name>) and the database. Future synchronization
for this domain will occur as changes are made in Active Directory.
7. Verify that this event is logged for all the domains that have users enabled for Office
Communications Server 2007. If you do not find event ID 30024, check for error events that
have OCS User Replicator as the source to help identify any failure to synchronize the users
in the domain in which Office Communications Server is deployed. If User Replicator fails,
an event will be posted to the log.

Step 4.6 Reassign Users to Public Beta Release of

Standard Edition Server or Enterprise Pool
After you have created your new Enterprise pool or Standard Edition Server, you need to reassign
the users to this server or pool.
To reassign users to the public beta release of Enterprise pool or
Standard Edition Server
1. Log on to a computer that is running Office Communications Server 2007 Standard Edition
or Enterprise Edition or a computer on which the Office Communications Server 2007
Administrative Tools are installed with an account that is a member of the appropriate group:
as a member of the RTCUniversalUserAdmins group.
2. Open Active Directory Users and Computers: Click Start, and then click Run.
3. In the Open box, type dsa.msc, and then click OK.
4. Expand the user container or the container where your users are stored.
5. In the details pane, right-click the users that you want to reassign and then click Enable
Users for Communications Server.
6. On the Welcome page, click Next.
7. In the Select a Server or Pool page, select the public beta Enterprise pool or Standard
Edition Server, and then click Next.
8. On the Specify Sign-In page, select the appropriate option, and then click Next.
9. On the Operation Status page, verify that the operation succeeded.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 15

Note
If the operation fails, click Export to save the XML file and
review it for problems. You can also use the Event Viewer to
troubleshoot the problem.

Step 4.7 Enable IP Video on Global Properties

(optional)
When you upgrade from beta 3 to the public beta release, the Enable IP Video setting is not
retained. If you want to enable IP meetings on your meeting policies, you must manually re-
enable this setting.
To enable IP video on your meeting policies
1. Log on to an Office Communications Server or a computer with the Office Communications
Server administrative snap-in installed with an account that is a member of the
RTCUniversalServerAdmins group.
2. Click Start, point to All Programs, point to Administrative Tools, and then click Office
Communications Server 2007, Administrative Tools.
3. Right-click the forest node, point to Properties, and then click Global Properties.
4. Click the Meetings tab.
5. On the Meetings tab, under Policy Definitions, select the policy that you want to edit, and
then click Edit.
6. Select the Enable IP video check box.
7. Click OK.
8. Repeat this procedure for each policy for which you want to enable IP video.

Step 4.8 Import User Data Back into the Public

Beta Release of Standard Edition Server or
Enterprise Pool
After enabling users on the public beta release, you are ready to import their data.
To import user data
1. Log on to a public beta release of a server or pool as a member of the Administrators group.
2. Insert the Office Communications Server 2007 (Public Beta) CD.
3. Open a Command Prompt window: Click Start, and then click Run. In the Open box, type
cmd, and then click OK.
4. At the command prompt, go to the <drive letter>:\Program Files\ Office Communications
Server 2007\Server\Support folder.
16 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
5. At the command prompt, run DBimpexp.exe by using the following command:
Dbimpexp.exe /import /hrxmlfile:”<file path for the user data XML file that
was previously exported from Office Communications Server 2007>”
For example:
Dbimpexp.exe /import /hrxmlfile:“c:\ SavedUserData2005ForRollBack.xml”

Step 5 Deploying a Archiving and

CDR Server Public Beta
After you have deployed your public release of pools or Standard Edition Servers, you can
deploy a new public beta release of Archiving and CDR Server, if required. For step-by-step
procedures, see the Office Communications Server 2007 Archiving and CDR Server Deployment
Guide.

Step 6 Migrating Your Voice Settings

If you deployed Beta 3 Mediation Server and configured Enterprise Voice, use the following
section to migrate to the public beta.
To fully migrate to the public beta, you must deploy a new Mediation Server and reconfigure any
normalization rules if necessary. To complete the migration of your voice deployment to public
beta, do the following:
1. Deploy each Office Communications Server 2007 (Public Beta) Mediation Server required in
your environment
2. Reconfigure your normalization rules. Office Communications Server 2007 Beta 3 allowed
you create a single set of normalization rules and then apply these rules to multiple location
profiles. When you migrate to public beta and rerun Prepare Forest, these settings will be
retained. However, because Communications Server 2007 Public Beta no longer supports a
single normalization rule shared by multiple location profiles, you must create separate
normalization rules for each location profile. To do this, you can copy any normalization rule
shared by multiple location profiles and give it a new name for each location profile in which
it is used.
3. Deactivate and uninstall your beta 3 Mediation Servers.

Step 6.1 Deploy Mediation Server

Use the steps in the Office Communications Server 2007 Enterprise Voice Guide to deploy your
Mediation Server.

Step 6.2 Reconfigure Your Normalization Rules

Use the steps in the Office Communications Server 2007 Enterprise Voice Guide to deploy your
Mediation Server.
 Migrating from Beta 3 to Office Communications Server 2007
Public Beta 17
As explained earlier, because Communications Server 2007 Public Beta no longer supports a
single normalization rule shared by multiple location profiles, you must create separate
normalization rules for each location profile. To do this, you can copy any normalization rule that
is shared by multiple location profiles and give it a new name for each location profile in which it
is used. Use the following procedure to copy a normalization rule.
To copy a normalization rule
1. Open the Communications Server 2007 administrative snap-in.
2. In the console pane, right-click the Forest node, point to Properties, and click Voice
Properties.
3. On the Location Profiles tab, select the localization profile from which you want to copy the
normalization rule, and then click Edit.
4. Under Normalization Rules, select the normalization rule that you want to copy, and then
click Edit.
5. In the Edit Phone Number Normalization rule dialog, click Copy to copy the phone
pattern and translation pattern of an existing normalization rule.
6. In the Copy Phone Number Normalization Rule dialog, select the normalization rule that
you want to copy, and then click OK. If you want to view a normalization rule before
copying it, select the rule, and then click View.
7. In the Description box, type a brief description (optional) of the normalization rule; for
example “Translates 5-digit extensions” or “Translates 7-digit numbers to Toronto local
number.
8. In the Phone pattern regular expression box, use .NET Framework regular expressions to
describe a phone number pattern; for example, ^9(\d{7})$, which describes a phone number
pattern consisting of the number 9 followed by any seven digits. For information on using
.NET Framework regular expressions, see http://msdn2.microsoft.com/en-
us/library/hs600312.aspx.
9. In the Translation pattern regular expression box, use .NET Framework regular
expressions to describe the E.164 phone number corresponding to the number entered in the
Phone pattern regular expression box.
10. Click Helper if you require assistance in formulating regular expressions.
11. In the Sample dialed number box, type a phone number to test whether the number
translation works properly. If the number matches the phone pattern, the translation will be
shown in the Translated number box.
12. If the translation matches the phone pattern, click OK.

Step 6.3 Deactivate and Uninstall Your Beta 3 Mediation Server

Use the following procedure to deactivate your beta 3 Mediation Server.
To deactivate a beta 3 Mediation Server
1. Log on to a computer as a user as a member of the DomainAdmins group for the domain
where the pool is deployed. If the domain is a child domain, you will also need to have
18 Migrating from Beta 3 to Office Communications Server 2007 Public Beta
RTCUniversalServerAdmins credentials. The computer can be anywhere in the enterprise
as long as it is joined to a domain and your user account has the necessary group
memberships or equivalent user rights.
2. Open the Office Communications Server 2007 administrative snap-in: Click Start, point to
Programs, point to Administrative Tools, and then click Office Communications Server
2007.
3. In the console, expand Mediation Servers.
4. Right-click the FQDN of the Mediation Server, and then click Deactivate Mediation
Server.
5. Complete the wizard.
6. Use the following procedure to uninstall Mediation Server.
To uninstall the files on the Mediation Server
1. Log on to the Office Communications Server by using local administrator credentials.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Microsoft Office Communications Server 2007 (Beta
3), Mediation Server, and then click Change.
4. On the Confirm Uninstallation page, click Next.
5. On the Program Maintenance page, confirm that the action is set to Remove, click Next,
and then complete the wizard.