Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

My Information

  • Location
  • Agent Count


    Gaming and reading.

Recent Profile Visitors

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

  1. Yup, you covered that case perfectly, just wanted to get the other method out there in case it was his end goal. ALL THE SOLUTIONS!!
  2. I thought the monthly health report only counted stats from the last ~30 days from the h_extrastatsdaily table. Not 100% sure on the backup part though.
  3. If it were me I wouldn't do the DriveID exception as it is a one off solution that would need to be done each time you come across a new USB drive (depends on how you like to approach the issue). The monitor conditions I use day to day and have not seen issues (with our setup at least) are as follows: Drives.Size > 6000 and Drives.FileSystem not in ('ERR','CDFS','UNKFS','UKNFS','DVDFS','FAT','FAT32','NetFS') and Drives.Missing !=1 and Drives.Model not like '%USB%' and Drives.VolumeName not in ('WCDisk')
  4. I don't know the stats off the top of my head, but the scores are pulled from h_extradata and h_extradatadaily (if I recall correctly) in the LT database. What are you really trying to accomplish? You may be better off just creating a modified version of the health check script that will accommodate whatever you are trying to do. In the past I have built other backup product checks into the script itself to get more accurate numbers for clients that used non-standard backup software.
  5. Unblock did the trick btw. I apparently lack troubleshooting skills late at night
  6. Looks like fun. I tried to load it in and it errored out on me. "There was an error uploading the new plugin." Running LabTech 10.5 on Windows Server 2008 R2 if that helps at all.
  7. Sure. I have not looked at it in a while so as usual it could probably use some work, but here it is. Basically I have an internal monitor that will look for agents where commands are stuck on executing and if they have been like that long enough they will initiate a script and ticket. The script will find an agent at the same location and will use "net use" to attempt a remote sc command to restart the LTService. It will attempt to use a master agent at the site and if none are found it will settle with a workstation if needed. It will also put the computer in maintenance mode for 15 minute while it attempts this so you don't get random offline alerts. The location credentials do need to be set under the deployment settings so it can use them to attempt the remote connection and restart of the service. Let me know if you have any questions! Here is a pic of the monitor configuration: Remote Agent Restart.zip
  8. I just took it for the agent service locking up sometimes. I created a script that will find another agent at the same location and initiate a service restart on the LTService service. This seems to fix the issue for me most of the time.
  9. I believe you still have to be logged into the server directly to access the Solution Center.
  10. I would think about creating a powershell or batch script that LabTech just calls on to do the job. That way when LabTech is uninstalled the script is just running like normal and can finish up the install (hopefully).
  11. I'm a fan of the startup scrips, but when you just look for ltsvc.exe I found that we kept missing computers sometimes. If an install is only partially successful the .exe will still be in the directory even though LabTech isn't running. I like to look for the services and check if they are running to confirm the install was successful.
  12. Not sure if this will be very helpful for your case or not, but here is an example of an Internal Monitor that I put together to help let me know if a Dell machine is missing OpenManage. For easy copy and paste: SELECT DISTINCT c.ComputerID AS TestValue, c.name AS IDentityField, c.Computerid AS ComputerID, acd.NoAlerts, acd.UpTimeStart, acd.UpTimeEnd FROM Computers c LEFT JOIN AgentComputerData acd ON (c.computerid = acd.computerid) WHERE OS LIKE '%Microsoft%Server%' AND c.computerid NOT IN (SELECT computerid FROM software WHERE NAME LIKE "%OpenManage%") AND c.os LIKE "%server%" AND c.biosMFG = "Dell"
  13. Are you sure that the UDP traffic on port 75 (I think that is right) is being allowed in/out from those servers?
  14. Usually you can stop the LTService and then the LTSvcmon to bring it offline. I think the LTSvcmon will try to start the LTService if it can.
  15. I'm sure this could be cleaned up and some more device support needs to be added, but there seemed to be some interest in this so I wanted to get it out there for everyone to view and tear apart if wanted, lol. There is some setup required as this was configured/created before you could setup network devices with encrypted passwords in LabTech. Also this does not rely on SNMP and other various Network probe functions. ------------------------------------------------------------------------------------- Network Probe Configuration: There should be a network probe at the locatino with the device (if possible). Along with having a network probe setup they must be set to have the TFTP server enabled. To do this you just need to open the Network Probe tab on the Network Probe Agent (these have blue text). You will see a TFTP Settings box. Make sure Allow Upload is checked. This is all that needs to be completed for the TFTP server to function. Network Device Input: Double click the client’s location in LabTech (It must be assigned to a location to work properly with the location’s network probe.) Click the Password tab This list is what devices will attempt to be backed up. This list is manually populated. Add an entry with the following setup/syntax: Title: Network Device - %devicemanufacturer% - %devicemodel% User Name: The username to access the device URL: IP Address of the network device. This is the IP address the network probe will attempt to use to connect. If SSH uses a non-standard port you can add :32 to the end to signify that. (e.g. Password: The password for the device. Notes: Enter details about the device if you have any (e.g. Serial, Role) [*]If the Cisco device requires an enable password, you will need to create another entry for that password with the following setup Title: Enable Username: Blank URL: IP Address of the network device the password applies to Password: The enable password for the device It will complete the following actions. Check to ensure the TFTP services are running on the Network Probe It uses a netstat check to ensure the process listening on port 69 is actually the LTSVC.exe process [*]Pull basic information about the device from the SQL database (Using the password entry you provided) [*]Detects if it is a supported device using the %devicemanufacturer% field you entered At the moment the script only works for Cisco and Fortigate [*]Opens a SSH connection to the device using the IP address This defaults to port 22 unless otherwise specified after the IP address Example: [*]Sends the enable command and password if required [*]Runs the various backup commands depending on the type of device (Cisco of Fortigate) that will back the configuration up to the TFTP server running on the network probe [*]Once this command is complete it will verify that the file was uploaded properly to the TFTP server. The file location is under %windir%\LTSVC\TFTP [*]Then it will upload the file to the LabTech server where it will be stored under (L:\Uploads\%clientname%\%computername%) [*]If there are any problems with any of these processes a ticket will be generated with the error [*]If all backups are completed successfully and it detects a previous ticket for backups failing it will close the ticket since the issue has been resolved [*]If you recently added the entries and want to ensure that all backups are going to complete successfully you can run the script from the following location Scripts > Backups > Network Devices > Network Device Backup The script will give you details on the process if you check the logs on the agent and at the end it will give you a total amount of failed backups (if any) Script can be downloaded at this link: http://www.labtechgeek.com/forum/scripts.php?m=src1&guid=30ef2eff-4b58-11e5-90ee-00505601001e
  • Create New...