Error message when you run the Active Directory Installation Wizard: "The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer"

Error message when you run the Active Directory Installation Wizard: "The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer".

SYMPTOMS

When you try to run the Active Directory Installation Wizard on a Microsoft Windows Server 2003 R2 server, the wizard does not finish, and you may receive the following error message:

The Active Directory Installation Wizard cannot continue because the forest is not prepared for installing Windows Server 2003. Use the Adprep command-line tool to prepare both the forest and the domain. For more information about using the Adprep, see Active Directory Help.

The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer.

CAUSE

This issue may occur when Active Directory has not been updated with the Windows Server 2003 R2 schema extensions..

RESOLUTION

To resolve this issue, run the adprep.exe /forestprep command from the Windows Server 2003 R2 installation disk 2 on the schema master. To do this, insert the Windows Server 2003 R2 installation disk 2, and then type the following command:

Drive:\CMPNENTS\R2\ADPREP\adprep.exe /forestprep

MORE INFORMATION

The correct version of the ADPrep.exe tool for Windows Server 2003 R2 is 5.2.3790.2075.

You can verify the operating system support level of the schema by looking at the value of the Schema Version registry subkey on a domain controller. You can find this subkey in the following location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

You can also verify the operating system support level of the schema by using the Adsiedit.exe utility or the Ldp.exe utility to view the objectVersion attribute in the properties of the cn=schema,cn=configuration,dc=<domain> partition. The value of the Schema Version registry subkey and the objectVersion attribute are in decimal.

System Schema Version ObjectVersion values and corresponding operating system support level

•	13=Microsoft Windows 2000
•	30=Original release version of Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 (SP1)
•	31=Microsoft Windows Server 2003 R2

Windows Server 2003 R2 installation disks

Windows Server 2003 R2 comes on two installation disks. Installation disk 1 contains a slip-streamed version of Windows Server 2003 with Service Pack 1 (SP1). Installation disk 2 contains the Windows Server 2003 R2 files. If the computer has Windows Server 2003 SP1 installed, you may only have to run installation disk 2 to upgrade to Windows Server 2003 R2.

Installation disk 2 is specific to the edition of Windows Server 2003. For example, you must use a Windows Server 2003 R2, Standard Edition installation disk to upgrade a Windows Server 2003, Standard Edition-based computer. Installation disk 2 contains installation files for the x86-based version and the x64-based version of Windows Server 2003 R2.

The Adsiedit.exe utility and the Ldp.exe utility are included with Windows Server 2003 R2 support tools. To install support tools, run Suptools.msi from the \Support\Tools folder on installation disk 1.

Preventing MAC Bridging on a Windows XP Host

VMware Workstation

Details
I get an error message that says a network adapter cannot be part of the Windows Network Bridge, because it may be incompatible with my local network. Why do I see this message? Do I need to make any changes to my configuration?

Solution
VMware products do not allow the Windows XP MAC Bridging feature to bridge a virtual machine's virtual network adapters to physical network adapters on the host machine. This is done to prevent the VMware DHCP Service from leaking DHCP traffic onto the physical network.
If you need to use MAC bridging with one or more virtual network adapters, you can override the MAC bridging prevention mechanism by creating an option in your Windows XP host registry called AllowBindingToMACBridge and setting it to 1.

• To set this option, do the following.
  Open the registry on your Windows XP host.Choose Start > Run > regedit.
  Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class and look for the key {4D36E972-E325-11CE-BFC1-08002bE10318}.
  Make sure it is the right key by selecting it and verifying that (Default) has the value Network adapters.
  Under {4D36E972-E325-11CE-BFC1-08002bE10318}, there are subkeys 0000, 0001, 0002 and so forth. Select each subkey until you find the one that corresponds to the VMnet adapter in question. The correct key has the DriverDesc with value VMware Virtual Ethernet Adapter ?.
  Add a DWORD value called AllowBindingToMACBridge, and set it to 1.
  Right-click the subkey, then choose New > DWORD Value.
  Type AllowBindingToMACBridge and press Enter.
  Right-click the new option and select Modify.
  In the Value date entry field, type 1.
  Close the registry.

Note: If you see more than one subkey that looks like the correct VMnet adapter, VMware suggests you add the AllowBindingToMACBridge DWORD to each subkey.
Overriding the MAC bridging prevention mechanism may cause DHCP traffic to leak onto your physical network.

Note: Do not confuse MAC bridging with the bridged networking used for virtual machines