Comments
-
Support case opened. I'll post the results. Thanks guys!
-
Thanks for the feedback George. These computers didn't reboot once even. I ran a PS script to verify last boot and it occurred last month during patching. So it still appears to be a failure of the reboot portion of the task.
-
You can highlight the WSUS server name under the patch manager interface. If the details tab is highlighted, scroll down to the bottom where it says "upstream server port". The other option is to open the IIS interface on the WSUS server and highlight the WSUS Administration site. On the right side under the actions pane,…
-
The patches were deployed. I am prompted with a reboot dialogue upon login. I tested the reboot action on one computer and it worked normally.
-
Hi jpregenzer, When I've had client issues I verify the following items. From the server not showing up, are you able to telnet to the port being used for WSUS communication (80, 443, 8530, 8531). This depends on which port you chose during configuration. If the telnet connection works, I like to use netstat on the WSUS…
-
I'm having this issue as well. It started out with scheduled tasks not completing. They would run for days and not time out as they should. This morning I opened the PM console and I can't view any of the groups or patches in WSUS. The WSUS server is running normally and the console there works fine. I'm assuming when…
-
I'll post the answer I received from support in case anyone needs the information. 1. Password length is the same as what is supported by Windows. 2. Credentials must be update manually using the credential ring wizard. No automation as this point. 3. This data is encrypted and stored in the DB and the local registry.
