Quantcast
Channel: Wsus Package Publisher
Viewing all articles
Browse latest Browse all 3825

New Post: Server 2016 with Win 10 clients - looks broken

$
0
0
I have a new environment with a 2016 Essentials Server and x86 / amd64 Windows 10 clients. While WSUS seems to run properly, the Package Publisher is not.

I have done all necessary steps: created and distributed the certificate, opened the Firewall and set the update policies.

I can send "detect now" and "report now" without errors, but nothing happens, the "last updated" value doesn't change - it remains the timestamp from where i locally searched for updates.

If I publish an update, also no errors are shown, but then also nothing happens. The id from the update doesn't show up in the update log (this function too is broken, you have to command get-windowsupdatelog in powershell to generate the log on the desktop). For some, it even says "installed", but it is definitively not.

I tried a custom update with a simple *.exe with doesn't do more than create a "helloworld.txt" in c:\windows, but on creation i got an "SQL Server error" and and of course, nothing happens. I tried to let it show in WSUS console, but it doesn't show up. The Updates are in the Folder "UpdateServicesPackages" in my WSUS folder, but it looks like they aren't called from the clients.

As much as I'd like to get it working - and so far that meant a lot of hours trying - it doesn't.

Viewing all articles
Browse latest Browse all 3825

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>