![]() Once the WSUS sync is finished (watch WSUS console), kick off a SUP sync from SCCM console and review wsyncmgr.log for status. The upgrade also took a bit longer because I chose to check for updates, it was fine though since I went right to 10586.218, yay for cumulative updates. (THE SCRIPT WILL KICK OFF A WSUS SYNC as it's last step).ģ. Run the below script from elevated Powershell. ![]() Install KB3095113 and reboot on your WSUS/SUP server(s).Ģ. If you are still having sync issues you may have other issues with your WSUS or SUP set up which this blog will not address (SORRY).ġ. The script does take some time, but thankfully it does pipe out what it is doing. After running this script, I could sync “Upgrades” into SCCM successfully and had no sync failures. The below script takes his very cool script and adds those other editions. In the comments section of that blog, user GolfUMC gives us a more complete PowerShell script to do this. Their solution is to use PowerShell to delete all the old (Pre KB3095113) “Upgrade” updates from WSUS and initiate a new sync (of course after you have installed KB3095113). Thankfully, Microsoft released a fix to this issue. These issues prevent Configuration Manager to successfully sync with the WSUS catalog. ![]() Update takes long: the same as initial install of the Windows 10 upgrade from Win7 so you can take a beer or something else :) 6. Selected: keep all my Apps and User data 5. Started from the current Windows 10 from drive with Windows 10 version 10586 (1511) the setup. If you selected the update classification “Upgrades” in your Configuration Manager's SUP (Software Update Point) properties before installing update KB3095113, then you caused some issues in your WSUS catalog and SUSDB. Look for MSDN iso of Windows 10 version 10586 (1511). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |