Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Task vs Package - Site Server Communication Question

Created: 20 Mar 2013 • Updated: 22 Mar 2013 | 9 comments
This issue has been solved. See solution.

Hello,

We are seeing some of our end user machines reporting to the wrong site server located on another subnet.  We believe the "reset task agent" is helping to get this corrected.  We were told by support that "package services" are treated differently than "task services".

The question we have is:  "How can we be sure that our end user machines will connect to the right package server?"  We don't want an end user machine in New York attempting to download a package from a site server in Los Angelos.

Thanks for any help on this concern.

Operating Systems:

Comments 9 CommentsJump to latest comment

andykn101's picture

The short answer is "you can't". You just have to hope that the agents speed testing for package downloads works correctly.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

SOLUTION
WK01's picture

Andy, Thank you.

Is it safe to conclude that even though an agent maybe registered to site server 1, it does not necessarily mean it will download a package from that server. It may in fact download a package from another site server 2 if the speed test is faster?

an agent might run tasks from a different site server than it downloads packages from?

andykn101's picture

I think that's right, the Task Server the Client Task Agent registers with has no direct bearing on the package Server the main agent uses, which can vary from package to package.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

WK01's picture

We are trying to setup a task to "reset task agent" in order to help us getting machines pointing to the right task/package server.  The problem we are facing is that a lot of machines are offline.  By the time they get back on the network.  The task has timed out.  Is there a best practice to address this issue of timeing out?

Gibson99's picture

in practice, we find that this works fairly well.  the only time we have complaints of packages downloading to machines slowly is when we're having bona fide network issues or if a package server is actually down/broken.  where a machine gets a task from is pretty irrelevant since that's such a low-bandwidth thing most times.  it's the packages that eat up the bandwidth.

we have offices across the US as well as london, the middle east and asia.  i once saw a machine in tokyo try to download something from our houston office, but that was because the tokyo package server was offline.  other than that, things tend to go pretty smoothly and download from the correct server.  

you can try constraining your package servers but it probably won't make much difference if your WAN links  are significantly slower than LAN, which is pretty much always the case.  

If a Connect post helped you out, be sure to click "Mark As Solution" or the "Thumbs Up" button to let other users know about it.

WK01's picture

Would using the option connect to the site server with the fastest connection be the best choice?

Also, we are trying to setup a task to "reset task agent" to help get machines pointed to the right site server.  A lot of machines are offline, is there a way to set this up to run on the machine when it comes back online?

andykn101's picture

You could try using a Policy with the Reset Task in it.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

WK01's picture

One final question.

It seems like using the "reset task agent" as a task or job does not always force the agent to correct the proper site server.

However, by using "Reset Agent" on the RAAD tool, it seems to have a higher success rate.  Is that normal?

andykn101's picture

I've not noticed, I don't see how it can be. Have you tried comparing client logs? Maybe turn on verbose logging.

Don't forget the Task Servers aren't really designed to minimise WAN traffic, if it wasn't for the requirements of Deployment Solution you could have 20,000 clients over 5 sites and put all the Task Servers in your datacentre and it would make no difference to the WAN traffic, the tasks still have to get from the NS to the clients.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.