We have a non-profit school who just ran the AD upgrade on our Windows 2003 Servers. Most things seem to work fine except Outlook client cannot connect to the exchange server.
Here was the previous setup:
All servers were Windows 2003 R2 with current SP's
One Forest, One Domain, One DC.
Server DC01 - AD + DNS + Global Catalog Server ( 10.0.0.4 ) ( This is the old DC+DNS )
Server DHCP ( 10.0.0.5 ) ( This is the DHCP server )
Server Exchange ( Exchange 2003 ) (10.0.0.10) ( This is the exchange server )
Server DC1 ( 10.0.0.6 ) ( This is the new DC and DNS )
Ran the ADPREP(Forestprep, DomainPrep, RODCPREP ) on the old DC01 server. ( No errors )
Logged on the NonMember Windows 2008 64Bit server and added the role of Active Directory Domain Services. Ran the Active Directory Domain Services Installation wizard (dcpromo.exe). ( No Errors)
Chose the additional Domain Controller Options with DNS and Global Catalog as defaults.
Moved the FSMO roles to the new DC1
Modified the DHCP server to show the new DNS server name/ip. All clients now have the new DNS server name.
Logged on the old DC01 and attempted to demote it but that failed so ran the /force option and then cleaned up the metadata. Removed the old DC01 from the sites and services, domain controllers OU and DNS.
So, after the restart of all workstations, devices can logon and access shares.
Users can access email via OWA but if they attempt to open Outlook 2003 then it times out and tells us that the exchange server cannot be found and whether you would like to work offline.
I have searched almost everywhere and just cannot find a solution, so need your help.
I have not yet manually promoted the new Global Catalog DC1 to the address site, the domain, or the forest. Do I need to do that ? Since the DC01 was a GC do I need App Server pointed to the offline global catalog server to poin to a live global catalog server ? If I need to do all this then how do I that ?