OK, so in my infinite stupidity, i made a big mistake. I was setting up the VMs for a branch office. To save time i cloned them from one install. And, i forgot to click the box that said 'Create new SID'. I neglected to notice this until after i got Exchange 2007 installed. The install was normal and the server functioned, even communicating with a sister server in another domain in the forest. Bu then wierd things started to happen. I discovered the duplicate SID on the file server first. And then checked the others. But basically, the file server, the exchange server, and the domain controller all ended up with the same SID. I have used sysinternals newsid to change the SID on both the file server and the exchange server. I left the DC with the original SID. Now, on the exchange server,I get an error 5513 'The computer xxxx tried to connect to the server \\dc using the trust relationship established by the domain. However, the computer lost the correct security identifier when the domain was reconfigured. Reestablish the trust relationship'.Can i unjoin an established exchange server from the domain and rebind it without screwing up exchange? If not, is there a way to reestablish the trust relationship without screwing up exchange?

Hi, I suggest you recover Exchange 2007 server by reinstalling a new Windows Server. For more detailed steps, you can refer to following article Recovering an Exchange 2007 Server using the RecoverServer switch http://www.msexchange.org/tutorials/Recovering-Exchange-2007-Server-RecoverServer-switch.html Mike

So is this the only option? I have a current support ticket in with MS for an Outlook Anywhere issue. I have brought this to their attention. I just want to know if there are any other options for resetting the security trust with the domain, without screwing up exchange. If i do this, i assume that i will have to have my SSL recreated (at cost). Also, can i just copy the existing mailbox database over and remount it to the new server?

Hi Russell I do not think disjoin and rejoin the Exchange Server to domain is able fix the issue without screwing up exchange. Please understand that Exchange configuration information is saved in the AD. Therefore, the recommended method is to create a new server with same name as original server, reset computer account, rejoin the server to domain and install Exchange Server by using /RecoverServer. Regarding the question can i just copy the existing mailbox database over and remount it to the new server, I think that you are able to copy the mailbox database and mount it on new server. For your reference: Database Portability http://technet.microsoft.com/en-us/library/bb123954.aspx Mike

Hi Russell,Any updates regarding the problem?Mike

Thank you for your help. I had a service ticket open with Microsoftfor a problem with the Outlook Anywhere feature. When i advised them of this issue, the tech consulted some windows techs and lab tested a solution. We ended up unjoining and then rejoining the Exchange server to the Domain. This worked well. The only hitch we had is that i had to remove and reinstall my UC certificate. After that, the Exchange server and all services started behaving normally. I learned a valuable lesson. Always make sure that you have unique SIDs when cloning machines to deploy them quickly. This will be burned into my brain for a long time.Once again, thank you for your assistance.

Hi Russell, Thanks for your response and I am glad to know that the issue could be solved. In addition, would you please share your solutionwithdetailed steps here in case other customers have same requirement? Thanks,Mike