We are installing Microsoft Office Communications Server (OCS) 2007 R2, Standard Edition on a Windows Server 2008 R2 virtual server in our lab environment. I undertook this installation as a side project while multi-tasking on some other things and it’s one of the most difficult product installations I’ve tackled.
In hopes of saving someone a big headache, I have documented the major issues that caused problems in our environment. First and foremost, go ahead and refer to the excellent installation guide by Desmond Lee. Desmond simplifies a very complex installation process into something you can actually get your head around pretty easily.
Now to the installation errors I came across during installation. The first error message is below when running the Deploy Server step—Step 1—on the Standard Edition of OCS 2007 R2. After completing all the prerequisites mostly on my own by feel and with the guidance of the installation wizard, this error on Step 1 stumped me pretty well since I figured I had properly completed all the preparatory steps.
Error message: The Windows Media Format Runtime is required in order to install the component...
This seems like a valid message and I clicked OK to move on and install the Windows Media Format Runtime…except nothing really happened at that point. After trying to run this step repeatedly a number of times (and remembering the definition of insanity), I searched long and far across the blogosphere for help. Lo and behold, I stumbled across Desmond’s blog post for the OCS 2007 installation guide and it proved to be the key to solving the problem.
The specific error and its related cause is referenced at http://www.leedesmond.com/weblog/?p=451 and ensure that you follow the steps below to work around this, particularly on Window Server 2008 R2, which seems to have more issues than Server 2008 since OCS 2007 was originally targeted to the Server 2008 platform and not R2.
Dealing with the Windows Media Format Runtime Error
The following guidance comes from Desmond’s blog post and helps explain part of the issue.Since we are putting R2 on Windows Server 2008 x64 and if any of the IIS role services are left out, misleading error messages will send you going around in circles until you figure out what the confusing references actually mean, such as this one here: ” Not available: IIS 6 Management Compatibility and IIS Windows Authentication role services must be installed before you Deploy Server. ” Also, you may be prompted to install the following component before Step 1 can actually begin:
——————————– Windows Media Format Runtime required ——————————– The Windows Media Format Runtime is required in order to install this component. Installing the Windows Media Format Runtime may require a system restart to complete the installation. Click OK to continue with the installation. ——————————– OK Cancel ——————————–
Make sure you install the correct IIS role services including all security and IIS 6 Management Compatibility services as shown below.
I had addressed the IIS 6 Management Compatibility error on my lab server and installed the proper role services for IIS. You will also want to check the installation account’s group memberships as mentioned in the blog article and ensure that the installation account already has membership in both the RTCUniversalServerAdmins and Domain Admins groups.
After verifying IIS and my installation account group memberships, I moved on with the Deploy Server step but received the Windows Media Format Runtime error and got stuck trying to figure out how to download and install the runtime to fix the error. The OCS 2007 R2 installer claimed it would install the Windows Media Format Runtime if I clicked OK but this did not work on Windows Server 2008 R2 so I had to do it manually.
Microsoft’s TechNet site didn’t have what I needed to manually install the Windows Media Format Runtime and other downloads for the Windows Media Format Runtime were suspect so it was time to move on to another solution. And come to find out it’s a pretty easy fix to install the runtime from the command line.
Run the following command from the Windows command line to install the Windows Media Format Runtime. It will require a reboot of the server after the installation completes.
pkgmgr.exe /ip /m:"C:WindowsservicingPackagesMicrosoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum"
Running the command shows the following dialog box.
Once the Windows Media Format Runtime was installed (after a server reboot, of course), I was ready to go on with the Deploy Server step for the OCS 2007 R2 installation. From this point, the installation went better but I did hit another hurdle: activation.
Dealing with the Activation Error
After running the Deploy Server step to near completion, I had an error on the activation portion of the step.
Failure[0xC3EC78D8] Failed to read the Office Communications Server version information. This can happen if the computer clock is not set to correct date and time.
This issue relates to Microsoft KB974571 and the fix is documented below. Once you implement the fix you should have full server deployment and be ready to move on to certificate installation, DNS, etc.
Steps to Resolve Activation Issues
Check out both articles for full information and you might have to restart the server again (for the 20th time it seems!) to complete activation.
Remove the KB974571 and run OCS setup again. After that run the ocsasnfix.exe download here:
http://go.microsoft.com/fwlink/?LinkId=168248. Then re-install the KB974571.
A fix that resolves this issue is available for download from the Microsoft Download Center. To obtain the fix, visit the following Microsoft Web page:
The fix (OCSASNFix.exe) is governed by the Microsoft Software License Agreement for Office Communications Server 2007 R2, Office Communications Server 2007, Live Communications Server 2005, Office Communicator 2007 R2, Office Communicator 2007, and Office Communicator 2005.From http://support.microsoft.com/kb/974571/