Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


toril last won the day on May 20

toril had the most liked content!

Community Reputation

1 Neutral

My Information

  • Agent Count
    2000 - 3000 Agents


Recent Profile Visitors

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

  1. Afraid I've not done that exact switch, but we did go from Vipre to Bitdefender GravityZone a few years ago. In our case we had the Vipre solution that included Vipre uninstall scripts, then I developed install scripts using this old post as a guide: That's not exactly an easy or quick setup though, and it really helps to have a handle on Automate scripting. At the time we weren't happy with the BD plugin for Automate, so this was best for us. You don't mention if you have the Bitdefender Solution for Automate installed, but if not, you might want to take a look at it. I know it's been updated since the days we decided against it, so it may be a lot better now. In theory, you could use your Ncentral console to issue uninstall commands (presuming that is an option), then use the BD plugin to do the install. Here's the BD documentation on that Automate plugin: https://download.bitdefender.com/business/Labtech/Bitdefender_GravityZone_ConnectWiseAutomateIntegrationGuide_enUS.pdf
  2. I think the monitor @WesleyNZ referenced is for when your network probe detects a new PC on the network. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/165/050/080#Automate
  3. Does the code below help? It uses the DATE_SUB() function to subtract 2 weeks from NOW(). I use something a bit similar in a script that runs on our Automate server every Monday to collect info like what is listed below. SELECT c.ComputerID, c.Name AS ComputerName, c.ClientID, cl.Name AS ClientName, c.LocationID, l.Name AS LocationName, c.DateAdded, c.Domain, c.OS, c.BiosMFG, c.BiosName, c.BiosFlash, c.BiosVer, c.LastContact, c.LocalAddress, c.MAC from (computers c JOIN clients cl ON c.ClientID = cl.ClientID) JOIN locations l ON c.LocationID = l.LocationID WHERE DateAdded > DATE_SUB(NOW(), interval 2 week)
  4. We put the workgrouped agents into their own separate location that uses our local admin creds for that client.
  5. Yes, that's what I was told. We were also having issues of some configurations not syncing, but the problems were VERY inconsistent. Some clients would sync up fine, others were just failing to update quantities under additions, and still a few others were syncing quantities but not creating configurations. The prorate checkbox was the first fix I was given, and while it fixed the issue for some of the sync problems, it didn't fix them all. (BTW, the effected clients were not all using the same agreement type, so the problem wasn't restricted to just one agreement type.) From my support chat on 10/9/2019: While that suggestion helped it didn't fix all my problems so I had them keep the ticket open. During a later phone call with a different support tech I mentioned the prorate again, and again was told that information was correct. If your agreement has an open invoice, then the prorate checkbox doesn't matter, but if there is no open invoice and you want additions to update, you must prorate. I guess the bottom line is if the configuration and quantities sync isn't working, there is no open invoice, and you've confirmed the Billing Information section of the agreement is populated, then try prorating the agreement and syncing again.
  6. I was also told that in addition to the Billing information section, if you want your additions to be updated whether or not the agreement has an open invoice, then the agreement must have the Prorate box checked.
  7. Hope this helps some... To me this kind of depends on what you want to consider oob. If you mean a clean Automate install with only Ignite, then the most useful scripts are probably the ones you are already familiar with, like the scripts for daily agent maintenance and offline server diagnostics/ticketing. (Although imho even those need customized for your company's preferences.) However, I think that if you take oob to include the plugins that you should get from the Solution Center for whatever products your company uses, then you'll probably get a lot more scripts/monitors/etc that will be more useful. Example, the StorageCraft Backup plugin includes the scripts needed to install/uninstall ShadowProtect and ImageManager, as well as monitors to alert to issues with those products. Again, to me this depends on what plugins you use. Backup/DR products can be so varied in how they work, I don't think there could be one way to check them all. The network probe has been completely rewritten, so you may have more success with it now than before. (Full disclosure, I haven't used it yet, but have heard some good things.) GPOs still work, of course, but if you already have a way to run a powershell command on your PCs, then you may find the Install-LTService function of LTPosh helpful. I sure do. The Control Center has a completely different look/feel then it used to, and, like most UI overhauls, it has good points and drawbacks. Some other new stuff that we use all the time: the new Patch Manager gives you more control over patching, including the ability to release patches is stages the new Report Manager is a little easier to design custom reports the Web Control Center has most of the agent info available in a web browser, which is pretty handy for techs (they're also adding more into that interface with every patch) speaking of patches, they release new patches about once a month or so now There's always something they are working on, such as adding the script editor the Web Control Center
  8. If I were doing this, I'd probably create an EDF checkbox and have both groups populate based on whether that EDF was checked or not.
  9. Editing originals monitors/scripts/etc VS. Making copies that are then edited There seems to me to be a downside to both ways, but one can be more problematic than the other. As Matthew1986 mentioned, customized originals that are overwritten during an update lose their local changes, and that could "break" your processes. Depending on what your tweaks do, that could be very bad. You'd have to re-customize changed objects as soon as possible every time you update a solution. On the other hand if you customize copies of the monitors/scripts and then CW updates the originals, your working copy will still function (in most cases). You might be missing out on new features or streamlined solutions, but things should still work as you designed. You'll just have to manually review the changes to the originals to see if you want them in your custom object, which can be done whenever you have time. I think this is why they say that editing copies is best practice, but if I'm wrong I hope someone will correct me.
  10. 1. EDFs are created in the System Dashboard. They are not applied to specific agents or agent types so all agents will have the EDF you create, but it doesn't need to have meaning for every agent. Simply ignore that EDF on your workstation agents. ***Note, you might want to give your new EDF a default value that is your most commonly used threshold. That way you only have to change the value of the EDF on servers with a threshold different than your default. CWA documentation on creating EDFs and their default values: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/060/140/020 2. Yes. In your script use the "ExtraData Get Value" function. It will let you assign the value of your EDF to a variable you can then use in your script. CWA docs on the Database Functions: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/240/050/040/020/040 3. The CWA docs will guide you through all those steps, but depending on which servers you want it to run on, CWA may already have the groups you need (such as Groups\Agent Types\Windows Servers). CWA docs on searches, using and saving: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/250/010 CWA docs on creating groups: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/090/020 CWA docs on scheduling scripts: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/240/030
  11. Just sharing my experience. I've had several support tickets about it with CWA support (one still open) and discussions with our sales rep. The last tech that worked the issue had an unofficial fix that addressed part of the problem I described (it was a query that would remove the mismatched standards), but not all of it, so he wasn't able to get our system fixed. He took lots of screenshots and notes, but that was 7/12/18. I haven't seen any progress yet, even after asking the sales rep to check on it for us . Just the occasional automated email saying someone will contact me soon. I'm not saying that all agents, workstations and servers alike, get the same score. I'm saying they are given scores/checks they shouldn't. If you look at the results of the Standards & Health checks for any agent, and if you have the same problem I do, then you will see that under standards both the workstation and server standards are being evaluated. Since those standards are also tied to health check scores, all agents have a score for both the "Workstation Standard" and the "Server Standard".
  12. Standards and Health is broken and no word on when/if they will fix it. All standards and health checks get evaluated globally, so workstations are scored for server standards/checks and vice versa. Also, in our case, when we did make customizations to the tool, like editing default standards/checks and/or adding our own, those changes were overwritten when the solution was updated from the Solution Center.
  13. Yes, by using a script and the ExtraData Set Value function. If you want the EDF to contain only the name of the agent's reboot group, then set the value of that function to the group name and run your script on the group.
  14. The remote monitors for disk space are created by a script: Scripts\_System Automation\Agent Maintenance\Agent Monitor Creation - Disk* That script is called by 2 other scripts: Scripts\_System Automation\Agent Maintenance\Agent Monitor Creation* called by Scripts\_System Automation\Agent Maintenance\Agent Maintenance - Contract* also called by Scripts\_System Automation\Onboarding\Onboarding Scripts\Maintenance\Agent\Agent Monitors - Disk - Remove and Rebuild
  15. Similar issue here. Installed v12.0.361 on Friday night (updated from v12 p5). Super Admins don't get these errors, but everyone else gets it for each Computer Management window. If the tech opens additional Computer Management screens within the same window, then there is no error. The Computer Management screen still seems to load properly. I contact support and was told:
  • Create New...