Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

0 Neutral

My Information

  • Agent Count
    3000 - 4000 Agents

Recent Profile Visitors

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

  1. Hi again, Figured it out not 20 minutes after posting. Seems you need to set the failMessage and successMessage variables to the data you want returned as well as returning your data that the check is to run against. Now all working as intended Cheers
  2. Hi all, We've recently made a few remote monitor based plugins for Automate to check on the status of a few things. However we seem to have an issue where whilst the monitors succeed/fail without issue, they never seem to save the result into the "Return Information" box. I've checked the database and confirm that is it also blank there. For example a monitor plugin I've made to check the status of a Virtual Server on Netscaler alerts when the returned data is not equal to "UP". This works. But instead of "DOWN" or whatever the returned data is being saved it instead has a bunch of spaces saved in its place. This is quite frustrating as we'd like to be able to read this information to pass it along to our alerts/tickets. Has anyone else come across this problem? Thanks
  3. Thanks to fullbrook on Slack for pointing out that a simple iisreset should resolve this. These are the steps I take now to load a plugin; 1) Ensure no scripts are running that can't be killed off safely. 2) Load/Update the plugin. 3) Open a Powershell window and use "Get-Content c:\Program Files)\Labtech\Logs\LTAErrors.txt -wait -last 20". This will give you a live view of the log as it updates. 4) Restart the DB 5) Monitor the log file in the powershell window and wait until it starts setting user permissions (something along the lines of "Perm User Admin:::") 6) Run "iisadmin" in an admin command prompt 7) Check IIS Work Processes to make sure agent check-ins and web requests are coming through and clearing.
  4. So this is kind of weird. In our dev environment the plugin will load and run fine however when I try to install it on Live it never seems to get the green check mark under "IIS Loaded". Shortly after all hell breaks loose and we're no longer able to login to Automate. Has anyone else experienced this?
  5. Is it just me or do parts of LT11s Patch Manager just not work? "Patch Job" always states "The selected device does not have any patch job information available" and clicking on a patch item in the dashboard applies a filter for something that doesn't seem to work.. or am I missing something?
  6. Sorry to reopen this but the above solution does not seem to work. LabVNC runs and causes TightVNC to fail.
  7. I've always had an issue with tunnels in Labtech. They connect just fine with a nice low ping but as soon as any data starts going through the ping goes through the roof and throughput is very slow. Am I missing a configuration somewhere or is this just how it's meant to be? Any redirectors going through it are practically unusable. (I'm on Labtech 10)
  8. After many hours of frustration I've finally got this to work. This will give you the full Powershell experience as if you'd used Enter-PSSession to access a server in your own LAN. (Requires Tunnels!) Name: Powershell Program: %windir%\system32\WindowsPowershell\v1.0\powershell.exe Arguments: -noexit -command "$cred = get-credential; enter-pssession localhost -port %LocalPort1% -credential $cred" LocalPort: 0 LocalIP: 127.0.0.1 RemotePort: 5985 RemoteIP: %RemoteIP% Socket Function: TCPLocalListen If you have the correct credentials set against the location you can use the following arguments to connect without having to manually enter them each time: -noexit -command "$secpasswd = ConvertTo-SecureString '%computerpassword%' -AsPlainText -Force; $cred = New-Object System.Management.Automation.PSCredential ('%computerdomain%\%computerusername%', $secpasswd); enter-pssession localhost -port %LocalPort1% -credential $cred"
  9. I found the "TunnelBasicBypass" property controls this. Setting this to True enables the behaviour I want. Thanks for your help
  10. Is there a way to force a "Basic" connection (ie not use a tunnel) on a redirector instead of turning off tunnels all together? I've always had speed issues with tunnels and have found that connecting with "Basic" to be much better for RDP and VNC. I know you can [Control]Click the redirector to do this but I'd like this to be default behavior. I managed to do this before in the past at a previous company and now I can't figure it out for the life of me!
  11. At my old employer I had a script that would run on patch day that created and set a new power profile that had settings that prevented the machine going to sleep due to being idle. A script would then run the next day to remove this profile and set it back to whatever it was set to previously. You could also try a scheduled task that triggers when it detects a shutdown event that runs a simple "shutdown.exe -a" to cancel it. I haven't tested this for when a user actually clicks shutdown, but I know it works when the shutdown command itself is used ("shutdown.exe -s -t 0" for example.)
  12. Would there be a way to use this to deny access to the Ignite tabs as well?
  13. Doesn't seem to work for all plugins. The Connectwise plugin for example. If I set that as disabled it still comes up for the user and if I check the permissions again it is not selected. I have noticed though that the ones it doesn't work for have no, what I guess you can call "internal" name next to the plugin name. I've attached a screenshot.
  14. * Process Explorer http://technet.microsoft.com/en-us/sysinternals/bb896653 * Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645 * Treesize http://www.jam-software.com/treesize_free/
×
×
  • Create New...