Support Forum

Beyond the powershell issues setting up for another client, the Expiry plugin is working for our local network which is my test bed. However, the threshold has been reached for a couple of users and instead of the beautiful HTML notice I created, their email notification only said, "The command...

Fixed an environment variable that did not include Powershell and allowed me to run the PoSh line check manually and returned 4. >powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -command $PSVersionTable.PSVersion.Major > 4 However, when running the script again, the result ...

Getting a Powershell error: The Script(6319) was successful in the Then section. Script: S6319 - Starting at Server Time: Thursday, June 06, 2019 1:12:19 PM IF F1 T: 1.417 L1 F129 Jump (P1): :WEARESERVER T: 1.417 L3 F139 Note (P1): :WEARESERVER T: 1.417 L4 F109 Delimiter (P2): Variable (P3): PoShVer...

I am running it on a hosted Automate 19 without issue.

I recommend the ScreenConnect RMM+Plus plugin to go with it. It helps with mobile devices that are not on the network so RPC calls will not work.

Having the same issue; although I have about 600 endpoints showing offline; 14 of which are listed with excessive commands.

Even if I highlight them all then right-click at title bar, it will only run on the last one in the list highlighted.

Online and working this morning!

Unable to import the DLL into labtech. "there was an error uploading the new plugin: could not load file or assembly 'Fil:///c:\users\\.....Temp\tempxxx.tmp" or one of its dependencies. operation is not supported. exception HRESULT: 0x80131515 Thoughts? I've gotten this before when instal...

Cubert! Save me!

I think I figured it out. I should have caught it sooner.

Instead of CN I should be using OU. Plugging in OU instead of CN and running the Get-ADUSer portion of the script, it worked fine.

Updated the plugin configuration and it worked.

Resolved!

Correct, Look in your LTagent folder on agent to see an expiry folder. Is there a PS1 file at c:\windows\ltsvc\expiryAD.ps1 ? If so open it an inspect it. It should be able "as admin" to create C:\windows\ltsvc\expiryAD.sql when executed. If it is not what error do you get when you run it...