We have problems with patch approval process in Languard 9. For example, a patch causes problems on server-x, but it's ok on server-y. If we approve that patch, it's applied on both servers.
Is there a way to solve this? I mean, approval with respect to groups formed for Languard..5 votes
To reduce Traffic/Bandwidth Consumption on slow networks. Instead of LanGuard Agents being installed from the main LanGuard Server consuming WAN Bandwidth.Allow installed Relay Agents to locally install\push normal LanGuard Agents to computers using it as a relay server since they are typically on the same LAN anyways.3 votes
Scan remote computer without enabling on it the feature of "File and Print Sharing" on Network interface for secured servers that this feature is not recommended.
I have multiple clients that are not on the network and hardly ever VPN into the network. We should have the ability to set the client to call home using a domain name. For example languard.companydomain.com. That would give us the ability to monitor those machines and apply patches to our users outside the network.
**The current version only allows for the internal IP of that server for the agents to call home with.**1 vote
Any idea when there'll be support for IPv6?
It would be great to be able to approve patches for auto-deployment from the 'Dashboard->Patches-Missing Patches' screen. This would much quicker approval for patches that are missing from the network. Currently the approach is to review this screen, make an off-screen note about the missing patch and then find it in the auto-deployment screen.1 vote
- Don't see your idea?