Aidan Finn, IT Pro

Considering how many people have downloaded my guide on how to build a Hyper-V cluster using the Microsoft iSCSI v3.3 target, I thought you might want to know about this new KB article from Microsoft: “Migrating iSCSI Target 3.3 settings before upgrading Windows Server 2008 R2 to Windows Server 2012”.

Consider the following scenario:

• You have a computer that is running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1)
• You have configured Microsoft iSCSI Software Target 3.3
• You start the upgrade of the operating system to Windows Server 2012.
• When you proceed through the Upgrade wizard, the compatibility report shows the following message: Installing Windows will affect the following features:
  Setup has detected that Microsoft iSCSI Software Target or Microsoft iSCSI VDS/VSS providers are installed on this computer. They will no longer function after the upgrade and configuration settings will be lost You must follow the instructions at <Link> prior to the upgrade to ensure they can continue to work after successful upgrade.

In this scenario, setup gives you a warning that, Microsoft iSCSI Software Target 3.3 or Microsoft iSCSI VDS/VSS providers may not be functional after the upgrade. It is best to uninstall the feature, then enable the feature after upgrade the server to Server 2012.

Cause: In Windows Server 2012, the Microsoft iSCSI Software Target and Microsoft iSCSI VDS/VSS providers are available as a built-in sub feature of the File and Storage Services Role.

Check out the original article for the solution.

Copyright Warning

This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.

Related posts:

1. KB2652137 – Communications Fail When You Use W2008 R2 Provider Package With WS2012 iSCSI Target
2. A WS2012 Hyper-V Converged Fabric Design With Host And Guest iSCSI Connections
3. How To Move Highly Available VMs to a WS2012 Hyper-V Cluster
4. Creating A WS2012 Hyper-V CSV Using VMM 2012 SP1 Via SMI-S
5. What The Hell Is WS2012 ReFS?