GFI LanGuard

How can we improve?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Agent "Pull" model with less dependency on active connection to Server

    The current Server-Agent model is largely a "Push" architecture rather than a "Pull" architecture - i.e. the scan/remediation jobs are entirely triggered/handled by the LanGuard server or relay agent.

    Unfortunately, this almost defeats the point of an agent-based approach, since there are a lot of real-time operations required between agent and server.

    I would like to see a future version of LanGuard evolve to a point where the agent is much more autonomous and that operates more on a "Pull" model:
    1) Policy is defined on the server
    a) Server pushes policy update out to any reachable Agent
    b) On…

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Block patches by minor versions

    Block patches by minor versions such as blocking Java 8 Update 112 but allow Update 102 for all Java 8 users.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Proactively email user when patch is delayed/released.

    Users do not receive any notification on patches being delayed/released, it would be nice if GFI Team does send and email when this happens.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Export list of Approved patches in each patch Profile.

    Hello, We have a requirement to get the list of approved patches in a particular patching Profile in GFI. We worked with the GFI engineer and understand that the current versions does not have this options to accomplish this. Hence, opening this feature request. Thanks.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add a notes tab for the approved/denied patches

    I think it would be nice to have a notes tab for the approved/denied patches. For example, I'm not the only person who does patching. It would could be beneficial to have a notes section where you indicate why a patch was denied or if it broke something.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create an API for retrieving all available products, including versioning

    We wish to be able to list all available products (not of a specific asset).

    The only way there is now to retrieve this list, is by manually manipulating the lanss_11_patchmngmt.mdb GFI file.

    Create an API for retrieving all products and also be able to retrieve the full list and just the deltas (probably API should include versioning of the retrieved data).

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow ability to manage patches by release date.

    Allow us to control released patches by date. For example, I want to deploy patches released before 11/30/2016 but nothing released after that.

    This is important because we have to test patches on test servers and the testing may last more than two weeks. During the two weeks, new patches may be released and they get mixed in with patches that we have already tested when it's time to patch the production servers.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. remediate until no more patches are availabe

    Currently we have to scan and remediate manually multiple times until all patches can be deployed.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. change the order patches are insstalled

    Any updates that need to come next(delayed install till reboot) gets purged from the temp directory, and gets flagged as failure to install. Right now we see a list of updates, we toss all of them at the system, system installs what it can, prior to its required reboot for certain patches, and then leaves the rest hanging and goes for the reboot.
    So if MS16-078 can't be installed because KB8675309 needs to be patched first, then the admin should say "Install it all", GFI sends KB8675309, system installs reboots, GFI sees the client comes back up and knows it…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. I would like to see power to reboot batches of machines before deployment

    I would like to see power to reboot batches of machines before deployment

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base