Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
  1. ryan1cf

    Mapped Network Drives

    Added to feature request as well: https://product.connectwise.com/communities/5/topics/13328-mapped-network-drives-in-dataviews-and-drive-detail-report
  2. ryan1cf

    Mapped Network Drives

    Hello! Anyone know of a report or can share one that along with the drives on an agent also shows the agents mapped network drives? I've found the table for this but when I add the table info it always shows duplicate in the report and only ever 1 drive letter per agent.
  3. For me it was enabling the mac address scanning.
  4. -.net on the probe Server is 4.5.2 or higher? Try .net repair from Microsoft if it is -are the ESXi IP's pingable, the Probe needs to be able to ping them -try re-sending config and system info for agent as well as remote agent\update plugins -do any of the ESXi hosts show under Network devices? If so, then you just need to set your ESXi (root) creds
  5. I enabled that, click save, waited maybe 15 seconds, then started a network scan.
  6. Thanks for this! I enabled that and voila, the probe is now picking up the ESXi host! Awesome
  7. Appears I can't disable or uncheck the "Enable New Probe" so I guess there is no choice in which gen Probe I can use.
  8. Yes it's the Gen2 probe. I admit I haven't tried this with the Gen1 probe, going to try that right now. Server type is a Lenovo ThinkServer TS440 and it's exactly ESXi 6.0 build 3620759. Nice to hear that it's not just us.
  9. SNMP doesn't appear to be a requirement as several of my ESXi hosts do not have it running. No firewalls involved as it's all internal and the internal firewall in Windows is disabled. I have a support session with Automate support this Thursday to deep dive this. What's odd is the Probe is picking up the IP as pingable, I can see this in the probe logs, but it doesn't detect that it's an ESXi host and it's ESXi 6.0 and I have other client hosts that are 4.5 and SNMP off and yet their probes detect the IP and that they are ESXi hosts.
  10. Yes you can create a basic script with the Function "Maintenance Mode Start" Set the duration but I think you just leave the ComputerID empty so it will apply to whatever agent you run this script on. Then you just need to figure out how schedule that script because I don't think you can choose every first and third Sunday.
  11. I've now been able to set this up for another client so I know the setup in Automate is correct, so something about this particular ESX host that the probe can't detect. I wonder if there are any requirements/settings in ESX to allow this. The ESX host that I'm trying to get to work is pingable and it's a licenced version of 5.5.
  12. Anyone using the Virtualization Manager with ESX hosts? I can't get my probe to detect an ESXi 5.5 Server. I have creds setup in Global, the Probe is showing the VM Manager Probe role and I've restarted the DB agent. I've resent config, updated plugins. Is there something in ESX I have to turn on? The probe doesn't even detect the IP address of the ESX host.
  13. ryan1cf

    Monitor - Time and autofix - anyone have?

    The N-Central monitor was called "Windows Clock Drift" and the script that ran was "Windows Clock Drift Fix" which was basically running these commands: w32tm /config /manualpeerlist:"ca.pool.ntp.org,0x1" /syncfromflags:manual /reliable:yes /update w32tm /config /update net stop w32time net start w32time w32tm /resync Just need to figure out how to monitor for clock drift with LT.
  14. Hello all, Back in my N-Central days there was a monitor that checked if the time was correct on a Server/Workstation etc and if it wasn't correct to then fire a script to fix it. IE. set new time variables and restart the time service. Rather than starting from scratch, does anyone have this monitor and can share? Thanks! Ryan
  15. ryan1cf

    Retired Assets Script & Monitor

    Thanks Tim, Do you know how I could get this script to email me the results, so I could get a report or list of machines and client names/locations of the agents that were retired? I tried using an SQL get command that inputs the full SQL command for the search but I ended up getting an email for each agent and in the email it just shows me the agent ID number. Ryan