RE: Mailbox Migration issues for modifying old calendar entries

  • From: "Mark Shevill" <Mark.Shevill@xxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 12 May 2005 12:50:59 +0100

Raj
        I tried this and it has made no difference. Any other ideas?
 
Thanks
 
Mark Shevill
Mobile: +44 7932 625510
Home Mail: Mark.Shevill@xxxxxxxxxxx
Business Mail: Mark.Shevill@xxxxxxxxx
Web: www.MSCCS.net
 

________________________________

From: Periyasamy, Raj [mailto:Raj.Periyasamy@xxxxxxxxxxxx] 
Sent: Thursday, May 05, 2005 3:53 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Mailbox Migration issues for modifying old
calendar entries


http://www.MSExchange.org/

Mark,
Is the problem only with modifying meetings booked in resource calendars
? Try this Mark, for a particular user object that has the problem, use
the ADSI Edit and modify the legacyExchangeDN attribute to be like 
 
"/o=organizationname/ou=5.5sitename/cn=Recipientcontainernamein5.5/cn=us
eralias"
 
Tell me if it works. Note down the original legacyExchanegDN value
before you modify.
 

HTH. 
Regards, 
Raj Periyasamy 
Systems Administrator 
MCSE(Messaging), CCNA 


________________________________

From: Mark Shevill [mailto:Mark.Shevill@xxxxxxxxxxx] 
Sent: Thursday, May 05, 2005 10:34 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Mailbox Migration issues for modifying old
calendar entries


http://www.MSExchange.org/

No I am afraid that doesn't work, adding an X500 address to the user
object with the old 5.5 DN name is supposed to create that relationship.
Removing and adding the user back again doesn't allow them to modify
entries that were created before the migration. This is only relevant on
for example a meeting room that is booked. The meeting room mailbox
stays on 5.5 and the user moves to 2003 so the meeting room mailbox is
not aware that the user moves. So removing and adding the user allows
them to create new things with author permissions but the old ones
cannot be modified since the meeting room mailbox sees them as a
different person
 
 
Thanks
 
Mark Shevill
Mobile: +44 7932 625510
Home Mail: Mark.Shevill@xxxxxxxxxxx
Business Mail: Mark.Shevill@xxxxxxxxx
Web: www.MSCCS.net
 

________________________________

From: Periyasamy, Raj [mailto:Raj.Periyasamy@xxxxxxxxxxxx] 
Sent: Thursday, May 05, 2005 3:16 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Mailbox Migration issues for modifying old
calendar entries


http://www.MSExchange.org/

Mark,
I think it could be related to the Exchange LegacyDN attribute. This
attribute changes when the user is migrated from 5.5 to 2000/2003 if I
am not mistaken. In 5.5 the legacy attribute is based on the Site name,
where as in 2000, the attribute is just based on the First
Administrative Group name. I am sure if you add the User again to the
permissions list of the calendar with Owner privileges they can modify
the calendar.
 

HTH. 
Regards, 
Raj Periyasamy 
Systems Administrator 
MCSE(Messaging), CCNA 


________________________________

From: Mark Shevill [mailto:Mark.Shevill@xxxxxxxxxxx] 
Sent: Thursday, May 05, 2005 10:06 AM
To: [ExchangeList]
Subject: [exchangelist] Mailbox Migration issues for modifying old
calendar entries


http://www.MSExchange.org/

Hi hope someone can assist    
    I am migrating users from Exchange 5.5 to Exchange 2003 cross site
using exmerge in batch mode. However, I have come across a problem with
calendar entries that were created before the migration of a user took
place. 
 
If a user is on 5.5 and makes creates an appointment in a calendar and
then that user is migrated from 5.5 to 2003, then when that user tries
to amend the entry they are denied access. Looking at the permissions on
the calendar folder for the mailbox where the appointment was placed
which is still on 5.5 then the explicit permission settings of the users
migrated show up as X500 addresses. Adding an X500 address to the
migrated users proxy addresses makes no difference. What I have found
that I need to do is change the default permission to Owner to allow
this to work. 
 
This is not a good solution and I would like some thoughts on a better
one.
 
Thanks
 
Mark Shevill
Mobile: +44 7932 625510
Home Mail: Mark.Shevill@xxxxxxxxxxx
Business Mail: Mark.Shevill@xxxxxxxxx
Web: www.MSCCS.net
 
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
raj.periyasamy@xxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
Mark@xxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
raj.periyasamy@xxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
Mark@xxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: