SCCM OS Deployment
- Thread starter anything I don't mind
- Start date
yea sccm osd is slow at every point. This is after making the capture image and setting up sccm. This process will need to be completed nearly every time you make a mistake or need to tweak the wim or the task sequence.
Capturing the image to USB (30mins)
uploading the image to the sccm server (20mins)
adding the image and distribute to dp (30mins)
create task sequence and distribute packages to dp (30 mins)
1) create the offline boot media (1 hour) = 25 mins image process
2) boot from pxeboot over gigabit network (5min) = 1 hour image process
This is when you know how to work it all.
Capturing the image to USB (30mins)
uploading the image to the sccm server (20mins)
adding the image and distribute to dp (30mins)
create task sequence and distribute packages to dp (30 mins)
1) create the offline boot media (1 hour) = 25 mins image process
2) boot from pxeboot over gigabit network (5min) = 1 hour image process
This is when you know how to work it all.
Associate
- Joined
- 5 Feb 2009
- Posts
- 424
I've worked with SCCM for 4 years - initially we just did s/w deployment but we moved to OS deployment. What you MUST do is take time to set up your environment properly. Driver Packages, your network, distribution points properly placed, servers adequately sized etc. We have many thousands of users and many different types of hardware in place, but it is an EXTREMELY powerful product and helps you automate a large proportion of your desktop management processes.
As mentioned you can also integrate with SCSM and SCOM and you can end up with a very near zero touch environment to free up your staff to do less mundane tasks. You can have lots and lots of self service, particularly if you hit SC 2012 versions.
It can be frustrating as it is not a simple product to master - I appreciate that.
Things like offline boot media you need to do once (unless your adding hardware and need to streamline network drivers into your WinPE boot image).
Also remember that, from 2012 (which is a big improvement again, akin to SMS 2003 -> 2007), you can service your OS image offline - slipstreaming updates into the image. 2007 did have it's quirks admittedly.
If you have a very similar image across all your network, you could quite feasibly operate a single image, single task sequence solution. You can alter the task sequence to include HTA frontends and/or you can use Collection variables to alter which parts of the task sequence executes. For example, say you want senior team members to have piece of software X, you include a collection variable for SMT machines, evaluate that variable during the task sequence and install software "X".
Honestly - get your head around it and you'll suddenly see a big gleaming light at the end of the tunnel.
Your times above are probably valid with the exception of 2 - the pxeboot seems long. Have you done a lot of customisation to the WinPE Image? You should only need to put network drivers in here most of the time and perhaps a custom background. Anything more and you'll end up with a bloated WinPE image.
Also make sure your DPs are multicast enabled AND the network is configured properly for multicast - I see a lot of problems occuring because of this. Over a gigabit connection, multicasting, we see download times of an image of a similar size to yours of ~12-15mins.
As mentioned you can also integrate with SCSM and SCOM and you can end up with a very near zero touch environment to free up your staff to do less mundane tasks. You can have lots and lots of self service, particularly if you hit SC 2012 versions.
It can be frustrating as it is not a simple product to master - I appreciate that.
Things like offline boot media you need to do once (unless your adding hardware and need to streamline network drivers into your WinPE boot image).
Also remember that, from 2012 (which is a big improvement again, akin to SMS 2003 -> 2007), you can service your OS image offline - slipstreaming updates into the image. 2007 did have it's quirks admittedly.
If you have a very similar image across all your network, you could quite feasibly operate a single image, single task sequence solution. You can alter the task sequence to include HTA frontends and/or you can use Collection variables to alter which parts of the task sequence executes. For example, say you want senior team members to have piece of software X, you include a collection variable for SMT machines, evaluate that variable during the task sequence and install software "X".
Honestly - get your head around it and you'll suddenly see a big gleaming light at the end of the tunnel.
Your times above are probably valid with the exception of 2 - the pxeboot seems long. Have you done a lot of customisation to the WinPE Image? You should only need to put network drivers in here most of the time and perhaps a custom background. Anything more and you'll end up with a bloated WinPE image.
Also make sure your DPs are multicast enabled AND the network is configured properly for multicast - I see a lot of problems occuring because of this. Over a gigabit connection, multicasting, we see download times of an image of a similar size to yours of ~12-15mins.