Deploy (i.e. download and by default install) either all available patches or specific patches to this device.
Should this be renamed to just "Deploy" because "Patch.DeployPatch" seems a little tautological?
Case is not significant.
For Windows, this is a comma-separated list of Knowledge Base article numbers. (See example below.)
What is the result if the patch is not available or not applicable to the device? Is that an error or just quietly ignored (so the method could return success-no-content)?
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.
Synchronous (asynchronous=false) patching with source SCCM is achieved by polling WMI as the CM client is totally independent of Tachyon and makes its own decisions. Tachyon requests the CM client to do something and monitors the progress to see whether the request has started and finished. There is a good chance that the installation will complete within the ten minutes allowed for 'synchronous' completion of this method, however Tachyon may decide that CM Client has taken too long and will report back that the timeout has occurred. The CM Client driven installation will however continue in the background though and the final status can be determined via Patch.ListUpdates using the appropriate PatchSpec.
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