Symptoms

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.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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 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.

The English (United States) 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 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies to" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows Server 2012 R2

    RTM

    GDR

  • 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 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 2012 R2

File name

File version

File size

Date

Time

Platform

Microsoft.iscsi.target.commands.dll

6.3.9600.17056

225,792

20-Mar-2014

04:02

x86

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File name

Amd64_3fda75fda23ba0de4f3e2cd02fa0c380_31bf3856ad364e35_6.3.9600.17056_none_4edb3a3331bbee80.manifest

File version

Not Applicable

File size

704

Date (UTC)

20-Mar-2014

Time (UTC)

08:59

Platform

Not Applicable

File name

Msil_microsoft.iscsi.target.commands_31bf3856ad364e35_6.3.9600.17056_none_158685cb46581091.manifest

File version

Not Applicable

File size

2,863

Date (UTC)

20-Mar-2014

Time (UTC)

04:37

Platform

Not Applicable

File name

Package_1_for_kb2953557~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

2,498

Date (UTC)

20-Mar-2014

Time (UTC)

08:59

Platform

Not Applicable

File name

Package_for_kb2953557_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

1,413

Date (UTC)

20-Mar-2014

Time (UTC)

08:59

Platform

Not Applicable

File name

Package_for_kb2953557_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

2,137

Date (UTC)

20-Mar-2014

Time (UTC)

08:59

Platform

Not Applicable


Status

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

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×