I V2V a Hyper-V guest in production running Exchange 2007 to ESXi 4.1 last night. Today I discovered that while the exchange works, I am not able to add new organizations and mailboxes to it. Been reading a little about the subject, and if I understand it correctly the SID has been changed, and therefor the trust between the AD and the Exchange server has been broken. It's to me a mystery users are able to use it at all then.
I have no prior experience of setting exchange up, so I'm willing to cross fire in order to get it working without doing a fresh install (using 'setup.exe /M:RecoverServer'?). From what I understand, I have about the following options:
Get old SID from old Hyper V based server and either change SID on the vmware exchange 2007, or change SID for the exchange in the AD. People seem to generally thing this is a world of trouble, but is it doable? I wouldn't be scared to test it out, I can always revert to snapshots of the virtual machine. Other Pros and Cons?
Re-install windows and exchange using the RecoverServer switch. Benefits would be R2 of windows 2008, and getting to know exchange in the process. But I know just a simple replacement of a ssl certificate was a hassle, and apparently we have loads of custom local rules because of the integration with (the now discontinued) DotNetPanel and the hosted exchange nature. To my knowledge, the DotNetPanel server binaries are no longer available, so it would also require us to fully test and then migrate 15 servers to WebSitePanel in production.
Reattach the mailbox databases to the old exchange 2007, and not being able to move from Hyper V on HP MSA hardware. Leave it be, move on and forget? :)
Throw in the towel and either get Microsoft support, or simply invest (a lot) in hiring a consultant.
Edit: The error message when creating a new mailbox is something like "Address list service failed". Will check the exact message when I arrive at work tomorrow. My apologies for not including it.
Edit 2: It's clearly not because of a change of SID, I will move this to a new post instead as the problem is completely unrelated to (a change of) SID. new thread here