Support Forum

Hi There,

We have been using this plugin for a while now, but recently a site in LabTech only sees the DC, not any other PC at the site. Is there a way we can troubleshoot whats going on?

It sounds like the location is not executing the ADMON script on all agents. Have a look at each agent to see if the ADMON script was scheduled and if so what its output was? Some error?

If no scheduled scripts show up then try restarting the DBagent on the LT host.

Hi Cubert,

The scrips seems to be running on the agent, and the script says it ran successfully.

There should be outputs in the command and script sections showing what was returned by script. Can you post images of the command log during script run?

See image for what we need from logs.. ( we need to see what executed and what the return was.)

Hi Cubert,

Sorry for the delay, i got caught on something else. When checking the command page, i dont see the Execute Command entry for AdMon.

On the working machine i see an Invoke Script entry, and the results returned, teh failed machine is returning in a different language

Hi Cubert,

I am having the same issue as yardstick, however on the failed device it displays in English.

- Failed to create temporary file. Username: domain\username. Profile. folder not found. Validate user has previously logged into the system.

See screenshot:
I did some more investigations and this is down to the client location 'Deployments and Defaults' password in automate being a domain account. Plugin worked previously using. domain admin\user account.

Thanks

Hi Cubert,

We followed the steps in http://support.plugins4labtech.com/view ... 98373c3762

and changed the ADMON script to NOT run as admin, and it resolved the issue
We are in the process of changing over scripting to run from a service account, instead of running as our technician account. The sites running as a service account did not have a profile folder to store the temp files in, which caused the errors

Changing to shell run worked, or id imaging setting a static temp directory would have resolved this for us.

Hi yardstick,

Great to hear that resolved the issue. I would be making these changes to the 'run as admin' later on today. Can you please post a screenshot of what option you have set so others can follow and also any alternative solutions you have to make it more reliable.

Hi All,

If your having this issue please change the script - Admon Maintenance Service
Line3 to run as local system from 'Run as Admin'
Thanks All