locked
Can not move Global Catalog to new server RRS feed

  • Question

  • Server1 is a DC  2003 server with exchange 2003, I setup a new server Server2 which is running server 2008 enterprise and Exchange 2010 All with latest updates. I transfered all the FSMO roles to Server2 and Made it a GC. I then removed exchange from Server1. After a few days i unchecked Global catalog from Server1 when i do that I can no longer receive emails and when i run exchange management console from server2 it errors with " The WinRM client received an HTTP Server error status (500), but the remote service did not include any other information about the cause of the failure." To get everything back up i have to enable GC on Server1 and reboot it. 

    C:\>netdom /query fsmo
    Schema master server2.domain.local
    Domain naming master       server2.domain.local
    PDC                         server2.domain.local
    RID pool manager  server2.domain.local
    Infrastructure master       server2.domain.local

    I noticed on the new server (server2) that the Netlogon and Sysvol shares were not there so i recreated them using this KB http://support.microsoft.com/kb/290762 but still have the same issue with the global catalog.

    Any suggestions?




    • Edited by Valcon54 Wednesday, October 3, 2012 3:34 AM
    Tuesday, October 2, 2012 9:02 PM

Answers

  • Please check if TCP/IP NetBIOS Helper service is running. 

    If the service is runnning then run the cmd mentioned below:

    Running "adprep.exe /rodcprep" command should take care of the DC issue.

    GC info comes from forest which is not accessable.

    Do let me know the result. You need Enterprise Admins permission.


    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 8:18 PM
  • i ran repadmin /syncall /AePd and now the 2080 event shows 

    In-site:
    server2.domain.local CDG 1 7 7 1 0 1 1 7 1
    server1.domain.local CDG 1 7 7 1 0 1 1 7 1
     

    so that part looks better. 

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 9:50 PM
  • i also enabled IPv6 on the new server. 

    I unchecked GC on the 2003 server and sofar it looks like everything is ok. 

    still testing.

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 9:57 PM

