Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


imurphy last won the day on August 2

imurphy had the most liked content!

Community Reputation

13 Good

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. I'd run an agent-remove-script on all their systems for a week or two. Move all the systems for that client to a single branch Create a temp group, add all nodes in that branch to the group manually Assign a script to the group which runs every 5 minutes and just contains a single line to uninstall the agent. This way, if anything does manage to try and connect, it will will automatically uninstall itself. After a week, just select the nodes in blocks and retire them using CC.
  2. The 8Gb in use by mysql looks to be your problem. We only have 500 agents and mysqld is using over 9Gb of memory. Logic would imply you should be seeing something more along the lines of 25Gb in use by mysql alone. I can't supply you settings for your number of agents but there are a fair number of postings in this forum on sizing mysql, with examples. I'd recommend starting with a default my.ini, apply the changes recommended in the CW docs and then apply the changes people recommend for similarly sized installs. One change at a time so you can roll back. I've attached my my.ini, which you should not use as-is, but it should show you which settings need to be modified. The slack channel is a good place to go to get advice as well. Pretty much everyone makes the investment in ssd disks for the db disks as least. Its worth it. There are people on here with 20k+ agents... so it does work, its just a matter of getting the tuning right. my.ini
  3. Theres already a monitor for this. From CC open All Monitors > Remote Agent Monitors > Filter on %rdp% you should have a load of monitors auto-created with a name of 'TCP - RDP Port 3389'
  4. You could monitor it from the outside, from your systems or from the systems of a client. Just create a ping monitor for each of the public IPs. or, you could use snmp from a probe on the clients installations which queried the pfsense, but I don't know if pfsense support snmp info to indicate if an interface is considered up or down. or, if the pfsense doesn't support that sort of thing, you could define routes on the pfsense to route a particular IP out over just one of the links. If each of the IPs was for a router in the ISPs network, then pinging IP1 would indicate that DSL1 was working and pining IP2 would indicate that DSL2 was working. I am assuming you can do this in the routing tables of the pfsense. This way a ping monitor on a probe could be used. or, if the pfsense can generate syslogs which correspond to interface down or route down (they're different obviously) then you can point those syslogs at the probe and use those to generate alerts. Never tried that, but in the end, they just go into a table in mysql.
  5. Date handling is always going to be a complex task. Are you dealing with a multi time zone installation? Are you intending to compare times across zones? If you are facing anything complex then it may be better to generate numeric values based against some fixed date in the past, like seconds-since-1/1/2000 and using UTC as a base, you could then store that as an int in an EDF. You can then use a powershell function or a mysql function to convert back to a date and to then calculate differences. If you want to just keep it simple, then remember that EDFs are text, so you will want to force the format of all dates and times to a fixed format (yyyy-mm-dd hh:mm:ss highly recommended) when outputting from Powershell and mysql queries and then converting back to internal dates when reading them back into mysql/powershell. This way you will avoid the date-back-to-front issue when dealing with using the default date formatting. This method doesn't handle multiple time zones, but you could by converting all times to GMT/UTC.
  6. Dataviews > Inventory > Printers To know which are local, just filter on port. USB% should catch those but, who knows, you may have serial port or parallel port printers still out there.
  7. Try taking a look at how to run a script on a logged in users console. You will need to launch the above script every time a new user logs into a PC as windows will add applications those newly logged in users.
  8. I'd go 11-> 12 and then 12 ->2020 but it should be simple enough. If you have a vm rather than a physical server, you can test the update on a copy, or do a snapshot and then upgrade so you can always roll back.
  9. When you say maintenance, do you mean run scripts? If this is the case just schedule them to run on the agent using 'advanced settings' > unmark 'skip offline agents'. If you mean that you want to know when a box switches on so you can connect to the screen, then you can write a one line script which sends a mail to your account with the text '%computername% has powered on'. Schedule that script to run using the above unmarked 'skip offline agents'. You could get even more clever and write a generic script to be used by anyone and which sent a mail to the person who scheduled the script. Look at some of Darren Whites scripts. In fact his Send email script does just this. Also, is wake on lan not available?
  10. Disk space alerting generates emails by default, so no need to go configuring. Same for quite a few other urgent issues. You can modify/create similar funcionality by creating a monitor and applying it to a group and then marking it to alert byt generating emails. From Control Center desktop, open Browse > groups > Services Plans > Windows Servers > Double click on "Managed 8x5" Open Computers tab > Remote Monitors tab The list of monitors it shows only applies to servers with an 8x5 maintenance plan. Click on one like 'Perf - Available MBytes' then click on the Details button at the top. This will display the details of what is being monitored. Beside that on the right there is a dropdown for the 'alert template'. This is how an email would be generated. You can use the canned alert templates or generate your own.
  11. imurphy

    Script Issue

    The way mike said to do it is the way to go. Running a monolithic script again and again on boxes which may or may not have the software already installed and which may or may not already be updated makes no sense. Write one script which installs what you need and only run the script on machines which need it...
  12. Better still, do it the Automate way. Rather than detecting the manufacturer in the script, only run the script on Dell machines. As an example, to push Dell support assist: Create a search called something like Just-Dell-Workstations. Create a group called something like Just-Dell-Workstations. Populated the group with Just-Dell-Workstations search and limit it to that search Create another search which is Machines-Missing-SupportAssist which selects only machines which do *not* have Support Assist installed Create a script called Install-Dell-Support-assist In the Just-Dell-Workstations group configuration > computers > scheduled scripts add a line to execute the Install-Dell-Support-Assist, but limit it to Machines-Missing-SupportAssist The above will run the Install-Dell-Support-Assist script on only Dell workstations which do not have Support Assist already installed No need to add checks in your script.
  13. Well, none of those things is going to work because its simply buggy. Its been buggy for years. It suffers memory leaks and probably other issues. The memory leak is very obvious. A couple of years back I supplied all the info to show that the console crashing issue was definitely a memory leak bug. All you had to do was to use the console for a couple of days and it was guaranteed to crash. The tests in which I managed to reproduceably crash it consisted in nothing more than opening and closing Computer View windows. Around 20 was enough. They tried to blame everything. Configuration, plugins, AV, whatever. I excluded all of these and I was able to finally get them to accept it was a bug. The next release they rushed out a fix for the problem. You now have me to thank for the fact that the desktop client automatically shuts down after a period of time. That was it. No other fixes applied. Nothing touched since then. It still crashes after nothing more than opening windows and closing them.Computer view especially so. Ian
  14. Try the following. Shell as admin: copy <source file> <dest file> >> c:\temp\cpy.log 2>>c:\temp\cpyerr.log it should write two logs to c:\temp (make sure c:\temp exists on the box you are testing on). The cpyerr.log should contain the text of the error which is occurring. Its almost certainly access denied. Ian
  15. Darren White wrote a monitor to do just this. Works like a dream. I've just been searching on mspgeek and I can't find it. It may be better to just ask Darren on the slack channel.
  • Create New...