Exchange 5.5 to 2k3 Migration 4

[fatboy1271]

Hi All,

We currently have five 5.5 Exchange servers that we want to migrate over to 2003. I am working with the ADC Tools right now: Steps 1-3 run fine; however, step 4 tells me

"Pass 1 of 2: Active Directory Connector Object Replication Check validation (objects processed: 825)
Active Directory Connector Object Replication Check completed. No unreplicated objects found.
Pass 2 of 2: Active Directory Object Replication Scan validation (objects processed: 838)
Warning: Active Directory still contains objects that are not replicated to the Exchange 5.5 directory. If you have just run Connection Agreement Wizard, allow time for directory replication to complete, and then rerun the verification task in Step 4. Otherwise, run the Connection Agreement Wizard.
Finished verifying the results of the ADC Tools."

I've been searching online on how to understand the various files that ADC creates (ntObjectCheck.xml, adcObjectCheck.xml, and NtdsNoMatch.xml) and have found nothing. It looks to me like the offending "object" would be found in ntObjectCheck.xml, but the file doesn't make any sense to me. I have limited knowledge in Exchange...

If someone who knows what to look for would be willing to look at a file, I could email it to them.

Any help/suggestions are greatly appreciated,
Patrick

 

[Burninator]

Hey Patrick,

If there is one bit of advice I will give you when upgrading from E55 to E2K3, is to take your time and do things right.

Below is a few bits of information which will help you understand whats happening. Including the ADC whitepaper, nevermind its for Exchange 2000, it still applies, and does the same thing in Exchange 2003.

Give the replication time to complere. ANd read the following articles.

Understanding and Deploying Exchange 2000 Active Directory Connector

http://www.microsoft.com/technet/prodtechnol/exchange/2000/library/udadc.mspx

Common Mistakes When Upgrading Exchange 5.5/2000 To a Exchange 2003

http://support.microsoft.com/?scid=kb;en-us;555262&spid=1760

LAter
Jay

 

[strongm]

>take your time and do things right

Couldn't agree more

 

[fatboy1271]

Thanks guys for the input... Do you know what would be causing this from BadResourceMailboxes.xml:

<?xml version="1.0" encoding="utf-16" ?>
- <NTDSNotMatched gc="FILESERVER" date="200504151440">
- <Objects>
- <object>
<ldapDN>CN=User Name,CN=Recipients,CN=DOHRING,CN=Users,DC=dohring,DC=com</ldapDN>
<Extension-Attribute-10 />
<ObjectGuid>A956D423B4473146AFF738DFEF8F8923</ObjectGuid>
<LegacyExchangeDN>/o=The Dohring company/ou=DOHRING/cn=Recipients/cn=ShellyG</LegacyExchangeDN>
<msExchHomeServerName>/o=The Dohring Company/ou=DOHRING/cn=Configuration/cn=Servers/cn=EXCHSRV</msExchHomeServerName>
</object>

There are six entries like this. On four of them there is a weird entry in the permissions: DOHRING\ADC_CFJKSGOAWRYSAXOQ... they seem to be random characters after the ADC_

I thought I would just remove that entry, but figured it best to ask about it first.

 

[fatboy1271]

Sorry, I should have looked before posting that last one... they are "Disabled Windows user account"(s). I don't understand why this would be in her permissions, unless it was maybe someone who has been removed from the system...?

 

[fatboy1271]

As far as I am concerned, this thread is closed... I have solved my issues and can now create and move mailboxes with the new Exchange 2003 server

 

[DColcl]

Thanks, Jay for the post..... and here's your star!
I have just now finished upgradeing NT4 to 2k3 AD. Next step will be to upgrade the Current NT4/Exchange 5.5 to Win2k and Exchange 2k3 server. After that, I will be migrating that exchange database to an entirly new server and 86'ing the old exchange server..........
..... and I'm skeered....LOL.

My Dream: copy the 16k Exchange 5.5 database to anohter server. Then remove that old server. Then, place the brand new server on the network with the exact same name and IP address as the older one. Install Exhcnage 2k3 on it. Then, as you would for a .pst file in Outlook, migrate in the old exchange database. <sigh> it it could ONLY be that simple....

Well, wish me luck. And thank you.

Dan

 

[fatboy1271]

Umm... yeah, if only it were that simple. I hope that you are joking about how you're going to approach this, because you should be skeered. It was a very long and drawn out process for me.

 

[DColcl]

yeah, I'm joking.
What I have done so far is to upgrade the network to AD. Next I will upgrade the old server to Windows 2k. Once completed, I will upgrade Exchange 5.5 to Exchnge 2k3. Oh, btw, now that we are on AD, I have added the NEW & powerful server to the network.

Now, here is where I'm a bit fuzzy. I need to migrate that Exchange server to a NEW server that has a lot of Umph. This is where I'm having an issue. So I install Exchange 2k3 on that computer as well? Will there not be a licencing issue since I've only got one copy of Exchange 2k3?

<sigh>.

 

[fatboy1271]

I'm not sure about the licensing issue, but that is a great question... you may want to call M$ and ask them if it's ok till you get the migration completed. ---> I just reread what you wrote; if you are migrating from 5.5 to 2k3 what is the licensing issue?

You will want to run through the Exchange Server Deployment Tools before installing the new Exchange. Do a search on M$ downloads page for the Service Pack that is out for it. Go through those steps, which will find all of the problems that you will face and help you sort out how to get it ready for the migration. Also get SP1 for Exchange 2k3.

Once you start working on that and you run into things you can't sort out, let me know

 

[NetworkDOC]

THe licing will be fine during an upgrade. I checked with microsoft and they told me that when used during an upgrade it is ok. I am sure there is a reasonable time limit though. Rememeber you can even down load an eval copy for 90 days or so.

 

[DColcl]

wow! Thank you BOTH for that information! I will the same Exchange on both the old server(that is going to be upgraded) and the new server (that the uprgaded Server will be migrated to). After all is said and down, the old, upgraded server will be erased and made into a testing platform using its original software.

And thank for the Deployment tools. I'm going to look those up on the Microsoft's website today, download it, and begin my review.....

... and here's a star for the both of you.

THANK YOU!

Danny