Hi,

Any services can be temporary stopped the client update definition from SEPM ??

Since hugh traffic make normal operation freezed .....

I want stop temporary then enable it later.

Thanks

This is not a normal situation but what you can do is go to the Clients page and select the group for which the problem is occuring, select the Policies tab and select Communication Settings

Under Download, uncheck "Download policies and content frm the management server"

Again, not a normal thing to do so you should troubleshoot the issue. Are you using GUPs? This will help lighten the bandwidth load

Hi Brian,

What's GUPs ??

See here:

Distributing content using Group Update Providers

About the types of Group Update Providers

About the effects of configuring more than one type of Group Update Provider in your network

With GUPs, you have the ability to set a specific machine or machines so they can provide content to clients on the LAN so they don't have to come back across the WAN to get updates from the SEPM. This greatly reduces bandwidth. I highly suggest using these.

Hi Bria,

Thanks.

Is anyway to check GUP is succeed or not ??

You can see here:

How to confirm if SEP Clients are receiving LiveUpdate content from Group Update Providers (GUPs)

Hi Brian,

Thanks.

Then I should wait the update the see the result ?? Or I can manually to control the update for checking ??

Because I haven't found any info about GPU server this moment.

Otherwise, should I uncheck "Use the default management server" ??

Do a search to check that the machine became a GUP

Searching for the clients that act as Group Update Providers

Hi Brian,

Tried but failure to search the GUP server.

Did the clients pickup the new policy change?

I have updated the policy in GUP server.

Just tried to search but still failure.

If you experiencing BW issue due to SEPM, then for the time being

Stop the SEPM service ( Symantec endpoint manager service)

If you go to the GUP and check the System log, does it show an entry relating to it becoming a GUP?

Hi Brian,

- What's the Event ID ??

- Otherwise, any port needed ?

There won't be an event ID in the SEP logs, there will be a statement that says something to the effect of "Start using Group Update Provider"

GUPs and clients talk over tcp 2967

- Just checked no this log....

- If 2967 is not allowed, will it affect remote server to be a GUP server ?? Or just affect connect between GUP client and server ??

it will affect both, gup will not get update from sepm and gup will not be able to update other clients

ok.

Otherwise, is the live update of GUPs can connect to either Symantec server or SEPM ??

Clients get updates from the GUP over 2967, GUP gets updates from the SEPM pver 8014

LiveUpdate goes out to Symantec over 80 or 443 so that will be different

I mean live update from Symantec or SEPM will affect establishment of GUP server ??

The client will get the new policy change from the SEPM, once it loads the new policy to tell it to become a GUP, it will do so.

Checked 8014 was opened in SEPM and succeed to telnet from GUP. But no log about GUP.

and you followed this article and the new policy is aplied to the correct groups?

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

please find for the attached file

and this new policy has also been applied to the group which contains the machine you want to be the GUP?

Already applied.

Is this setting correct ??

Looks to be, are you using any location awareness?

Enabling location awareness for a client

- Just checked. All setting same as your reference link.

- Is it means definition of GUP server must update from SEPM ??

Just Check Gup System are showing True in SEP client property As per below screen shot

Just checked the remote server can act as GUP but doesn't know the client can update through it or not.

Since the port 2967 not blocked but can't be telent.

Does windows firewall are disabled ?

Troubleshooting the Group Update Provider (GUP) in Symantec Endpoint Protection (SEP)

Did you also apply the policy to the group the clients are in?

Hi Brian,

It's been fixed.

Thanks

Great, glad it's working for you.

Take care