Hello All, Recently installed Exchange 2007 for a client who was using a simple POP system. Having installed Exchange I went to purchase a certificate and found the client did not own the domain name they were using internally and they wanted to run Office 2007 across the board. Network is quite simple, an old member server running Win 2K3 & ISA2006 and a DC running Win 2K3, SQL 2005 & Exchange 2007. As there was only a single DC (pop mail was on a workstation),I uninstalled Exchange 2007 and renamed the 2003 domain. After reboot checked everything was working OK, users could log on and everything seemed fine. I found the DC was saying it was still in the "old" domain but all network functionsworked fine. DNS had two "trees" one for the old domain and one for the new. Reinstalled Exchange 2007 which completed fine. Ordered the SSL certificate for the new domain and installed that OK. At this point I shot myself in the foot and tweaked the DC configuration so it showed it was in the correct domain using system properties and removed the "old" domain tree from DNS. Setup the administrator account in the Exchange system but could not get OWA to login correctly. Going back to ESM I discovered I was now getting errors accessing elements of the Exchange CAS configuration. I hunted around on the Internet using the error messages from OWA and ESM and the fix seemed to be to reinstall IIS and Client Access. Followed one article to remove IIS and reinstall it, then tried to remove CAS role using add remove programs but got errors about connecting to the exchange server in the old domain name. Trying to add the IIS directories again with cmd scripts but they could not connect to the Exchange server. cmd used was:- get-owavirtualdirectory -server <new FQDN> -DomainController <new FQDN> | ? {$_.OwaVersion -eq "Exchange2003or2000"} | remove-owavirtualdirectory -DomainController <new FQDN> error was:- Get-OwaVirtualDirectory : Exchange server "<FQDN>" was not found. Please make sure you have typed it correctly. At line:1 char:24 + get-owavirtualdirectory <<<< -server <FQDN> -DomainController <FQDN> | ? {$_.OwaVersion -eq "Exchange2003or2000"} | remove-owavir tualdirectory -DomainController <FQDN> I hoped by putting back the DNS treeI removed I would be able to uninstall the CAS, but no joy. The error message did change to one about access denied to IIS virtual directories however. Figured I'd try and recreated all the virtual directories in IIS manually (matched configuration to another E2K7 we have) but still get problems accessing Client Access in ESM or trying to uninstall Client Access. Uninstalling other Exchange roles fails to. I have all the exchange setup logs if they will help. Errors I get in ESM Errors refreshing view in Server Configuration, Client Access are Get-OWAVirtualDirectory Error uable to create IIS directory entry. Error Meessage is Access is Denied. HResult = -2147024891 Get-ActiveSyncVirtualDirectory Error uable to create IIS directory entry. Error Meessage is Access is Denied. HResult = -2147024891 Get-OabVirtualDirectory Error uable to create IIS directory entry. Error Meessage is Access is Denied. HResult = -2147024891 When I click on Recipient Configuration it shows the old domain name in the banner at the top of ESM, however the Organisation Configuration admin accounts all show the new domainname. I attempted to add an additional Organisational Full Administrator and it's looking by default in the old domain for the account. Anyone got any ideas what else I can try to fix my blunder and clean up this mess? Ray

I have this same problem did you ever find a solution or did you have to start from scratch?

I generally don't jump to this conclusion, and would be happy to help with some more technical advice, but based on the single server environment, I think it would be easier to start over than to try to repair the layers of damage. You have certificate issues, messed up IIS, Exchange deployment incompatibilities and other problems related to uninstalling and reinstalling in the order that you did. The good news I do have, is that if you are worried about cost of the ssl cert, you can export it and use it again after the rebuild (this matches the external namespace, right?) Read here about certificates: http://msexchangeteam.com/archive/2007/07/02/445698.aspx but like I said, you have layers of problems and some of which might be irreversible, such as the multiple versions of exchange being installed and uninstalled from a DC.

Jason, what issues were you having? I cant imagine you are truly in the exact same scenario - it seems far to complex.

Oddly enough it is the exact same scenario. We just created a brand new domain offsite and when we brought the servers to the site currently on a workgroup we realized that the domain name 'TLC.local' conflicted with the current fileservers name TLC. Normally we would just rename the other file server but the users are very touchy and on edge about hiring us and we decided to go the domain name change route. Exchange has only been configured with mailboxes and users, but never used in a production environment. We renamed the domain and everything worked fine except exchange giving those IIS errors in Exchange, we figured uninstalling and resinstalling exchange would fix this but we cannot uninstall as a result of the same error, Access is denied with the IIS name still having the old domain name suffix. Bottom line is this is an offsite issue, about a 2 hour drive, we are working off of Dell Remote Access Console and would love it if there was a way around starting from scratch.

This may apply to both of you, but perhaps not the original post, as the entire situation needs more explanation: In short, you cannot rename a domain that has 2007. Answer is to rename it back. http://support.microsoft.com/kb/925822/en-us While potentially confusing, there is nothing wrong with a file server called tlc on a tlc.local domain. It would just read tlc.tlc.local

Mike Crowley said: While potentially confusing, there is nothing wrong with a file server called tlc on a tlc.local domain. It would just read tlc.tlc.local How would the network clients know the difference between trying to access a domain based DFS namespace (eg \\tlc\dfsroot\whatever) vs the server (eg \\tlc\share\whatever), I'd imagine this is a recipie for disaster, or at best, a terrible DFS deployment headache.

Totally agree, its asking for trouble with complex deployments. Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

A Microsoft Doc workaround said " To work around this issue, use Rendom.exe to rename the domain its original name", which is in http://support.microsoft.com/kb/925822/en-us , which may be too late for your case but you may consider. there are lots of docs says" it is not a good idea to rename Doamin, if you have exchange 2007.Some of are1. http://www.petri.co.il/forums/showthread.php?t=264722. http://msmvps.com/blogs/andersonpatricio/archive/2008/02/15/single-label-domain-names-and-exchange-server-2007-sp1-part-2.aspx3. http://www.petri.co.il/forums/showthread.php?p=192171#post192171But having say that, if you have resolved your problem or found a solution to rename windows 2003 domain, with Exchange 2007 is installed, please let me know