sccm software updates question
hey
[/align]we just upgraded from sms to sccm recently and just tryin to work out a few things with software updates.
In sms i used to split up updates for office, xp, xp64 and vista. This was because the package would be huge and every pc regardless of if it needed it would download it all.
So i know the new one is better and it seems to work pretty well. Is there still a need to split things up? if i just package all required updates for all office and all operating systems and just assign it to an all workstations collection would that be ok?
thanks [/align]
[/align]we just upgraded from sms to sccm recently and just tryin to work out a few things with software updates.
In sms i used to split up updates for office, xp, xp64 and vista. This was because the package would be huge and every pc regardless of if it needed it would download it all.
So i know the new one is better and it seems to work pretty well. Is there still a need to split things up? if i just package all required updates for all office and all operating systems and just assign it to an all workstations collection would that be ok?
thanks [/align]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
LB3
15 years ago
You can build a collection based only on ones that need your updates right ? Then only push to those machines.
When you put your package in SCCM you also have the option to check the box to download the package locally to the PC before launch or not.
I'm not sure if it may be better to let them run it without downloading the whole thing to the local PC for you at your location.
I'm not aware of a size limitation in SCCM for packages but you have to think about the size going out to the distribution points then also transferring to the users PC if you choose to let it download locally first.
We used to do system wide pushes at night when we were using tivoli for larger packages. I haven't been responsible for doing system wide pushes where I am right now but just building advertised packages in SCCM so users can install software on demmand.
If you haven't seen it already there's some really good technet webcasts on various parts of SCCM here:
http://www.microsoft.com/events/series/technetmms.aspx?tab=webcasts&id=42364
hope some of that is helpful..
When you put your package in SCCM you also have the option to check the box to download the package locally to the PC before launch or not.
I'm not sure if it may be better to let them run it without downloading the whole thing to the local PC for you at your location.
I'm not aware of a size limitation in SCCM for packages but you have to think about the size going out to the distribution points then also transferring to the users PC if you choose to let it download locally first.
We used to do system wide pushes at night when we were using tivoli for larger packages. I haven't been responsible for doing system wide pushes where I am right now but just building advertised packages in SCCM so users can install software on demmand.
If you haven't seen it already there's some really good technet webcasts on various parts of SCCM here:
http://www.microsoft.com/events/series/technetmms.aspx?tab=webcasts&id=42364
hope some of that is helpful..
Posted by:
DeployTech
14 years ago
SCCM uses WSUS for updates, so there is no need to package and deploy to collections, the settings apply from GPO
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.