?
Solved

Problem after migrating Exchange server 2007 to 2010

Posted on 2010-09-07
14
Medium Priority
?
557 Views
Last Modified: 2012-05-10
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
Comment
Question by:mkuehngoe
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
  • 2
14 Comments
 
LVL 2

Expert Comment

by:tspreeth
ID: 33617023
the command for that is

Set-ExchangeServer -Identity <ServerIdParameter> [-StaticConfigDomainController <String>] [-StaticDomainControllers <MultiValuedProperty>] [-StaticExcludedDomainControllers <MultiValuedProperty>] [-StaticGlobalCatalogs <MultiValuedProperty>]
 
0
 
LVL 32

Expert Comment

by:endital1097
ID: 33617087
did you make the new DB with 2008 a GC
0
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33617774
Yes I made the new DC a GC.
tspreeth: can you give me examples for the parameters needed?
0
Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

 
LVL 2

Expert Comment

by:tspreeth
ID: 33618304
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
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33624872
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
 
LVL 32

Expert Comment

by:endital1097
ID: 33626770
you don't want to statically assign the domain controller to exchange

run dcdiag on the new server/dc and post the results
0
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33628301
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
 
LVL 32

Expert Comment

by:endital1097
ID: 33628356
danke
there is an option with this tool to fix some issues like DNS
dcdiag /fix
0
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33628465
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
 
LVL 32

Expert Comment

by:endital1097
ID: 33628531
yes, you need to look at the logs on the domain controllers
that is definitely outside dcdiag capabilities
0
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33646567
I fixed the problem with the sysvol share, but I still cannot use my new DC for AdAccess.
0
 
LVL 32

Expert Comment

by:endital1097
ID: 33646589
run the dcdiag again and verify there are no errors
0
 
LVL 6

Author Comment

by:mkuehngoe
ID: 33646736
No errors so far
0
 
LVL 6

Accepted Solution

by:
mkuehngoe earned 0 total points
ID: 33648053
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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question