Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 560
  • Last Modified:

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.
0
mkuehngoe
Asked:
mkuehngoe
  • 7
  • 5
  • 2
1 Solution
 
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
 
mkuehngoeAuthor Commented:
Yes I made the new DC a GC.
tspreeth: can you give me examples for the parameters needed?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
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
 
mkuehngoeAuthor 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

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 7
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now