Exchagne 5.5 users are not able to open calendar of the shared mailboxes migrated to Ex 2003 though they have got reviewer permission.
Exchagne 5.5 users are not able to open calendar of the shared mailboxes migrated to Exchange 2003 though they have got reviewer permission. When we reapply the permission, it starts working and this is not happening to all the migrated mailboxes but for only few.
July 23rd, 2009 2:00pm

I would ask you to run pfdavadmin and then connect to that mailbox and then expand the Top of Information Store then right click on the calendar and check DACL state. Note. export the permission before you make any changes Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2009 3:42pm

I have already done that. DACL state is Good.
July 23rd, 2009 5:17pm

Check info: 1. Please describe the current mixed exchange topology 2. Whats the error info if ex5.5 (Exchange 5.5) users cant open ex2k3 (Exchange 2003) users Calendar folder? 3. Is there any related event on the application log among the exchange servers if we reproduce such issue? 4. Does the symptom occur if other ex2k3 users were trying to open those migrated users Calendar folder? 5. Hows the move mailbox report for those migrated mailboxes? Please check the log files. The logs are saved in XML format to the following path: systemdrive\Documents and Settings\profile name\My Documents\Exchange Task Wizard Logs Resources: Move Mailbox improvements in Exchange 2003
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2009 5:41am

Have you seen the following KB articlehttp://support.microsoft.com/KB/926084
July 24th, 2009 3:44pm

Its mixed mode organization and first exchange 2003 server installed into existing 5.5 sites. Already exchange 2003 servers are installed in the organization. We have more than 50 sites into existing organization. There are 4 exchange 5.5 servers and 2 exchange 2003 servers are available in our site. We have NT domain migrated to windows 2003 server domain (Inter-forest Migration) and co-exiting exchange 2003 server into existing exchange 5.5 site. After moving from one way to two way connection agreement of ADC the permission of the Exchange 5.5 mailboxes got changed from users to custom. We have changed it thought scripting but its again got changed from user to custom. Below article mentioned that msExchsecuritydescriptor got corrupted because of the ADC connection agreement. http://support.microsoft.com/kb/329169 http://support.microsoft.com/kb/317721 Users are able to login into both domains after moving mailboxes. We have cloned users from Windows NT to windows 2003 using ADMT. Its not generating any error message after moving mailboxes and while moving mailbox its showing successful. After migrating its creating problem to access shared calendar for e2k3 and exchange 5.5 users. There is no error message on the exchange 5.5 and Exchange 2003 server related to this issue. Out of 10 its creating problem for 2 users. Just started pilot testing. Error Message: Unable to display folder. The calendar folder couldnt found. (Client side) Exchange task wizards not showing any error and its successful.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2009 4:25pm

After further research, I found that the behavior you encountered shall be expected and is due to the SID history migration When you use ADMT (Or ADClean) on the 5.5 mailbox, it merges all the information mainly legacyExchangeDN attributes of the users. Then, users will only be able to use their 2003 account and not use the NT\5.5 account for login Workaround: Not run ADMT (Or ADClean) until you are ready for the users to start logging in with their AD accounts
July 27th, 2009 5:25am

Hi James, It's not that the user is trying to view the calendar using his NT/5.5 account login, but it happen to other users who are still not migrated and are not able to view the calendar (though they have got permissions on the shared calendar which is migrated to exchane 2003). Resetting the default permission resolves the issue. Also, its nothappening to all the migrated shared mailboxes but only few. Like 2 out of 10 migrated ina batch.
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 6:10pm

Please note that January 11, 2006 has brought a close to Support for Exchange Server 5.5 as part of the Microsoft Lifecycle Policy All the support for the issues on the exchange server 5.5 sides is no longer available Thanks for your understanding Support Life-Cycle Policy for Exchange Server 5.5
July 29th, 2009 7:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics