[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 321
  • Last Modified:

Lync 2010

Here is our situation.

We are running a trial version of Lync 2010 to get our feet wet with the technology.  Our internal network consist of a parent domain (parent.com) w/ a child domain (child.com).  Neither of these domains are ours from an internet perspective, so we have a third domain that we use for email communication (email.com).

Using the sip of <username>@parent.com works just fine but has to be configured manually for each user as we add them - trying to use one of the preset options fails.  Ideally, we would want to use the first option (email address) for the sip, which would mean they would log in using <username>@email.com.   I added the email.com domain as one of the usable options in the topology and was able to assign it to a user - however, I initially wasn't able to log on to Lync server because it didn't know where to route the traffic to.

I created a DNS entry that points sip.email.com to the Lync server and that allowed for me to log on to the server BUT it doesn't seem to know about availability (I'm not reporting my calendar status to other users) unless I log in the old way (<username>@parent.com).  Is there another DNS entry I need to make to send that information?  Is there a better way to do all of this?
  • 3
1 Solution
unless I totally misunderstood your question you should change the upn of your users to be name@email.com instead of name@parent.com or name@child.com

to do this http://support.microsoft.com/kb/243629
Open Active Directory Domains and Trusts.
Right-click Active Directory Domains and Trusts in the Tree window pane, and then click Properties.
On the UPN Suffixes tab, type the new UPN suffix that you would like to add to the forrest.
Click Add, and then click OK.

after you do that go to the user properties in ad and change the upn from @domain.com or @child.com to @email.com and test
LoendarAuthor Commented:
We wiped the server and started over to approach with a fresh build.
LoendarAuthor Commented:
Closing Question
LoendarAuthor Commented:

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now