Deploy (i.e. download and by default install) either all available patches or specific patches to this device.
Case is not significant.
For Windows, this is a comma-separated list of Knowledge Base article numbers (without the "KB" prefix) or the GUIDs of specific patches, or even a mixture. (See example below.)
Case is not significant for the hex digits in GUIDs.
This does not apply to the SCCM source; the effect is that it is ignored.
This must be specified if
If the path is specified it must be to a local CAB-file. Shared, i.e. remote, CAB-files are not supported by Windows Update Agent.
Setting this to
This parameter is incompatible with
If the timeout occurs the install will continue in the background as though nothing happened but
It will be necessary to call List to determine the new state of the device.
|Return values||For each of the supplied patches or if not supplied for all available patches the following is returned:|
Updates will be performed only if they do not require user input. However, any license agreements are accepted automatically.
Windows may refuse to allow installations if a reboot is pending.
If no update information is available then the method will return success with no rows.
The method does not fail with an error if the
Patch Success uses 4 intructions, 1 from SLA inventory and 3 from the 1E-PatchSuccess product packs.
Patch Success uses this method it its 1E-PatchSuccess-Deploy instruction to cause a specific KB to be deployed. The instruction then returns one of the following results.
This method was called "DeployPatch" for a short time but never released with that name.