![]() ![]() I am helping support a @4500 endpoint SEP v12.1.2 infrastructure over 32 locations. We have two SEPM servers each running SEP v12.1.2 on Win 2k8 R2. The SEPM servers are configured in a dual configuration w/ priority 1 then priority 2. The SEPM backend database is SQL also running on a Win 2K8 R2 server. Since we upgraded to 12.1 R2 (aka '12.1.2'), we changed our overall 'GUP' configuration. We had multiple 'single' GUP policies for each 'remote' site. Jan 13, 2017 - Our software and services protect against more risks at more points. A v14 gup doesn't help with providing the subnetmask for v12.1. Group Update Provider Mapping entries usable by the client' in the policy: 0. As i understand only endpoint with SEP14 can be GUP if used SEPM14? The Symantec Endpoint Protection 14: Differences course is designed for the network, IT security, and systems administration professionals in a Security Operations position who have experience with SEP 12 and need to understand the new features, how to upgrade to and manage SEP 14. (Group update provider) and the NMD (non managed detectors) limited to s ingle subnet. Explaining and walkthrough overview of SEP distribution & rollout methods. Symantec helps consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored. The Symantec Connect community allows customers and users of Symantec to network and learn more about creative and innovative ways to. ![]() ![]() Update group configuration; 3. How much memory should i install solar. 63. Get the information about the computers in a specified domain and group. Get a list of group update providers (GUPs) 3.79. Authenticate and return an access token for a valid user. Send a command from Symantec Endpoint Protection Manager to Symantec Endpoint Protection endpoints to request a suspicious. We have now migrated to including this information into our companywide default 'LiveUpdate' policy as 'multiple GUP' w/ 'explicit GUP' subnet networking information. When this extra GUP configuration data is contained/applied to various SEPM groups as part of a 'LiveUpdate policy' in our infrastructure, the machines configured as GUP's get updates from our 2 SEPM servers but the clients (desktops/laptops/virtual PC's) in various groups with this modified policy DO NOT get antivirus updates regularly. Our overall mode/heartbeat configuration is 'pull' w/ a 1-hr heartbeat and 2-hr randomization window. Any suggestions? Hello, Are these client machines also migrated to the Latest version of SEP 12.1 RU2?? Make sure you have SEPM and GUP on the same version of SEP 12.1 RU2 You may like to check these Articles: SEP 12.1 RU2 And Explicit Group Update Providers About the types of Group Update Providers Configuring Group Update Providers What is the processing order of an Explicit GUP list within version 12.1.2 of Symantec Endpoint Protection? Ttp:// Understanding 'Explicit Group Update Providers (GUPs) for Roaming Clients' in Symantec Endpoint Protection (SEP) 12.1.2 ttp:// Hope that helps!! Hello, Are these client machines also migrated to the Latest version of SEP 12.1 RU2?? Make sure you have SEPM and GUP on the same version of SEP 12.1 RU2 You may like to check these Articles: SEP 12.1 RU2 And Explicit Group Update Providers About the types of Group Update Providers Configuring Group Update Providers What is the processing order of an Explicit GUP list within version 12.1.2 of Symantec Endpoint Protection? Ttp:// Understanding 'Explicit Group Update Providers (GUPs) for Roaming Clients' in Symantec Endpoint Protection (SEP) 12.1.2 ttp:// Hope that helps!!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |