Support Forum

In all scripts we reference "%locationdrive%". This variable is auto generated by Automate when any agent runs script and "should" be a direct representation of the agents "location" drive settings for that Location.





Each location will have its own set of locations and drive credentials. If agent is not generating this information in the script then there is a problem with Automate. Make sure you can verify that the agent in questions current location falls with-in the configured parameters as see above.

Sorry, I miss read your last post. You are asking about "LTSVCDIR" variable not location drive variable. My confusion, but the same process stands. LTSVCDIR is a system and script variable that should be pre filled out for every agent that runs scripts.

This however is not uncommon and we have seen this issue before. Some script functions take the variable just fine where others may not.

The work around is to either simply replace variable with "c:\windows\ltsvc\" where ever its called or create a test at the top of script that tests for that location and if present set variable to that location.

This is how ever a Automate scripting issue and not a misuse of the variable or typo.

Looks to me like it is jumping there from Line
134: (IF %sqldatasetrowcount% = 0 THEN Jump to :NOSQLDATASET)
the line before that is:
133: (SQL Get DataSet) SELECT ID, RepoName FROM `plugin_p4a_chocolatey_applications`

If I run that command in Automate Database Commander, I get:

Didn't want you to think I was ignoring you, I am looking into this.

My problem is that the original 3.0 was meant to work against a pre determined list based on software matches found in installed software. C4A 3.5 is trying to breach the gap between that way of doing things and what is expected with a plugin set to interoperate with chocolatey.
Let me look over things in code base and see if we need to make a larger change to how operations are done. I am contemplating a rewrite based more on our latest works.

I'll post again tomorrow what I going to do.

Thanks... and just FYI, I am not sure if you are on the MSPGeek Slack channel any longer, but the advise SOME of them give is to avoid C4A due to:

- It’s very limited in configuration, typically you end up making every agent a standalone agent
- The P4A scripts also have a nasty configuration in all of them that they don’t rely on searches, groups, etc. they blast the script against all agents on 1 hour intervals for some of the plugins. The script then determines if it’s applicable or not.

^^ Which makes me think that since it is setup for the scripts to be "blasted against all agents in 1 hour intervals" (or even if it is 2hr intervals)... this seems like it can get VERY resource intensive against our agents AND our Automate server.
So I would suggest the ability to DEFINE the interval... maybe more often for machines that are not yet considered 'up to date' -- and less often for ones that are.

And the reliance on the Automate Sync service doesn't seem efficient at all... I should be able to test on one small location/site immediately to ensure everything is working.

Anyhow... I am willing to hang in there with you to see how this shakes out... hopefully we can get it functional and efficient.

Thank you for your perseverance!

Any updates?

Yes sir, working on some significant updates. I'll have some thing shortly.

Can you see the replies I sent for your 2 PMs?
I expected them to go to "Sent Messages" but they are still in "Outbox"

Any progress on this, Sir?