Home  |  Service Status  |  Team Blog  |  Forums
Outlook Web App > For Exchange Online Administrators > Outlook Live for Live@edu > Implement Outlook Live Directory Sync for Live@edu > Outlook Live Directory Sync for Live@edu Reference >

Outlook Live Directory Sync for Live@edu Known Issues

Applies to: Live@edu

Topic Last Modified: 2011-12-02

Dd878115.important(en-us,EXCHSRVCS.140).gifImportant:
Outlook Live Directory Sync (OLSync) is the synchronization solution for Microsoft Live@edu customers. If you are running a cloud-based e-mail service with Microsoft Office 365 for enterprises, you must use the Microsoft Online Services Directory Synchronization tool to synchronize your directories.

The current version of Outlook Live Directory Sync (OLSync), formerly known as GALSync 2010, has the following known issues. As such, there are some known issues that you should review before you deploy.  

Issue Description

Microsoft Forefront Identity Manager (FIM) 2010 or Microsoft Identity Lifecycle Manager (ILM) 2007 reports the error, exported-change-not-reimported, on a full import.

You may see this error when you try to run a full import on the Hosted management agent after you configure OLSync.

This error occurs when the Windows Live ID of a provisioned account in Outlook Live doesn't match the corresponding primary SMTP address on the on-premises user account.

This is a transient error. To fix it, re-run the full import operation on the Hosted management agent.

PCNS reports the error, Error copying string value.

The Password Change Notification Service (PCNS) may return this report when it tries to synchronize passwords. This error is often the result of an automatic update that requires a service restart. To fix it, restart the PCNS.

FIM 2010 or ILM 2007 reports the error, completed-transient-objects.

This error is benign. It means that there are some transient objects in the on-premise Hosted management agent connector space that cannot be synchronized. These transient objects don't represent anything on-premise.

You can ignore this error.

Read more