HPC Pack 2016 Update 1 fixes

This update fixes some known issues of HPC Pack 2016 update 1 as described below

- Fix an issue caused local user can’t be created on non-domain joined compute nodes in a domain joined cluster;
- Add ability to read common data through Azure Blob Storage to non-domain joined compute node;
- Fix an Azure IaaS node deployment failure due to deployment template file not found in HA cluster;
- Support operating system with French for broker/compute/workstation node;
- Allow the node action “Maintain” for domain joined Azure IaaS nodes;
- Linux extension is updated, the “Linux not showing up in Azure” issue is resolved;
- Add option to disable the windows compute node from syncing hpc cluster admin to local administrator group, to do this, you need to add following value on the target node under registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HPC
      Name: DisableSyncWithAdminGroup
      Type: REG_DWORD
      Data: 1

Installation Instructions
This update needs to be run on all head nodes, broker nodes, workstation nodes, compute nodes (Windows and Linux), Azure IaaS nodes and clients

Before applying the update, please check if HPC Pack 2016 Update 1 is installed. The version number (in HPC Cluster Manager, click Help->About) should be 5.1.6114.0. Please take all nodes offline and ensure all active jobs finished or canceled. If there are Azure PaaS 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.

To start the download, click the Download button next to the appropriate file (KB4342793_x64.exe for the 64-bit version, KB4342793-x86.exe for the 32_bit version) and then:

Applying the update on Single Headnode
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;
4. The version number (Start HPC Cluster Manager, click Help->About) now should be 5.1.6125.0;
5. If you want to revert the patching, please go to Control Panel -->Programs and Features -->View installed updates, un-install below updates in order (Please don’t reboot in the middle): KB4342793 under “Microsoft ® HPC Pack 2016 Web Components”, “Microsoft ® HPC Pack 2016 Client Components” and then “Microsoft ® HPC Pack 2016 Server Components, then reboot;

Known Issue: During patching sometime "HPC Web Service" may stuck in "Starting" status as its dependency HPCScheduler Service is not started. You may need to manually start the HPCScheduler service so that the patching will continue. We will address this issue in Update 2.

Applying the update on Three Headnodes
Note: If you have at least three head nodes, you need to download HpcApplicationType.sfpkg and Upgrade-HpcApplication.ps1 as well and put them together on one of the headnode, for example, c:\5.1.6125.0. And run through below steps:
1. To upgrade service fabric application, please open an elevated powershell command prompt window, run:
       Upgrade-HpcApplication.ps1 -ApplicationPackagePath C:\5.1.6125.0\HpcApplicationType.sfpkg
2. After the service fabric application upgrade done, you then need to run theKB4342793_x64.exe on headnode one by one;
3. Reboot the headnode one by one (Please check https://localhost:10400 to make sure the original reboot headnode back to health state before you reboot a new headnode, so that your service will keep available);
4. The version number (Start HPC Cluster Manager, click Help->About) now should be 5.1.6125.0 on all headnodes;
5. If you want to revert the patching, for every headnode please go to Control Panel --> Programs and Features --> View installed updates, un-install below updates in order (Please don’t reboot in the middle): KB4342793 under “Microsoft ® HPC Pack 2016 Web Components”, “Microsoft ® HPC Pack 2016 Client Components” and then “Microsoft ® HPC Pack 2016 Server Components; then downgrade service fabric application through below command;
       Connect-ServiceFabricCluster
       $hpcApplication = Get-ServiceFabricApplication -ApplicationName fabric:/HpcApplication
       $appParameters = @{}
       foreach($appParam in $hpcApplication.ApplicationParameters)
       {
       $appParameters[$appParam.Name] = $appParam.Value
       }
      
       Start-ServiceFabricApplicationUpgrade -ApplicationName fabric:/HpcApplication -ApplicationTypeVersion 1.1.1 -ApplicationParameter $appParameters -HealthCheckStableDurationSec 60 -UpgradeDomainTimeoutSec 1800 -UpgradeTimeout 3000 -FailureAction Rollback -Monitored | Out-Null
You can run "Get-ServiceFabricApplicationUpgrade -ApplicationName fabric:/HpcApplication" to track the upgrade status. If you find it is stuck at "PreUpgradeSafetyCheck" due to some service fail to cancel, you could try to manually kill the corresponding process on the right node. When if finished, reboot headnode one by one (you need wait the original rebooted node fully healthy in the service fabric cluster before you reboot the next one.

You can open "Service Fabric Explorer" at "https://localhost:10400" to monitor the service fabric cluster upgrade progress (You need to import the pfx certificate used during cluster setup to CurrentUser\My to avaid HTTP 403 error). There is little possibility that some service is stuck on the headnode during patching. If that happens, you could manually kill the process on that node.

Applying the update on Windows nodes
1. Log on interactively, or use clusrun to deploy the fix to the compute nodes, broker nodes, unmanaged server nodes, Azure IaaS nodes and workstation nodes;
If you want to use clusrun to patch the QFE on the compute nodes, broker nodes, unmanaged server nodes, Azure IaaS 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\KB4342793-x64.exe -unattend -SystemReboot
             clusrun /nodegroup:BrokerNodes \\<headnodname>\HPCUpdates\KB4342793-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.
2. If you want to revert the patching, please go to Control Panel --> Programs and Features --> View installed updates, un-install below updates in order (Please don’t reboot in the middle): KB4342793 under “Microsoft ® HPC Pack 2016 Web Components”, “Microsoft ® HPC Pack 2016 Client Components” and then “Microsoft ® HPC Pack 2016 Server Components, then reboot;

Applying the update on Linux nodes
1. For 3-headnode Cluster, download and Copy “hpcnodeagent.tar.gz” to the remote install share of the HPC Cluster (Default should be \\<HN>\REMINST\LinuxNodeAgent ); while for single headnode cluster, this package will be replaced during headnode patching. Thus please back up the existing one so that you could downgrade to original version
2. Mount the share on linux node (Suppose you already created /mnt/share on all linux node):
       Clusrun /env:CCP_MAP_ADMIN_USER=0 /user:system /NodeGroup:LinuxNodes mkdir /mnt/share ^& mount -t cifs //<yourheadnode>/REMINST/LinuxNodeAgent /mnt/share -o vers=2.1,domain=<domainname>,username=<username>,password='<password>',dir_mode=0777,file_mode=0777
3. Clusrun with root on all linux node to update the package:
       Clusrun /env:CCP_MAP_ADMIN_USER=0 /user:system /NodeGroup:LinuxNodes /workdir:/mnt/share echo “python /mnt/share/setup.py -update” ^| at now + 1 minute
4. Wait for clusrun completion and the real update will start in a minute on the linux node; After the update completes, you can run Clusrun command to check the linux agent version by running below command (the version now will be 2.3.5.0):
       Clusrun /env:CCP_MAP_ADMIN_USER=0 /user:system /NodeGroup:LinuxNodes /workdir:/opt/hpcnodemanager ./nodemanager -v
5. If you want to revert back to the original linux agent version, you could restore the "hpcnodeagent.tar.gz" to the old version and apply the same above steps;

Applying the update on Linux nodes on Azure
If your linux node is on azure and deployed through our ARM template, the linux node will update its Linux Agent Extension automatically.

Applying the update on Client
1. 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;
2. If you want to revert the patching, please go to Control Panel --> Programs and Features --> View installed updates, un-install KB4342793 under “Microsoft ® HPC Pack 2016 Client Components” then reboot;