Support Forum

Ah I see yea, a # sign sorry, reading comp was not my strong suit

Really, so what special chars did you originally have? That looks like I need to go look at how we pass the passwords.

Check build 4.0.0.62 to address the system not ready issue you are reporting below, as for a client failing rerun with new build to see if standard scan fails, Place scanner in debug mode before starting the scan by clicking the very top left corner (Blue with white squares image) while holding down...

Yea, thats an older plugin so does not automatically bring in scripts and such like our more recent plugins do. We need to circle back around to some of these older plugins and give them a good refresh.

Let me have a quick peek and I'll post back. Can you shoot over a screenshot of the error location?

Now looks for Mac, Linux and Windows
New build 1.0.0.6
Added Timer for command statuses
Fixes bug in OS determination request.

https://delivery.shopifyapps.com/-/a518 ... 284ee0629b

Ah the old oneies, twoies issue

i.e. - 1, 11, 2, 24, 3, 33, etc. vs 1, 2, 3, 11, 24, 33.

Hmm... lets see what we can do with that.

Build 4.0.0.40 released, fixed sveral issues with the CIM data collection and cleanups. Fixed issues with LT script not sending full command to local agent. LT truncated command causing the CIM data from not being outputted. Added new type field for HP servers, Type 30 error is now set as critical F...

Here is build 4.0.0.38,

Fixes issues where new probe failed to parse cim data. Install new plugin and restart the DBagent.

https://delivery.shopifyapps.com/-/2458 ... 4525de45ce

What version of Patch Remedy are you both using?

Reason, I can not duplicate that issue in .41 or newer

See images:


Missing Windows sorted by number of misses Critical Patches sort by date and number Hotfix issues sort by number