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
    7500+

Recent Profile Visitors

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

  1. @mikey090tx I haven't tried this yet but you are probably having problems if you run with just shell. You need to run shell as the logged in user. se the script function "IF Console Logged On". Leave the username blank, then tell it what label to go to if a user IS logged in like :loggedOn After your :loggedOn label, insert another line and use the script function "Console Shell", put your command in the command text box, then fill out the Console Number box with %consolenumber% (which now = the console number of the user detected to be logged in from step 1)
  2. I'm not too familiar with VBS but the fact that it doesn't run properly when pushed through Automate may have to do with how the agent is executing the script. When you run the code locally you are running it under your user account. Typically when Automate does it is running as system. You may want to save the vbs script to the local machine and run it as the logged in user using 'if console logged on' to grab the %consolenumber% variable and then execute your vbs by calling the cscript with Console Execute
  3. Thanks that is what I needed. Just in case someone else runs into this. I had some machines missing the iLO3/4 Channel Interface Drive and iLO3/4 management Controller Drive Package too which are required. So I added that to the insight install script too.
  4. It looks like the original file pulled from the HP ftp server doesn't exist anymore. Does anyone have an updated link for this?
  5. Make an alert template that runs a script as its action. Then have the script query to grab that additional information and creates the ticket.
  6. What detection role is everyone using for 2016? mine is {%_and|{%_eq|{%-HKLM\Software\Microsoft\ExchangeServer\v15\Setup:MsiProductMajor-%}|15_%}|{%_eq|{%-HKLM\Software\Microsoft\ExchangeServer\v15\Setup:MsiProductMinor-%}|1_%}_%} and seems to be applying to 2013 servers
  7. Doesn't seem to affect the plugin at all and everything works correctly. Just pops up every now and then. attached screenshot here
  8. Is anyone else having an issue in labtech 11 patch 8 with intermittent .net errors? I'm seeing unhandled exceptions referencing the RedFlag.uc_Computer.onLoadTime_Tick(Object sender. EventArgs e).
  9. I am getting the same error. Anyone know what the problem is?
  10. Its actually built into the control center under 'tools' -> 'options'. Then check the box under Debugging 'Display SQL Queries for development and debugging' That way you can see how the control center is querying the data.
  11. I went back and forth with LT support on this for a bit before figuring it out. You have to take your param and store it in a variable and then do the null check on the variable Example Paramater @maintenanceduration@ and stored it in variable @check@
  12. Here is a copy of the script we use when we use to migrate agents. Just import this to the lt server you are moving agents off of and change line 1 and 2 to match your target lt server address and password. When you run it you can set the target clientid and locationid as for where they should signup on the target server. https://aldridgeco-my.sharepoint.com/personal/cmatheson_aldridge_com/_layouts/15/guestaccess.aspx?guestaccesstoken=RdApZAZ%2fFzNsamEG%2f6HnYyQh%2fEocqtim9fQdlY%2fYcv0%3d&docid=0bd5d492bde02407da268cec1b8fb0ecd&rev=1
  13. This is correct. We have to do this all the time due to the number of acquisitions we've done that use labtech as well. Additionally, if you already have the client setup in your LT Server you can set the 'HKLM\Software\LabTech\Service\ LocationID' & 'HKLM\Software\LabTech\Service\ClientID' to match the clientid and locationid in your server so they signup in the appropriate place.
  14. Mathesonian

    Skype for Business

    post a screenshot. Remember when you are using the 'File Download' function that the 'ltshare\transfer' portion of the path is assumed. So, for example, if the path to the msi is 'ltshare\transfer\software\skype\skype.msi' then you would just put 'Software/skype/skype.msi' on the local file line.
×
×
  • Create New...