+ Post New Thread
Results 1 to 6 of 6
Cloud Services Thread, Office365 Dirsync Error in Technical; Hi Guys, I made some changes to our proxyAddress attribute in AD a week or so ago to make sure ...
  1. #1

    Join Date
    Aug 2009
    Posts
    280
    Thank Post
    20
    Thanked 22 Times in 19 Posts
    Rep Power
    14

    Office365 Dirsync Error

    Hi Guys,

    I made some changes to our proxyAddress attribute in AD a week or so ago to make sure every user had their jbloggs and joe.bloggs e-mail addresses for Office365 and now I'm receiving this error for two of our users. Has anyone got any ideas as to how I can track the cause down? The user's accounts are now 'In cloud' on the Office365 admin panel, too. I can't see any conflicting settings in our AD...

    Code:
    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: [ProxyAddresses SMTP:first.last@school.county.sch.uk;]. 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.
    The idFix tool on the Microsoft support page showed nothing wrong

    Thanks!
    Last edited by Blue_Cookeh; 15th August 2014 at 12:45 AM.

  2. #2

    Join Date
    May 2011
    Location
    Jus North of London, close but not too close
    Posts
    862
    Thank Post
    192
    Thanked 72 Times in 67 Posts
    Rep Power
    50
    In AD Users and computers check that you have no one else with the same proxy address, you could do this with an AD query and add the Proxy Address Column in and do a visual scan.

  3. #3

    CPLTD's Avatar
    Join Date
    Apr 2008
    Location
    Northamptonshire
    Posts
    4,072
    Thank Post
    1,404
    Thanked 652 Times in 507 Posts
    Blog Entries
    1
    Rep Power
    261
    If the Cloud account and the AD account are not showing “synchronized” it is probable that they have stopped synching because the proxy attributes are no longer matching.

    Check to see if these two users have any old mail attributes that could be confusing things. Check that you have the correct SMTP primary addresses listed in the local directory and in the Exchange mailbox for each miss matched account. Making sure that your SMTP primary is in capital in AD and the correct Primary is set in Exchange.

    Then rerun Dirsync if you had to make changes. This MAY allow the system to soft match on the SMTP addresses of the users.

    It is unlikely to match and if it doesn’t then it is likely that the AD and WAAD accounts have conflicting a GUID/ImmutableID.You will need to take the GUID convert it to an immutableID and set the immutableID in WAAD for the affected UPN using the script below in the Azure Powershell tool.

    Set-MsolUser -UserPrincipalName User@domain.com -ImmutableId [ENTER IMMUTABLEid HERE]

    Good Luck!

    Andy
    Last edited by CPLTD; 15th August 2014 at 01:25 PM.

  4. Thanks to CPLTD from:

    Blue_Cookeh (22nd August 2014)

  5. #4

    Join Date
    Aug 2014
    Location
    United States
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    its the same with me : /

  6. #5

    Join Date
    Aug 2009
    Posts
    280
    Thank Post
    20
    Thanked 22 Times in 19 Posts
    Rep Power
    14
    Quote Originally Posted by CPLTD View Post
    If the Cloud account and the AD account are not showing “synchronized” it is probable that they have stopped synching because the proxy attributes are no longer matching.

    Check to see if these two users have any old mail attributes that could be confusing things. Check that you have the correct SMTP primary addresses listed in the local directory and in the Exchange mailbox for each miss matched account. Making sure that your SMTP primary is in capital in AD and the correct Primary is set in Exchange.

    Then rerun Dirsync if you had to make changes. This MAY allow the system to soft match on the SMTP addresses of the users.

    It is unlikely to match and if it doesn’t then it is likely that the AD and WAAD accounts have conflicting a GUID/ImmutableID.You will need to take the GUID convert it to an immutableID and set the immutableID in WAAD for the affected UPN using the script below in the Azure Powershell tool.

    Set-MsolUser -UserPrincipalName User@domain.com -ImmutableId [ENTER IMMUTABLEid HERE]

    Good Luck!

    Andy
    Brilliant, you got me on the right track!

    - Firstly I had to stop the link between on premises and Office365 AD accounts using the Forefront Identity Mgmt client to enable deletion
    - Then I had to force a full export into Office365 from the FIM client
    - The account changed to 'In cloud'
    - I could then use Powershell to delete the account and remove it from the Recycle Bin on Office365 (otherwise the account still exists and you get immutableID non-unique errors later)
    - I then changed the "real" 'In cloud' user's immutableID to be the same as our on premises user
    - I forced a full synchronisation with Powershell and start-onlinecoexistencesync

    That's the two affected accounts now working perfectly and sync'd back to AD, thanks!
    Last edited by Blue_Cookeh; 22nd August 2014 at 10:25 PM.

  7. #6

    CPLTD's Avatar
    Join Date
    Apr 2008
    Location
    Northamptonshire
    Posts
    4,072
    Thank Post
    1,404
    Thanked 652 Times in 507 Posts
    Blog Entries
    1
    Rep Power
    261
    Good Effort! That would work as a means to an end! There are a few risks in doing it that way that the less enlightened might trip over.
    The major one is if you remove the Exchange licence from an account you delete the mailbox.

SHARE:
+ Post New Thread

Similar Threads

  1. Office 365: dirsync error 611 and Invalid Namespace warning
    By sonofsanta in forum Cloud Services
    Replies: 21
    Last Post: 13th February 2014, 04:27 PM
  2. Office365 DirSync & Usernames
    By Blue_Cookeh in forum Cloud Services
    Replies: 3
    Last Post: 6th September 2013, 10:09 PM
  3. DirSync errors event ID 0,110, 655,6801,6803
    By MrWu in forum Cloud Services
    Replies: 2
    Last Post: 27th August 2013, 08:39 AM
  4. office365 add new UPN question and other Dirsync woes
    By RabbieBurns in forum Cloud Services
    Replies: 1
    Last Post: 15th July 2013, 07:19 PM
  5. Replies: 0
    Last Post: 20th June 2013, 03:58 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •