Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

1 Neutral

My Information

  • Agent Count
    Less than 100

Recent Profile Visitors

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

  1. Hi all,I've been reading more and more articles about how Windows Defender in Windows 10 is now beating out other 3rd-party anti-virus engines. (See https://blog.knowbe4.com/av-test-compares-19-antivirus-tools-windows-defender-reaches-maximum-detection-score)I asked at a recent Microsoft event what their current stance is, do we still need 3rd-party AV? Their answer was "no". I understand they are biased, but really for what gain? They're not selling Windows Defender...so why care?So I'm curious about what others are doing. We spend a lot of money on Webroot licenses every year. While Webroot has been great, if I can cut a cost without incurring extra cost somewhere else, I'm all for it.Anyone else started to use Windows Defender alone for AV protection? I'd love to hear your feedback!
  2. Thanks for the response Michael, that makes more sense! Certainly I can appreciate that the management of it is easier.
  3. Sorry Michael but that is not true and is one of the biggest misunderstandings of cloud. Simply moving your infrastructure to cloud does not eliminate the need for DR/BC/Backups. You still have to back up the servers, you still have to monitor those backups, you still have to have a DR solution in place if your server dies in the cloud. Thinking you can do away with all of these items just because you moved your server to Azure is short-sited and false. Call Microsoft and ask their support if that new VM you just spun up in Azure is backed up and they'll state no. What happens if you have data corruption or ransomware, how do you recover from that with a cloud server that does not have a backup? You still need a backup solution in place. So many people want to state that moving servers to the cloud will remove all head-aches and that's simply untrue. We had more server outages when our servers were in Azure than we did when they were running on our own infrastructure. In addition to that, the required spec of server you need to run Automate in Azure often makes it much more expensive to run a VM in Azure than host it yourself. I'm not anti-cloud, but we have to be careful that we realize it doesn't always make sense for everyone in every instance.
  4. Really appreciate your insight into this, fascinating to hear what others are doing!
  5. Thanks for that! Wow, I see that's $820/mth just for the server. That's pretty pricey. For that money it seems a heck of a lot cheaper to do it in-house, but perhaps that's short-sighted...
  6. Would you mind sharing what you're using? Michael Martin was using a DS12, I earlier spec'd a E2s V3 (2 Core, 16GB RAM). What are you running? I'm just trying to get a handle on what others are doing as Azure spec'ing is still a bit of a mystery to me.
  7. Hi George, Which report was this? Perhaps I happened to pick a different report when I tested it. Let me know which report you run that gives you incorrect totals and I'll test it in our system to see what results I get. Adrian
  8. Hi George, Apparently I'm getting you back with delayed replies! 😁 One big difference I see is that I actually wasn't looking at the reports as I don't use them. I was looking at the data presented in the plug overview. This data all added up for me. One clarification, while it may appear that both workstation and server standards are tracked, it's not docking you points if the standard doesn't apply. If you go to a workstation and hover over the "Server standards" line, you should see something similar to the following: As you can see, these server standards aren't evaluated because it isn't a server and therefore they don't apply. So you need to think of this in the opposite regard. If it IS a server, and one of these standards doesn't match, then you will get docked points. These standards work on a deduction system, you get full points unless something is wrong. For workstations since none of the server standards apply, you will always get full points on the server standard. CW Automate chose to take away points for issues and so if none are taken away you get full points. I'm not sure if you spent time with tech support or not on this as you indicated, but there seems to be something wrong with your report from what I can see. I just ran one from our system and it seems to add up properly. I'm sure you probably have resolved this already, but I thought it might still benefit others to understand this. Regards, Adrian
  9. Hi Martyn, Do you have any updated documentation on how to use the new probe? We've upgraded the probes on in our Automate, however, now when I try to run network probe commands (Scans or re-detects) nothing seems to happen. The Probe Commands windows doesn't show anything either. I used to be able to force this with the old one. Has that changed?
  10. Thanks very much, very helpful information!
  11. Sorry to resurrect an old post, however, we're contemplating shifting our Automate workload into Azure. If you had to re-do your setup, what would you use today? I was looking at the E2s V3 model (2 Core, 16GB RAM). We have approx. 1,300 endpoints. We will be going with the 3 SSD disks as well. Also, one thing I've always been confused on, is support for Azure offered through the Microsoft partner hours, or is it necessary to purchase standard support? It's an extra $100/month so it adds up. You still happy running it in Azure? Any other advice you can give would be great. Thanks!
  12. Have you considered using a consultant to help with this? When we first launched LabTech it took me months to make serious headway and I was still getting a lot of noise in. I engaged a consultant after struggling for a number of months at the time (no longer in the industry unfortunately) who helped me ratchet the noise down to a much more manageable number in a couple of weeks. Consultants cost, but they allow you to ramp up much faster. They would be able to assist with which option above would be the best route to take. I'm not sure who's all out there, but I've heard of Stack Advisors (https://stackadvisors.com). I've never worked with them so I can't vouch for how good they are but they've been around for a while. Give it some thought, my take is that while they can be pricey, you're going to spend it anyway, whether it be on someone else's time or theirs. Adrian VanderLaan
  13. We don't use the "Standards" portion of it, but I do use the "Health" portion. The health portion from our experience does properly split workstations/servers. Here's a snapshot from an old server from one of our clients: Here is how we've set up the Health Check portion: We use BrightGauge to send our Executive Summary reports and it pulls the data from here to display health scores for all machines. I'm not sure if we have it perfect yet, but we're certainly using it and we do find it helpful. Hope that helps! Adrian VanderLaan
  14. I'm curious, how have you found it since April? Have you made any changes to the VM specs you're running it on in Azure? We're contemplating moving from On-Premise to Azure so I'm really interested in your current feedback on this. If you don't mind me asking: 1. How many agents do you have reporting in? 2. What is the specs of the VM you have provisioned for it? (Processor, memory) One of the big pushes to put it in Azure for us is disaster recovery. If our building blows up, we can still operate properly from home... Thanks in advance for your insight! Adrian
  15. This is awesome, thank you MPriest!! Adrian Okay, maybe I spoke to soon, I updated the _sysMonSensorTemperatureVariance to 0 + 55 on my system and ran the script to remove and rebuild the monitors. Soon after this I started to receive temperature alerts from all our servers that the monitors had failed. The message of each monitor read something like the following: "Sensor - DIMM-core-Temperature  FAILED on  at Main office for Sensor - DIMM-core-Temperature  result core on DIMM reads 32.75 with a max of 32.75 with a monitor limit of 55.00." Can anyone help explain, why it's failing when it's not set to fail until it hits 55 degrees? Thanks! Adrian
  • Create New...