You are using an ad blocker that is interfering with our web typography and internal javascript. Please whitelist our domain to live in a more beautiful world. No ads here, just really great software!

Nexthink helps you deliver a great experience to employees working from anywhere. Learn More

cookie alert

We use cookies to offer you a better browsing experience, analyze site traffic, personalize content, and serve targeted advertisements. If you continue to use this site, you consent to our use of cookies.

Nexthink Library

Windows Update

Latest Version: 1.0.0.0
Install

Required Products

Nexthink Act

Platforms

Windows 7
Windows 10

Compatibility

V6.14 and later

Description

This Library pack is a collection of different Remote Action scripts which help improve the compliance level by ensuring that the latest security updates have been installed.Please use the links on the left menu to learn more about the function and range of action of each script.

Versions

  • 1.0.0.0 - 05 Dec 2019 - Initial release

Get Last Feature Update Status

Script Description

Retrieves the local date, the installation status and the name of the Windows Feature Update that was most recently processed on the device.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 120 seconds is recommended.

Parameters

None.

Outputs

Label Type Description
Installation Date DateTime Local device time of the last Windows Feature Update installation attempt
Installation Status String Result status of the last Windows Feature Update installation attempt. Possible values are: 'Unknown', 'InProgress', 'Succeeded', 'SucceededWithErrors', 'Failed', 'Aborted'
Feature Name String Full name of the last Windows Feature Update processed on the device

Restrictions

Get Windows Feature Update Diagnosis

Script Description

Executes Microsoft tool SetupDiag.exe, that process Windows Feature update log files and returns a list of possible failure reasons or upgrade confirmation.For further information regarding SetupDiag.exe please visit this link.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 1020 seconds is recommended.

Parameters

Label Description
Maximum Delay In Seconds Maximum random delay set to avoid overloading server hosting virtual machines. Provide number of seconds less than 600
Setup Diag Path Absolute path to the location of SetupDiag.exe tool on target device. For example "C:\temp\SetupDiag.exe"

Outputs

Label Type Description
Total Matching Reasons Count Int Total count of matching rules detected by SetupDiag.exe tool
Matching Reason List StringList A list of matching rules with detailed description that may assist with further investigation

Restrictions

Further Information

Depending on the size of the Windows Update log file, investigation time may vary. With a log file of a total size of 160MB, processing lasts around 5 minutes.

Install Windows Update

Script Description

Using Windows Update Standalone Installer (wusa.exe), performs .msu patch installation from a given either URL or UNC path.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 1200 seconds is recommended.

Parameters

Label Description
Maximum Delay In Seconds Maximum random delay set to avoid network overload. Provide number of seconds lower than 600
Hotfix Source Provide URL or UNC path to retrieve the msu file. Example values: http(s)://domain/folder/windows6.1-kb4503292-x64.msu, \\server\SharedFolder\windows6.1-kb4503292-x64.msu

Outputs

Label Type Description
Reboot Required Bool Whether the patch requires device reboot or not

Restrictions

Further Information

In case of you want to install a specific patch on several devices, it is recommendable to download and share it over the internal network.
If you want more information about Servicing stack updates, please visit this link.
To get the URL for a KB patch follow these steps:
* Go to Microsoft Update Catalog.
* Search for target KB.
* Click on Download button
* Copy link from popup menu and set HotfixSource parameter value with it.

Test Scenarios

TestNonMsuFile
Test Case Trying to install a non .msu file
Environment VM Windows 10 x86/x64 several languages, VM Windows 7 x64 several languages
Results Failure - Only MSU files can be installed
TestMsuFileForx86Devices
Test Case Trying to install x86 hotfix on devices with x86/x64 devices
Environment VM Windows 10 x86/x64 several languages, VM Windows 7 x64 several languages
Results Success on x86 devices and failure on x64 as that patch is not available for that architecture
TestAlreadyInstalledPatches
Test Case Trying to install hotfixes which are already installed
Environment VM Windows 10 x86/x64 several languages, VM Windows 7 x64 several languages
Results Success - Remote Action returns the hotfix was already installed
TestSuitablePatches
Test Case Trying to install hotfixes which were available to be installed
Environment VM Windows 10 x86/x64 several languages, VM Windows 7 x64 several languages
Results Success - Hotfixes are installed and they required device reboot. (Exit code 3010)

Invoke Windows Update

Script Description

ADVANCED SCRIPTRestarts Windows Update service and starts BITS service (if needed). It forces the device to scan for system updates. The script is designed for Windows 10 and 7.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 720 seconds is recommended.

Parameters

Label Description
Maximum Delay In Seconds Maximum random delay set to avoid virtual environment and network overload. Provide number of seconds less than 600

Outputs

None.

Restrictions

Further Information

Parameter 'MaximumDelayInSeconds' can be used to add random script execution delay. It should be used to spread over time number of I/O requests on server hosting virtual machines and reduce network workload.

Test Pending Reboot

Script Description

Script retrieves information if device is pending reboot and the reason. Possible causes covered are as follow:

   * Computer renaming.
   * Domain join.
   * File rename operations.
   * SCCM Agent.
   * Software installation.
   * Windows update.

Execution context and suggested scheduling

Run the script as 'local system'. The script should be executed manually.

A timeout of 120 seconds is recommended.

Parameters

None.

Outputs

Label Type Description
Pending Reboot Bool Device is reboot-pending (Yes/No)
Pending Reboot Reason String All detected reasons for reboot-pending
Thank you!