Deploy (i.e. download and by default install) the specified patch 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 in the form of a KB ID, not a low level GUID. (See example below.)
Should a list be supported so that mutiple patches can be deployed in one action?
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.
For each patch that was deployed: