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

This update fixes some issues of HPC Pack 2012 R2 Update 3

• Fast Balanced Scheduling Mode
  Fast Balanced mode is a new mode in addition to Queued and Balanced mode. In this mode, cores are allocated to jobs according to their extended priority. Different from the Balanced mode which calculates balance quota among running jobs, the Fast Balanced mode calculate the balance quota among queued and running jobs together and the preemption in this mode happens in node group level and gracefully, so that it can achieve final balance state more efficiently.The Fast Balanced mode has some constraints on job settings. Non-compatible jobs will fail with validation error.. To enable the fast balanced mode you need to run below powershell cmdlet:
         set-hpcclusterproperty -schedulingmode FastBalanced
  
  This update fixes some known issue of HPC Pack 2012 R2 Update 3 as described as below
  
  HPC Pack fixes
  - Fix an issue which causes folder C:\programdata\Microsoft\Crypto\RSA\MachineKeys being filled up with temporary files
  - In a rare case, HPCSync may fail with Access Denied error when moving the extracted temp folder to the target. We handle it a bit nicer this time.
  - Make the hard coded 4 hour and 15 minute auto grow timeout into a configurable parameter GrowTimeout. The default value is 60 minutes. You can change it through below cmdlet:
         set-hpcclusterproperty -growtimeout <your_own_timeout>
  - Fix the issue that cluster manager keeps crashing after clicking “Node Templates” if there is un-approved node.
  - Fix the wrong display name issue in script ConfigARMAutoGrowShrinkCert.ps1.
  - The speed of selecting a node in the node list in HPC Cluster Manager is improved, especially when there are a large number of nodes in the cluster.
  - Now you can modify task commandline within job submission filter which is not possible before this fix.
  - Add command “hpccred listcreds” for listing credentials. Add parameter “owner” for command “hpccred setcreds” so that cluster admin could set credentials for other users.
  - Automatically recover the scheduler service in case the https server is faulted
  - Fix a memory leak in HpcBrokerWorker which happens when there are lots of requests.
  - Auto grow would count the online/OK nodes in the excluded node groups for the capacity check. E.g. if there are 2 online/OK nodes in the excluded node group and the queued jobs/tasks require 3 nodes, it would be possible to grow only 1 node for the workload.
  

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
KB4039431_x64.exe	53a7ad5a3307518ef12f6d588940a630761471fb	56.09 MB
KB4039431_x86.exe	5518af9f63c7a37511c32a574daa3567e02ccfff	56.02 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 QFE 3189996 (build 4.5.5161.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.5161.0 (or 4.5.5168 if KB4032368 installed, 4.5.5170 if KB4035415 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.
  
  Applying the update
  
  To start the download, click the Download button next to the appropriate file (KB4039431-x64.exe for the 64-bit version, KB4039431-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\KB4039431-x64.exe -unattend -SystemReboot
        clusrun /nodegroup:BrokerNodes \\headnodname\HPCUpdates\KB4039431-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.5187.0