Jump to content

adelamora

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
    100+
  1. I was wondering if anyone else does this, but I am thinking of setting up a small form factor or micro PC to use as the Automate network probe, as well as the launchpoint for other services like Liongard Roar, Auvik, Network Detective (for onboarding), and even Veeam Backup and Recovery (for smaller clients). It would provide a secure place (separate from their domain) which we can use. Specs: 4 core CPU (i5 or greater) 16-32 GB RAM 500GB-1 TB SSD Does the network probe HAVE to be on a DC? What do I lose by not having it on a local DC? What do I lose by having my services non on a local domain? They will all be configured with the appropriate domain accounts, so I do not see a downside to that. They have wireless built in, so we can test wifi (if the MDF is within reasonable range/signal of wifi) The basis for this is that I am a bit tired of onboarding clients with such different environments, and having to squeeze in our services where ever we can. This would give us a platform for standardized onboarding/deployment, for only $500-1k per client. I think this is worth the cost, no? What have you done?
  2. adelamora

    Citrix PVS and LabTech

    This is one of the only references I have found to this issue, and it is still not a official part of labtech! Does anyone use this on Labtech 10.5 or Automate 11? I want to make sure this is still a working solution before we try it out. Thanks!
  3. So we have these nifty tabs to store passwords and licenses on a per-client, per-site basis. How can I access them in a labtech script? I was hoping to create simple scripts to apply licenses via windows command. Either to activate Windows OS, Office, or anything that has command line activation. Is this not possible?
×