Task Server Confusion
I'm having trouble wrapping my head around Task Server functionality and was hoping someone could answer a few questions.
1. I have several Site Servers configured with Task and Package Services and each have only that particular sites subnet assigned to it. For other locations (without a Site Server) with computers on subnets that have not been assigned to a site, will those computers just choose any Task Server available?
2. If I have a "Site Server 1" with only Package Service installed assigned to subnet 1, and then I have another "Site Server 2" with Package Service and Task Service installed assigned to a subnet AND the subnet of Site Server 1 (for Task purposes), will a package delivery to a computer on subnet 1 try to use Site Server 2 as the Package Server instead of Site Server 1?
3. Should a "Site" be created for the Notification Server and assigned it's own subnet? I did this and only assigned the subnet for the server which has very few systems but I still have computers from other subnets connecting to my NS.
Thanks.
Comments 1 Comment • Jump to latest comment
I suspect you might have read it but most of the answers are here:
"Best Practice: Managing Task Server Communications in 7.0 and 7.1"
http://www.symantec.com/docs/HOWTO48411
1. Yes. Reset Task Agent on a PC on a site with no Task Server and watch the log to see if there's any clue as to how it's working in your environment.
2. I don't think Task Service affects package downloads. So the client will just act like it has two pacakge Servers and use the fastest I think.
3. I think the only way round this is to schedule a Reset Task Agent Task on the Filter of Task Agents connected to the NS (Filters > Computer Filters > Task Service Filters)
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
Would you like to reply?
Login or Register to post your comment.