frgpugs

It fits me and I would be happy to talk with you, however, I did not find orion useful so I dont really use it if that matters.

Nicole i posted here regarding the applicability rules for DC problem im having. Im not sure if anyone else is having the problem yet but I have always patched reader from SPM so it seems a little odd to me. Reader DC?

Thank you!

You can also view any created inventory (and other) tasks in the scheduled tasks section under administration and reporting. You can edit them from there as well

Oracle can manage it when its installed via the website. It makes sense to by DEFAULT uninstall any old java versions and if people need to keep certain computers not getting updated they can create a target group that does not get java updates approved. Every time there is a java update I go in and edit the package, put…

Awesome to see Patch Manager getting some love from SW!

Solarwinds: Patch Manager Other: Whats Up Gold The Dude Icinga Wireshark

I would do it via PDQDeploy. Put the package on a network share somewhere, make a powershell script to install it, and then push that out with PDQ. I dont see any way to do it with solarwinds until they support powershell.

Yep the difference here is going to be console targeting or client side targeting. We use console targeting so that wont work for us unfortunately. Good info for everyone to know though

When you right click on an update and select approve you will get this window that lists your target groups. I also have a no java updates group and I just dont approve it for that group. I leave my default view filtered to not show the updates in the no java update target group as well but dont worry about that I dont…

At this point ill suggest contacting solarwinds support because im not sure what you are trying to do. Also if you dont know how to use or create an active directory account they may be the better place to ask.

You add it in as a task in the packageboot.xml. The one thing to know about that is it only removes out of date from the security baseline. The security baseline may leave a version or two previous. Just so you don't see it not remove the most recently previous version and think it doesn't work.

I cant believe i didnt think of that, thats a great way to do it. For whatever reason I always just did the 1 previous version. Man I feel stupid lol

This is old but in case anyone else wants to do this I found my problem awhile ago I use console targeting and manually move computers into target groups and automating updates this way into a deployment is not easily doable. Ive tried to follow the tutorials that hack the MDT scripts which allow the functionality but I…

Oh! Ok it makes sense now. No I have never had that problem, it takes a second or two to create the group. It does not communicate with AD as far as I know. You can create the groups in the WSUS console and see if you get the same behavior, because that is where patch manager is actually creating those groups in and then…

I guess I cant be 100% sure when they get provisioned but it always seemed to get them before I had inventory or discovery set up yet. I suppose a check for updates could be considered running a task against it? I dont know, whatever, do what you need to do

Thats wierd. Does it install on another PC? Can you delete the update and republish and approve it. I believe the error means there is something wrong with the 7zip package. If deleting it from the local store didnt clear the error then maybe its an error with the actual package? Of course I could be wrong about…

So on your WSUS server, if you are using a WID, you just open SQL management studio and connect to the DB. The name of the connection is fun, its \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query Then you just put the script in a query window and execute it. It should default to the SUSDB in the drop down but if not just choose…

right click on the package you want to change and select edit Then click next a few times until you get to the packageboot screen. Youll want to click where the arrow shows for i already have the file and select the update you want to include in this package. Then just click next and publish it.

nope its just the 1 additional adobe catalog. I never paid much attention to settings but ive never had any users complain so i assume it keeps them. Get the catalog and have a look to see whats in it

Nope, its PDQ Deploy. https://www.pdq.com/pdq-deploy/ Its really great software. I use PDQ deploy and PDQ inventory and pay for both but the free version does a lot

It looks right. This topic has been beaten to death on this forum. Maybe this thread could help? Remove old versions of Java 8

Do you mean a WSUS target group? That would work if I used one container for all machines but I have them broken out into groups already for test group, no java, etc.

Go to approve, then select which groups to NOT APPROVE from there, or select the parent as not approved and then choose same as parent for all other target groups

right but is that 8u45 x64, 8u45 x86, 8u45 x86 for x64, 8u45 x86 (upgrade), 8u45 x64 (upgrade)

That IS strange. You should be able to mass uninstall through patch manager as well. If you go to the update management window and change it from install to uninstall, then add whatever update you want to remove it should get rid of them. Still cant explain why its working on some and not others, ive always had it work.

The way patch manager works is you attach it over the top of your WSUS server and then patch manager also can import other catalogs for third party software like the solarwinds catalog which contains most of the available third party updates or the adobe catalogs. When there is an update available in those catalogs WSUS…

Im not really sure. Its a pretty straightforward process most times. You get the cert from GPO, then WU installs the WMI provider. I would suspect that WU GPO you have is not working right but I dont know group policy well enough to even look at it and tell. Have you published the WMI provider in patch manager and assigned…

The removeoutofdatejres is added in the Apply Package run jre-8u112-windows-i586.exe under command line parameters. Like I said earlier though, it only removes versions outside of the security baseline so if you have 8u101 or 8u102 it will probably leave those installed as they are still in whatever Oracle has determined…

yeah it could be that, i dont KNOW for sure, its just a guess because its not working at the moment. Ive had things in the past where just flat out a registry value would not detect as applicable but a file version would, or a file version wouldnt work and only the MSI product code worked. Its very picky at times to make…