frgpugs

Comments

  • Hey Steve, Im running .NET 4.7.1 on Server 2016 with PM 2.1.5. No issues
  • You can install them all on the same server, and ideally you would use an external SQL DB. I would also recommend just skipping the orion part of patch manager installation because its useless. Just my opinion here but just use the MMC console and forget the orion tab even exists.
  • This may not be totally helpful but Orion with patch manager is near worthless. I would not even attempt to look at or use anything in Orion with PM, just stick to the MMC
  • As far as I know you cannot, if automatic 3rd party updates are enabled you will get them all.
  • I would test one PC to see if its the check in. Go to one PC or RDP to one and run wuauclt /detectnow. Wait a few minutes to let it finish and then run wuauclt /reportnow. If it locks up the PC doing that you know theres a problem with the check in and if not the problem is elsewhere. I have not personally seen any…
  • There is a group called Managed Computers which gets populated via your discovery scans. Once its detected via discovery you can then "manage" it with patch manager. The WMI provider is now called client components. I distribute it by group policy but im sure there are other ways to get them installed. It will show up in…
  • One other thing to check is when you set up patch manager you can choose what products and classifications to sync. You may be getting offered things via MU that WSUS isnt offering because you dont sync them. Take skype for instance or maybe you left out .net or whatever.
  • You can go to patch management (not the patch management wizard), select the update you want and in the drop down choose uninstall. then just add all computers and voila. Im at home here but if you need some screenshots or more clarification I can get pictures when im at work.
  • I did it but I called a bat file as post action that called the ps1 file. Kind of a runaround but it worked
  • I dont use SCCM but both of those once they are published should be stored as packages that WSUS will deploy so the location shouldnt matter. What does the windowsupdate.log show?