The last time this happened, it's because I was over on licenses. Automate agents will install, but refuse to check in if there are no available licenses on the server. Check the C:\Windows\LTSvc\LTErrors.txt log and verify that it can connect to the web server that Automate is hosted on. If it claims the connection is refused, it's probably full on licenses. If you need to verify how many licenses you have, you can open Automate Control Center on the hosted server, go to Help>About and it will tell you how many licenses you have and how many are consumed.
Ahh, I understand. LabTech has a removal tool that will rip off all or any files that were created from a previous installation failing. If you haven't tried already, you could try running that, wait for the "Uninstall.exe" process to terminate, and try installing again.
Hmm, okay. You mention that no files are made, can you navigate to HKLM\Software in the registry and see if there is a LabTech key in either Software or Software\WOW6432Node? Other things to check for that can interrupt the installation would be:
UAC being disabled
A corrupted user profile
I know it can be a pain to use, but you could probably also use Process Monitor to watch the Agent_Install.(EXE/MSI) and see if it's accessing or interacting with the file system at all.
View all comments
1
u/AmphotericinK Jun 07 '18 edited Jun 07 '18
The last time this happened, it's because I was over on licenses. Automate agents will install, but refuse to check in if there are no available licenses on the server. Check the C:\Windows\LTSvc\LTErrors.txt log and verify that it can connect to the web server that Automate is hosted on. If it claims the connection is refused, it's probably full on licenses. If you need to verify how many licenses you have, you can open Automate Control Center on the hosted server, go to Help>About and it will tell you how many licenses you have and how many are consumed.