Troubleshooting an Active Directory Virtualized Machine

Follow

Scope

This article describes how to troubleshoot an Active Directory virtualized machine. The article includes steps for both VirtualBox (Ubuntu 12.04) and KVM (Ubuntu 16.04) virtualizations.

Overview

Use the following procedure to reconfigure the IP address of a virtualized Windows Server.

This procedure applies to environments with a single domain controller, such as a Small Business Server, where the virtual machine is the domain controller responsible for Active Directory.

As a result of migrating into a virtual environment, the virtualization might encounter IP conflict errors. These are the result of a duplicate network adapter hidden in the Windows Device Manager.

The following Microsoft TechNet article explains this issue in detail:

Prerequisites

To perform the troubleshooting steps in this article, the Datto appliance needs to be accessible via VNC. By default, you can reach your Datto appliance using any VNC client on the local network. See How To Connect To A Datto Device Via VNC Locally And Remotely for an overview of this process.

We do not recommend following this procedure through an RDP connection, as it can be unreliable. 

This procedure also uses Safe Mode and Directory Services Restore Mode.

Ensure that all required volumes are included in the backup

Verify that the Datto appliance is backing up all volumes holding Active Directory data. Missing database files can cause a STOP: c00002e2 error.  A common database file that could cause this is ntds.dit. If you discover that a volume holding Active Directory data was excluded from the backup, include the volume, and then start a backup from the Protect tab of the appliance GUI.

Try to virtualize with each storage controller.  In some instances, if the VM is using an incorrect storage controller, the restore will boot to a 2e2 error.

If you are experiencing a 2e2 error message on the offsite server,  boot into DSRM mode (on the DC) and have the date changed to the date of the restored point. For example, if it is July 10th 2:00pm EST, and you are booting on July 22nd, boot into DSRM and change the date back to July 10th at any point before 2:00pm EST.

Booting up the Virtual Machine on the Datto in Directory Services Restore Mode

1. Start a local virtualization with networking enabled. Use the Firewalled on a private subnet, or the Firewalled on a private subnet, with no Internet access option, if the production machine is still live on the network.

2. Log into the Partner Portal, and select Devices.

3. Under the Advanced tab, send the remoteVNC command to the device (Figure 1).


Figure 1 - "remoteVNC" Partner Portal Task

4. Using your preferred VNC client, access the Datto appliance. Log in with the VNC credentials shown on the Partner Portal. If it has not been changed, the VNC password is the first eight characters of the backup-admin password, which can be found on the Partner Portal (Figure 1).

Procedure

Ubuntu 12.04 Devices (VirtualBox)

1. After connecting to the Datto device, double-click on the VirtualBox icon on the desktop (Figure 2).

vbox.jpg
Figure 2 - VirtualBox icon on the Datto device's desktop

2. If there are no virtual machines running in the VirtualBox program (Figure 3), restart the VM from the Datto appliance GUI on the Local Virtualization tab. Once the VM has been started, continue to the next step.

vnc_virtualbox.JPG
Figure 3 - VirtualBox launched with no virtual machines mounted

3. If the virtual machine appears in VirtualBox and is running, stop it from the Local Virtualization tab on the device GUI (Figure 4).

virtualboxrunning.JPG
Figure 4 - VirtualBox launched with virtual machine in a Running state

4. Once the virtual machine's status shows Powered Off in VirtualBox, launch the VM by clicking on the name of the virtual machine. Then, click the Start button (Figure 5).

virtualboxidle.JPG
Figure 5 - VirtualBox showing virtual machine mounted but not running

5. The virtual machine will start to boot on the screen. Immediately press F8 to access the Advanced Boot Options screen (Figure 6).

Note: If it fails to get the Advanced Options Menu, power down the virtual machine and repeat the previous step by immediately pressing F8 until booted into the menu (Figure 6).

Server2003.DirectoryServicesRestoreMode.jpg

Figure 6 - Windows 7 Advanced Boot Options Screen - Safe Mode selected

6. From the Advanced Boot Options screen, select the Director Services Restore Mode (Figure 6).

7. Proceed to the Once booted into the Server in Directory Services Restore Mode section of this article.

Ubuntu 16.04 Devices (KVM)

1. After connecting to the Datto appliance, double-click on the KVM icon on the desktop (Figure 7).

kvm-1.png
Figure 7 - KVM icon on the Datto device's desktop

2. If there are no virtual machines running in the KVM program (Figure 8), restart the VM from the Datto appliance GUI on the Local Virtualization tab. Once the VM has been started, continue to the next step.

 

kvm-2.jpg
Figure 8 - KVM launched with no virtual machines mounted

3. If the virtual machine appears in KVM and is running, stop it from the Local Virtualization tab on the device GUI (Figure 9).

kvm-3.jpg
Figure 9 - KVM launched with virtual machine in a Running state

4. Once the virtual machine's status shows Powered Off in KVM, launch the VM by clicking on the Open button. Then, click the Start button (Figure 10).

kvm-4.jpg
Figure 10 - KVM showing virtual machine mounted but not running

5. The virtual machine will start to boot on the screen. Immediately press F8 to access the Advanced Boot Options screen (Figure 11).

Note: If it fails to get the Advanced Options Menu, power down the virtual machine and repeat the previous step by immediately pressing F8 until booted into the menu (Figure 11).

kvm-5.jpg

Figure 11 - Windows 7 Advanced Boot Options Screen - Safe Mode selected

6. From the Advanced Boot Options screen, select the Director Services Restore Mode (Figure 6).

7. Proceed to the Once booted into the Server in Directory Services Restore Mode section of this article.

Once booted into the Server in Directory Services Restore Mode:

Follow these steps to finish the procedure:

1. Select Start followed by Programs.

2. Navigate to Accessories, and select Command Prompt.

3. At the command prompt, type the following lines, pressing ENTER after each line:

set devmgr_show_nonpresent_devices=1
cd\%SystemRoot%\System32
devmgmt.msc

4. In Device Manager, go to View | Show hidden devices.

5. Navigate to the Network Adapters section.

6. Locate any gray or faintly outlined devices - these devices are not present and can safely be removed by right clicking and selecting Uninstall.

When using Active Directory Domain Controllers (DC):

Because this is an important tool, do the following:

1. When the first boot of a restored domain controller happens, immediately press F8 on the keyboard.

2. Then, select the AD Restore Mode. This ensures that the AD will not run.

3.  Once complete, perform all the steps above, and ensure that the correct IP address is configured to the LAN interface. This can take up to two reboots.

Note: If this is not done properly, and the server is allowed to boot normally, it will sit at the Preparing Network Connections stage for a long amount of time and then still possibly fail. Also know this solution can be used to remove all other devices not present on the new server.


Was this article helpful?

1 out of 2 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!