SRV Record Setup for OCS 2007 Standard Edition Server Install

Posted on 2008-10-29
Last Modified: 2013-11-29
We are a large enterprise and installing OCS 2007 in our lab environment.  installing a Standard Edition Server, Communicator Web Access Server and Archiving server.  Strictly for internal use only, will not be doing any external federation or Public IM with this test platform.   I have already successfully installed the Standard Edition server and ready to get into the next steps of configuration and certificate installation.  Question has to do with setup of SRV records to allow automatic client authentication.  See the attached document which has an excerpt in it from the OCS Standard Edition Deployment guide.  Our test lab Forest has a root domain we will call for discussion  Labt and two child domains called Wizt and SWizt.   These would be the actual domain names.   DNS A record pointing to the FQDN of the Standard edition server has already been created.  In DNS on one of our DC's I went to the Forwarding Zones and under the zone for Labt, Wizt and Swizt I created an SRV record associated with those domain names for sipinternatls which points to the name FQDN of the Standard Edition server.  We also have mulitple email domain names for our users.  So various users could have different SIP addresses associated with their the primary SMTP address of their mailbox.   It states in the documentation that also for Automatic Client sign-in you will need to create an SRV record for each SIP domain.   So I am wondering now if I need to do this and if so where will these SRV records be created ?    I need someone to shed more light on this area for the Standard Edition Server.  
Question by:svmEMDS
  • 2
LVL 15

Expert Comment

ID: 22838395
Server locator records, pretty easy, just need to create one for each SIP domain, not each AD domain in your forest....

eg... you may have bob.local, and as your AD domains, but for whatever reason use for your SIP domain.... in which case you need to create a dns zone and put the sipinternal entry into that zone.

Author Comment

ID: 22840326
That's where some confusion layed.   In the test lab when I look at DNS on one of the DC's we have three forward lookup zones for the following examples: (Forest root domain), (child domain) and (child domain).  So it begged the question where do I create the SRV record for each SIP domains (which in reality are the Primary SMTP email address that each user could be assigned and they are not the same name as the domains in the AD forest).  Like in LCS when you assign a user to LIve Communications Server in ADUC a SIP: address gets created in the users email addresses tab  i.e.  SIP:  which is the same address as the users Primary SMTP email address set on that users mailbox.   I wasn't sure if i had to create new forward lookup zones for each SIP domain and then create an SRV record in each new lookup zone.   Or could these SRV records be created in the existing three Forward Lookup Zones already present for the forest domains.    
LVL 15

Accepted Solution

HayesJupe earned 250 total points
ID: 22846764
Yer - i read all that and your not making much sense!

ok, when it comes to OCS - basically forget about your AD dns zones..... for a server locator record all you need to have is the SIP domain you are using setup as a dns zone, and the appropriate records in that. In your case, create that zone on one of your DC's, then setup condiftional fowarders or stub zones or whatever you to enable clients to be able to find that zone.

So to make it very clear, in a environemnt where you have: (Forest root domain), (child domain) and (child domain), (sip domain)

setup as a new zone (i prefer AD integrated) perhaps on your forest root. Create appropriate records in that zone, then use forwarders to ensure clients can resolve those records...

for auto-location - ONLY sip domains matter, get that other stuff out of your head.

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is my 3rd article on SCCM in recent weeks, the 1st ( dealing with installat…
Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below.…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question