Installation Exchange 2007 on new Windows 2008 domain controller global catalog error

Hi,

I'm migrating from SBS2003 to Windows 2008 environemtn.
I install the AD services on Windows 2008 together with the GC. (I checked that it is installed and runnig on the new win2008dc with the active directory sites and services mmc.

I unchecked global catalog on the sbs2003 server and verified that the win2008dc is global catalog is checked.

The problem is that when I want to install Exchange 2007 I get an error (see code)

I already tried a different scenario, first installing Exchange 2007 and then deactivating gc on the sbs2003 server but when I want to move the mailboxes I get a similar error.

How can I make sure that Exchange 2007 finds the gc.
In the event viewer no explicit events are visible during the installation of exchange 2007
Summary: 3 item(s). 0 succeeded, 3 failed. 
Elapsed time: 00:00:59
 
Hub Transport Role Prerequisites
Failed
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find any Global Catalog in forest Forcea.local.
Error:
Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=67aca4a0-bc3f-4f8f-8297-b13e0d347942
Error:
Setup cannot continue because one or more SMTP/Send connectors have invalid settings: Could not find any Global Catalog in forest Forcea.local.
Elapsed Time: 00:00:53
Client Access Role Prerequisites
Failed
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find any Global Catalog in forest Forcea.local.
Error:
The 'IIS 7 Dynamic Content Compression' component is required. Install the component via Server Manager.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=41a25c5e-0d39-4e55-a1f0-7be885982236
Error:
The 'IIS 7 Static Content Compression' component is required. Install the component via Server Manager.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=41a25c5e-0d39-4e55-a1f0-7be885982236
Error:
Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=67aca4a0-bc3f-4f8f-8297-b13e0d347942
Elapsed Time: 00:00:02
Mailbox Role Prerequisites
Failed
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find any Global Catalog in forest Forcea.local.
Error:
Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.3&id=67aca4a0-bc3f-4f8f-8297-b13e0d347942
Warning:
If Outlook Web Access is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once Setup completes.
Elapsed Time: 00:00:02

Open in new window

techneitsolutionsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andres PeralesCommented:
have you checked you DNS to make sure that it is pointing to where you what it to be pointing too?
0
KrisdeepCommented:
Install exchange 2007 and specify the DC you would want to use.


http://blog.flaphead.dns2go.com/archive/2007/07/25/exchange-2007-setup-switches.aspx

0
KrisdeepCommented:
setup /DomainController, /dc
         
Specifies the domain controller that setup will use to read and write to Active Directory.Netbios or FQDN format can be used.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

joeywCommented:
Did you run adprep on the sbs2003 server to update the active directory schema to the server 2008 schema?  
0
techneitsolutionsAuthor Commented:
Hi peralsa,

Well the DNS has replicated and I don't see any problems in it. It contains a (a) record voor the sbs2003 server and one for the win2008 server.
I've been looking into that direction as well because at startup I get an error. "The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly."

Hi krisdeep, the error I get is at the readiness check, before the actual installation takes place
0
KrisdeepCommented:
The setup should have update the schema automatically. Don't have to run the setup.com /prepare ad
0
techneitsolutionsAuthor Commented:
Hi Joeyw,

I ran adprep before installing AD on the windows 2008 server
0
KrisdeepCommented:
Using this will force the setup to use the specified domain controler as the GC

setup /dc
         
Specifies the domain controller that setup will use to read and write to Active Directory.Netbios or FQDN format can be used.
0
techneitsolutionsAuthor Commented:
The only flags I get are

Setup.com /help:Install         - Installing Exchange Server roles.
Setup.com /help:Uninstall       - Uninstalling Exchange Server roles.
Setup.com /help:Upgrade         - Upgrading Exchange Server roles.
Setup.com /help:RecoverServer   - Recovering an existing Exchange Server.
Setup.com /help:PrepareTopology - Preparing your topology for Exchange.
Setup.com /help:Cluster         - Installing Exchange on Clusters.
Setup.com /help:Delegation      - Delegated server installations.
Setup.com /help:UmLanguagePacks - Adding/removing UM language packs.
0
techneitsolutionsAuthor Commented:
F:\>setup /dc:win2008dc.forcea.local
The parameters specified are missing additional required parameters or are not v
alid together.
To list the available command line parameters, type Setup /?
0
KrisdeepCommented:
iv used Setup /PrepareSchema  /DC:FDQN before I'm sure you can use it for installing it as well . Had the same issue with the DC(GC) ---> the old DC wasn't decommissioned properly.Give it a try and let me know and see how it goes im sure sicne the same method was used on Exchange 2003
0
johnpittCommented:
Run "dcdiag /test:dns /a" to make sure you have no errors listed.
0
techneitsolutionsAuthor Commented:
Hi,

I ran the DNS tests and got the following: (see code snippet)


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
 
C:\Users\administrator.FORCEA>dcdiag /test:dns /a
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = win2008dc
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\SERVER
      Starting test: Connectivity
         ......................... SERVER passed test Connectivity
 
   Testing server: Default-First-Site-Name\WIN2008DC
      Starting test: Connectivity
         ......................... WIN2008DC passed test Connectivity
 
Doing primary tests
 
   Testing server: Default-First-Site-Name\SERVER
 
   Testing server: Default-First-Site-Name\WIN2008DC
 
      Starting test: DNS
 
         DNS Tests are running and not hung. Please wait a few minutes...
 
               Starting test: DNS
                  ......................... SERVER passed test DNS
         ......................... WIN2008DC passed test DNS
 
   Running partition tests on : DomainDnsZones
 
   Running partition tests on : ForestDnsZones
 
   Running partition tests on : Schema
 
   Running partition tests on : Configuration
 
   Running partition tests on : Forcea
 
   Running enterprise tests on : Forcea.local
      Starting test: DNS
         Test results for domain controllers:
 
            DC: server.Forcea.local
            Domain: Forcea.local
 
 
               TEST: Basic (Basc)
                  Warning: adapter
                  [00000011] VMware Accelerated AMD PCNet Adapter has invalid
                  DNS server: 10.11.1.4 (<name unavailable>)
                  Warning: adapter
                  [00000011] VMware Accelerated AMD PCNet Adapter has invalid
                  DNS server: 10.11.1.5 (<name unavailable>)
                  Warning: The AAAA record for this DC was not found
 
               TEST: Records registration (RReg)
                  Network Adapter
                  [00000011] VMware Accelerated AMD PCNet Adapter:
                     Warning:
                     Missing AAAA record at DNS server ::1:
                     server.Forcea.local
 
               Warning: Record Registrations not found in some network adapters
 
 
            DC: win2008dc.Forcea.local
            Domain: Forcea.local
 
 
               TEST: Forwarders/Root hints (Forw)
                  Error: Root hints list has invalid root hint server:
                  a.root-servers.net. (198.41.0.4)
                  Error: Root hints list has invalid root hint server:
                  b.root-servers.net. (192.228.79.201)
                  Error: Root hints list has invalid root hint server:
                  c.root-servers.net. (192.33.4.12)
                  Error: Root hints list has invalid root hint server:
                  d.root-servers.net. (128.8.10.90)
                  Error: Root hints list has invalid root hint server:
                  e.root-servers.net. (192.203.230.10)
                  Error: Root hints list has invalid root hint server:
                  f.root-servers.net. (192.5.5.241)
                  Error: Root hints list has invalid root hint server:
                  g.root-servers.net. (192.112.36.4)
                  Error: Root hints list has invalid root hint server:
                  h.root-servers.net. (128.63.2.53)
                  Error: Root hints list has invalid root hint server:
                  i.root-servers.net. (192.36.148.17)
                  Error: Root hints list has invalid root hint server:
                  j.root-servers.net. (192.58.128.30)
                  Error: Root hints list has invalid root hint server:
                  k.root-servers.net. (193.0.14.129)
                  Error: Root hints list has invalid root hint server:
                  l.root-servers.net. (198.32.64.12)
                  Error: Root hints list has invalid root hint server:
                  m.root-servers.net. (202.12.27.33)
 
         Summary of test results for DNS servers used by the above domain
         controllers:
 
            DNS server: 10.11.1.4 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 10.11.1.4               Name resolution is not functional. _ldap._tcp.F
orcea.local. failed on the DNS server 10.11.1.4
 
            DNS server: 10.11.1.5 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 10.11.1.5               Name resolution is not functional. _ldap._tcp.F
orcea.local. failed on the DNS server 10.11.1.5
 
            DNS server: 128.63.2.53 (h.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 128.63.2.53
            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 128.8.10.90
            DNS server: 192.112.36.4 (g.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.112.36.4
            DNS server: 192.203.230.10 (e.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.203.230.10
            DNS server: 192.228.79.201 (b.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.228.79.201
            DNS server: 192.33.4.12 (c.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.33.4.12
            DNS server: 192.36.148.17 (i.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.36.148.17
            DNS server: 192.5.5.241 (f.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.5.5.241
            DNS server: 192.58.128.30 (j.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 192.58.128.30
            DNS server: 193.0.14.129 (k.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 193.0.14.129
            DNS server: 198.32.64.12 (l.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 198.32.64.12
            DNS server: 198.41.0.4 (a.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 198.41.0.4
            DNS server: 202.12.27.33 (m.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 202.12.27.33
         Summary of DNS test results:
 
                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: Forcea.local
               server                       PASS WARN PASS PASS PASS WARN n/a
               win2008dc                    PASS PASS FAIL PASS PASS PASS n/a
 
         ......................... Forcea.local failed test DNS
 
C:\Users\administrator.FORCEA>

Open in new window

0
johnpittCommented:
I believe some of those errors are IPv6 related. Some others appear to be a possible problem.

What are the IP addresses of your dns servers? Are they 10.11.1.4 and 5?
0
gauravbhandariCommented:
Hi,
1. I would suggest to uncheck IPv6 option from network card properties & provide static IP address in IPv4 (assuming single NIC).
2. Promote W2008 as GC & reboot both W2008 (assuming there are only sbs2003 & W2008. There is no W2000 GC in environment. If yes, demote them as E2K7 does not support W2000 as GC)
3. Run the following commands from setup files folder from command prompt:
* setup.com /mode:install /r:m, ca; ht; mt (m: Mailbox, ca: CAS; ht: HUB; mt: Management tools) /dc:FQDN of W2008 (GC).

Hope this help!!!
0
techneitsolutionsAuthor Commented:
The Ip-addresses are 10.11.1.4 and 5, they are unavailable since I'm running in a test environment.

I deactivated IPv6 but I just get the same error again.
It looks like there's no gc installed but I'm sure there is.

How can I check in command line that a gc is installed on my w2008 machine and that it's working?
0
gauravbhandariCommented:
You can check the same from Active Directory Sites & Services console by following below steps:
1. Open Active Directory Sites & Services console.
2. Expand the site name where we have Windows 2008 server & then the servers.
3. Expand server name (W2008) & under it you will find NTDS settings.
4. Right click NTDS settings & click properties.
5. If the box "Global Catalogue" is checked then it is a GC. If not check the box & then reboot the server.
I would also recommened to reboot the exchange box as well.
You can do the same for all the DC's that are present in your domain.
0
techneitsolutionsAuthor Commented:
I maybe found the cause, but not the solution.
If I take a look at the NTDS settings i still see that the inter-site topology generator is the sbs2003 server how can I change this to the win2008 server? Could this solve the problem?

If I leave the global catalog check of the sbs2003 server enabled the wizard of exchange finds the sbs2003 gc but no sign of the win2008 gc.

I changed the primary dns on w2008 to itself but that didn't change anything.
0
johnpittCommented:
I'm sorry, I must have missed something. If your DNS servers are not available, how will your exchange install be able to find the GC?
Do you have other dns servers active?
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hello,
Can you run the replmon and add the Windows 2008 server and go to properties and verify if it can advertise itself as a GC or not.
Secondly do not uncheck IPv6 ass its a DCa nd GC that would hold Exchange and if DC GC are not having IPv6 it would be a problem.
Make Windows 2003 as GC and also tell which server holds the FSMO roles.
Have you run the command
setup.com /pl as its very important in a legacy server invironment, if not please run it now.
If you run the command
Setup.com /m:install /roles:the roles that you want to install /dc:FQDN of the SBS 2003 server

Also check for the event 2080 in the App logs on the SBS 2008 and share them with me.
0
techneitsolutionsAuthor Commented:
Hi,

I found the solution, apparently there was a problem with the replication of AD to the W2008 server so I deleted the server from the domain and did the same procedure again and it works now.

Right now I'm moving the mailboxes from the old sbs2003 server to the w2008 server some mailboxes seem to be failing but some others work.
0
techneitsolutionsAuthor Commented:
I'm going to close this post, since the problem is resolved.
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
HUmm move mailbox failing .... ?
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hello techneitsolutions were you able to get the move mailbox issue resolved ?
0
techneitsolutionsAuthor Commented:
Yep, the problem there was diskspace, so that's solved as well.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.