There's a lot of history here (including paying Microsoft to help change the domain name for a domain with 2008R2 servers and Exchange 2010 - we're having problems as you can imagine. Having gone through this, I can't even believe they agreed to attempt this.), but suffice it to say SP1 won't install on our Exchange 2010 server as it still is trying to find the server at the old domain name. I wish I knew where the old domain name/Exchange server name is hiding - I've been all through ADSI and the registry and found nothing. I'm at the point where I'm going to blow away the entire domain, rebuild the Exchange server, and restore the old database. My question is, what is the best way to get the mailboxes back? Is it as simple as reassiciating a mailbox to a user account? I'm not sure what information is maintained in the Exchange database, but there won't be any references to the old domain, will there? I've read about potential internal mail flow problems when the mailboxes are reassociated, but I don't follow the reason why. Can anyone shed some light on this? Thanks

There's a lot of history here (including paying Microsoft to help change the domain name for a domain with 2008R2 servers and Exchange 2010 - we're having problems as you can imagine. Having gone through this, I can't even believe they agreed to attempt this.), but suffice it to say SP1 won't install on our Exchange 2010 server as it still is trying to find the server at the old domain name. I wish I knew where the old domain name/Exchange server name is hiding - I've been all through ADSI and the registry and found nothing. Can you post the error message you get?Jesper Bernle | Blog: http://xchangeserver.wordpress.com

This is a virtual server, and unfortunately I didn't grab the error message when it occurred as I was thinking at the time I'd just grab it off the logs. I had to roll back to the snapshot, so unfortunately the log no longer exists. Essentially, the Exchange 2010 SP1 upgrade errored out saying it couldn't find exchange.olddomain.com, and this occurred right after the installation said it removed the old Exchange files and installed the new Exchange files - I think at the hub transport upgrade. Just FYI, after changing the domain name, with the Exchange Management Console, the Microsoft Exchange On-Premises still showed the old server name, so I change it to point to the new. Even after that, I wasn't able to manage mailboxes or the Exchange server because it is still trying to find the old Exchange server: "Unable to find 'exchange.olddomain.local' computer information in domain controller 'exchange.olddomain.local' to perform the suitability check. Verify the qualified domain name. It was running the command 'Get-OrganizationConfig'." In the Management Console, I had to add a new Exchange Forest and point it to the new FQDN of the Exchange server, so between the old Exchange forest and the new, I can manage Exchange. However, neither of these can manage all of the Exchange functionality. This Exchange server is also a DC.

It sounds like some steps were skipped to clean up Exchange after the domain rename. I'd highly recommend against a full rebuild, it can be avoided by properly fixing the current domain. Take a look at this article as it relates to Exchange. You may still be able to save this by using the Exchange Domain Rename Fix-Up tool. http://www.google.com/url?sa=t&source=web&cd=3&ved=0CCQQFjAC&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2Fc%2Ff%2Fc%2Fcfcbff04-97ca-4fca-9e8c-3a9c90a2a2e2%2Fdomain-rename-procedure.doc&rct=j&q=domain%20rename&ei=FUKTTY7hGdKz0QHfrPzMBw&usg=AFQjCNHyCOlZiesTsNb_MYrxhhv829FY5w&sig2=gkeXk41tNnZpnRAlfoNhvg Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

I will start going through this, and I really appreciate the information. What I find odd is that this domain rename was escalated up the Microsoft chain, and I was told there was nothing else that could be done. They ended up refunding my money, because at the time, I couldn't manage anything within Exchange. I'll try to get through this today and tonight and post the results. Thanks very much.

Yeah, it is a little odd, I have run through this process a few times. Anyway, good luck and let me know how it goes! Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

I went through the document you referenced, and I recall doing the bulk of this. I knew at the time this was possible for Win2K3 and Exchange 2K3, but the guys at MS said this was the first one for Win2K8R2 and Exchange 2010. However, there isn't an Exchange 2010 Domain Rename tool from what I can find, although I know we did somethings within Exchange - don't recall what, though, as it was too long ago. I do recall performing various tests with the Microsoft AD engineer, and he said the domain was healthy. I dealt with MS engineers on both the AD and Exchange sides, and they were occasionally conferenced in together. I've already mentioned I've searched for the old domain name in ADSI, registry, and even within all files on the server, but I don't get a single hit.

If you look here: Exchange and Domain Rename Operations you see that there is a tool (XDR-fixup.exe) that should be run after a domain rename operation to fix some left over issues with Exchange. But one of its requirements is that Exchange isn't installed on a Domain Controller and there's your big ooops I think. So, I'm leaning towards your first comment regarding this and rebuild the whole thing. FOr the Exchange mailboxes, I'd export them to PST-files and later on import them into your new shiny and functional Exchange.Jesper Bernle | Blog: http://xchangeserver.wordpress.com

I feel pretty certain we used this, but I can always create a snapshot and try again. I think there was a compatibility issue with 2010. I'll post how this goes tonight. Thanks

I forgot to add we had demoted the Exchange server prior to the domain renaming.

I forgot to add we had demoted the Exchange server prior to the domain renaming. You mean uninstalled, or?!Jesper Bernle | Blog: http://xchangeserver.wordpress.com

No. The thread took a turn back to the original domain rename. Before we started the process of domain renaming last summer, we demoted it, renamed the domain, and eventually repromoted it. I've been presented with an option to check out prior to uninstalling Exchange in order to clean up all the Exchange attributes.

Any luck with your testing? Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

I've decided to wait until Friday night. The backups run until 9:00, and I want more time to spend on this than a week night.

I hear ya, good luck. I'll be anxiously waiting for good news come Monday morning! Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

I didn't mark this as an answer, and I'm as certain as I can be this does NOT work with Exchange 2010.