Solved

Office 365 directory sync  issue

Posted on 2014-12-16
1
150 Views
Last Modified: 2014-12-23
Hello Experts,

I have a customer that recently performed a migration of all their operations from one site to another location.

In order to summarize the issue, whenever an account is enabled for O365 sometimes is never showed up in the o365 management console.

From what I understood on the initial assessment, the account was enabled by the name of jdoe@domainA.com email address for O365, and like I mentioned earlier, was never showed up in the o365 Management console.

Later on, the System Administrator found that the 0365 account used for sync is jdoemscloud@domainA.microsof.com. As per client “the password is definitely wrong on the DirSync server”

After further investigation, the network team has indicated that this could be a ADFS issue, however they also recommended to implement multicast for the Windows network load balancer [as per link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006558].

Initial thoughts pointed to check the multicast setup on the upstream switch, static ARP entry.

What could be happen here that passwords and users are not synchronizing here?

Can you please send your thoughts regarding the ADFS troubleshooting steps and recommendation to fix this issue? Please provide step-by-step instructions.

Can you please provide your input regarding the Windows network load balancer option?

Is the article explained on link above accurate to isolate the network side of things? Could this be root cause of issue?

Please see environment below:

Exchange servers in an internal network with IP address 10.x.x.x

ADFS servers in a DMZ doing NAT with a Public IP address 4.x.x.x

Exchange is using another new IP public for the exchange server itself. I meant, is not going to NAT to the WNLB ADFS IP, it's going to NAT to the new Exchange server IP.

Your feedback is highly appreciated
0
Comment
Question by:Jerry Seinfield
1 Comment
 
LVL 38

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 40504196
If the on-prem UPN is jdoe@domainA.com, but the user ends up created as jdoemscloud@domainA.ONmicrosoft.com make sure that domainA.com is added and verified in Office 365. Best thing to do is to open the MIISClient (located in the dirsync install dir), go to the metaverse tab, search for the user. It will show you how the user was synced to the cloud and whether any errors occurred.

Exchange and AD FS are totally independent, and the logging issue is most likely caused by the different UPN for the user in the cloud. Or by the fact that the user is not synced at all (at least this is how I interpret the "never showed up in the o365 management console" bit, or you mean the EMC console?).
0

Featured Post

Free book by J.Peter Bruzzese, Microsoft MVP

Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

Join & Write a Comment

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
how to add IIS SMTP to handle application/Scanner relays into office 365.

707 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now