Well, we are being cautious... We've upgraded our lab, using the manual steps, so far so good, there. But not prod yet. But if you go to the Microsoft wsus forum, you'll see lots of people with concerns. It's unclear on most posts if the issues are because they haven't done the manual steps.
But one post the person, with cm, clearly did the steps. And he had issues with wsuspool stopping. He upped some iis settings to resolve (but it is too soon to know if all is well), but still... Something to monitor at least, even after doing the manual steps. On May 12, 2016 3:46 PM, "Heaton, Joseph@Wildlife" < [email protected]> wrote: > Is the advice to not install the update, or just be aware that there is > post-install stuff that has to be done? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sherry Kissinger > *Sent:* Wednesday, May 11, 2016 12:58 PM > *To:* [email protected] > *Subject:* [mssms] WSUS Heads up > > > > Just a heads up. There's an optional update, > https://support.microsoft.com/en-us/kb/3159706 > > , which replaces KB3148812. > > > > > https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ > > > > Just be aware that as soon as you install KB3159706...your SUPs might > start having issues. For us, clients can't scan for updates successfully, > and WCM.log can't connect to your top level SUP. You have to go do the > manual post-install, post-reboot steps in > https://support.microsoft.com/en-us/kb/3159706 to get them working again. > > > > -- > > Thank you, > > Sherry Kissinger > > > My Parameters: Standardize. Simplify. Automate > Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, > http://www.smguru.org > > > >
