We understand why you might not want to pull such a large file from the Internet once for each of your clients, and are figuring this out as soon as we can. Again, the workaround is to pull the 1607 feature update from Windows Update instead of WSUS. This is a newly reported issue that we are currently investigating. WSUS can sync/distribute feature updates (such as 1511), but cannot deploy the 1607 feature update The workaround here is to simply wait longer than usual, or to scan directly against Windows Update if you've waited several days and haven't seen any download success in that time.ģ. In the meantime, clients may experience some delay in getting the monthly content, but they will eventually download it. This is a bug in the Windows client that will be fixed in an upcoming cumulative update. Clients have upgraded to 1706 using Anniversary Update, but cannot get Cumulative Updates We'll choose a less disruptive strategy for future WSUS updates.Ģ. As folks have noted, these post-install steps caused unnecessary pain and confusion. WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs Note that Configuration Manager will exhibit the same symptoms as each of the scenarios below.ġ. This thread calls out several different symptoms, for each of which I'll provide guidance. "Hi everyone, and apologies for the frustration you're experiencing. Just a little bit more information as it looks like microsoft are at long last on the case as I have just found this:
0 kommentar(er)
