| Home | Kaiming |
Create profiles for outlook 2003
Create profiles for outlook 2007
Open all profiles and share their calendars. So far, open other person shared calendars without problem.
Do a test –ADSIEdit.msc
Clear the LegacyExchangeDN property for Ex20032 and Simon Also.
The outlook 2003 clients cannot open Simon.Also shared calendar. Outlook 2007 has no problem to open both Simon.Also shared calendar and Ex20032 shared calendar.
Take a look at the value of LegacyExchangeDN:
For Ex20032 mailbox, it is /o=Workopera/ou=First Administrative Group/cn=Recipients/cn=ex20032.
For Simon.Also mailbox, it is /o=Workopera/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Simon.Also
Then, Move the ex20032 mailbox to Exchange 2007 server. Its LegacyExchangeDN property has value of /o=Workopera/ou=First Administrative Group/cn=Recipients/cn=ex20032. It keeps the old value. This is important observation. Don’t delete First Administrative Group, even though there is no Exchange 2003 server anymore, unless all your mail clients are outlook 2007.
How about you move the Ex20032 mailbox from Exchange 2003 to Exchange 2007?
When you manually modify the LegacyExchangeDN to /o=Workopera/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=ex20032
Outlook 2003 clients still cannot open Ex20032 shared calendar.
LegacyExchangeDN
This attribute is for backward compatibility.
All versions of MAPI clients (outlook 200/2002/2003/2007) and servers built to date can use the LegacyExchangeDN to locate objects.
Do not delete any Exchange 2003 or Exchange 2000 administrative groups that ever contained mailboxes. The LegacyExchangeDN property on a mailbox from an Exchange 2003 or Exchange 2000 administrative group still references the Exchange 2003 or Exchange 2000 administrative group even after you move the mailbox to a server in the Exchange 2007 administrative group. Office Outlook 2003 and earlier versions use the LegacyExchangeDN property to get free/busy information. If the administrative group that the LegacyExchangeDN property references no longer exists, Outlook will not be able to find free/busy information. In addition, all versions of Outlook use the LegacyExchangeDN property when a user delegates access to folders by using the Outlook client. If you delete the legacy administrative group that the LegacyExchangeDN property references, Outlook will not be able to find the assigned delegated user.