Win2003 AD Upgrade Effect to Exchange 2007 Sp2
hi we had win 2003 Domain and Exchange 2007 enviroments, recently we upgrded our Domain to Win 2008 R2( before that we install Excahnge 2007 SP2 ). after move all roles every thing, we are facing issues with exchange Server. Domain controller are working find , but when we shutdown Old Win 2003 Domain Controller( which was holding all roles - now we haev move to win 2008 Servers). Exchange will stop working. as i found from the web http://blogs.msdn.com/b/keithmg/archive/2009/01/06/exchange-topology-discovery-failed-error-0x80040a02-dsc-e-no-suitable-cdc.aspx will add Excahnge Servers to domain admin group. is their any other things to be done from exhchange side. we didn't touch excahnge server and they still running on win 2003 EE -64 bit server. we change the DNS IP address to new DC only. do we have to do any thing with IPV6 . Thank you Indunil
December 5th, 2010 1:26am

are the new win 2008 servers GCs? make sure that exchange is able to find a GC when server 2003 is off, try to manually start the exchange services and see what errors you get.MCSE | MCITP - Server 2008 | MCITP - Exchange 2007 | MCTS - Exchange 2010
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 2:08am

yes all new Win 2008 R2 Domain controler are GC. on exchange Server, we have put first DNS as New win 2008 R2 DC, and secound as win 2003 DC. new DC & old exchange Server are in same subnet and same site. it's seems All DC are workign fine. only once we shutdown Old DC( other old DC can shutdown, but DC which was holding FMSO Roles can't shutdown - now all FMSO role are in win 2008 R2 DC) Exchange give these event errors: Event ID : 2102 , 2114 , 2103 , 4001 , 1022 , 8365 , 9662 , 9154, 8364, 7200) as i found , it's not recommeded to add domain admin group. aslo there are few comments for run Exchange setup.exe /domainprep and add to auditing and security logs. not sure will resolved issues. is there any workaround to resolve this issues. hope this is commen issue(Upgrade Win2003 Ad to Win 2008 R2 in Exchange 2007 enviroment) Indunil
December 5th, 2010 2:36am

try two things 1. in EMC - Org Config --> set the Modify Configuration Domain Controller see if it works then check what you see here 2. In EMC - Server Config - Properties for each exch server and see if you see all DCs listed in System Settings. if nothing works try setup /prepareAD on a new DC/GC MCSE | MCITP - Server 2008 | MCITP - Exchange 2007 | MCTS - Exchange 2010
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 2:50am

hi Here thanks for reply. i belive this will work, cos in EMC-Server Config -(Cluster Server name has only old win 2003 Domain Name -which was causing to issue. hope after modifiy configuration domain controller setting from EMC--Org Confi, new server will come automalically. if it's not come , hope it's okay to add manualy new DC to system Settings . i have to wait for 4-6 hours . cos i have to do these changes after office hours. anyway will check and confirm in eveing. thanks for valuable help . Indunil
December 5th, 2010 3:03am

Check for the events like 2080 and 2081 in the eventviewer.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 7:36am

hi all after change the domain controller setting from EMC. we can't move exchange service to secound node. it's give this error. Event ID 2141 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1716). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. secound node still trying to connect old win 2003 DC( event ID 2080 say it's try to connect old win 2003 DC ) and give Event ID 2141 Error Indunil
December 5th, 2010 9:09am

HI All if some one can give some solution for this issues. that would be greate. here is the setup details Old Enviroment( Main Site) ------------------------------------------------------------------------------------------------------------------- Win2003SE---- FSMO roles hold( forest funcational Level win2000, domain funcational level 2003) Win2003R2---Additional DC ABCMXB1---Exchange 2007 Mail Box Node 1( win 2003 R2- 64 bit ) ABCMBX2--Exchange 2007 Mail Box Node 2( win 2003 R2- 64 bit ) EXMBX -- cluster 2 Servers for HUB/CAS Server with NLB DR Win2003DR--Addional DC DRMBX --- Exchange Mail Box for DR DRHC - DR Hub CAS Servers ---------------------------------------------------------------------------------------------------------------------------------- 1: upgrade Exchange 2007 SP2( to support Win 2008 R2 Domain ) 2: move forest funcational Level win 2003 3: moved FMSO to Win2003R2( didn't allow to upgrade schema from Win2003 Server, then move roles to win2003R2 and succefull upgrade schema) 4: Add Win2008 R2 Addicational DC to domain.(win2008R2) 5: add another Additional DC to DR Site ( win2008DR) 6: move all role so Win2008R2 7: change Bridge Head Server to Win 2008 Servers 8: change Exchange Domain Controller ( EMC- Org Config-- Modify Configuration Domain Controller to Win2008R2), 9: shutdown All Win 2003 Domain controllers 10:Now Exchange Secound Node( AMCBMX2) will work without any error, but when we try to move Excahgne Service to ABCMBX1, then Microsft Excahnge Host Service doesn't start. first it's give Event ID: 2080 ( it's show , while trying start the MSExchangetolplogyservice, it's trying to connect Old Win2003R2 Domain Controller (Win2003R2) only. can't see other DC in list. since Win2003R2 DC is not availble, that exchange service will not work. from secound node, we can see the MSexchangetoplogyserive try to connect all domain controllers which are avaible( even DR Site DC are avaivlble ). then start all services automalticall and that is why secound node is working fine. but in first Mail box node , when it's try to start Microsoft Excahnge Host Service, it's failed ( if Wi2003R2 Server is avavilbe, then all exchange serivces in ABCMBX1 will start automatically and we can move exchange roles to first node. we need to decommission those old DC. bu since still ABCMBX1 Server depends on Old Win2003R2 domain for Exchange Servies, we can't do this.( even if we remove Globle Catalog from Win2003R2 DC, ABCMBX1 will not work( Event ID: 2080 -trying to connect Win2003R2 and give error with Event ID :2114 )). i tried to find solution and coundn't . as i see ABCMBX1 Still trying fine GC as Win2003R2 and that is why Excahgne Service can't start. if This server can find Win2008R2 Server as GC , every thing will work fine. i found some workaround to run Exchage Domain rep( Setup.exe /domainRep in New Win2008R2 domain), but why it's working in secound node and only for first node. please if some one can check this and give soultion , that will be greate.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 12:00pm

hI all i found few things and as follows, 1: manually setup GC servers for DSAccess (http://support.microsoft.com/kb/250570) 2: Change group Policy (Add Exchange Servers to " Computer Configuration->Windows Settings->Security Settings -> Local Policies -> User Rights Assignment -> Manage Auditing and Security Log "http://technet.microsoft.com/en-us/library/bb218747(EXCHG.80).aspx 3: run Setup.exe /domainPre ( final Option). will these things work fine or some else i have to resolve this issues. Indunil
December 5th, 2010 1:23pm

hi all there was manual setting has been configure in register in node 1. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeDSAccess\Profiles\Default\ UserGC1 UserGC2 remove those and restart Excahnge Service. it work for me. anyway thanks for all INdunil
Free Windows Admin Tool Kit Click here and download it now
December 6th, 2010 2:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics