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.
LVL 6
mkuehngoeAsked:
Who is Participating?
 
mkuehngoeConnect With a Mentor Author Commented:
Ok I found the solution here:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_25151912.html

"The solution to this problem ended up being enabling IP v6 on my exchange server running windows 2008 and then disabling it through the registry....LEAVING IT ENABLED IN THE TCP/IP properties.

That seemed to clear up issues and it started to keep new dc.domain.com in the GC and DC fields of exchange."
0
 
tspreethCommented:
the command for that is

Set-ExchangeServer -Identity <ServerIdParameter> [-StaticConfigDomainController <String>] [-StaticDomainControllers <MultiValuedProperty>] [-StaticExcludedDomainControllers <MultiValuedProperty>] [-StaticGlobalCatalogs <MultiValuedProperty>]
 
0
 
endital1097Commented:
did you make the new DB with 2008 a GC
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
mkuehngoeAuthor Commented:
Yes I made the new DC a GC.
tspreeth: can you give me examples for the parameters needed?
0
 
tspreethCommented:
example:
Set-ExchangeServer -identity Exchangeserver2010  -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’,'newdc2.domain.com'
 -StaticGlobalCatalogs ‘newgc.domain.com’, 'newgc1.domain.com’ -StaticConfigDomainController ‘newdc.domain.com’, ‘newdc1.domain.com’
0
 
mkuehngoeAuthor Commented:
I tried to set it like this:
Set-ExchangeServer -identity Exchangeserver2010  -DomainController newdc.domain.com -StaticDomainControllers ‘newdc.domain.com’
-StaticGlobalCatalogs ‘newdc.domain.com’ -StaticConfigDomainController ‘newdc.domain.com'
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\CurrentControlSet\services\MSExchange ADAccess\Profiles]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default\UserDC1]
"HostName"="newdc.domain.com"
"IsGC"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default\UserGC1]
"HostName"="newdc.domain.com"
"IsGC"=dword:00000001

back to

indows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default\UserDC1]
"HostName"="olddc.domain.com"
"IsGC"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange ADAccess\Profiles\Default\UserGC1]
"HostName"="olddc.domain.com"
"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 :)
0
 
endital1097Commented:
you don't want to statically assign the domain controller to exchange

run dcdiag on the new server/dc and post the results
0
 
mkuehngoeAuthor Commented:
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.
0
 
endital1097Commented:
danke
there is an option with this tool to fix some issues like DNS
dcdiag /fix
0
 
mkuehngoeAuthor Commented:
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.
0
 
endital1097Commented:
yes, you need to look at the logs on the domain controllers
that is definitely outside dcdiag capabilities
0
 
mkuehngoeAuthor Commented:
I fixed the problem with the sysvol share, but I still cannot use my new DC for AdAccess.
0
 
endital1097Commented:
run the dcdiag again and verify there are no errors
0
 
mkuehngoeAuthor Commented:
No errors so far
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.