Endpoint Protection

 View Only
Expand all | Collapse all

Using a server as a GUP for clients with different installed features

  • 1.  Using a server as a GUP for clients with different installed features

    Posted Mar 26, 2009 05:00 PM
    Running SEP 11, MR4.

    I'm not exactly sure how best to ask this question, as I'm only beginning to understand how GUPs work, but here is what I want to accomplish:

    I have 2 locations (linked wirelessly, so they're on the same LAN), with the SEPM installed at 1 of the locations. At the other location, I have one file server (also a DC), and then a mixture of client desktops. Because the server is both the most reliable computer at the location, as well as really the only one that's always on, I was thinking it would be the best computer to be the GUP. However, I only have the basic Antivirus features installed on this system, as I don't want the firewall, IPS, TruScan, etc on there (as recommended by Symantec; this is also a DC). And thus the policies for the unused features are disabled. Does this prevent the computer from properly acting as a GUP for computers that DO have all of the features installed, and all of the (different) policies enabled? I read that the GUP must have the same LiveUpdate policy as the clients it will update, but what about all of the other policies/features? Can there be differences? 

    Is there any way to make this work? I'm willing to rearrange my groups if necessary.


  • 2.  RE: Using a server as a GUP for clients with different installed features

    Posted Mar 26, 2009 05:27 PM
    It will work absolutely fine, just make sure the clients and server share the SAME LU policy - they can still be in different groups.

    The GUP functionality is a core component of SMC, which is the management component of the SEP client, all installs get SMC so it doesn't matter what features you have installed the GUP will work no matter what.