Support Forum

Interesting OK, From logs... It looks like the following is being triggered. LTAgent v240.146 - 5/15/2024 12:05:48 AM - Plugin PatchRemedy, Version=1.0.5.18, Culture=neutral, PublicKeyToken=null: (Windows Update Assistant) Service Disabled.::: Here is where we test for disabled services and exit sch...

Sounds like you have a stuck DLL on your local PC.


Here is how to fix.

viewtopic.php?t=5523

Also let us know if any of the searches or scripts are not where images show they should be in the folder structure for searches and scripts.

Make sure you on lates version 3.6.0.11, Next, it sounds like your install of Chocolatey failed to couple the groups with their search scripts and maybe even the scheduled script tasks. This is a problem and will prevent services from working and is not by design. Automate likes tossing us curve bal...

Yes, There are server level logs at C:\Program Files\LabTech\logs\plugin_patch_Remedy.log This is where Automate stores all the automation requests the plugin makes. We log when schedules are fired off so if it was attempted, it would show here. Was this scheduled same day or did you schedule it out...

If you add a key, We will enable encryption, you can see it in the error you provided.


outside of adding a protector, Disable/enable button should send a request to bitlocker to enable or disable.

We do not provide a way to ignore certain updates in Patch Remedy. Patch Remedy was designed to be a stark reminder of where your agents are at in the realms of updates and security fixes. Even drivers can have exploits, neglecting drive updates could allow for kinks in ones armor just as any other ...

That's the kicker, MFA expects to interact with a user to provide additional authentications. As a scripted automation, it does not have this ability. MFA is not a supported feature of this plugin.

It's always plausible that Microsoft has changed something in the authentications recently.

Give me a day to research and test our plugin in house to see if there is something that has changed in the process.

We released build 2.0.0.6

A small bug fix when excluding an agent fails to engage. We resolved a bug where when selecting to exclude an agent it would fail to be excluded.