Problem after migrating Exchange server 2007 to 2010
I have a problem after I migrated my Exchange 2007 server to 2010.
I have a DC with 2008-64 with Ex2007 on it. I set up a new DC with 2008R and installed ex2010.
I mirgated everything from 2007 to 2010 and deinstalled the ex2007 afterwards. The I moved the roles from the old DC to the new one (except infrastructure master).
Now everything seems to work fine, but in the console of the Excange 2010 server I can only see the old 2008 server as responsible DC (server/client access for example).
How can I change that? I would prefer some powershell command. Because I would like to remove the old DC I have to get in a new one for exchange.
I have a DC with 2008-64 with Ex2007 on it. I set up a new DC with 2008R and installed ex2010.
I mirgated everything from 2007 to 2010 and deinstalled the ex2007 afterwards. The I moved the roles from the old DC to the new one (except infrastructure master).
Now everything seems to work fine, but in the console of the Excange 2010 server I can only see the old 2008 server as responsible DC (server/client access for example).
How can I change that? I would prefer some powershell command. Because I would like to remove the old DC I have to get in a new one for exchange.
did you make the new DB with 2008 a GC
ASKER
Yes I made the new DC a GC.
tspreeth: can you give me examples for the parameters needed?
tspreeth: can you give me examples for the parameters needed?
example:
Set-ExchangeServer -identity Exchangeserver2010 -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’,'newdc2
-StaticGlobalCatalogs ‘newgc.domain.com’, 'newgc1.domain.com’ -StaticConfigDomainControl
Set-ExchangeServer -identity Exchangeserver2010 -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’,'newdc2
-StaticGlobalCatalogs ‘newgc.domain.com’, 'newgc1.domain.com’ -StaticConfigDomainControl
ASKER
I tried to set it like this:
Set-ExchangeServer -identity Exchangeserver2010 -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’
-StaticGlobalCatalogs ‘newdc.domain.com’ -StaticConfigDomainControl
Afterwards I could not connect to the exchange server (on newdc) anymore with RDP and a lot of the exchange services ceased to start. I found out that I had to change this
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="newdc.domain.c
"IsGC"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="newdc.domain.c
"IsGC"=dword:00000001
back to
indows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="olddc.domain.c
"IsGC"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="olddc.domain.c
"IsGC"=dword:00000001
After that everything worked as before, but I still have only the old DC as a reference in the exchange console.
Sorry that it took a little bit to answer, but I had no email for a while :)
Set-ExchangeServer -identity Exchangeserver2010 -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’
-StaticGlobalCatalogs ‘newdc.domain.com’ -StaticConfigDomainControl
Afterwards I could not connect to the exchange server (on newdc) anymore with RDP and a lot of the exchange services ceased to start. I found out that I had to change this
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="newdc.domain.c
"IsGC"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="newdc.domain.c
"IsGC"=dword:00000001
back to
indows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="olddc.domain.c
"IsGC"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM
"HostName"="olddc.domain.c
"IsGC"=dword:00000001
After that everything worked as before, but I still have only the old DC as a reference in the exchange console.
Sorry that it took a little bit to answer, but I had no email for a while :)
you don't want to statically assign the domain controller to exchange
run dcdiag on the new server/dc and post the results
run dcdiag on the new server/dc and post the results
ASKER
My OS language is german, so I think you will have difficutlies with the DCdiag results, but it was a good idea. I already found 2 errors, which I will explore.
danke
there is an option with this tool to fix some issues like DNS
dcdiag /fix
there is an option with this tool to fix some issues like DNS
dcdiag /fix
ASKER
dcdiag /fix did not fix it. The \\dc\netlogon is unreachable and there seems to be a problem with advertising as DC. I think I have a problem with the sysvol share.
yes, you need to look at the logs on the domain controllers
that is definitely outside dcdiag capabilities
that is definitely outside dcdiag capabilities
ASKER
I fixed the problem with the sysvol share, but I still cannot use my new DC for AdAccess.
run the dcdiag again and verify there are no errors
ASKER
No errors so far
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Set-ExchangeServer -Identity <ServerIdParameter> [-StaticConfigDomainContro