LGarvin

I had actually closed the Snap-in, reopened it and refreshed every level and tab before I sent the screen shots just to be sure. Well, shucks, that's definitely not the expected behavior. I would suggest opening a support ticket on this so that we take a deeper look at that package logic,

When do they expire? Aug 27, 2017 Are they using SHA-1 or SHA-256? SHA-1 You should investigate this as a possible cause of the cert invalidation.

Three things I note from the PackageBoot log 1. The uninstaller is generating a reboot required condition. That may or may not be impacting the remainder of the operation. As previously noted, Ideally the installer will handle any required uninstallations. 2014/03/18 15:02:37:502 PID: 7040 TID: 6240 [INFO]…

In your original PackageBoot package you have enablemsilogging set to FALSE on the installer. Did you set it to TRUE to capture a log file? It's also disabled for the installer; please enable it and rerun the entire package. One of the possible considerations here is that it's th *installer* doing the uninstall and then…

can just be downloaded as a ZIP and dropped in a file location. Hmm.. that would complicate things a lot. That also means there's no guarantee as to the actual installation pathname. One would almost have to do a DIR /s /p | FIND /i "bash.exe" from the ROOT of every drive in that case. Were that the case, I'd say put that…

A screenshot might be helpfu ... at least to ensure I'm understanding what you're actually seeing.

Reporting on Patch Manager groups with respect to WSUS activities is not possible. Consider that all of the WSUS reporting data comes from the WSUS server based on what has been reported to the WSUS server by the WUAgent. The WSUS server and WUAgent know nothing about PM groups, so there is no way to correlate WSUS…

Why package state is different between the USS and the DSS? Because the update is not approved, and files are only downloaded for approved updates.

and then the package will see no java when it gets ready to install and it will fail. This somewhat depends on which package of JRE8 you're using to do the installation. If you are using the *upgrade* package, then the absence of JRE7 would certainly be problematic. But if you're using the *FULL* installer package, then…

When you say "You can then use the Computer Explorer -> Installed Software feature to select the line item for JRE7 and then target it to multiple systems (or even create a custom group to contain the machines that need JRE7 uninstalled) to uninstall JRE7". Are you referring to inside Patch Manager? Yes. Right click on a…

Does it matter that the update is not approved? Well, up until a few days ago I would have said no... but recent observations have determined that the Update Management tool will deploy an update that is Not Approved, if the binary is present on the WSUS server. In effect, the UM overrides the native behavior of the WUA.…

Those don't exist, so I'm resorting to what I can find. Sometimes that's what ya gotta do. :-)

if I make an amendment to RULES only to a package do I have to republish or not? You still have to republish, but you don't have to duplicate the package or manipulate anything on the WSUS side. When you publish a package that already exists on WSUS (based on the UpdateID), WSUS will automatically create a new revision of…

Yep. That's where I was headed. I'm baffled as to why this is not working correctly. Let me ponder on this a bit.

Thank you for the clarifications. The "NoAutoUpdate" value has absolutely nothing to do with where the client downloads updates from. If "NoAutoUpdate" is set to TRUE, the client will not update at all. At this point, I would suggest you review my series of blog posts on configuring the Windows Update Agent, as well as the…

That's an acceptable target, as it functionally gets you to the file you need to test (e.g. trillian.exe) However, since the Registry Value "DisplayIcon" contains the fully qualified pathname, you should leave Sub-Path empty. Sub-Path is only defined when you need to complete the relative path to the actual file when the…

I would suggest installing the April 2012 KB931125, enabling the Root Certificates Update feature, and then you should be able to install the SolarWinds SSL certificates. My educated guess is that you do not have the current Thawte Root CA certificate, and thus the requisite SSL certificates cannot be installed (i.e. are…

Not from a Patch Manager perspective. You're going to publish to the primary SUP, and any secondary SUPs will replicate that locally published content automatically. The advantage of such features are to support geographical distribution of CM clients and/or provide a more fault-tolerant SUP infrastructure for CM Software…

One reason I could see not sending a blanket uninstall command would be that you do not want the uninstall to occur if the Java 8 install has not yet happened. Okay, so build a Patch Manager Computer Group from a report of systems with JRE8 installed and target the uninstall task to the PMCG contaning known (and confirmed)…

The option "Install can request user input" has two fundamental impacts: * It allows the WUAgent to present UI to a logged on user. * It precludes the installation of that update in an unattended fashion -- which means that you cannot deploy such an update using Patch Manager Update Management or Update Management Wizard…

Have you seen this article? http://pitss.com/us/2013/02/20/how-to-use-java-7-with-oracle-forms-11g-in-an-oracle-supported-environment/

jmcsparin wrote: In answer to your other question about the console. I am RDP’d in to the Patch Manager server from my desktop. Would it make a difference if I was working directly on the console? Not necessarily. I just needed some context in how the package was being initially created and where the files were being…

The original version of this message was technically inaccurate on so many levels... all I can say is that my brain wasn't properly in gear when I wrote the part I've now struckout that is below. To be specific: The revision number of the update published IN WSUS has absolutely nothing at all to do with the revision number…

Would you have any other suggestions, I could try? Yes. Email me the MSI logs generated from the uninstaller (and installer, if one was) and the PackageBoot.log. SolarWinds Knowledge Base :: How to enable logging for PackageBoot issues (Email address is in my Thwack profile.) Is it actually possible to uninstall a program…

Until the client systems actually execute a detection and see the revised package in WSUS, the behavior will not change -- so Approving the update is still early in the full cycle of remediation. Once the WUAgent sees the revised package, it should cache the revision and apply that logic and report the package as…

I approved the package and still the same thing happens. I would suggest setting aside the concerns about whether the update installs at shutdown for now, and for the moment focus on whether the package is even installable at all. Is the package listed as "Not Installed" in the console for this system? Run a DETECTION…

I'd need to see exactly what you're doing, Andrew, in order to answer that question. If you want to export the package and email me the CAB I'd be happy to take a look.

But it not work, why? My apologies. I misunderstood. What do you mean by "it doesn't work"? As previously suggested, please remove the sample code from the PackageBoot Editor so the only thing that is there is YOUR code. Specify the command-line parameter using the special enviroment variable, %modulepath%, e.g. /c…

I'd be happy to chat with you on the phone. My email address is available in my Thwack profile. Feel free to email me and we can set up a time.

Ouch. That certainly complicates the applicability testing! Good catch, Justin! Hey.. no problem with the SpiceWorks post; that was actually a great place to ask the more generic question about file version attributes and managing that information. I just happen to be active in both communities. :-) What issues are you…