Exchange Server 2007 SP1 Woes... 2

[jcrapps]

Hello,
I am having big problems with trying to install SP1 into my current environment.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2496277&SiteID=17

I have one 2003 Server running as a DC. I have a second brand new server running Exchange 2007. Unfortunately, I'm unable to proceed because of my single-labeled domain name (ie. domainname instead of domainname.local). Since Microsoft doesn't want to support single-labeled domain names (even though they gave no warning whatsoever when I first installed Exchange 07 to begin with) I have no choice but to re-configure my domain name. So here is my question:
Will I need to start my DC from scratch, as in reinstall the whole OS and everything? The reason why I ask this is that I know the Exchange 2007 installation totally changes the schema for AD. I was thinking that I could just demote the DC and promote it. The restore AD with ADMT. Then install Exchange 2007 again with the new domain name. Would this work? Or would I have to reinstall the DC's OS from scratch ? Thanks in advance!

 

[ntinlin]

Your DC would be the forest root domain and that domain can't be renamed.

No alternative but to demote and start over I'm afraid.
Can't see how ADMT would be of any help in this instance.

Neill

 

[jcrapps]

Hi Neill, if I can't use ADMT, then what would I use to back up AD so I could restore it for use after the demotion and promotion? Would I need to use ASR? I've never had to re-do a domain name.

 

[jcrapps]

I guess my next question is this. If I backup AD. Then create a new domain with a different name, can I restore the users and computers from the old domain to the newly used domain name or will I have to recreate those users all over again. There are only about 35 users so it isn't too bad to recreate all of them, but I'd like to avoid wasting time.

 

[BobSchleicher]

Some extra reading from Microsoft on this issue.

http://msexchangeteam.com/archive/2008/01/17/447869.aspx

BobSchleicher

 

[ntinlin]

Well spotted Bob.

Seems to be a problem for a lot of people.

As to backing up restoration wouldn't work since the SID of the new domain would be different.

I wonder if you could use ADMT to migrate users to another forest with the new domain name and with SIDHistory enabled.
i.e. Create a new AD infrastructure on a workstation or something temporarily.

Then demote your old DC which would make it a standalone server, join to new domain and repromote.
SIDHistory on the accounts and groups should then allow access to the 'old' files.

No idea if the above would work obviously. I've sort of done a similar thing going from an NT4 resource domain to a W2K domain but whether it would work 2003-2003 I don't know since it didn't involve SIDHistory.

You'd obviously have to dump out all the mailboxes and recreate XC2007 from scratch though and still a lot of work.

Neill

 

[jcrapps]

Hi Bob,
Yes, the Exchange Team has finally acknowledged the issue and we were given hope yesterday! I know that flat labeled DNS isn't smart, but it's something that I inherited so I have to clean up the problem.

ntinlin,
Thank you for your advice. I am planning on creating a new AD infrastructure and will try migrating for testing purposes. I'll look into the SID history thing. Never used it before.

 

[Zelandakh]

Here's a couple of thoughts...

You can't use rendom on a DC with Exchange on it. Well, technically you can but Exchange no longer works

So in your situation I would either:
1. Take out Exchange 2007. New Exchange 2003 on new box. Full migrate. Uninstall Exchange from existing DC. Then use rendom on DC. Then bring Exchange 2007 SP1 into the mix and move to that box for email.
2. PST the emails. Blow the DC and reload it as a DC only without Exchange. New Exchange 2007 SP1. New (temporary) Exchange 2003 box to push the PSTs in.
3. As per 2 but use Outlook if there are not too many staff then you can avoid the Exchange 2003 box.

 

[Knackster]

I too am in the exact same boat.

Microsoft should have not allowed the installation of ex2k7 with sld's in the first place.

Looks like I am going to have to create a new domain and start from scratch.

1. Create new domain with correct domain naming
2. Create trust between the 2 domains.
3. Build new ex2k7 server on new domain.
4. Migrate users to new domain.
5. ( insert stuff about geting mail moved over with exmerge)
6. ???


Does that look like it will work for the 20,000 foot view of things?

Chris
IT Manager
Houston, Texas

 

[Zelandakh]

looks good so far.

 

[Knackster]

It just really frustrates me that M$ allowed us to install ex2k7 with a sld with no way out.

Chris
IT Manager
Houston, Texas

 

[markdmac]

Dismount stores. Verify logs were committed with Eseutil /mh priv1.edb
Eseutil /mh pub1.edb
Make a good backup of Exchange databases.
Remove Exchange.
Rename the domain. (

http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx)

Reinstall Exchange.
Mark databases can be overwritten by restore.
Restore database.
Mount the stores.
Install SP1.

The whole process will take you just a few hours to correct.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Knackster]

Mark,

Unfortunately, once you commit the AD schema changes for ex2k7, you can't go back, so the domain rename will not work unless you can find a way to remove all evidence in the schema of ex2k7.

Chris
IT Manager
Houston, Texas

 

[Zelandakh]

I've not tried it but if you follow Mark's details and at the point of "Reinstall Exchange", if you redo the schema updates then AD ought to update everything.

But I stress that I've not tried.

 

[Knackster]

After rereading Mark's post, I was taking for granted that removing exchange was just removing the ex2k7 server.

Since I also have a ex2k3 currently existing, I presume that I would remove exchange completely from the organisation.


This is also what I have been following over at msexchangeteam.com:

http://msexchangeteam.com/archive/2008/02/15/448140.aspx

I'm going to have to really think this through. If I couldget away with removing exchange completely, reinstalling ex2k3, then think about the domain rename, I'd probably feel alot better about it.


Chris
IT Manager
Houston, Texas

 

[Zelandakh]

Yes - take Exchange out completely but leave AD in place then rendom and reload Exchange and restore from backup.

 

[Knackster]

One more question:

If I do remove exchange from the org, do the domain rename so it is no longer a single label, then reinstall exchange 2k3 and import the mailboxes back, all of the email address will be unaffected correct?

Chris
IT Manager
Houston, Texas

 

[markdmac]

Oddly enough, I posted what I did because we just did this for a customer yesterday.

That was a swing migration to replace an SBS Server. The original domain (which my company did not set up) had a single domain name, we can call it "company". We introduced a new DC into the mix, allowed AD to replicate then took the SBS box off line and seized all FSMO roles onto the new swing server. From there we had no Exchange other than the attributes within AD, but no Exchange tools on the box. The domain rename worked great to make it "company.local" (NetBIOS name remained the same) and we were able to complete the SBS Swing migration with a new SBS box. Once that new SBS box was a DC and FSMO roles were transferred to it, we completed the SBS installaion which includes Exchange. We were then able to restore the database, mark that it could be overwritten by restore and the stores mounted without incident.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Knackster]

Thanks Mark, that's great to hear.

I really inhereted a monster here last year and everything was finally going really well infrastructure wise until ex2k7 bit me.

But, I needed to do a domain rename anyway..... Just now I have to do it sooner than later.

Chris
IT Manager
Houston, Texas