Legacy Update: Get back online, activate, and install updates on your legacy Windows PC

This update fixes SOA, Management and Azure burst issues of HPC Pack 2012 R2 Update 3.

• This update fixes some known SOA, Management and Azure burst issues of HPC Pack 2012 R2 Update 3:
  
  SOA fixes
  - Added SOA HoldUntil Support. For a SOA session, users can now pause a running session by modifying session job's HoldUntil property to a future time.
  - Fixed the possibly broker unload when the connection timeout happens between the broker and the client which may cause calculating requests discarded.
  - Updated EchoClient for random message size and time; add flush per number of requests support; add message operation (send/flush/EOM/get) timeout parameter.
  - Added two optional parameters jobName and projectName in ExcelClient.OpenSession method for Excel VBA.
  - Other bug fixes around stability and logging for SOA.
  - Fix node exclusion too long for SOA jobs: Finish task when exit call failed.
  
  Scheduler fixes
  - Carry hresult on node manager exception for better troubleshooting of node manager exceptions.
  - Linux node manager execution filter support.
  - Fix the task dependency issue that a job could be stuck in running state if a task is added and its dependent parametric sweep task is in running state with some finished sub-tasks.
  - Improve the performance of scheduler by decreasing the validating time of a job which contains a large number of tasks with task dependency.
  - Fix the issue that node release task may fail if the job resource type is “Socket” or “GPU”.
  
  Management fixes
  - Add JobId in HpcTask object for powershell, so user can get JobId in cmdlet Get-HpcTask.
  - Enhance HpcSync.exe command, if no package to sync from Azure storage, exit with 0 instead of -1.
  - Fix one issue to let user set SubscribedCore and SubscribedSocket for GPU compute node.
  - Support running SOA job for Azure PaaS deployment using internal load balancer.
  - Fix one UI bug, when select “By Node Template” in node view, if click “Add Node”, it will be failed and popup error dialog.
  
  This QFE will supercede QFE 3134307 and QFE 3147178 released earlier
  

Files

Status: Live This download is still available on microsoft.com. The downloads below will come directly from the Microsoft Download Center.

File	SHA1 Hash	Size
KB3161422-x64.exe	5064e748e5e9e701c39b480f39efe6b5dc76be77	61.55 MB
KB3161422-x86.exe	3fa1b0cf56fa4c3525c664123b2d6526cb9e1d1e	61.49 MB

File sizes and hashes are retrieved from the Wayback Machine’s indexes. They may not match the latest versions of files hosted on Microsoft servers.

• HPC Pack 2012 R2 Update 3 (build 4.5.5079.0) with or without QFE 3134307/3147178 (build 4.5.5094.0/4.5.5102.0) installed.

• This update needs to be run on all head nodes, broker nodes, workstation nodes, compute nodes and clients
  
  Before applying the update, please check if HPC Pack 2012 R2 Update 3 is installed. The version number (in HPC Cluster Manager, click Help>About) should be 4.5.5079.0 (Or 4.5.5094.0/4.5.5102.0 if early QFE is installed). Please take all nodes offline and ensure all active jobs finished or canceled. If there are Azure nodes, please make sure they are stopped before applying this patch. After all active operations on the cluster have stopped, please back up the head node (or head nodes) and all HPC databases by using a backup method of your choice.
  
  Important:
  The upgrade package KB3161422 does not support uninstallation. After you upgrade, if you want to restore to HPC Pack 2012 R2 Update 3, you must completely uninstall the HPC Pack 2012 R2 Update 3 features from the head node computer and the other computers in your cluster, and reinstall HPC Pack 2012 R2 Update 3 and restore the data in the HPC databases.
  
  Applying the update
  
  To start the download, click the Download button next to the appropriate file (KB3161422-x64.exe for the 64-bit version, KB3161422-x86.exe for the 32-bit version) and then:
  
  1. Click Save to copy the download to your computer.
  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 high availability 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.
  4. Log on interactively, or use clusrun to deploy the fix to the compute nodes, broker nodes, unmanaged server nodes, and workstation nodes.
  To use clusrun to patch the QFE on the compute nodes, broker nodes, unmanaged server nodes, and workstation nodes:
  a. Copy the appropriate version of the update to a shared folder such as \\headnodename\HPCUpdates .
  b. Open an elevated command prompt window and type the appropriate clusrun command for the operating system of the patch, e.g.:
  clusrun /nodegroup:ComputeNodes \\headnodname\HPCUpdates\KB3161422-x64.exe -unattend -SystemReboot
  clusrun /nodegroup:BrokerNodes \\headnodname\HPCUpdates\KB3161422-x64.exe -unattend -SystemReboot
  Note: HPC Pack updates, other than Service Packs, do not get automatically applied when you add a new node to the cluster or re-image an existing node. You must either manually/clusrun apply the update after adding or reimaging a node or modify your node template to include a line to install the appropriate updates from a file share on your head node.
  Note: If the cluster administrator doesn’t have administrative privileges on workstation nodes and unmanaged server node, the clusrun utility may not be able to apply the update. In these cases the update should be performed by the administrator of the workstation and unmanaged servers.
  c .To update workstation nodes and unmanaged server nodes you may need to reboot.
  
  5. To update computers that run HPC Pack client applications apply the following actions:
  a. Stop any HPC client applications including HPC Job Manager and HPC Cluster Manager
  b. Run the update executable
  c. Reboot your client computer
  
  6. You can run get-hpcpatchstatus.ps1 on headnode/computenodes/client under %CCP_HOME%bin to check the patch status. And the client version and server version will be 4.05.5111.0
  
  7. To update on premise Linux compute nodes:
  a. Set up a file share to share update binaries from head node to Linux compute nodes , for see Get started with on-premises Linux compute nodes).Here we suppose we have established an SMB share C:\SmbShare on the head node as \\headnodename\SmbShare, and mount it on all the Linux compute nodes with path /smbshare.
  b. Find the on-premises Linux compute node installation binaries in the following folder: %CCP_DATA%InstallShare\LinuxNodeAgent. Then, copy the binaries hpcnodeagent.tar.gz and setup.py into \\headnodename\SmbShare in the head node, and check that the files can be seen in the path /smbshare from the Linux compute nodes.
  c. Run update command on the Linux compute nodes in the /smbshare with HPC 2012 R2 Update 3 nodemanger (version 1.7.7.0), e.g.:
  python setup.py –update
  d. (Optional) You can check whether the Linux compute nodes have been updated successfully by using command “/opt/hpcnodemanager/nodemanager -v” on the Linux compute nodes. The updated nodemanager version is 1.7.7.0.