HPC Pack 2012 R2 Update 3 scalability and auto grow shrink fixes

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

Management fixes
- Fix GUI freeze issue when there are lots of azure nodes, node templates in the system
- Fix perf counters may not collected issue when there are lots of azure nodes (serveral thousand)
- Bring the support on ARM deployed Azure IaaS nodes in auto grow shrink service
- Add "AzureOperations" in the Operations View so that admin can check the auto grow shrink script easily; The auto grow shrink logs will be purged after 48 hours
- Improved AzureAutoGrowShrink.ps1 script as below:
      1. Able to handle parametric task with millions of sub-tasks;
      2. Multiple azure batch operations on grow and shrink instead of one operation to prevent azure side throttling and blocked by one azure operation;
      3. Bring node online after successful azure deployment instead of bringing node online before node provisioning;

Supported Operating Systems

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

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. 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 (KB4032368-x64.exe for the 64-bit version, KB4032368-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\KB4032368-x64.exe -unattend -SystemReboot
      clusrun /nodegroup:BrokerNodes \\headnodname\HPCUpdates\KB4032368-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.5168.0