SINC_dmack
asked on
Exchange 2010 services not starting after creating second server with same name
We have an Exchange '10 Server called EXCH10. In preparation for migrating to Exchange '13, I created a new VM, intended to be called EXCH13. I joined it to the domain and then realized that I had mistakenly named it EXCH10 as well. I changed its name to EXCH13 and that's where I left it for the day.
A few hours later, I was notified that users couldn't connect to Exchange. I connected to EXCH10 but couldn't log in--I got a trust relationship error. I logged in as the local administrator account and found that the Exchange Transport Service wasn't running. I removed the server from the domain, rebooted, and then readded it. (The removal and readding processes each took close to 10 minutes after I entered the domain credentials.) After the reboot, about half of the Exchange services wouldn't start.
I removed EXCH10 and EXCH13 from the domain again and "reset" their accounts in ADUC. I then joined them back to the domain. That had no effect--the same services won't start. I'm guessing that something is messed up with the SID but am not sure what to do next. Please advise.
A few hours later, I was notified that users couldn't connect to Exchange. I connected to EXCH10 but couldn't log in--I got a trust relationship error. I logged in as the local administrator account and found that the Exchange Transport Service wasn't running. I removed the server from the domain, rebooted, and then readded it. (The removal and readding processes each took close to 10 minutes after I entered the domain credentials.) After the reboot, about half of the Exchange services wouldn't start.
I removed EXCH10 and EXCH13 from the domain again and "reset" their accounts in ADUC. I then joined them back to the domain. That had no effect--the same services won't start. I'm guessing that something is messed up with the SID but am not sure what to do next. Please advise.
ASKER
The other thing I was considering was removing EXCH10 from the domain, deleting its computer object in ADUC, and then joining it back to the domain so that the account is recreated. I've done that in the past with workstations with no problems, but I'm not sure what the ramifications would be of deleting an Exchange-enabled computer account.
The Application Log is riddled with Exchange-related Active Directory authentication errors.
The Application Log is riddled with Exchange-related Active Directory authentication errors.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I sent some test emails via OWA and they got hung in the drafts folder. I did some research and found an article talking about it being a SID issue. However, none of the devices should be sharing SIDs--each VM was created from scratch--so I disregarded it.
I ran the Exchange BPA and it threw an error about EXCH10 not being a member of Exchange Trusted Subsystem group, so I added it to that group. I then restarted the Exchange Submission service. After doing so, OWA emails seem to be delivered immediately, rather than being hung up in the Drafts folder.
I ran the Exchange BPA and it threw an error about EXCH10 not being a member of Exchange Trusted Subsystem group, so I added it to that group. I then restarted the Exchange Submission service. After doing so, OWA emails seem to be delivered immediately, rather than being hung up in the Drafts folder.
ASKER
Solved it by myself. (If "by myself" can include extensive Googling.)
ASKER
I have a backup of the domain controller and EXCH10 from two nights ago. Can I back up the mailbox store from EXCH10, then restore the DC and EXCH10 to pre-broken status, and then import the mailbox store? (There is no other data being stored on the DC or EXCH10, so as long as I can save the mailbox store, I should hopefully be safe overwriting them.)