asked on Exchange 2010 wont recognise Domain Controllers
I have been involved in a server migration from SBS 2003 to Windows Server 2008 r2, Exchnage 2003 to Exchange 2010
Everything seemed to be going well until we got to the stage of turning off the SBS server.
It seems for some reason that its not recognising itself as a domain controller. There should be a 2nd server in that attachment image called fileserver.
I have not been able to get it to show up at all. so everytime I turn off the SBS server I am unable to access the exchange console and mail stops working
Any ideas?
domaincontrollers.jpg
Everything seemed to be going well until we got to the stage of turning off the SBS server.
It seems for some reason that its not recognising itself as a domain controller. There should be a 2nd server in that attachment image called fileserver.
I have not been able to get it to show up at all. so everytime I turn off the SBS server I am unable to access the exchange console and mail stops working
Any ideas?
domaincontrollers.jpg
Active DirectoryWindows Server 2008Exchange
Last Comment
Manpreet SIngh Khatra
Have you removed Exchange from the SBS server?
If not then that will cause problems. When Exchange is installed on a DC, it is the ONLY DC that all Exchange servers will use. You need to remove Exchange from that DC and ensure that you have another DC with the global catalog role enabled. Once you have done so then you can restart the Exchange services on the new server and it will pick up other domain controllers.
Simon.
If not then that will cause problems. When Exchange is installed on a DC, it is the ONLY DC that all Exchange servers will use. You need to remove Exchange from that DC and ensure that you have another DC with the global catalog role enabled. Once you have done so then you can restart the Exchange services on the new server and it will pick up other domain controllers.
Simon.
ASKER
- Rancy, the new server is Server 2008 r2 sp1
- Sembee2, No I have not removed it from the old server yet, I was hoping to make sure it was working correctly on the new one first. I am a bit cautious about removing it from the SBS server in case I do and the new one still doesn't work. I have another DC with GC already.
- Sembee2, No I have not removed it from the old server yet, I was hoping to make sure it was working correctly on the new one first. I am a bit cautious about removing it from the SBS server in case I do and the new one still doesn't work. I have another DC with GC already.
You are stuck then - as until you remove Exchange from the old server, the other server will not use any other domain controller.
Simon.
Simon.
ASKER
Process MSEXCHANGEADTOPOLOGYSERVIC
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
main.*****.local CDG 1 7 7 1 0 1 1 7 1
FILESERVER.*****.local CDG 1 0 0 1 0 0 0 0 0
DC1.*****.local CDG 1 7 7 1 0 1 1 0 1
Out-of-site:
Fileserver is the new exchange server
main is the old exchange server
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
main.*****.local CDG 1 7 7 1 0 1 1 7 1
FILESERVER.*****.local CDG 1 0 0 1 0 0 0 0 0
DC1.*****.local CDG 1 7 7 1 0 1 1 0 1
Out-of-site:
Fileserver is the new exchange server
main is the old exchange server
It has found it, but it will not use it for the reasons I have given above.
You installed Exchange 2010 on to a domain controller?
Simon.
You installed Exchange 2010 on to a domain controller?
Simon.
ASKER
Yes it was, as it will be taking over as the only server on site, the 3rd is just a temp domain controller that wont be staying
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
- Rancy