Comments on: DNS Records and Office Communicator Automatic Client Sign-In

By: How can I connect Outlook to Office Communicator (Different Email accounts) - Admins Goodies

Sun, 21 Aug 2011 05:18:05 +0000

[...] to the Front End server so that the auto-discovery process will work properly. The specifics are summarised here. Autodiscovery will still work even without SRV records provided you have the relevant aliases [...]

By: ECL

ECL — Mon, 08 Nov 2010 10:57:24 +0000

Thanks for you reply Curtis.

I am actually using LYNC 2010 and I thought OCS 2007 would be simular.

If I create a new user in the domain A which i have installed LYNC 2010 and the login – the sip sign-in in communicator is automatically populated and user automatically signs in. No user intervention at all (I don’t need to manually enter the SIP) – I have tested on a few users and works really well – not sure how it does it but I guess the new communicator must query AD?

I setup a trust to domain B and when I login as a domain B user the sip sign-in is not automatically populated in communicator and I need to manually enter the sip login. Once logged in subsequent logins are fine.

As all the users will be on domain B (the user domain) I wanted to have the same autologin function (i.e. auto populated the users communicator login in domain b on 1st login). I am guessing that since LYNC 2010 is not installed in Domain B it is unable to query the users SIP login to automatically log them in?

I thought this also happens in OCS 2007 according to this post

http://www.proexchange.be/blogs/ocs2007r2/archive/2009/09/24/reset-sign-in-address-in-communicator-automatic-vs-manual-configuration.aspx

Thanks

ECL

By: Curtis Johnstone

Curtis Johnstone — Fri, 05 Nov 2010 19:21:00 +0000

I am not sure I fully understand your scenario, but OCS automatic sign-in means having the correct DNS settings so that Communicator client automatically finds the OCS Front-End server to login to. You are suggesting that the Communicator client queries AD for user’s SIP details. The users SIP details are manually entered into the Communicator client (or auto-populated by a GPO or provisioning software); it does not query AD for this information, and it not part of the automatic sign-in feature.

To my knowledge automatic sign-in should work fine if OCS is deployed in a resource forest.

Hope that helps, Curtis

By: ECL

ECL — Fri, 05 Nov 2010 18:01:06 +0000

Hi, Great post I have question which I hope you can help with.

Does automatic sign-in work when the OCS installation is in the resource forest? I find the users able to login in the Accounts forest when they manually enter their SIP:email. But I just can’t get it to auto populate the sign on the 1st login. P.S automatic login works fine in the resource forest. I think it is something to do with the fact that the Accounts forest does not have the users SIP details hence the OCS client can’t query AD for the users SIP address on login?

Any pointers will be most welcomed.

Thanks

ECL

By: Communicator Automatic Sign-In when SIP Domain Different from AD Domain « Inside OCS

Mon, 14 Sep 2009 21:14:21 +0000

[...] OCS server or pool to sign into via DNS SRV records (this process is well documented – my posting DNS Records and Office Communicator Automatic Client Sign-In describes it). Normally the SRV record resolves to the FQDN of the OCS standard edition host or OCS [...]

By: The OCS 2007 Automatic Sign-In Troubleshooting Tool V2.0 « Inside OCS

The OCS 2007 Automatic Sign-In Troubleshooting Tool V2.0 « Inside OCS — Wed, 12 Aug 2009 05:11:15 +0000

[...] DNS Records and Office Communicator Automatic Client Sign-In [...]

By: The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 « Inside OCS

The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 « Inside OCS — Fri, 24 Jul 2009 21:39:58 +0000

[...] DNS Records and Office Communicator Automatic Client Sign-In [...]

By: Automatic Office Communicator Sign-In (Part 1 – The Correct DNS Service Location (SRV) Record) « Inside OCS

Fri, 24 Jul 2009 21:07:16 +0000

[...] the SIP domain of the user attempting to sign-in. The SRV record must be of a particular format. See my previous blog post on what the format of the DNS record should be. The SIP domain is the right-hand-side of the [...]

By: Troubleshooting Microsoft Office Communicator Issues 101 « Inside OCS

Troubleshooting Microsoft Office Communicator Issues 101 « Inside OCS — Mon, 29 Jun 2009 19:50:54 +0000

[...] previous post, DNS Records and Office Communicator Automatic Client Sign-In, summarizes how Communicator uses DNS to connect to the [...]

By: Bill Dishman

Bill Dishman — Wed, 17 Sep 2008 21:37:51 +0000

Hi.

I have a pretty large deployment in progress. One thing I dont really understand.

I have one external srv record. _sip._tls.. This points to my server in a datacenter in Atlanta.

I also want a pool in the UK, Australia, and Singapore.

Since I only have one srv record externally for my domain, that means for an internet user, they will always start first by hitting my datacenter in Atlanta, then the director takes over and sends the traffic back to Singapore?

In Singapore, UK, Australia I will have a front end server, a director an edge server, and isa firewall and possibly a mediation server.