GFI LanGuard Review

Improves network visibility and keeps our products up to date with the latest patches


What is our primary use case?

The primary function for GFI LanGuard is as a patch solution, which updates all of my software. My second use is to perform vulnerability scans to give me insight into my network, and how it is looking. I also use it to check on the open ports, as well as to have visibility in terms of what is running on every user's machine.

What is most valuable?

The most valuable feature is that I am able to patch third-party solutions.

The visibility that it gives me is not just on the endpoints, but also on mobile devices.

What needs improvement?

The documentation on how to use this solution in a Linux environment is not clear, which is something that should be improved because it is complicated.

In the next release, I would like to see more support for pushing custom software.

For how long have I used the solution?

I have been using GFI LanGuard for five years.

What do I think about the stability of the solution?

The current version is very stable and we appreciate it because it has improved from past versions, where it was not as good. This solution is used perhaps three or four times per week. It gives a lot of insight as to what is happening on our machines.

Our users are content with the way the solution is functioning, so we do not have plans to increase our usage at this time. In the future, we will eventually expand it.

What do I think about the scalability of the solution?

This is a very scalable product and I really like it. We have about 110 devices that are covered by LanGuard.

How are customer service and technical support?

I opened a case with technical support and the person who was assisting me was very helpful. I was able to resolve my problem in minimal time.

Which solution did I use previously and why did I switch?

I was using ManageEngine prior to GFI LanGuard, but we switched because it gave us much more visibility and control. ManageEngine had a limitation where it would only support Microsoft Update.

How was the initial setup?

The initial setup is easy and something that you can manage. The installation took place over a single day. Apart from the ports that have to be opened and the exclusions that need to be made in the firewalls, there is not much in terms of installation issues.

The part that takes time is the patching process because it is more vigorous, and it keeps repeating.

What about the implementation team?

I performed the installation myself and I have a team of three engineers who help with the maintenance. 

Which other solutions did I evaluate?

We evaluated Microsoft System Center Configuration Manager (SCCM) but we found that it had almost the same limitations as ManageEngine in that it could not patch third-party applications.

What other advice do I have?

This is a solution that I recommend. In fact, those without it are at a disadvantage when it comes to managing their network.

The biggest lesson that I have learned is in terms of visibility. GFI LanGuard has given me a wakeup call in terms of what is happening on endpoint machines. However, it is more than just having visibility. It is about having control in terms of what you want to block and what you're able to block. It keeps our network stable in that there are no running applications that you don't even know you have.

 I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
**Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Add a Comment
Guest