All logs were showing that it had worked, the Update service logs showing that the phone had found the right sw, and IIS logs showing me a 200 OK sent to all phones…

Troubleshooting finally led me to try downloading the CPE.nbt file manually from

http://frontendfqdn/DeviceUpdateFiles_Int/OCInterim/ENU/cpe.nbt

which just gave me a blank page.

I tried comparing the IIS configuration to one I knew was working, and saw that I had a lot less IIS roles installed on the one that was not working.

When I installed this Front End server, i used the commands in this post to install the prereqs. Turns out that if you are going to use CPE, you will probably also need the “Static Content” role service in IIS to configure the correct MIME types on the fileextensions the update serrvice uses.

There exists default MIME types for both the .xml and the .cat extensions that is used by the updater. There is however no default for the .nbt extension.

If this role service is not installed, the updater does not work. You will have to add this feature, and then manually add the correct MIME types to the DeviceUpdateFiles_Int/ and DeviceUpdateFiles_Ext/ folders, which should be:

<mimeMap fileExtension=”.nbt” mimeType=”binary/octet-stream” />

<mimeMap fileExtension=”.cat” mimeType=”binary/octet-stream” />

(I have no idea as to why the bottom one is smaller than the other, but I cant get them equal size for some reason :S)

Hey presto! The phones update themselves like magic has happened!

TI

—

Commands to install the necessary prerequisites for OCS 2007 R2 on Windows Server 2008

Front End on Windows Server 2008
Servermanagercmd.exe -install web-windows-auth web-mgmt-compat web-mgmt-console web-http-logging msmq-server msmq-directory powershell was-process-model was-config-apis rsat-addc

Installs the following components:

• [Web-Windows-Auth] – Windows Authentication
• [Web-Mgmt-Compat] – IIS 6 Management Compatibility
• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration
• [RSAT-ADDC] – Active Directory Domain Controller Tools
• [WAS-Process-Model] – Process Model
• [WAS-Config-APIs] – Configuration APIs
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Http-Logging] – HTTP Logging
• [PowerShell] – Windows PowerShell

The last 3 in the list are not required, but they are highly recommended. IIS 7.0 Management Console is IMHO much easier to use than the IIS 6.0 version. The logging tools often come in handy when troubleshooting OCS IIS issues and PowerShell makes working with OCS WMI values a piece of cake.

Monitoring Server on Windows Server 2008
Servermanagercmd.exe -install msmq-server msmq-directory

Installs the following components:

• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration

CWA Server on Windows Server 2008
Servermanagercmd.exe -install web-windows-auth web-mgmt-compat web-mgmt-console web-http-logging

Installs the following components:

• [Web-Windows-Auth] – Windows Authentication
• [Web-Mgmt-Compat] – IIS 6 Management Compatibility
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Http-Logging] – HTTP Logging

Mediation Server on Windows Server 2008
Servermanagercmd.exe -install rsat-addc

Installs the following components:

• [RSAT-ADDC] – Active Directory Domain Controller Tools

Post used as a reference for this post

http://waveformation.com/2009/06/02/installing-ocs-2007-r2-prerequisites-on-windows-server-2008/