Note that there are some explanatory texts on larger screens.

plurals
  1. PODirSync & Office 365 - how I can sync users?
    primarykey
    data
    text
    <p>Couple days ago I have turn-on DirSync on Office365 and AD. Unfortunately All users, that was not create on Office 365 account has been created and sync with domain. </p> <p>I work on <strong>Windows Server 2012</strong></p> <p>I have get information like that:</p> <blockquote> <p>[UserPrincipalName user@domain.com;WindowsLiveNetId System.Collections.Generic.List`1[System.Byte];]</p> </blockquote> <p>The solution for this problem is probably here: </p> <p><a href="http://support.microsoft.com/kb/2647098" rel="nofollow">Problem solution</a> or <a href="http://technet.microsoft.com/en-us/library/hh852469.aspx#bkmk_adcleanup" rel="nofollow">Microsoft Solution #1</a></p> <p>But how I can sync this users without delete them? <strong>I can't lose their data and e-mails.</strong> Have you know any solution for that? </p> <p>Update description:</p> <blockquote> <p>I will try to describe my problem better than at the begging.<br> I have AD in my company :) and we use Office 365 - until couple days ago we turn on DirSync. Unfortunately there is some serious problem. Only users that have not been created in Office 365 are created by AD and fully Sync. Users who has been created in Office 365 before turn on DirSync has not been sync.<br> I have try to change UPN -> AD create new user.<br> I try to use MOSDAL and Office 365 Deployment Readiness Tool - with no effects.<br> I don't have any idea to resolve this problem. Have you any solution, instruction, advice? </p> </blockquote> <p>Best regards.</p> <p>Tanks for any info!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload