OCS 2007 서버 제거 (Uninstalling OCS 2007)

 

원본 출처 : http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=31

 

OCS  설치도 설치거니와 제거도 그리 쉬운일은 아니다. 특히나  AD 에 여러 가지 작업을 하니

제대로 삭제 하지 않으면 재설치 시 곤란을 격기도 한다.

다음 글을 참조하여 삭제시 확인 한다.

그리고 LCScmd 명령 실행지 잘 듣지 않으면 /Force 옵션을 사용할 수도 있다.

 

------------------------------------------------------------------------------------------------------------------------------------

The most common reasons I have seen for uninstalling Office Communications Server 2007 from an environment are typically to remove a pre-release beta version or test deployment, or to start from scratch after a botched deployment.  In either scenario it's often desired to completely remove all aspects of OCS and start fresh.  This approach is often started by simply uninstalling the OCS components from the Front-End server, and doing so will generate this alert:

If 'Yes' is chosen and all other component removed, then the Active Directory forest and domain(s) will still contain remnants of OCS and promptly beginning a new installation in the same forest will probably lead to even more problems then before.  There is a little more to it than just running the Add/Remove Programs wizard.

Supported Uninstall Path

The correct order of steps to completely uninstall OCS 2007 are:

1. Deactivate Servers
2. Uninstall Software Components
3. Unprep Domain and Forest

Deactivating Servers

Each registered server component (e.g. Standard Edition Front-End, Edge, Web Components, Mediation) can be deactivated by using either the Management Console or the LCSCmd.exe command utility.

The simplest way is to use the console and navigate to the menu shown below:

But if the server components have already been uninstalled and the console is therefor also removed, then the command line must be used.  Since the server files have been removed then the LCSCmd.exe command must be run from the setup\i386 directory of the OCS installation files.  The OCS 2007 Administration Guide contains all of the documented switches and examples required to deactivate and unprep components, but here are some examples for removing common components.

Deactivate Standard Edition Server
lcscmd.exe /Server /Role:SE /Action:Deactivate /Force

Deactivate Enterprise Edition Server
lcscmd.exe /Server /Role:EE /Action:Deactivate /Force

Deactivate Consolidated Edge Server
lcscmd.exe /Server /Role:AP /Components:AP,DP,MR /Action:Deactivate /Force

Deactivate Proxy Server
lcscmd.exe /Server /Role:Proxy /Action:Deactivate /Force

Deactivate WorkGroupProxy Server
lcscmd.exe /Server /Role:WorkGroupProxy /Action:Deactivate /Force

Deactivate Web Components Server
lcscmd.exe /Web /Action:Deactivate /Force

Deactivate Mediation Server
lcscmd.exe /MedServer /Action:Deactivate /Force

If the original server has been completely removed from the domain, then issuing the command from another server requires a slightly different format in order to specify the desired AD object:

lcscmd.exe /Server:ocs1.schertz.lab /Action:Deactivate /Role:SE /Refdomain:schertz.lab

Removing Programs

After deactivating all components then uninstall each program on the server(s).

When removing the Standard Edition Server component, uncheck the option to "Keep the user database" to have the local SQL database files deleted by the process.  The folders will still reside on the local disk (by default C:\LC Data and C:\LC Log) but will be empty.

Unprepping the Forest

The final steps are to remove the related configuration information in Active Directory.  Note that the Schema extensions created by the original SchemaPrep step can not be removed, but if the eventual goal is to reinstall OCS then this present no problems.  The Schema extensions are generic and contain no instance-specific configuration information.  By unprepping the Domain and Forest, all configuration information will be removed.

lcscmd.exe /Domain:schertz.lab /Action:DomainUnPrep
lcscmd.exe /Forest:schertz.lab /Action:ForestUnprep

After allowing for any AD replication to fully complete, a new installation of OCS can be started.  I'd recommend using a new, unique servername for the second go-around just to be on the safe side.