iSCSI Target on computers that have a single-character DNS label cannot be remotely managed through PowerShell or Server Manager in Windows Server 2012 R2

Koskee seuraavia: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 Standard


Consider the following scenario:
  • You have a Windows domain, for which the DNS label contains only a single character.
  • You install the iSCSI Target role service on a domain member that runs Windows Server 2012 R2.
  • You try to create an iSCSI virtual disk that uses either the iSCSI PowerShell cmdlet or the "New iSCSI Virtual Disk" wizard.

In this scenario, iSCSI Target runs a verification of the server DNS name before it connects. This verification fails for domains that contain a single character DNS label.


Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website: 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.


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

Additionally, you must first install update 2919355 on Windows Server 2012 R2.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


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


Learn about the terminology that Microsoft uses to describe software updates.