- Microsoft office communicator 2007 r2 download how to#
- Microsoft office communicator 2007 r2 download update#
Microsoft office communicator 2007 r2 download update#
MCS UK Unified Communications Blog – Site Home – TechNet Blogs Microsoft Premier Support UK – Site Home – TechNet Blogs Antigen & ForefrontįoreFront Server Security Support Blog ExchangeĮxchange Team Blog – Site Home – TechNet Blogs The “Earlier server versions” branch should now be empty. Once AD replicates, open the OCS 2007 R2 Management Console and check. On the right side, right-click on the server you wish to remove, and choose Delete. You should see the pools and servers listed. If your Global Settings are in the System container, as was the case for this customer, Select the “Default naming context”.Įxpand the domain, then expand CN=System, then expand CN=Microsoft, then expand CN=RTC Service. If you’re Global Settings are in the System container, open ADSIEdit and select “Configuration” in the Select a well known Naming Context field. These settings can info can either be in the root domain System container, such as if the environment originally held LCS and/or OCS 2007 servers and the settings were never migrated, or the Configuration container, where they would be if they had been migrated, or if OCS 2007 R2 was installed in a greenfield deployment. And for God’s sake, have a backup of AD.ĭepending on where the OCS Global Settings are in Active Directory dictates where to connect to in ADSIEdit. Remember, we’re deep into Active Directory internals here, so tread lightly.
Microsoft office communicator 2007 r2 download how to#
If you’ve got this issue, follow along as I show you how to remove it.
This meant that the only way I could remove this server is via our friend ADSIEdit. And the OCS 2007 R2 management tools can’t remove the server. Unfortunately, there was also no other servers in the environment with the OCS 2007 (non R2) management tools installed. This server would likely cause issues with publishing a Lync 2013 topology since OCS 2007 isn’t supported in a Lync topology. The customer confirmed that it was an OCS 2007 server that had long been removed from service. I verified that the server no longer existed in Active Directory or DNS. When I opened the OCS 2007 R2 management console, I noticed a server listed under “Earlier Server Versions”.
Migrating a customer from OCS 2007 R2 to Lync 2013 recently, I came across an issue that needed some extra work before I could continue.