As you probably know by now, the setup process for Office Communications Server 2007 R2 has changed a little bit. One of the changes is that now you must manually install the Administrative Tools in a separate step (before, they were automatically installed with the product).
Whether you’re installing them on an OCS server or on any other x64 server you use for administration purposes, just kick the Setup Deployment Wizard and select Administrative Tools.
What about the Edge?
By now, you are wondering if the process for the OCS Edge server role is the same. The answer is YES! As you know, the administration of the Edge server is made through the Computer Management snap-in, rather than through the OCS R2 Management Console available in the Administrative Tools folder.
You only get the extended Computer Management snap-in *after* you manually install the OCS Administrative Tools.
Can I install the OCS R2 Admin Tools on a 32-bit machine?
Yes, you can. The supported platforms to deploy the OCS R2 Administrative Tools are: Windows Server 2003 with SP2 (x86, x64), Windows Server 2008 (x86, x64) and Windows Vista Business or Enterprise with SP1 (x86, x64).
Although OCS 2007 R2 is only supported on a 64-bit platform, the 32-bit Administrative Tools are available as part of the 64-bit installation media. You can find them under \SUPPORT\I386. In this folder there are a couple of files that are required as pre-requisites. Install them in the following order:
- sqlncli.msi – SQL Server Native Client
- vcredist_x86.exe – VC++ 2008 Redistributable
- .NET Framework 3.5 SP1 – Download from web or use \Setup\amd64\dotnetfx35.exe
- OCSCore.msi – Office Communications Server 2007 R2 Core Components
- AdminTools.msi – Office Communications Server 2007 R2 Administrative Tools
The 64-bit experience is much better, because the Setup Wizard will install all the pre-requisites automatically. Just for fun, if you didn’t know the correct order for the x86 installation process, this is the pop-up you’d get when running the AdminTools.msi file:
OK, i see there’s a file OCSCore.msi, so let’s double click it. Damn! Another pop-up:
Hummm, the SQL Server Native Client must be this file: sqlncli.msi. Success, it’s installing! So, let’s try again the OCSCore.msi… Another pop-up, what else is new???!!
Running vcredist_x86.exe… Success! I’m pretty sure this was the last pre-requisite, let’s try again the OCSCore.msi. Ah, the .NET Framework 3.5 SP1, of course!!!
Did you have fun? I sure did 🙂