Jump to content

WesleyNZ

Members
  • Content Count

    75
  • Joined

  • Last visited

  • Days Won

    6

WesleyNZ last won the day on September 9

WesleyNZ had the most liked content!

Community Reputation

17 Good

My Information

  • Location
    NZ
  • Agent Count
    3000 - 4000 Agents

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To answer your question; The SYSTEM context doesn't resolve usernames. To fix it - just use a hardcoded path like C:\Users\Public (or c:\programdata)
  2. To troubleshoot this you should hit the remote CommandPrompt button and then just explore the variable yourself - by typing: ECHO %username% Then in the response you can see what went wrong.
  3. It sounds like you want something checked regularly - when scheduling a script you can already schedule this regularly. So it sounds like what you should do is delete that external monitor (optional) and do everything from your script, and then schedule this to your hearts content.
  4. Well, the good news is that you'll probably never forget now haha
  5. Just doubleclick it. Welcome to Automate.
  6. This stock script is perhaps a reasonable example. Change the top IF FILE CHECK to be IF TRUE and do yours similar.
  7. Check the solution center .. it should just overwrite it again when you download the related solution.
  8. I would only do reporting on the %scriptid% tho, not the name (names are not unique, but ID's are for sure)
  9. This should work from a script (every script already has %scriptid% populated) - to extract the name you then just: select scriptname from lt_scripts where scriptid='%scriptid%';
  10. Be sure to use the variable in your console command (this is your step2)
  11. The console command is actually a two-step thing. It's possible you missed the first step which is this:
  12. Once you get your tokens deployment working yeah you can use it to generate MAC clients all the same. Here's how we display the win and mac agent on each location (as well as an option to email the tech etc)
  13. This fixed the Enable script for me, keeping both lines active just in case (i added the top one)
  14. FWIW - You don't actually need to do your own counting, the command has it included for you:
  15. When you say single server, do you use Screenconnect (Connectwise Control)? If so, that'll be the first thing to move off the server and onto a seperate VM. The rest should be fine. You should be able to double your capacity before needing to split servers so maybe something else broke your installation.
×
×
  • Create New...