Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot install Active Directory on an iSCSI boot computer that is running Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have an iSCSI boot computer that is running Windows Server 2008 R2.
  • You assign an iSCSI Logical Unit Number (LUN) to each logical disk on the computer. Additionally, each drive on the computer uses the NTFS file system.
  • You run the Active Directory Installation Wizard (Dcpromo.exe) to install Active Directory on this computer.
In this scenario, the installation operation fails, and you receive the following error message:
This computer has no disk drives formatted for the NTFS file system. Because the SYSVOL folder is replicated among Active Directory domain controllers, that folder must be on a disk formatted with NTFS

(You can convert drivers formatted with the FAT file system with the convert.exe command-line tool)

↑ Back to the top


Cause

The Active Directory Installation Wizard does not support saving the Active Directory database and the SYSVOL folder on to an iSCSI volume.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies to" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dcpromo.exe6.1.7600.20621183,80819-Jan-201010:24x64
Dcpromoexe-ppdlic.xrm-msNot applicable2,99319-Jan-201010:40Not applicable
Dcpromoui.dll6.1.7600.206211,862,65619-Jan-201010:26x64
Dcpromocmd.dll6.1.7600.206211,283,58419-Jan-201010:26x64
Dcpromo.exe6.1.7600.20621131,58419-Jan-201011:54x86
Dcpromoexe-ppdlic.xrm-msNot applicable2,99319-Jan-201013:22Not applicable
Dcpromoui.dll6.1.7600.206211,189,37619-Jan-201011:55x86
Dcpromocmd.dll6.1.7600.20621769,02419-Jan-201011:55x86
For all supported IA-64-based versions of Windows Server 2008 R2

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

After you install this hotfix, the Active Directory Installation Wizard supports saving the Active Directory database and the SYSVOL folder on to an iSCSI volume.

Notes
  • This iSCSI volume must be the system volume. If you want to save the Active Directory database on to an iSCSI volume that is not the system volume, you must create a new DWORD value�named AllowIscsi with value data of 0x1 in the�following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AdminDebug\dcpromoui
  • The operating system cannot start if you save the Active Directory database to a non-system volume that is not available during the startup process. Therefore, do not put the Active directory database on an iSCSI volume that may not be available during the startup process.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_0095f4082e19e747102a256b707d53f5_31bf3856ad364e35_6.1.7600.20621_none_b7caa09302ae3d0c.manifest
File versionNot applicable
File size745
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_488cc6f9052fbbd45bcca5aea0fb9364_31bf3856ad364e35_6.1.7600.20621_none_f464e1a76c1afa46.manifest
File versionNot applicable
File size730
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_55e0bf7b68d19040efefb94d92d98392_31bf3856ad364e35_6.1.7600.20621_none_8ce6c8b0e2ab9d4b.manifest
File versionNot applicable
File size744
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_630ce4a59aada331c875b175d7032231_31bf3856ad364e35_6.1.7600.20621_none_dccda36fb006ed92.manifest
File versionNot applicable
File size732
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_7784b163c6c60afb1fe6519f5b23ca96_31bf3856ad364e35_6.1.7600.20621_none_ea4c7cbf95262aff.manifest
File versionNot applicable
File size742
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_a329cdb5510f8609baecb9edba9f689b_31bf3856ad364e35_6.1.7600.20621_none_bc6351dcb275ad98.manifest
File versionNot applicable
File size743
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameAmd64_microsoft-windows-d..-setup-bootstrapper_31bf3856ad364e35_6.1.7600.20621_none_78bbcb0fce47a0b9.manifest
File versionNot applicable
File size4,170
Date (UTC)19-Jan-2010
Time (UTC)13:38
PlatformNot applicable
File nameAmd64_microsoft-windows-d..aincontroller-setup_31bf3856ad364e35_6.1.7600.20621_none_319adebbb21b42eb.manifest
File versionNot applicable
File size3,045
Date (UTC)19-Jan-2010
Time (UTC)13:42
PlatformNot applicable
File nameAmd64_microsoft-windows-d..r-commandline-setup_31bf3856ad364e35_6.1.7600.20621_none_28808f8c9ab97ee5.manifest
File versionNot applicable
File size3,077
Date (UTC)19-Jan-2010
Time (UTC)13:45
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,777
Date (UTC)19-Jan-2010
Time (UTC)18:15
PlatformNot applicable
File nameX86_microsoft-windows-d..-setup-bootstrapper_31bf3856ad364e35_6.1.7600.20621_none_1c9d2f8c15ea2f83.manifest
File versionNot applicable
File size4,166
Date (UTC)19-Jan-2010
Time (UTC)13:39
PlatformNot applicable
File nameX86_microsoft-windows-d..aincontroller-setup_31bf3856ad364e35_6.1.7600.20621_none_d57c4337f9bdd1b5.manifest
File versionNot applicable
File size3,041
Date (UTC)19-Jan-2010
Time (UTC)13:42
PlatformNot applicable
File nameX86_microsoft-windows-d..r-commandline-setup_31bf3856ad364e35_6.1.7600.20621_none_cc61f408e25c0daf.manifest
File versionNot applicable
File size3,073
Date (UTC)19-Jan-2010
Time (UTC)13:46
PlatformNot applicable

↑ Back to the top


Keywords: KB977184, kbqfe, kbsurveynew, kbfix, kbautohotfix, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 977184
Revision : 5
Created on : 2/22/2012
Published on : 2/22/2012
Exists online : False
Views : 365