• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1534
  • Last Modified:

Exchange 2003 migration to Exchange 2010: Lingering Questions

I migrated from Exchange 2003 to Exchange 2010. Everything seems to be working fine, except I have some lingering questions that I'd like to find answers to before I pull the trigger on decommissioning the 2003 box.

1. When I create a new user and new user mailbox it takes a few days before the user shows up in the Global Address list.  They eventually do show up, but why does it take so long?

2. Warnings are generated in the event logs when I create a new mailbox. This is what I see: Failed to find the address type object in Active Directory for address type "CCMAIL:AMD64".  I have done some reading on this and saw the posts that say to go to ASDIEdit and find "disabledGatewayProxy" and remove them from there, but there is no entry for "disabledGatewayProxy".  If I go into Exchange System Manager on the Exchange 2003 server, I can edit the default Recipient Policy and uncheck CCMAIL and MS. When I do that, then I see the entry in ADSIEdit for "disabledGatewayProxy".  In any case, the warning is generated. I don't think i need either the CCMAIL or the MS email aliases, so how can i get rid of this problem?

3. I went through the procedure of moving all replicas out of the Public Folders on Exchange 2003.  There were a dozen or so of them listed in the "Public Folder Instances" before, and then after I executed the move there was only one left.  It has been 3 days and it is still lingering in there.  How can I get rid of it so I can delete the store? (I think it does say that it is located in the Exchange 2010 Database... not sure why it is still listed in this "instances" folder.)

Thanks,
Mark
0
Ad-Apex
Asked:
Ad-Apex
  • 4
  • 3
1 Solution
 
markpalinuxCommented:
Hi Mark

1. Where are you looking at the GAL? Does it show up on OWA  right away?
Exchange 2010 Management Console, click mailbox, click offline address book. An Exchange 2010 GAL is created on the mailbox , then picked up by the CAS. I would test by manual updates to the address book, I think by default it is once at 4am or something.
Outlook 2010 should get GAL from CAS web interface , outlook 2003 would pull gal from public folders.

2. ADSI edit, in the configuration container
Follow
Option 2: Remove the invalid or unwanted address type from all recipient policies
http://support.microsoft.com/kb/286356

I would suggest ..dumping your ldap config partition to text before just as a before snapshot
ldifde -d cn=configuration,dc=my,dc=domain -f out-ldifde.txt


3. I would dismount then remount the public store then see if the instance still shows.

Mark
0
 
Ad-ApexAuthor Commented:
Thanks for the reply!

1. I was looking in Outlook 2010.  The same problem exists with users in Outlook 2003. When I just checked in OWA it is there. It is definitely taking a couple days in Outlook, though, for all versions.  I'll have a closer look. I did make some changes recently that may have affected this. I'll report back.

2. I'll try option 2 in the link you suggested.

3. I have dismounted it on the 2003 Exchange server and remounted it already and it is still there.  I have not dismounted the 2010 Exchange store, though. I have since powered off the 2003 server (not fully decommissioning it yet) just to see if I ran into any errors. It's been a few days and everything is functioning fine including the shared calendar that was still showing up in 2003's Public Folder Instances (it really does exist on the 2010 server). So that tells me I can probaly just delete the store and not worry about it.
0
 
markpalinuxCommented:

3.
 Before doing so you may try to remove the replica again for that server / folder from both Exchange 2010 and Exchange 2003.
Another attempt to more safely delete it would be to stop the store, rename the pub file and mount the store again. Then try to delete.
After that I would say safe to delete ( only real fear is non-replicated content).
 
You can check the server\folder item count with PFDAVadmin (2003 ) and on the 2010 side Exfolders ( be sure to get the sp1 version)

Did you drag and drop the public folder hierarchy folder to the Exchange 2010 admin group yet?

good list of steps here:
http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/

Hope this helps.
Mark
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
Ad-ApexAuthor Commented:
I have a few updates.  Yesterday I noticed some mail was hung up in the 2010 queue. The affected mail was all being sent to distribution groups and not individual users. As soon as I powered on the 2003 Exchange server these messages went through.

One of the things I hadn't done yet was to update the address lists using the following commands:

Set-AddressList “All Users” –IncludedRecipients MailboxUsers
Set-AddressList “All Groups” –IncludedRecipients Mailgroups
Set-AddressList “All Contacts” –IncludedRecipients MailContacts
Set-AddressList “Public  Folders” –RecipientFilter {RecipientType –eq “PublicFolder”}
 Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact'
-or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass
-eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group'
-or ObjectClass -eq 'publicFolder'))}

I ran those just now, but I am not sure if that was the reason why those messages to a specific distribution list weren't going through.

The only steps I have not yet perfromed in the links you sent me above is to remove the routing group connector and remove the stores on 2003.

0
 
Ad-ApexAuthor Commented:
I figured out the distribution lists problem.  A few of the distribution lists had the old Exchange 2003 server listed as the "expansion server" in the advanced tab for the group's properties.  So before delivering the message, it needed to look at the old sever to "expand" the group members so it could deliver to them.  Since the server was offline, the message was getting stuck in the routing group connector queue.
0
 
markpalinuxCommented:
Also Exchange 2007 and 2010 like to use Universal Groups rather then global groups. I would recommend if you have a single ad domain that you convert global distribution list and mail enabled security groups to universal.

Mark
0
 
Ad-ApexAuthor Commented:
Yes, I noticed that as well when in there looking at all of them for the "Expansion Server" setting.

The old server is now full decommissioned. I deleted the stores,deleted the routing group connectors, and uninstalled exchange fully. Everything appearsto be running very smoothly.

Thanks for the tips!
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now