O365 - DirSync - Wrong name on email

[Steve21]

Morning Guys,

 

New user starting soon so just sorting out their emails etc and noticed they're picking up the wrong name on O365 from AD as I'm guessing the email address has been used in the past.

 

Instead of Jack Bob it's Jo Brown etc.

 

I've done a full resync in dirsync assuming this would clean it but doesn't seem to and can't manually change it on 365 as it's sync'd to AD. Is there a cache somewhere else it might be sitting as the account doesn't exist in AD (old one anymore), and obviously DirSync isn't pulling it across unless a Full Sync Import won't do name changes?

 

Thanks,

Steve

[Marshall_IT]

So you have a user with the upn [email protected] and it is displaying a different display name on office 365 to AD?

 

Have you looked at the detail for that user on the last full sync in the gui for dirsync?

 

Are you using the latest update to DIRSYNC?

[Boredguy]

Hey Steve

 

Full Sync for Active Directory,

Full Import Full Sync for Windows Azure,

Export Windows Azure

 

should force your AD to fully sync up to 365 with name changes etc

[Steve21]

So you have a user with the upn [email protected] and it is displaying a different display name on office 365 to AD?

 

Have you looked at the detail for that user on the last full sync in the gui for dirsync?

 

Are you using the latest update to DIRSYNC?

 

Yep to first bit, all changes sync'd across and looked happy on last one, and it's an older version so might need updating if this doesn't like it

 

Hey Steve

 

Full Sync for Active Directory,

Full Import Full Sync for Windows Azure,

Export Windows Azure

 

should force your AD to fully sync up to 365 with name changes etc

 

Will try the "full sync" as only did "full import full sync" (assumed that was higher)

 

Thanks,

Steve

[Marshall_IT]

Hey Steve

 

Full Sync for Active Directory,

Full Import Full Sync for Windows Azure,

Export Windows Azure

 

should force your AD to fully sync up to 365 with name changes etc

 

Overview fund this never works for me, unless it's been updated since I last tried.

 

You can also run the following command from powershell

 

Start-OnlineCoexistenceSync

 

To perform a full sync.

[Boredguy]

Overview fund this never works for me, unless it's been updated since I last tried.

 

You can also run the following command from powershell

 

Start-OnlineCoexistenceSync

 

To perform a full sync.

 

It certainly worked for us when we first set it up. the powershell command works all the time, but it's normally only does the delta sync

[Steve21]

Mmm same issue, but digging a bit further into the error:

 

Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [Mail [email protected];]. Correct or remove the duplicate values in your local directory. Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values.

 

Even though there isn't a duplicate user, and that program can't find one :s Silly MS!

 

Aye the coexistence does delta syncs.

 

Gonna try the force matching it mentions above.

 

Steve

[EduTech]

Guys,

 

You should never really run the Run Jobs manually because if you do this in the wrong order and things are broken this could have adverse affects on your synchronization health which will then become harder to correct so I wouldn't recommend it. If you need to run a manual delta sync then use the Start-OnlineCoexistenceSync Command. If you need to do a FULL SYNC then you can provide the -FullSync Switch.

 

If your still having problems, then you will find that running the commands above won't help unless there is a specific reason for it. You should only run those Run Jobs if you actually understand fully what they are doing i.e. you understand the connector space, metaverse and what each profile actually does or/ do it via guidance from a Microsoft Support Engineer.

 

In terms of the issue you are having, assuming by name you mean UPN... has the UPN been replaced completely? i.e. with a *.onmicrosoft.com UPN for example or has just the first part been modified to be something you don't expect.

 

Thanks,

James.