Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 54
  • Last Modified:

SIPAddresses post Office 365 migrations

We are having some issues with Office Communicator after migrating users to the Office 365 cloud.

The trouble, I think, is because we have one AD domain to log into (Contoso.com), but users some users may have an alternate PrimarySMTPAddress based on their site (NorthwindTraders.com) and Communicator allows the SIP of NorthwindTraders.com.

Communicator used to be able to use their SAMaccount to log in, so now when Communicator tries to connect to Outlook for meetings or contact info, it prompts the users continuously for their credential...

Example:
SAMAccount:     John.Doe
UPN:      John.Doe@contoso.com
PrimarySMTPAddress:      John.Doe@NorthwindTraders.com
EmailAlias:     John.Doe@contoso.com
SIPAddress:     John.Doe@NorthwindTraders.com

I assume that we would simply have to change all msrtcsip-primaryuseraddress addresses to match the users UPNs?

If so, does anyone have a script to assist please? Probably need to firstly export a list of users with non-Contoso.com SIP addresses then just change those to match the UPN?

Thanks for any help in advance.
0
Christian Hans
Asked:
Christian Hans
1 Solution
 
Ganesamoorthy STech LeadCommented:
Active Directory On-premises SMTP did not match with their Office365 SMTP name, need to sync this

http://www.windowstricks.in/2016/08/active-directory-premises-user-name-not-match-office365-user-name.html
0

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

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