Video Screencast Help

System Requirement for RU2 (Confused)

Created: 15 Nov 2012 | 5 comments
SUPPORT-2-SUPPORT's picture

Hi Team,

Am referring the below article of Symantec Requirement for 12.1.2 (RU2) in which have bit confused on one statement.

Note: Windows To Go for Windows 8 is not supported.

http://www.symantec.com/docs/TECH195325

Can anyone explain what exact they wanted to say?

And also referring:

What's new in Symantec Endpoint Protection 12.1.2

http://www.symantec.com/docs/HOWTO81091

Where in which the last new feature in LiveUpdate setting ...

The LiveUpdate Settings policy includes an additional type of Group Update Provider (GUP) that allows clients to connect to Group Update Providers in a different subnet.

In earlier version (RU1) when we configure multiple GUP (e.g. 192.168.38.42) for remote locations then all respective clients will fetch the update from the GUP but in the same network where clients having different IP range (e.g. 192.168.28.x) will not get update from 192.168.38.42. As I understand from the above article that now in RU2 192.168.38.42 GUP will distribute the definition to 192.168.28.x or any.

Need your explaination.

Thanks in Advance.

Regards,

S2S

Comments 5 CommentsJump to latest comment

pete_4u2002's picture

Windows to go for windows 8 is not supported as this is like OS on USB not hard drive

Windows To Go is a new feature for enterprise users of Windows® 8 that enables users to boot a full version of Windows from external USB drives on host PCs.

 

42. As I understand from the above article that now in RU2 192.168.38.42 GUP will distribute the definition to 192.168.28.x or any.

Yes, use the roaming GUP option. Check this article

http://www.symantec.com/docs/TECH198640

SameerU's picture

Can any one explain what is the feature of explicit GUP in SEP 12.1 RU2

Regards

 

 

Ian_C.'s picture

that now in RU2 192.168.38.42 GUP will distribute the definition to 192.168.28.x or any.

As quoted from Tech Article 198640 linked by pete_4u2002

In previous SEP versions, the clients would only connect to a GUP outside of their own subnet, if such a GUP was configured as "backup" GUP

This means that when you have a multi GUP list defined (pre v12 RU2), then that GUP will only service clients in its own IP subnet, not outside of it's subnet.

To paint you a picture (in words)

Imagine you have three sites with an IP assignment like this

  • Site 1, IP subnets 10.1.1.x, 10.1.2.x and 10.1.3.x
  • Site 2, IP subnets 10.2.1.x, 10.2.2.x and 10.2.3.x
  • Site 3, IP subnets 10.3.1.x, 10.3.2.x and 10.3.3.x

Before SEP 12 RU2, you would have to create 9 GUPs to cover all clients, one for each subnet, three per site. As you can imagine, this is a problem for most people because they only want to use one GUP per site, not one GUP per subnet.

Now in SEP 12 RU2 you can specify one GUP per site and which subnets that GUP services. This still requires manual work, but is still easier to manage.

 

For me an auto discovery of "local" GUPs based on next hop / default gateway would be ideal. If anybody from Symantec is interested, I'd gladly expand on the idea.

Please mark the post that best solves your problem as the answer to this thread.