Exchange 2007 Services Hang On Startup AFTER DCPROMO /FORCEREMOVAL
Recently we needed to move a server from one location to another. In preperation we needed to demote it out of being a DC. I have several other DC/GCs in the enviroment so I wasn't too worried if a failure occured.
However, it wouldnt do so gracefully. It kept complaining that it couldnt transmit it's comple data to the other DCs. This was on varying DCs and wasnt spevific to one. Finally, I used a DCPROMO /forceremoval to get it out.
It unjoin the domain, and removed ADDS role, and deleted it from AD on the other servers. and re-joined it to the domain.
Now when it boots exchange is not working., and I get STARTING on many of the services Thank you for all your help in advance!!!
However, it wouldnt do so gracefully. It kept complaining that it couldnt transmit it's comple data to the other DCs. This was on varying DCs and wasnt spevific to one. Finally, I used a DCPROMO /forceremoval to get it out.
It unjoin the domain, and removed ADDS role, and deleted it from AD on the other servers. and re-joined it to the domain.
Now when it boots exchange is not working., and I get STARTING on many of the services Thank you for all your help in advance!!!
That DC is also hosting Exchange?
What errors arr you getting in the event logs?
What errors arr you getting in the event logs?
ASKER
Odeadeal - Thanks for your optimisim.
The DC was also hosting Exchange yes
The current error is that Service Manager - The IMAP client hung on start.
The DC was also hosting Exchange yes
The current error is that Service Manager - The IMAP client hung on start.
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 have tried the FixItNow and it just hangs at Installing
I tried in SAFE mode - it wont run that way
Setup/Recover server... Will that maintain the Mailbox Store?
I tried in SAFE mode - it wont run that way
Setup/Recover server... Will that maintain the Mailbox Store?
ASKER
Also, the DC role is GONE.
I do have a Windows Server Backup from yesterday. Would it be better to just restore the system from that? Will it work seeing how I have removed it from the Domain Controllers group?
I do have a Windows Server Backup from yesterday. Would it be better to just restore the system from that? Will it work seeing how I have removed it from the Domain Controllers group?
ASKER
I have a call in to Microsoft at this point. However, I would like to know if anyone have a resoution. We're a non-profit and would rather not spend $259.00if we dont have to.
I think your organization didn't validate or did consultation. There is case when people don't do proper study & things are setup & later on it creates a big issue.
The option i can think of you install other server, remove exchange completely from dc & on other server install Exchange server 2007.
There is more demerit for exchange as messaging is business critical application.
The proper method to dc with exchange server installed id first remove exchange server then remove DC role using dcpromo.
I'm afraid little can be done but if your Ad is working fine, take backup of mailboxes & reinstall exchange on new server.
Refer the link below, why Exchange 2007 is not recommended on DC.
http://theessentialexchange.com/blogs/michael/archive/2008/03/29/exchange-server-2007-and-domain-controllers-a-summary.aspx
The option i can think of you install other server, remove exchange completely from dc & on other server install Exchange server 2007.
There is more demerit for exchange as messaging is business critical application.
The proper method to dc with exchange server installed id first remove exchange server then remove DC role using dcpromo.
I'm afraid little can be done but if your Ad is working fine, take backup of mailboxes & reinstall exchange on new server.
Refer the link below, why Exchange 2007 is not recommended on DC.
http://theessentialexchange.com/blogs/michael/archive/2008/03/29/exchange-server-2007-and-domain-controllers-a-summary.aspx
ASKER
I have to tell ya this issue isn't unrecoverable at all in Exchange 2007 or Server 2008. Believe it or not it was pretty simple. I called Microsoft and then I had 2 hours to find the issue, before they called and I would get charged. I found the soloution.
Here is the way to resolve this. When you demote a DC it will unjoin the domain (at least in Server 2008). Even once your re-join the domain you still have to make sure adjustments as the rights that used to be there for that computer account arent there any longer.
Make sure that the computer in Active Directory Users and Computers has all the rights it needs.
In this case I added the server to have Domain Admin, and all groups relating to Exchange. Once rebooted the server's services stared without incident.
The bottom line is to ensure your server has the same rights as it had before.
Another thing you need to check is to make sure that the Exchange Information Store services start on boot. If they don't typically you can start it manually, and find the registry fix for this easily on-line. .
Here is the way to resolve this. When you demote a DC it will unjoin the domain (at least in Server 2008). Even once your re-join the domain you still have to make sure adjustments as the rights that used to be there for that computer account arent there any longer.
Make sure that the computer in Active Directory Users and Computers has all the rights it needs.
In this case I added the server to have Domain Admin, and all groups relating to Exchange. Once rebooted the server's services stared without incident.
The bottom line is to ensure your server has the same rights as it had before.
Another thing you need to check is to make sure that the Exchange Information Store services start on boot. If they don't typically you can start it manually, and find the registry fix for this easily on-line. .
ASKER
Tqtran,
Thanks for not automatically saying "You screwed your Exchange server" as a resolution. I feel your answer was exceptional.
I have to tell ya this issue isn't unrecoverable at all in Exchange 2007 or Server 2008. Believe it or not it was pretty simple. I called Microsoft and then I had 2 hours to find the issue, before they called and I would get charged. I found the soloution.
Here is the way to resolve this. When you demote a DC it will unjoin the domain (at least in Server 2008). Even once your re-join the domain you still have to make sure adjustments as the rights that used to be there for that computer account arent there any longer.
Make sure that the computer in Active Directory Users and Computers has all the rights it needs.
In this case I added the server to have Domain Admin, and all groups relating to Exchange. Once rebooted the server's services stared without incident.
The bottom line is to ensure your server has the same rights as it had before.
Another thing you need to check is to make sure that the Exchange Information Store services start on boot. If they don't typically you can start it manually, and find the registry fix for this easily on-line. .
Thanks for not automatically saying "You screwed your Exchange server" as a resolution. I feel your answer was exceptional.
I have to tell ya this issue isn't unrecoverable at all in Exchange 2007 or Server 2008. Believe it or not it was pretty simple. I called Microsoft and then I had 2 hours to find the issue, before they called and I would get charged. I found the soloution.
Here is the way to resolve this. When you demote a DC it will unjoin the domain (at least in Server 2008). Even once your re-join the domain you still have to make sure adjustments as the rights that used to be there for that computer account arent there any longer.
Make sure that the computer in Active Directory Users and Computers has all the rights it needs.
In this case I added the server to have Domain Admin, and all groups relating to Exchange. Once rebooted the server's services stared without incident.
The bottom line is to ensure your server has the same rights as it had before.
Another thing you need to check is to make sure that the Exchange Information Store services start on boot. If they don't typically you can start it manually, and find the registry fix for this easily on-line. .
read more
http://theessentialexchange.com/blogs/michael/archive/2007/11/13/exchange-server-2003-and-domain-controllers-a-summary.aspx
best
ocd