All replies

  • First of all, it is not recommended to install Exchange Server on the DC.

    In your this issue, I suggest you follow this steps to do that:

    1, Server Configuration->Modify Configuration Domain Controller->Specify a domain controller to point to new DC.

    2, run the cmdlet Set-ExchangeServer -staticdomaincontrollers  -staticglobalcatalogs -staticconfigurationdomaincontroller to point to the new DC.

    3, Restart the Exchange server. If it works, you can change it back:

    set-exchangeserver -staticdomaincontrollers $null -staticglobalcatalogs $null -staticconfigurationdomaincontroller $null

    Set-ExchangeServer

    http://technet.microsoft.com/en-us/library/bb123716.aspx

    Thanks,

    Evan


    Evan Liu

    TechNet Community Support

    Wednesday, October 3, 2012 5:44 AM
    Moderator
  • When i input this cmdlet


    [PS] C:\Windows\system32>Set-ExchangeServer  server2.domain.local -staticdomaincontrollers server2.domain.local -staticglobalcatalogs server2.domain.local -staticconfigurationdomaincontroller

    i get this error 

    A positional parameter cannot be found that accepts argument '-staticconfigurationdomaincontroller'.
        + CategoryInfo          : InvalidArgument: (:) [Set-ExchangeServer], ParameterBindingException
        + FullyQualifiedErrorId : PositionalParameterNotFound,Set-ExchangeServer

    This command went through fine

    [PS] C:\Windows\system32>Set-ExchangeServer -Identity server2.domain.local -staticdomaincontrollers server2.domain.local -staticglobalcatalogs server2.domain.local -StaticConfigDomainController server2.domain.local
    [PS] C:\Windows\system32>

    I rebooted after this cmdlet and when i login to the server its just a blue screen so far no desktop 

    After waiting for 30min i launched task manager and ran a cmd prompt launched exchange management shell and put everything back to Null ( Set-ExchangeServer "ExchangeServerName" -StaticDomainControllers $Null -StaticGlobalCatalogs $Null) 

    then rebooted and back to desktop so i dont know why the other command prevents the server from fully booting up. 



    • Edited by Valcon54 Wednesday, October 3, 2012 4:56 PM
    Wednesday, October 3, 2012 3:13 PM
  • I don't see any issue in running Exchange on DC. Offcourse this will save a windows 2008 license cost.

    Please publish the output of dcdiag of the problem server


    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    Wednesday, October 3, 2012 6:16 PM
  • I agree with exchange running on a DC. No small business is going to purchase a new server and Licenses. And this server only has 6 users. I understand its not recommended but why would MS come up with SBS 32bit with only allowing 4GB of Ram when you know you will exceed that if you enable all the services. But that is for another discussion. 

    Directory Server Diagnosis
    Performing initial setup:   Trying to find home server...   Home Server = Server2   * Identified AD Forest. 
       Done gathering initial info.
    Doing initial required tests   
       Testing server: Default-First-Site-Name\Server2      Starting test: Connectivity         ......................... Server2 passed test ConnectivityDoing primary tests   
       Testing server: Default-First-Site-Name\Server2      Starting test: Advertising         ......................... Server2 passed test Advertising      Starting test: FrsEvent         There are warning or error events within the last 24 hours after the         SYSVOL has been shared.  Failing SYSVOL replication problems may cause         Group Policy problems. 
             ......................... Server2 passed test FrsEvent      Starting test: DFSREvent         ......................... Server2 passed test DFSREvent      Starting test: SysVolCheck         ......................... Server2 passed test SysVolCheck      Starting test: KccEvent         ......................... Server2 passed test KccEvent      Starting test: KnowsOfRoleHolders         ......................... Server2 passed test KnowsOfRoleHolders      Starting test: MachineAccount         ......................... Server2 passed test MachineAccount      Starting test: NCSecDesc         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have             Replicating Directory Changes In Filtered Set
             access rights for the naming context:         DC=ForestDnsZones,DC=domain,DC=local
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have             Replicating Directory Changes In Filtered Set
             access rights for the naming context:         DC=DomainDnsZones,DC=domain,DC=local
             ......................... Server2 failed test NCSecDesc      Starting test: NetLogons         ......................... Server2 passed test NetLogons      Starting test: ObjectsReplicated         ......................... Server2 passed test ObjectsReplicated      Starting test: Replications         ......................... Server2 passed test Replications      Starting test: RidManager         ......................... Server2 passed test RidManager      Starting test: Services         ......................... Server2 passed test Services      Starting test: SystemLog         ......................... Server2 passed test SystemLog      Starting test: VerifyReferences         ......................... Server2 passed test VerifyReferences   

       Running partition tests on : ForestDnsZones      Starting test: CheckSDRefDom         ......................... ForestDnsZones passed test CheckSDRefDom      Starting test: CrossRefValidation         ......................... ForestDnsZones passed test         CrossRefValidation   
       Running partition tests on : DomainDnsZones      Starting test: CheckSDRefDom         ......................... DomainDnsZones passed test CheckSDRefDom      Starting test: CrossRefValidation         ......................... DomainDnsZones passed test         CrossRefValidation   
       Running partition tests on : Schema      Starting test: CheckSDRefDom         ......................... Schema passed test CheckSDRefDom      Starting test: CrossRefValidation         ......................... Schema passed test CrossRefValidation   
       Running partition tests on : Configuration      Starting test: CheckSDRefDom         ......................... Configuration passed test CheckSDRefDom      Starting test: CrossRefValidation         ......................... Configuration passed test CrossRefValidation   
       Running partition tests on : domain      Starting test: CheckSDRefDom         ......................... domain passed test CheckSDRefDom      Starting test: CrossRefValidation         ......................... domain passed test CrossRefValidation   
       Running enterprise tests on : domain.local      Starting test: LocatorCheck         ......................... domain.local passed test LocatorCheck      Starting test: Intersite         ......................... domain.local passed test Intersite

       
    Wednesday, October 3, 2012 6:53 PM
  • This is the issue

    Starting test: NCSecDesc        

    Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have "Replicating Directory Changes In Filtered Set" access rights for the naming context:

    DC=ForestDnsZones,DC=domain,DC=local

    Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have "Replicating Directory Changes In Filtered Set" access rights for the naming context:        

    DC=DomainDnsZones,DC=domain,DC=local

             ......................... Server2 failed test NCSecDesc 


    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    Wednesday, October 3, 2012 8:10 PM
  • Please check if TCP/IP NetBIOS Helper service is running. 

    If the service is runnning then run the cmd mentioned below:

    Running "adprep.exe /rodcprep" command should take care of the DC issue.

    GC info comes from forest which is not accessable.

    Do let me know the result. You need Enterprise Admins permission.


    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 8:18 PM
  • i am running tcp/ip helper and i did run the adprep.exe /rodcprep and that did fix the dcdiag error. 

    Wednesday, October 3, 2012 8:35 PM
  • Is it possible to take a restart of the server and ensure Global catalog check box is checked..

    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    Wednesday, October 3, 2012 9:07 PM
  • i ran this command again

    [PS] C:\Windows\system32>Set-ExchangeServer -Identity server2.domain.local -staticdomaincontrollers server2.domain.local -staticglobalcatalogs server2.domain.local -StaticConfigDomainController server2.domain.local 

    after this command i rebooted. When i logged in i got to the desktop but when i check the services none of the exchange services were started and i could not start them So i had to set everything back to $Null to get exchange to start. 

    As of now GC is checked on both servers. 

    Wednesday, October 3, 2012 9:21 PM
  • I am sorry, I wanted to see how does server 2 behave after fixing the global AD partition issue.

    So rerun the cmd and make it  null and uncheck GC on server1.


    Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

    Wednesday, October 3, 2012 9:28 PM
  • I think this is the issue i see in event log event ID 2080 

    Server2 CDG 1 0 0 1 0 0 0 0 0

    The 0's are an issue. 

    Wednesday, October 3, 2012 9:37 PM
  • i ran repadmin /syncall /AePd and now the 2080 event shows 

    In-site:
    server2.domain.local CDG 1 7 7 1 0 1 1 7 1
    server1.domain.local CDG 1 7 7 1 0 1 1 7 1
     

    so that part looks better. 

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 9:50 PM
  • i also enabled IPv6 on the new server. 

    I unchecked GC on the 2003 server and sofar it looks like everything is ok. 

    still testing.

    • Marked as answer by Valcon54 Wednesday, October 3, 2012 10:26 PM
    Wednesday, October 3, 2012 9:57 PM