This content has been marked as final. Show 8 replies
the wakeup would work for global updateing to indiv. subnets but if you are already using update tasks anyway then you can tell the workstation only sites to run down the repository list using ping time and pick the nearest one, they would just be updateing on the schedule you have set rather than global updateing (which isnt much of an issue at all)
Thank you very much for your help Tonyb99 !
I won't use the global updating features.
I would like to use a classic server task to upgrade the SuperAgents repositories.
Will my clients be able to go to the SuperAgents repositories even they're not on the same subnet ? I think so.
not to the superagents but if you set distributed unc respositories instead then yes
The policy will be applied to a group in which all servers will be upgraded from standard agent to super agent with the following parameters checked
* convert agents to superagents (windows only)
* use system runing superagents as distributed repositories
So for me, these superagents become distributed repositories and the SITELIST.XML is updated. Because ALL clients get this file, I don't understand why the clients won't be able to communicate with the repositories who are on the superagents ? :rolleyes:
Thank you for your precious help.
Infact they will, in my opinion
But they will be not waked-up by SuperAgents wakeup calls, be aware of it.
So if u want to use them only for repositoring targets, it's ok.
Tonyb99 : not to the superagents
And the winner is ... ? grin
You correctly stated that the SAs will appear in the sitelist.xml on all CMA (if u do not set different CMA policies).
So the list will be compiled by every CMA, according to your default Rep list policy, and CMA will update from the first valid Rep found, even if not on the same subnet.
The clients will be able to use SAReps just as any other distributed reps. Even if global updating is disabled.