Hello everyone,

 

we found a problem after doing swing migration (once to a new hardware, once on the same hardware) and that is that after the migration homeMTA parameter in Active Directory was wrongly set for users that existed before and during the migration.

 

All the users created after the migration are not affected.

 

homeMTA is set to:

CN=Microsoft MTA\DEL:e8b60430-4dfc-4902-8891-6651a6d141c8,CN=Deleted Objects,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix

CN=Microsoft MTA,CN=YourServerName,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=YourOrganization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix

This problem results in Delegates tab in Outlook reporting an error.

ADSIEdit tool from Windows 2003 Support Tools can be used to fix homeMTA parameter for affected users.
 
Microsoft Support Article: http://support.microsoft.com/default.aspx?scid=kb;en-us;199964

 

Hope this helps to someone having the same problem as we did.

 

BTW: Does anybody know if we did something wrong in the swing migrate procedure that could have caused such an error?

Igor,

 

The issue you pointed out is something that I had really only seen for the first time in the last month, and I've seen it a couple of times. I'm trying to determine the exact origin of why this comes up rarely. I will be including documentation on this resolution in the future if I am not able to determine how to prevent the condition.

 

- Jeff Middleton

YCST@SBSmigration.com

Hi,

 

oh I see. Well to me what's interesting here is that we've done the swing procedure only twice and in each case (as mentioned in the first post) we've ended up with this error.

Thats why I've asked if we've done something wrong in the procedure.

Igor,

 

What can I say? If you bring the information to me directly, I'm in a better position to try to analyze this sort of thing. What I can tell you is that 99% of all information I have says this doesn't happen....and yet it is something that I started seeing for the first time in the last 6 weeks.

 

The best i can offer is that I can help with anything that is brought to my attention or that I discover in my own testing, but this is not something that is typical, common, or historical in all experiences I saw in 2005 or 2004.

 

- Jeff Middleton

 

I know this thread is really old, but I have just come across this problem and have not found any solution elsewhere.

 

The Microsoft article referred to in the post is for Exchange 5.5 and 2000. Is it also applicable to Exchange 2003 in an SBS 2003 server?

 

I have found that I can seem to fix it by deleting the users mailbox in Exchange Systems Manager, running the cleanup utility, then using Reconnect to add the mailbox back to the user. This also seems to retain the previous delegate settings.

 

Would this be a valid method to fix things? Or would it create other problems with things such as cached or offline folders? I only have 12 users, so I would be able to do it manually. May be easier than using ADSI Edit.

 

Mark Wilton

Sydney, Australia

My Swing Migration of a little over three years ago also seems to have this issue.  It was only recently reported to me by a client who reported getting Outlook invite bounce backs from a user that left the firm a couple of years ago.  This user was set up as a delegate for the owner and now I cannot get into the owner's delegate tab in Outlook to remove the old user.  Anyone found an easier way to resolve this besides the manual fix or recreating profiles??

 

Edit:  Using the ADSIEdit tool and manually editing the homeMTA variable worked for me.  This was on an SBS 2003 server with a mix of XP Pro SP2 and Win2K SP4 workstations.

Hi Shawn,

 

Did you contact Jeff about this?