Hello. I am looking for some assitance with Task Sequences for Deploying Windows 7 using SCCM 2007 & MDT 2010 Our Task Sequences for OSD were created & configured by a Contractor, who has now left the Organisation, with scant documentation left behind. I have now "inherited" management of these Task Sequences. We are proposing to use Windows 7 Professional for all Desktop deployments, and Windows 7 Ultimate for laptops. We thus have different Task Sequences for the Win 7 Pro and Win 7 Ultimate deployments. In addition, there are 2 Task Sequences named "Reference win 7 Pro" and "Reference" Win 7 Ultimate"; these "Reference" TS's have the "core build" configurations & software (eg, Flash, shockwave, AV software, MS Office, .NET etc) Both the Pro and ultimate "reference" builds contain the same software in the "Install Software" stage of the Task Sequence. Next, there are 2 TS's - "Deploy Win 7 Pro" and "Deploy Win 7 Ultimate" - these will be used as the basis for the "Departmental Builds", containing the "business software" for the various Departments. (Note - it is my understanding that the TS's were configured in this way to reduce admin overhead, e.g., if there is an update to any of the "core software", only 2 TS's need to be amended. It is also my understanding that the "Deploy..." TS's are to be used for any actual deployment, and that the "Deploy..." TS's are linked to the respective "Reference" TS's) Ok, so far, so good. I am able to successfully deploy the Windows 7 Ultimate OS to laptops, using the steps described above; all the expected software etc is installed on the laptop. However, with the Desktops & Win 7 Pro TS, when we deploy an OS, the "core software" is absent. I have checked the respective TS's, for woth Pro & Ultmate, and for both the "Reference" and "Deploy" versions; other than the versions of Windows being used etc, I can see no difference between the Pro & Ultimate versions. I am also unclear as to how the "Deploy..." TS's might link to the "Reference..." Ts's, so I can confirm that is working. Can someone please give me some pointers as to how I might debug this, and identify what step is incorrect and preventing the core software loading for the Windows 7 Pro deployments? (Note - I can supply XML extracts, screenshots, etc if required) Regards Stan

To start learning OSD/MDT - take a look at these videos http://www.deploymentresearch.com/Videos.aspxKent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

Thanks for the pointer Kent, however, this doesn't really answer my question. Many of the videos at the link are native MDT, as opposed to sccm; also, some are over an hour long, and I do not have the time right now to sit thru hours of video trying to answer my questions. I am reasonably comfortable with the basics of OSD; for this particular issue, I am looking to answer two specific questions: 1 - how can I debug the TS to understand why software is installing successfully from one Ts but not the other? 2 - how can I identify the "mechanism" whereby the "deploy.." TS links to the "reference" TS? IE, how can I dentify the "join"? Many Thanks Stan

Guys: I've managed to dig thru the documentation & found an aswer to at least one of the questions: - The reference build is created from source media and produces a WIM file containing Windows and a core set of applications -The deployment build is deployed from the aforementioned WIM and customised by the TS using sysprep, usually more applications are installed at this time Excellent! I am now happy with how the "reference" & "deploy" Ts's are "linked". As to the question of why some software is not installing; this software is in the "reference" TS; therefore it will be in the WIM file used by the Deploy TS. This WIM may have become corrupt; is there a way to recreate the WIM file? Presumably, I would then update the DPs? Regards Stan