HPC Pack 2012 R2 Update 1 Fix for Task Dependency issue

This update fixes below issue with the job scheduler in HPC Pack 2012 R2 Update 1.

*Task Dependency incorrectly created in some cases when new task is added when the job is running.

Supported Operating Systems

Windows 7, Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2

Windows Server 2012, Windows Server 2012 R2 with HPC Pack 2012 R2 Update 1 (build 4.3.4562.0) installed and updated to QFE KB3073419.

This update needs to be run on all head nodes

Before applying the update, please check if HPC Pack 2012 R2 Update 1 and KB3073419 is installed. The version number (in HPC Cluster Manager, click Help>About) should be 4.3.4673.0. Please take all nodes offline and ensure all active jobs finished or canceled.

Applying the update

To start the download, click the Download button next to the appropriate file KB3149958.exe and then:

1. Click Save to copy the download to your headnode.
2. Close any open HPC Cluster Manager or HPC Job Manager windows.
Note: Any open instances of HPC Cluster Manager or HPC Job Manager may unexpectedly quit or show an error message during the update process if left open. This does not affect installation of the update.
3. Run the download on the head node using an administrator account, and reboot the head node.
Note: If you have HA head nodes, run the fix on the active node, move the node to passive, and after failover occurs run the fix on the new active node. Do this for all head nodes in the cluster.

Uninstalling the update

Before uninstalling the update,
1. Take all compute nodes, workstation nodes, and unmanaged server nodes offline and wait for all current jobs to drain

To uninstall the update, in Control Panel, click Programs, select View installed updates, and double-click HotFix KB3149958 for Microsoft HPC Pack 2012 R2 Update 1.
Remove the update for Microsoft HPC Pack 2012 R2 Server Components.
Note: If you have high availability head nodes, uninstall the update on all passive head nodes, move a passive head node to active, and then uninstall the update on the previous active head node.