Академический Документы
Профессиональный Документы
Культура Документы
Communications
Server 2007
Evaluation to the Full
Released Version
Published: August 2007
Error! No text of specified style in document. 2
Information in this document, including URL and other Internet Web site references, is subject to change without notice. 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.
Microsoft, Active Directory, MSDN, MS-DOS, Outlook, Windows, Windows NT, and Windows Server are trademarks of the Microsoft
group of companies.
3. During any particular upgrade, if you cancel the evaluation to full released version of the
file installation portion of the upgrade, your server will not perform as designed.
Note
To upgrade from the Evaluation to the full released version
across editions, such as an evaluation version Standard
Edition Server to a fully released version of Enterprise pool,
you must run a side-by-side migration with the move users
procedure. Deploy the full released version of the pool or
server and then run a move users procedure before removing
the evaluation version.
The following sections in this document explain the supported methodologies for upgrading each
of the previously mentioned types of server roles:
• Overview of the Upgrade Process
• Upgrading for Enterprise pools and Standard Edition Servers
• Upgrading for Director
• Upgrading for Edge Servers and Proxies
Otherwise, you will also have to specify the /dbname and the /sqlserver parameters. For
more information about these parameters, see the Dbbackup Readme file.
Upgrading for Edge Servers and Proxies 5
Note
Dbbackup.exe can be found in the Program Files\Microsoft LC
2005\Server\Support directory on a Standard Edition Server.
On an Enterprise pool Back-End Database, you will need to
copy the Dbbackup.exe file from one of your Enterprise Edition
Servers in the same directory mentioned earlier in this note,
or from the CD or installation share in the Support folder.
For example:
Note
Specify /qn parameter to run a silent upgrade of installation
files during which no wizard pages or dialog boxes appear. If
you run a silient install, specify the logging option with /l*vx
<file path> parameter. You can also use the, /qn+ parameter
to run a silent installation that displays a dialog box at the end
of the procedure indicating whether the procedure is
successful.
Use the following procedure to upgrade the evaluation version of a Standard Edition Server using
the command line.
To upgrade the installation files for each Standard Edition Server
1. Log on to the evaluation version of Standard Edition Server using local administrator
credentials.
2. Upgrade the installation files for the Standard Edition Server. Use Server.msi, which can be
run from the installation folder or the CD (Setup\i386\setup directory)
MsiExec.exe /i Server.msi EVALTOFULL=1 [/l*v
<Drive:\Directory\FileName.log>] [/q[n|b|r][+]]
For example:
MsiExec.exe /i Server.msi EVALTOFULL=1 /l*v C:\Upgrade.log
Note
Specifying the /qn parameter will make the upgrade of
installation files procedure silent and no wizard pages or
dialog boxes will appear (step 3 is skipped). For the silent /qn
case, the Windows Installer recommendation is always to
specify the logging option with /l*vx <file path> parameter.
See the syntax in step 2. Also, the /qn+ parameter can be
used for silent installs but a dialog box appears at the end of
the procedure indicating whether the procedure succeeds.
3. Look for Office Communications User Replicator as the source and event ID 30024. The
event displays 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 with users enabled for Office Communications Server.
To verify that user replicator is complete in a full released version of
Office Communications Server Enterprise pool
1. Only one server in the pool is assigned the user replication task. Determine which server in
the pool runs the user replicator:
a. Run the Dbanalyze tool. (This tool is available in the Office Communications Server
2007 Resource Kit Tools.)
b. In the Office Communications Server 2007 Back-End Database, from a command
prompt, type dbanalyze.exe /report:diag /poolfqdn:<pool fqdn for the pool>. The
report shows which server within the pool is assigned the user replicator. In the
following example, server03 is assigned the user replication task.
Task Name Fqdn
----------------- -------
Endpoint Expiration server01.contoso.com
2. On the server that is assigned the user replicator, open the Event Viewer. Click Start, point
to All Programs, point to Administration Tools, and then click Event Viewer.
3. Click Application Logs, and then click the Source column to sort by source.
4. Look for OCS User Replicator as the source and event ID 30024. The event displays 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 with users enabled for Office Communications Server.
8 Upgrading Office Communications Server 2007 Evaluation to the Full Released Version
For example:
MsiExec.exe /i Server.msi EVALTOFULL=1 /l*v C:\Upgrade.log
Note
Specifying the /qn parameter will make the upgrade of
installation files procedure silent and no wizard pages or
dialog boxes will be displayed (step 3 is skipped). For the
silent /qn case, the Windows Installer recommendation is
always to specify the logging option with /l*vx <file path>
parameter. The /qn+ parameter can be used for silent installs
but a dialog box appears at the end of the procedure
indicating whether the procedure succeeded.
For example:
MsiExec.exe /i Server.msi EVALTOFULL=1 /l*v C:\Upgrade.log
Note
Specifying the /qn parameter will make the upgrade of
installation files procedure silent and no wizard pages or
dialog boxes will be displayed (step 3 is skipped). For the
silent /qn case, the Windows Installer recommendation is
always to specify the logging option with the /l*vx <file
path> parameter. See the syntax in step 1.
/qn+ parameter can be used for silent installs but a dialog box
appears at the end of the procedure indicating whether the
procedure was successful.