Traitée windows server 2008 additional domain controller

  • dimanche 18 mars 2012 12:16
     
     

    Dear All,

    recently i installed a fresh copy of windows server 2008 32bit and i configured to be ADC to my primary 2003 DC, but suddenly after applying some MS updates the 2008 ADC cannot boot and giving the following error :

    ---------------------------------------------------------------------------------------------------------------------------------------

    "Windows failed to start.  A recent hardware or software change might be the cause.  To fix the problem:

    1. Insert your Windows installation disc and restart your computer.

    2. Choose your language settings, and click "Next."

    3. Click "Repair your computer."

    If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

    File: \Windows\system32\config\system

    status: 0xc00000e9

    Info:  Windows failed to load because the system registry file is missing, or corrupt.

    ---------------------------------------------------------------------------------------------------------------------------------------

    I tried to repair using windows disc but cannot coz i don't have image or restore point from the system.

    What i can do regarding this issue as i don't want to reinstall the windows coz it's ADC.

    Please advise..........

    Regards,


    Dubai Media Incorporated System Administrator www.emaratalyoum.com

Toutes les réponses

  • dimanche 18 mars 2012 14:00
     
     

    1. Have you used adprep correctly for forest and domain? (32 bit version)

    2. Could you describe all steps of new server installation and configuration?

    3. What is the hardware configuration?

    Regards

    Milos

  • dimanche 18 mars 2012 16:21
     
     

    Know it doesn't really help now but the server should have had system update readiness tool applied and fully patched before dcpromo. Is 2003 DC still functional? If so you'll need to remove 2008 from 2003 active directory.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]


  • dimanche 18 mars 2012 16:57
     
     

    Something happened that crashed your registry. If you don't have any backup. You will have to erase any trace of the Win2008 on the 2003....

    http://support.microsoft.com/kb/216498

    http://support.microsoft.com/kb/555846/en-us

    In 2008, just erasing the computer account of the DC you want to remove make all those step, but Iam not sure in 2003 if it act the same way. If all FSMO role are still on the 2003, it's not a big poblem.

    After that re-install the Win2008 and do a system state backup to disk after promoting it !


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

  • dimanche 18 mars 2012 21:11
     
     Réponse proposée

    Hello,

    As this is an additional DC, you can simply proceed like that:

    • Seize FSMO roles to the old DC if the new DC was an FSMO holder: http://support.microsoft.com/kb/255504
    • Perform a metadata cleanup: http://support.microsoft.com/kb/216498
    • Re-install the new server
    • Promote it and make it a DNS and GC server

    I think that some registry changes had been made and this made the registry database corrupted.

    Please note that, before any changes on the registry databases, you have to export the database or perform a system state backup before proceeding. Wrong registry changes are not supported by Microsoft.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

  • lundi 19 mars 2012 03:28
     
     

    Yes 2003 DC still functional. are there steps to remove 2008 smoothly ?

    thnkx for your reply


    Dubai Media Incorporated System Administrator www.emaratalyoum.com

  • lundi 19 mars 2012 03:34
     
     

    You can follow along here.

    http://technet.microsoft.com/en-us/library/cc781245(v=ws.10).aspx 

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

  • lundi 19 mars 2012 03:58
     
     
    this is applied to 2003 server, is it applied to remove 2008 DC from 2003 primary DC ?

    Dubai Media Incorporated System Administrator www.emaratalyoum.com

  • lundi 19 mars 2012 04:48
     
     

    i'm trying to seize fsmo roles and i succeeded to seize RID and PDC but infrastructure, schema and domain naming i got the following:

    Win32 error returned is 0x20af(The requested FSMO operation failed. The current
    FSMO holder could not be contacted.)

    any help ?


    Dubai Media Incorporated System Administrator www.emaratalyoum.com

  • lundi 19 mars 2012 10:46
     
     Traitée

    Hi qais

    before seize FSMO. check what DC holds the fsmo roles. you can check this by typing following command in your DC.

    netdom query fsmo.  

    because just adding an additional DC it wont transfer any of the FSMO roles automatically. 

    give me the results. 


    Asitha

  • lundi 19 mars 2012 10:48
     
     

    i'm trying to seize fsmo roles and i succeeded to seize RID and PDC but infrastructure, schema and domain naming i got the following:

    Win32 error returned is 0x20af(The requested FSMO operation failed. The current
    FSMO holder could not be contacted.)

    any help ?


    Dubai Media Incorporated System Administrator www.emaratalyoum.com

    That is the output of you try to transfer these FSMO roles. Before seizing, the DC will try the transfer operation and you will get such errors. Please ignore them. To make sure that the DC is holder of all FSMO roles, run netdom query fsmo on it.

    Please make sure that the old DC is offline and it should never come back online if you have done the seizing operation.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

  • mercredi 21 mars 2012 03:51
     
     

    Hi Asitha,

    i confirm that all fsmo roles are held by the live DC. thanks all for your support.

    regards,


    Dubai Media Incorporated System Administrator www.emaratalyoum.com