none
Repair install in a Windows 2003 R2 domain controller

    Question

  • Can you do a repair install on a Windows 2003 R2 domain controller without breaking active directory?
    Sunday, April 17, 2011 2:38 PM

Answers

  • Actually, I was able to do a repair-install on a W2K03 R2 domain controller, and it works fine.
    • Marked as answer by Goochland02 Monday, July 18, 2011 8:58 PM
    Monday, July 18, 2011 8:57 PM

All replies

  • What is the issue?  How many DCs do you have?  Please provide more information. 

    You can add a new server and perform DCPROMO on that server.  It will add additional DC for your existing domain.

    http://msdn.microsoft.com/en-us/library/ee797379(CS.10).aspx


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara
    This posting is provided AS IS with no warranties,and confers no rights.
    Sunday, April 17, 2011 2:49 PM
  • Hello,

    is your DC infected by viruses, spyware or malware programs?

    If you have got multiple DCs for your domain, you can:

    • Transfer the FSMO roles that it is holding to another DC
    • demote the DC
    • Repair/re-install the server
    • promote again the DC

    If you have an only one DC, I recommand that you add an additional DC/DNS/GC server and proceed like I mentioned previously.

    If you are unable to do that then you can restore your DC from a backup that dates before the appearance of your problem.

    If you have multiple DCs and you are unable to demote the faulty DC then:

    • Isolate the DC
    • Resize the FSMO roles that it was the holder to another DC
    • Perform a metadate cleanup
    • Delete all remaining DNS records for the old DC
    • run dcpromo /forceremoval on the faulty DC
    • Repair/re-install the server
    • promote it again

    To get a list of FSMO holders, run netdom query fsmo.

    Microsoft Student Partner

    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


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

    Sunday, April 17, 2011 2:56 PM
  • Repairing might break your domain controller, so its better to introduce new server, configure ADC on it & transfer all the FSMO roles along with DNS/DHCP & also make new DC as GC too. Point new DC to its own DNS server in NIC & client to point to the new DC. You need to configure new DC as time server too bu modifying the registry settings.

    Even though below article deals with windows 2000 but it applies for other version too & it didn't mention you can repair a domain controller, you can use ERD but the easy & better solution is fresh install OS post transferring all AD related services to new DC.

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

    I tried once in a lab & it didn't worked for me & the best way is install new server & configure DC using DCPROMO on it, allow time for complete the replication cycle.

    Creating an additional domain controller

    http://technet.microsoft.com/en-us/library/cc738032%28WS.10%29.aspx

    http://www.petri.co.il/how_to_install_active_directory_replica_on_windows_2003.htm

    Transfer FSMO role to another DC.

    http://www.petri.co.il/transferring_fsmo_roles.htm

    Configure authoritative time server

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

     

    Regards  


    Awinish Vishwakarma| MY Blog

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Sunday, April 17, 2011 4:18 PM
    Moderator
  • Hi Goochland02,

     

    If you need further assistance, please provide more information.

     

    1.    What’s issue?

    2.    How many Domain Controllers do you have?

    3.    Do you have a backup?

     

    If you only have one DC, this article might be helpful for you:

     

    How to replace single domain controller in domain with a single domain controller?

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

     

     


    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, April 18, 2011 2:46 AM
  • Hello,

    please provide smore more details about what happened on that server and if also other DCs exist in the domain. This is too less infomration to suggest something.

    Theroetical you can do a repair install but let's have a look on the details before to be sure about AD.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, April 18, 2011 6:26 AM
  • The best I can figure is that I un-installed a third-party server management tool client from about 15 servers.  The next time these servers rebooted, they all blue-screened before the logon prompt window with the following error.

    STOP: c000021a {Fatal System Error}
    The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000080 (0x00000000 0x0000000)
    The system has been shutdown.

    The only way I found to fix them was to do a repair install.  Fortunately I found the problem before rebooting my domain controllers.

    Monday, April 18, 2011 5:53 PM
  • Don't know if the problem was caused by the tool uninstall alone or in combination with something else.  The first server with the problem DID NOT have April MS patches, the next two had the problem upon rebooting from April patches.  All servers are Windows 2003 with one Windows 2003 R2.  All are service packed, and patched up-to-date (with the exception of April patches).  All have ESET NOD32 AV installed.  Have about 25 other servers where this management client was NOT installed, and none have the problem as far as I can tell (mixture of Windows 2008 and 2008 R2, and 2003).
    Monday, April 18, 2011 6:10 PM
  • Hello,

    please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps) and post a link here. Once done I will try to determine the cause of the problem.

    If you want to debug dump files without my help, refer to this Microsoft article:

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

    You can also proceed like I mentioned previously but the repair install may not solve your problem so upload dump files.

     


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

    Microsoft Student Partner

    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

    Monday, April 18, 2011 6:15 PM
  • Hold a minute, I did find one.  Uploading now.
    Monday, April 18, 2011 6:26 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WINLOGON_FATAL_ERROR (c000021a)
    The Winlogon process terminated unexpectedly.
    Arguments:
    Arg1: e18c8e00, String that identifies the problem.
    Arg2: c0000005, Error Code.
    Arg3: 77f473c7
    Arg4: 00c5f5ac

    Debugging Details:
    ------------------

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase

    BUGCHECK_STR:  0xc000021a_c0000005

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 8069e587 to 805435b9

    STACK_TEXT: 
    f78dad50 8069e587 0000004c c000021a baa22b30 nt!KeBugCheckEx+0x19
    f78dad80 804eebdb 00000000 00000000 8a316620 nt!PopGracefulShutdown+0x197
    f78dadac 8059b35e 00000000 00000000 00000000 nt!ExpWorkerThread+0xe9
    f78daddc 805008e6 804eeb10 00000000 00000000 nt!PspSystemThreadStartup+0x2e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0xc000021a_c0000005_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  0xc000021a_c0000005_ANALYSIS_INCONCLUSIVE

    Followup: MachineOwner
    ---------

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

    There is a problem with the winlogon process.

    Please refer to this Microsoft article for resolution:

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

    Personally I recommand that you proceed like I mentioned in my first reply, re-install the faulty DC and then promote it again. This is the easiest way to proceed.


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

     

    Microsoft Student Partner

    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

    Monday, April 18, 2011 6:43 PM
  • Thanks for your help.  Yes, I had seen this article.
    Monday, April 18, 2011 6:47 PM
  • Hi,

     

    If you would like to troubleshoot the blue screen problem, it’s suggested to contact Microsoft Customer Support Services (CSS) so that a dedicated Support Professional can help you on this issue.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below.

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Thanks for your understanding.


    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Bruce-Liu Friday, April 29, 2011 12:00 PM
    • Unmarked as answer by Goochland02 Monday, July 18, 2011 8:56 PM
    • Marked as answer by Goochland02 Monday, July 18, 2011 8:57 PM
    • Unmarked as answer by Goochland02 Monday, July 18, 2011 8:57 PM
    Thursday, April 21, 2011 6:50 AM
  • Actually, I was able to do a repair-install on a W2K03 R2 domain controller, and it works fine.
    • Marked as answer by Goochland02 Monday, July 18, 2011 8:58 PM
    Monday, July 18, 2011 8:57 PM