We're running SCCM 2007 R2 with XP SP3 and Office 2007. First of all, I'm not the SCCM admin but I am allowed to make reasonable requests to him.

What we're looking at now is we have a department that is broken up into smaller divisions. Each division has a specific set of apps that they need installed.

The corporate XP image is essentially locked and we can't make any changes since it is used globally across the company.
Therefore we've come up with task sequences that will run to set up each division with their special set of apps.

So here's what I've been trying to do:

I have collections for each group and have the task sequences advertised to them with manditory high priority run immediately, ignore all maintenance windows etc.

So when I deploy XP to a new system, I add the computer name to the collection ahead of time. So hopefully it would pick up right after the initial OS build. Unfortunately it does not. SCCM being what it is does not give the instant gratification that I need and building a single system this way takes up to a day.

I've tried prodding it along by updating the machine policy and updating the collection membership every so often but still after the OS load is done, it can take up to an hour to populate.

We're trying to hand off SCCM system builds to our stockroom guys and would like to make it as simple as possible without requiring them to prod the client and console along.

Do you have any suggestions that don't require making image changes? What about putting something in the initial menu from Win PE that allows you to pick the OS and secondary task sequence? Or some kind of advertisement that has both?

At some point we are going to the third release of SCCM 2007 with the dynamic collections, but that may be a bit off from now and we're retiring our old Symantec Live State system that we currently use to deploy the software for this group.

The current method involves us loading the company image onto the computer, and then after that's done, installing the Symantec Livestate client and dropping the profile with all the apps on it on the system and hitting "Wake/Push" This gives us an immediate deployment and 15/20 minutes later the system is built completely. With SCCM it takes 45 minutes to an hour for it to even show up in the collection.

Any ideas?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


I ran into a similar issue, we support 100+ applications that any one can go to a particular machine. Management wanted it so that when a machine is reimaged, all of their software was immediately available. I ended up using a "Run Command Line" task that runs a VB script that determines what software is suppose to be on the machine that isn't already in that particular image and sets a TS variable that then when my "Install Software" task runs it installs each of the applications that are needed completing the task sequence. The techs then deliver the machine and I then let SCCM catch up on the backend at its own pace.
Answered 11/11/2010 by: spottedcoin
Senior Yellow Belt

Please log in to comment

Why not copy the OS Task sequence and modify to include the relevant software titles that you require, you will however have to create one for each collection.

This way it will be one Task sequence that images the machines (core image can be used)and then installs the relevant software for that department, with no waiting
Answered 11/23/2010 by: langa100
Senior Yellow Belt

Please log in to comment
Sounds like you need just the one task sequence, but within that TS you can put conditions on the software to only install if they are met. You can then set Collection Variables which can be used as the conditions within the TS.

Quite simple really, but will take a little time to set up.
Answered 11/23/2010 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity