Happy Days: OCS 2007 and Exchange 2007 Installation

During my demo environment installation (OCS and Exchange 2007), I got a few blockers that I couldn't find documented on the Internet. Maybe, it could be of your help. Here they are:

OCS Deployment:

Failure [0xC3EC7924] Schema definition for the requested Active Directory attribute isn't available. Please ensure local ADSI schema cache is up-to-date.

This problem occurred during the Deployment step of the OCS installation. Every AD schema preparation step ran successfully prior to this one. Checking the logs, it turns out that the AD schema class "Phone Route Usages" doesn't exist or there's a problem reaching it. The solution was to delete the schema cache file on the local server. The schema cache file is stored under C:\Windows\SchCache and this is used by ADSI to avoid the roundtrips to download the schema for every AD request. Simply delete the files stored in this folder (every domain has its own schema cache file) and re-run the installer.

There was a problem verifying the certificate from the server. Please contact your system administrator.

This problem occurred during the first logon with Office Communicator 2007. The resolution was to go to the server, start mmc, open the Certificates snap-in (computer account and local computer), find the root certificate (the issuer of the certificate used by OCS - VeriSign or your organization's KDC), export it to a file, and import it on the workstation. Don't accept the automatically determined location when importing the certificate on the client. Choose the folder yourself, it has to be the "Trusted Root Certification Authorities".

Presence icons didn't appear on the SharePoint site:

Presence icons are the result of a client-site JavaScript and ActiveX core running in the browser. Of course, they needs to be trusted. So, if your MOSS site is not trusted or not in an intranet zone (which is also treated as a "trusted" zone), this code won't be allowed to run. I found this info on Andrew Woodward's blog, thanks Andrew! 🙂

Exchange 2007:

Error: Opening package 'Z:\Exchange 2007\Setup\ServerRoles\UnifiedMessaging\umlang-en-US.msi' failed. This installation is forbidden by system policy.  Contact your system administrator. Error code is 1625.

I got this one when tried to install the Unified Messaging Role for Exchange 2007. I tried to run the installer package from the network (mapped drive) which was forbidden by System Policy. So, copied it to the local disk.

The Unified Messaging server has encountered an argument that is missing or not valid: "AttachmentName".

I got this error message to the event log. I tried to create a fake voicemail message for the Unified Messaging service on Exchange 2007 by copying a WAV and TXT file to the UnifiedMessaging\Voicemail folder on the server. The TXT file is a descriptor that contains a link to the WAV file (the actual voicemail message). I dropped these 2 files together to the same folder, but it seems that the TXT file got there first and when UM got notified about the new file, it tried to open the WAV file which was not yet there. The resolution was to copy the WAV file first, and *THEN* the TXT (has to be very fast).

Free/Busy lookup was not working from Outlook

When tried to look up other user's F/B information, Outlook showed me a grey line (no information) for them. Enabled Outlook logging and the following error message was logged to the log file:

2007/08/27 14:29:57.431: Getting ASURL
2007/08/27 14:30:10.589: Failed to get ASURL. Error 8004010F

Checked with MfcMapi that the SCHEDULE+ FREE BUSY folder was accessible and it was populated with every mailbox. Then, asked some more clever guys and they told me that in order for F/B to work, AutoDiscovery also has to work. I could check how AutoDiscovery works by holding the Ctrl key and right-clicking on the Outlook icon in the system tray area and selecting the "Test E-mail Autoconfiguration" menu. From the dialog, I cleared the Guessmart and Secure Guessmart checkboxes, typed the email address and password of the current user and ran the test. It turns out that I needed another DNS entry with a name of autodiscover.yourCompany.com. Outlook then calls this host on SSL and tries to retrieve a file called autodiscover.xml to retrieve AutoDiscovery information. You can check if this request works: https://autodiscover.yourCompany.com/autodiscovery.xml - if it does, then try again and OOF will work now.

Comments (7)

  1. George says:


    Trying to configure a test environment that connects (Federates) to the public IM WITHOUT using an edge server.

    Any insight on whether this can be done / how it can be done would be helpful.



  2. Iris says:

    consumed immediately, and in which one day’s expense can neither alleviate Bank of England was obliged to supply them. The Scotch banks, no doubt, paid

  3. NitinB says:

    Well I will like to install OCS 2007, Exchange server 2007 and MOM 2007 can anyone help with this and they should be integrated with each other so that mom will moniter all the other server … Can any body give me the details, how to install it ?

  4. dszabo says:


    Here’s some info on integrating MOM/System Centre with MOSS/WSS and OCS:

    For MOSS:


    MOM 2005 Management Pack for WSS3

    Also see the following blog: http://blogs.msdn.com/sharepoint/archive/2006/12/08/wss-3-0-mom-management-pack-rtw.aspx

    MOM 2005 Management Pack for MOSS 2007

    Note: requires MOM2005 sp1

    If you are evaluating System Center Ops Manager (SCOM) 2007, there are Management Packs for WSS3 and MOSS 2007 also.

    See blog: http://blogs.msdn.com/sharepoint/archive/2007/12/10/announcing-new-system-center-operations-manager-2007-packs-for-wss-3-0-and-moss-2007.aspx

    For OCS:


    Office Communications Server 2007 Quality of Experience Monitoring Server MP for MOM 2005: QoE Monitoring Server Management Pack for MOM 2005 monitors the audio and video quality for Office Communications Server 2007 Server Enterprise Voice deployment.

    Office Communications Server 2007 Management Pack for MOM 2005: The Office Communications Server 2007 Management Pack for MOM 2005 monitors the health of computers running Office Communications Server 2007 on Windows Server 2003



  5. Ibrahim says:

    Excellent instructions on this error: "There was a problem verifying the certificate from the server. Please contact your system administrator"

    Thank you!

  6. Rudy says:

    I also had this "problem verifying the certificate" and installing the root certificate did not solve the problem yet.

    Second part of the problem was that I used Advanced Manual Connection Settings and entered the IP address of the server. Changing this to the FQDN made it work.

    You may also need to setup your network adapter IP properties to use the DNS server of OCS.

Skip to main content