Tuesday, May 20, 2008


We finally finished deploying OCS. Let me tell you this up front the OCS look rock. I am sure it will improve the work quality in a short time. So those of you who don't know much this is the product for internal Chat, file sharing, virtual meeting ( round table) and more. Installation of OCS is kinda of tricky, but the installation wizard is extremely helpful. It was easy to follow it trough.

Installation Tips:

Keep your database files on a separate Drive and keep transaction logs on separate drive if it is possible.

  • Installation Path: C:\Program Files\Microsoft Office Communications Server 2007\
  • Main service account name: RTCService
  • Conferencing service account name: RTCComponentService
  • Internal web farm FQDN: NHQOSC001.smtp25.org
  • External web farm FQDN: <Empty>
  • User database path: O:\LC Data\
  • User database log path: C:\LC Log\

Problem: Failed to activate Office Communications Server Standard Edition Server on machine

  • Event Type: Warning
  • Event Source: OCS Setup
  • Event Category: (1007)
  • Event ID: 30502
  • Date: 5/19/2008
  • Time: 3:10:55 PM
  • User: N/A
  • Computer: NHQOSC001
  • Description:
  • Failed to activate Office Communications Server Standard Edition Server on machine NHQOSC001.archq.ri.redcross.net.
  • Error: 80004002
  • Description: No such interface supported


The command needs to be executed on the Root Domain rather than the Child domain. This scenario you are installing OCS on a child domain and there is empty root domain, so go to command prompt on the OCS server and execute following command

PS: RCODC3CHI005 is the name of the ROOT DC in this case.

LCSCmd.exe /Server /Role:SE /Action:Activate /Password:My$tr0ngPwd /RootDC:RCODC3CHI005 /GC:RCODC3CHI005


  • Event Type: Warning
  • Event Source: Communicator
  • Event Category: None
  • Event ID: 1
  • Date: 5/20/2008
  • Time: 11:13:14 AM
  • User: N/A
  • Computer: OOZUGURLUPC
  • Description:

Communicator was unable to locate the login server. No DNS SRV records exist for domain smtp25.org, so Communicator was unable to login.


Please double-check the server name to make sure that it is typed correctly. If it is correct, the network administrator will either need to use manual configuration to specify the login server's fully-qualified domain name (FQDN), or add DNS SRV records for the smtp25.org domain in order to allow automatic client configuration. The DNS SRV records

  • _sipinternaltls._tcp.smtp25.org
  • _sipinternal._tcp.smtp25.org

Go to DNS Server

Create SRV record, new, other records, service record, on the service erase and type _sipinternaltls

Sip.smtp25.org (change the smtp25.org to your own domain)


Office communicator cannot use auto sigh in, receiving following errors

"Cannot sign in because the server is temporary unavailable. If the problem persists, contact your system administrator"


This is purely DNS issue; if you fix the previous issue you won't see this error. You can still make client work by configuring it to manual configuration, by clicking on left upper corner,

  • Tools
  • Options
  • Advance
  • Manual configuration
  • TLS
  • Name or IP address of the OCS Server


Oz Ozugurlu

Systems Engineer



Security Project+ Server+


No comments: