-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Please add support for using WSUS #28
Comments
Can you elaborate a bit more what the issue you're having with using xWindowsUpate to achieve those points ? |
I am not sure if this is a feature request or just confusion of current functionality. Looking through the examples/docs I am under the impression that setting a machine to use a local WSUS server as the source of patching is not currently available. Is that correct? |
Hi, Is there any new information regarding this request? We would also be interesed in using this resource for configuring our VMs to use a local WSUS server. Thanks! |
*This is not an endorsement and I have not used the following resource. I found this resource that might do what you need. https://pwrshell.net/powershell-desired-state-configuration-resources-for-wsus/ That is what we will look at when we get back to working on this for our setup. |
Great. Thanks |
We are using the xWindowsUpdateAgent resource to manage clients installing updates via WSUS. To get around the terminating error that FinickyCode pasted above, we modified the resource as shown below. To make this completely work, we use a Registry resource to set the needed registry values under "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" (see "https://docs.microsoft.com/en-us/windows/deployment/update/waas-wu-settings for the specifics") Here's the change needed for Test-TargetResourceProperties:
|
We want to use xWindowsUpdate and WSUS to patch our servers because:
The text was updated successfully, but these errors were encountered: