Поделиться через


Properly Handling an EBS 2008 Setup Failure

[Today's post comes to us courtesy of Shawn Sullivan]

If EBS setup encounters a fatal error and cannot continue, you will be presented with the following window once you cancel:

clip_image002[1]

Figure 1: Installation not finished

Note the warning: Do not manually delete any objects or settings in Active Directory. The Windows Essential Business Server Installation Wizard handles all of the necessary cleanup tasks for Active Directory objects and settings. By deleting objects and settings yourself, you could unintentionally damage the Active Directory environment required by Windows Essential Business Server.

Configuration information for your EBS environment is written to and read from the MMSConfiguration container in Active Directory, including the status of each server setup. EBS setup uses this information to determine if you are running as a clean install, as a recovery from a failed setup, or as a replacement mode install.

If setup encounters a fatal error, you will be required to fix the root cause of the failure, format the machine, and reinstall. After the domain join portion, all of the proper cleanup steps will be performed automatically before proceeding.

clip_image004[1]

Figure 2: Clean up an incomplete installation

If you have not followed the instructions and decide to manually perform cleanup steps after setup fails, like running dcpromo and removing computer objects in Active Directory, you will cause a condition during domain join where EBS setup is expecting to find the computer object in Active Directory that doesn’t exist. This will result in the following errors:

clip_image006[1]

Figure 3: Domain Join Error: Setup failed to find the server : <> in Active Directory.

clip_image008[1]

Figure 4: The DNS query for <> did not complete, because a DNS server could not be contacted

If you are in this situation, you can restore the computer object using ADRestore from Sysinternals:

https://technet.microsoft.com/en-us/sysinternals/bb963906.aspx

Launch ADRestore from the Management server with the following syntax:

Adrestore –r <MessagingServerName>

For example:

clip_image010[1]

Figure 4: Restoring the computer object

At this point, you must format and reinstall the failed server and allow EBS setup to perform the proper cleanup steps.

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://servercoach.com/?p=142

  • Anonymous
    January 01, 2003
    [Today&#8217;s post comes to us courtesy of Shawn Sullivan and Mark Stanfill] When installing Microsoft

  • Anonymous
    January 01, 2003
    [Today's post comes to us courtesy of Kunal Ghotge and Mark Stanfill] EBS setup disables all network

  • Anonymous
    January 01, 2003
    Installed EBS 2008 premium - updated a 2003 AD domain. Everything appeared to be okay but now the security server cannot contact the management server and can't do updates.. What joy.  can I reinstall the security server, format drive or not? thanks barry barry.borror@starofhope.org

  • Anonymous
    January 01, 2003
    I'm in a similar position to Jeff above. Only stumbled on this post after obviously mismanaging my setup and ending in a serious error...is there any way to remove all trace of previous installations and status in order to start again?

  • Anonymous
    January 01, 2003
    Hi, I get a fatal error (EBS Setup  not responding) every time I try to install, the log says that the CA TASK failed! What can I do? Regards Thomas

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Jeff, I'd like to help you if you are in a failed install.  Please contact me offline at markstan [at] microsoft dot com and I'll be happy to see if we can't fix your issue. For what it's worth, the installer works very well in production.  The reason we wrote this blog was to help people from getting in to a situation where they did extra work that prevented the installer from working like it was designed. Hope this helps, Mark Stanfill

  • Anonymous
    May 02, 2009
    The comment has been removed

  • Anonymous
    May 05, 2009
    I'm having a problem which is the other side of this - I can't get my security server to join the domain because it already exists - I have removed it from the AD as requested by the setup - but still I can't get it to rejoin the domain I get this error: DOMAIN JOIN ERROR Cereberus is connected to the network.  The server cannot be replaced if it is connected.  To continue, disconnect Cereberus then press Join Domain. Can you help?