IF GUP could Handle Product Updates aswell
Say i have a network of 10,000 clients
One main site having 5000 clients and 50 other sites having 100 cients each.
Many of the sites are remote off-shore sites with as usual bandwidth problems
I am using GUP for Definition updates on all of these sites.
Now as there are so frequent MR and MP releases that everytime a product update comes I have to push it out to all the clients.
Even if I assign the package all the clients try to upgrade at once that chokes up the whole bandwidth.
The only option available to me at the moment is Export a package and send it to the Admins in each location with Clientremote.exe so that they can deploy it locally.
So if GUP could have Downloaded the Delta package from SEPM and distributed it to all the Clients in that group it would have Solved this bandwidth issue everytime there is a update.
Comments
This is being considered
Hi all,
Thanks for the feedback, we are considering implementing this.
Note, with SEP 11.0.5 the average size of a product update which is distributed via 'auto-upgrade' via the SEPM console 'install packages' tab of a client group will decrease to 10-15mb. This is down from what used to be 45mb+, so hopefully this will help a little in the meantime.
Plus, since 11.0.4 MP2, it is possible to specify a remote HTTP server location to host client update packages.
All that said, I understand how allowing GUPs to update the product would be useful.
Best Rgds,
GrahamA Product Management, Symantec Security Solutions
very good idea.
very good idea.
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Functionality for GUP
Hi,
This is really required. A good feature to have.
Mostly organizations have a centralized operation centre where they would obviously keep all their master (central) servers. The remote offices would always have a lower pipe of bandwidth which is primarily used to synchronize data between centralized operation centre or to get the updated policies from the domain or servers like SEPM, SCCM, etc. With the current design of SEPM; all remote SEPM clients will jump back towards the central SEPM server to get the product updates. This will surely choke up the bandwidth.
An ideal way would be to create an update package from the central server and execute this package to update the GUP on all remote offices by executing them on individual GUP's (but would not be feasible if an organization have a huge number of GUP's). Best option to have is that-SEPM should provide a functionality that once the SEPM master server is upgraded all GUP's will get updated as per the defined schedule (defined schedule would be the non-peak hours). SEPM clients in individual locations would request their GUP to have an update.
I agree. A good feature to
I agree. A good feature to have!
Update Packages per Location or per GUP
Using the feature to specify a remote HTTP server location to host client update packages you can only specify per Group. If the Group has more locations, the client gets the upgrade in only one location.
If we could specify Update Packages per Location would help us.
If you have 10,000 clients
If you have 10,000 clients you really should already be using Altiris, SCCM, or some other software package management infrastructure for deployments.
The ability of SEP to upgrade is better suited to smaller environments. I can't even remember the last time I used client remote in a large environment.
Although it would be nice if ALL SEP communications went through the GUP's.
Z
Would you like to reply?
Login or Register to post your comment.