After further re-thinking, there are three issues here:
-
first, the "show Update Log" - that is definitively broken inside WSUS Package Publisher. That command should be changed to create the log first, and after that command returns display the file - see above.
-
second, the RPC commands. This can be an firewall issue, so I'm going to test that again with all firewalls down. I set all the rules I could find and WPP shows "OK" after executing the command, but it's worth a try.
-
third and most important, why doesn't my Win10 1607 clients don't detect either the custom updates nor the msi updates? This question can be broken up into multiple parts:
- is the update really advertised? My version info says Update Services 10.0.14393 - so the "publish" can simply failing. I have all my clients upgraded to that Win10 version, so unfortunately, I can't test it with an earlier Windows version myself. The "publish visible on WSUS console" is broken, there I get that SQL server error.
-
or is it a question of Win10 - it is advertised, but doesn't get sought out for installation. I don't know how the Windows Update works inside, which side picks what is to update.