Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

My Information

  • Location
    Bizkaia, Northern Spain
  • Agent Count
    < 500 Agents


Recent Profile Visitors

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

  1. Yes. Each client has a permissions tab and you can add a class there. These steps should get you going: in control center, open system > users and contacts > user class manager click on the plus to add a new class. Give it a generic name, it can be used for multiple clients and multiple users. Don't assign it any rights. close the user class manager open system > users and contacts > users Select your new client user account assign them the new class you've created on the groups and clients tab, remove all the default groups and clients assigned Assign them only the group-membership = the client they need access to. Close the dialog Open the client properties, permissions tab. Assign the new user class (right click in the list) To this new class assign all the roles you want. I allow everything except delete.
  2. imurphy

    Automate Security Issue- Patch 11 and 12

    Weird, the example darren posted above doesn't work for me either. with http://localhost:12413/..../Windows/LTsvc/LTErrors.txt I get a 404, even when opening it locally from the console of the server.
  3. imurphy

    Automate Security Issue- Patch 11 and 12

    hmm, interesting that port is open and listening on the server but I get 404 if I try and open the url. What on earth is that listening on 12413. In any case, I've repeated the test above, dropping a test.txt in the root of the C disk and then trying http://LTServer.yourdomain.com:12413/..../..../test.txt http://LTServer.yourdomain.com:12413/..../..../..../test.txt through to http://LTServer.yourdomain.com:12413/..../..../..../..../..../..../..../..../..../..../..../..../test.txt all of which are returning 404 I am only running Automate on my server. Could it be another component?
  4. imurphy

    Automate Security Issue- Patch 11 and 12

    I can't reproduce it either. My IIS log file shows the following: 2019-01-04 10:32:05 GET /..../..../..../..../..../..../..../..../..../windows/win.ini - 443 - Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/71.0.3578.98+Safari/537.36 - 404 0 2 15 and I'm on patch 12 As a test I tried creating a test.txt file in the root of the disk and then tried generating a path by successively adding multiple '..../'s without managing to pick up the file in the root. Is it possible you've modified something in the standard IIS config?
  5. Love this monitor. I should have imported it ages ago. Thanks. You mention that it only considers the NIC with the IP address matching the Agent public Router IP matches Location Router IP, but it seems to also pick up agents where the router address is not configured - which is perfect as in quite a few cases at small clients they have a dynamic IP and so the router ip is empty.
  6. imurphy

    Mass finish ALL open Automate tickets

    CREATE TEMPORARY TABLE oldtickets (INDEX(ticketid)) SELECT DISTINCT ticketid FROM tickets WHERE tickets.updatedate <= DATE_SUB(NOW(),INTERVAL 30 DAY); DELETE FROM tickets WHERE tickets.ticketid IN (SELECT DISTINCT ticketid FROM oldtickets); DELETE FROM ticketdata WHERE ticketdata.ticketid IN (SELECT DISTINCT ticketid FROM oldtickets); DELETE FROM ScriptState WHERE LOWER(Variable) LIKE '%ticketid' AND VALUE NOT IN (SELECT ticketid FROM tickets); DROP TEMPORARY TABLE oldtickets; This deletes all tickets over 30 days old. It should solve your problem.
  7. imurphy

    BgInfo Script Doesn't work

    Try this: Add a line of type 'execute script' function In script type select batch Click on the dots on the right of the script field to open the text editor. Paste this into your editor Echo starting %date% %time% >> c:\windows\temp\bg.log %windir%\Temp\BgInfo64.exe" /i "%windir%\Temp\BgInfo64.exe" /q >> c:\windows\temp\bg.log 2>> c:\windows\temp\bg-error.log Exi Echo Ending %date% %time% >> c:\windows\temp\bg.log now run your script. It should generate \windows\temp\bg.log and maybe a bg-error.log file. These logs will tell you - if the script is running at all - If it finished. If it started but didn't finish then that would imply that bginfo.exe started up but didn't close, probably displaying a prompt of some kind. - if the bginfo generated an error (unless the error was a dialog box, in which case you get no info back)
  8. imurphy

    VBScript - issues

    Strange that noone else has responded yet.... Writing the file out should work. So, time to diagnose whats going on. Using file download is easier for debugging this type of problem. Drop your vbs file into l:\transfer\somesubdir\ Create a batch file mybatch.cmd and add the following lines: Echo Starting %date% %time% >> %temp%\myscriptdebug.log Echo Starting %date% %time% >> %temp%\myscriptdebug-errors.log dir %temp%\MyVBSScript.vbs >> %temp%\myscriptdebug.log cscript %temp%\MyVBSScript.vbs >> %temp%\myscriptdebug.log 2>> %temp%\myscriptdebug-errors.log Echo Finishing %date% %time% >> %temp%\myscriptdebug.log Echo Finishing %date% %time% >> %temp%\myscriptdebug-errors.log Drop the batch script into l:\transfer\somesubdir\ In your Automate script add lines to do the following: - download each of the above files to %temp% - Shell as admin %temp%\mybatch.cmd now you should have some sort of diagnostic information indicating what is going wrong.
  9. imurphy

    Get list of Computers over 5 years old

    This response is a bit late, but better late than never. Basically no. There isn't any standard way to get the age of a computer. However, you *can* get - Date Automate agent was installed - Date windows was installed - some other dates, all of which have problems in using them. If you are lucky enough to have all systems from the same manufacturer, when you may be able to pull a motherboard date. If you are happy with one of the above dates then by far the easiest way to work out what you have is via dataviews. You can export a view to excel and work from that, which would be my preference.
  10. I monitor for basic windows iscsi login failures and disk errors in all servers. The only boxes where I've actually seen disk errors occuring have been in Azure and ESX and the event monitors have picked them up when there really were errors. Monitor for iscsi drives missing : table: drives field to check: missing result: 1 additional condition: model like '%iSCSI%' (we add iSCSI to the names of all iSCSI partitions on each machine) Monitor for disk Errors: Table to check: eventlogs Field to Check: EventID Check condition: Equals Result: 153 Additional Condition: eventlogs.source='disk'
  11. I monitor for basic windows iscsi login failures and disk errors in all servers. The only boxes where I've actually seen disk errors occuring have been in Azure and ESX and the event monitors have picked them up when there really were errors. iscsi drives missing : table: drives field to check: missing result: 1 additional condition: model like '%iSCSI%' (we add iSCSI to the names of all iSCSI partitions on each machine) I'll have to look up the others when I have battery....
  12. imurphy

    Windows 10 update Script from Network Share help

    This is a bit late but if you are trying to do anything like this you will find it useful to write your batch file so that it writes a log to c:\windows\temp\, or similar. In the first line do something like echo %date% %time% >> c:\windows\temp\win10upd.log In the last line do the same. The above line should also have >> c:\windows\temp\win10upd.log added to it. You could also add a few more diagnostics, like net use >> c:\windows\temp\win10upd.log dir \\server\share >> c:\windows\temp\win10upd.log Echo %username% >> c:\windows\temp\win10upd.log All of this will give you information on why the update may have failed to even start. As Mnewman mentioned, in this case its most likely that the admin credentials didn't work as expected. Ian
  13. imurphy

    Post-Patching Email Notification

    yes, theres an option to run a pre and post patching script. The script runs on the machine, so it should be fairly simple to pull out the users email from the machine contact info, or whatever logic you want to follow.
  14. imurphy

    Help with Uninstall/Install Script

    If the existing software supports silent uninstall then you can just use a dataview to remove it from all machines. Open dataviews > Software > full software listing filter on the package name and client name (you may have to add the client name as a column to the dataview by right clicking on the column header) Once you have filtered down the list of machines which are running the software you want to remove just right click > software > uninstall and wait. If the software is well behaved the list will simply shorten until they're all gone. That rarely happens as theres always a problem machine. Once removed, drop your package into l:\transfer in some sub directory. Create a new script Add a line to download the file and select the file you dropped into the sub directory, download to %temp% Add a line to shell something like msiexec /qn /i %temp%\yourdownloadedfile.msi Add a line to resend software This depends on you having an msi for the new package. If you don't have an msi, you have to work out a way of silently installing the software with no interaction with the desktop. This depends on each package. thats it, three lines. Ok its not a good script, it may fail, it may give you grief but thats the bare bones. Now try open a dataview of, say, computer status filter on the client, filter on workstations (OS name not like %server%) Select all rows, right click, agent, scripts, select your installation script and complete the dialog to run it on the machines. If you are lucky it will run on all machines and work first time. If you are unlucky and some install, some don't, you will need to use a different method. Create a search for machines which do *not* have your package installed (look on the forum for this gavsto has a blog post on how to do this as well) Create a group and select the autofill group option and select the search you just created. This will result in a group of machines which *do* not have your software installed. Now you can repeatedly run scripts on the whole group by just selecting all lines and running your script. The group should gradually empty. Ian
  15. imurphy

    Email the initiating tech script stats and results

    Easier way: Use Darrens script Take a look around LTG and find some of the scripts posted by Darrenwhite. One of his is a script to send an email. By default it sends it to the tech who executed the script. The question is, why on earth LT don't make scripts like this available as standard.