Hi, According to the live@edu Implementation Guide (http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/CommunityServer-Blogs-Components-WeblogFiles/00-00-00-99-63/6406.Live_4000_edu_5F00_Implementation_5F00_Guide_5F00_V2.pdf) Prerequisites for Identity Lifecycle Manager: You can't install OLSync on a server running Identity Lifecycle Manager in addition to other management agents I may be reading this incorrectly, but wouldn't one deploy ILM 2007 with an AD MA, to pull the users in from AD - so that they can in turn be passed along to the OLSync MA to provision the users in the live@edu environment. Hence 2 MAs on the same ILM server? Please could someone clarify, thank you Sk

Ah, based on the deployment guide: Test the configuration to verify the import of the OLMA configuration To verify that the import of the OLMA configuration, open the Identity Manager and make sure the Hosted and OnPremise management agents are listed. Click Start > All Programs > Microsoft Identity Integration Server > Identity Manager. In the Identity Manager window, click Management Agents. Under Management Agents, verify that the OnPremise and Hosted management agents are listed in the Name column. So it looks like it creates the 2 MAs that are required. All is good.

Ah, based on the deployment guide: Test the configuration to verify the import of the OLMA configuration To verify that the import of the OLMA configuration, open the Identity Manager and make sure the Hosted and OnPremise management agents are listed. Click Start > All Programs > Microsoft Identity Integration Server > Identity Manager. In the Identity Manager window, click Management Agents. Under Management Agents, verify that the OnPremise and Hosted management agents are listed in the Name column. So it looks like it creates the 2 MAs that are required. All is good.

S. Kwan, Actually, its not that other MAs can't be created when using this OLSync solution. It is that it removes the default object classes and replaces them with the single SyncObject class. Of course, object classes could be added to the MV schema after doing this. Glenn Zuckemran, Microsoft Identity Technologies

S. Kwan, Actually, its not that other MAs can't be created when using this OLSync solution. It is that it removes the default object classes and replaces them with the single SyncObject class. Of course, object classes could be added to the MV schema after doing this. Glenn Zuckemran, Microsoft Identity Technologies If I remember right, the installer has an option in the wizard to extract itself to a directory. If you do this you can manually import the custom MV schema and the two MAs to an existing ILM instance.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

S. Kwan, Actually, its not that other MAs can't be created when using this OLSync solution. It is that it removes the default object classes and replaces them with the single SyncObject class. Of course, object classes could be added to the MV schema after doing this. Glenn Zuckemran, Microsoft Identity Technologies If I remember right, the installer has an option in the wizard to extract itself to a directory. If you do this you can manually import the custom MV schema and the two MAs to an existing ILM instance.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Yeah, the confusion is between OLSync and OLMA. OLSync is the solution that includes both MA's and a bunch of provisioning code... OLMA is the Outlook Live Management Agent. Generally I just install the OLMA and write the code myself. - Ross Currie