Although not very common except perhaps in test or lab environments, there are legitimate reasons to uninstall a fully functional installation of OCS 2007 R2 from a production environment and start again from scratch.
Essentially, you have to carry out two steps to accomplish this, namely deactivate and uninstall OCS server roles. Prior to that, all OCS services should be first stopped to prevent connections (link). Make sure that you use the default domain Administrator account or elevated account privilege (”Run as Administrator”) to perform all the tasks if R2 is installed on Windows Server 2008. This account must be a member of the local Administrators group as well as RTCUniversalServerAdmins. Apparently other user accounts lack certain rights to uninstall a number of OCS components even if they are members of the Domain Admins security group. Expect errors similar to the following if the said account or elevated account is not used:
Office Communications Server 2007 R2, Web Components Server
Error 0×80070005 (Access is denied) binding to IIS metabase path IIS://localhost/W3SVC/1. Make sure the website exits.
Whether R2 servers are setup in a consolidated Enterprise topology or installed using the Standard Edition (standalone pool), I recommend that you perform deactivation of the registered OCS components in the following sequence. You can use the OCS 2007 R2 MMC snap-in by drilling down to the Enterprise pool (or Standard Edition Servers), select then right mouse click on the server and pick the Deactivate option:
- Application Host*
- Application Sharing Server
- A/V Conferencing Server
- Web Conferencing Server
- Web Components Server
- Front End Server
At the end of each deactivation, it is a good idea to view the log and confirm that success is shown under Execution Result column.
Next, uninstall the registered OCS components using Add/Remove Programs or Programs and Features from the Control Panel following the sequence listed:
- Application Host
- Application Sharing Server
- Audio/Video Conferencing Server
- Conferencing Announcement Service
- Conferencing Attendant
- Outside Voice Control
- Response Group Service
- Web Conferencing Server
- Enterprise Edition Server (Front-End)
- Managed API 2.0 Core Redist 64-bit
- Managed API 2.0 Speech Redist x64
- Managed API 2.0 Windows Workflow Activities Redist
- Server Speech Language Pack (en-us)
- Web Components Server
- Core Components
Otherwise, expect to find error messages such as:
Office Communications Server 2007 R2, Core Components
Other applications may still be using Microsoft Office Communications Server 2007 R2, Core Components. Uninstalling may cause these applications to no longer work.
Finish off the uninstall process with a reboot of the server when prompted.
It is not necessary to reverse the changes made by the Prep Forest and Prep Domain processes if you intend to install OCS 2007 R2 in the environment again. Otherwise, you must use the LCSCmd.exe command to complete the process as follows:
x:\setup\amd64\lcscmd.exe /domain:swissitpro.ch /action:domainunprep
x:\setup\amd64\lcscmd.exe /forest:swissitpro.ch /action:forestunprep
Verify that you see “Action completed successfully” at the end of each unprep step and review the log file for details.
Since changes to the Active Directory Schema are permanent, there is no further action to take (to “unprep”AD schema). Ensure that AD replication is given sufficient time to complete before you attempt to rebuild or install R2 into the same environment.
* do not check the Force deactivation of Application Host unless fail
Reference:
- Office Communications Server Deployment Guide
- Microsoft Office Communications Server 2007 R2 Trial Download
- Removing Servers and Server Roles, Removing Enterprise Pools, and Decommissioning Servers and Pools
- Decommissioning Standard Edition Servers and Enterprise Pools
Technorati tags: LCS/OCS, OCS 2007 R2