Allow product updates to be distributed via the Group Update Provider
Updated: 01 May 2010 | 6 comments
Status:
Reviewed
(re-posting previous requested item)
We have a large number of remote sites which are connected across low-bandwidth network links to the site where our SEPM resides. It is difficult for us to distribute new maintenance releases and product patches to the machines on these remote sites due to the bandwidth. We use Group Update Provider on these sites to distribute content updates every day. We would like to also be able to use the same method to distribute product updates.
Comments
IF GUP could Handle Product Updates aswell
Already posted
IF GUP could Handle Product Updates aswell
https://www-secure.symantec.com/connect/idea/if-gup-could-handle-product-updates-aswell
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
That would be great
We have several offices all around the world but only one Endpoint Manager.
This was recommended from Symantec !!
The last update of the product was a complete disaster. Our network connections were overloaded for two days.
But in every office we have a gup.
Symantec told me three weeks ago, this item is on the roadmap, but last week they said it disappears from the roadmap.
Is this true??
Thanks
Martin
Really need this
We have aprrox 1000 VSAT locations. The low bandwidth is preventing me from ever upgrading the client agents.
------------------------------------------------------------
MR99 will fix it all.
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
Anything happening on this?
Anything happening on this?
------------------------------------------------------------
MR99 will fix it all.
Already discussed
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 have posted same comment where this discussion happened some days back. see link - https://www-secure.symantec.com/connect/idea/if-gup-could-handle-product-updates-aswell
Would you like to reply?
Login or Register to post your comment.