http://blogs.technet.com/msonline/archive/2008/08/29/non-exchange-active-directory-user-directory-synchronization-configuration-settings.aspxIf you are running in a non-messaging (Exchange 2000 or higher) Active Directory environment, and you want to use the Microsoft Online Services Directory Synchronization Tool, you must configure certain Active Directory User attributes if you want theen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/msonline/archive/2008/08/29/non-exchange-active-directory-user-directory-synchronization-configuration-settings.aspx#3114310Sat, 30 Aug 2008 05:45:18 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3114310Business blog &raquo; Blog Archive &raquo; Non-Exchange Active Directory User Directory Synchronization &#8230;<p>PingBack from <a rel="nofollow" target="_new" href="http://business.pitauto.com/2008/08/non-exchange-active-directory-user-directory-synchronization/">http://business.pitauto.com/2008/08/non-exchange-active-directory-user-directory-synchronization/</a></p> http://blogs.technet.com/msonline/archive/2008/08/29/non-exchange-active-directory-user-directory-synchronization-configuration-settings.aspx#3119960Fri, 05 Sep 2008 20:48:56 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3119960jtregear<p>Ryan,</p> <p>While I now understand how dirsynch works, I do think it is a design inconsistency with how MOS works in other user provisioning scenarios (i.e. manual and bulk user management) with some practical consequences.</p> <p>MOS allows for the administration and provisioning of many domains within one license. However, if you want to provision those domains via dirsynch than I don't see how you can do that other than to have separate licensing for each domain.</p> <p>Jon</p>