Hi all,I have 4 departments that I would like to have different OS deployments too. In other words, they are all Windows XP SP3 however one department may need Office 2007 whereas another needs Office 2003. There is other varying software as well. I want to have a ZTI for each department in my organisation.What I wanted to be able to do was have 4 different OSD Task Sequences, all advertised and when I PXE boot, have the abillity to select which Task Sequence I would like to run. At the moment, WinPE just picks up the latest Task Sequence I have advertised to the collection. I am currently using one collection I created (Build and Capture Windows XP).Couple of options:1. Is it possible to have multiple Task Sequences available to select in WinPE on PXE boot so I can select which Task Sequence I would like to use. This is assuming if I had 20 desktops - I imported all 20 blank desktops into one collection and could select which Task Sequence I wanted to use (e.g. 4 desktops are one department, 5 to another and so on)2. My Active Directory is setup so that I can havecollectionsbased on department in SCCM. I have also created these Collections in SCCM based on OU. Do I need to import the PC I want to image (these are new PC's from Dell) into the Active Directory OU setup in SCCM assigned to the appropriate department and have a Task Sequence OSD deployment advertised on that collection.Any help would be appreciated on which way is best practise or what other people have found good.My current system setup is as follows:1 x Windows Server 2003 Server (AD / DNS / DHCP)1 x Windows Server 2008 Server (SCCM 2007 / SQL 2005 / IIS)Regards

You probably madea MandatoryAdvertisements of the Task Sequences.

Another option is to try and use a single TS for all departments... most of the TS steps can be customised at runtimethrough collection variables so you can deploy systems to different business units (with different configurations) using a singe TS. In terms of application installation you can use the "Install Multiple Applications" step and use collection variables to specify the package IDs and program names.All you need to do is set up a collection for each dept and configure the appropriate variables against each collection to customise the deployment process. PCs added to one collection would then install Office 2007 during the task sequence and another collection could be used for PCs that require 2003. However the same TS can be advertised to all collections.We are using this approach for a large enterprise environment. The TS, boot image, os image, drivers and core apps are all centrally managed from the primary site. The child site admins then just create collections,add their own local packages, set the collection variables etc. and then advertise the TS. They can customise most elements of the deployment process to meet their needs (disk partitioning, service pack level, domain, language, regionalisation, applications etc.).I guess it really depends on whether the additional development time for creating the single TS is really worth it in your environment. If it is only 4 departments then perhaps it's no big deal to have separate TS's. Just a thought...

Thanks for the responses guys.The enterprise level solution is probably a little overkill for our organisation however very interesting to see how you've done this.peterwoude - yes they are mandatory advertisements. However, when I don't set them as mandatory I am unable to PXE boot to them. My PXE is picked up fine and I'm assigned an IP however it then just pops up with TFTP download for about 5 seconds then continues on to boot to the OS that is installed (or next bootable device).Do I need to do something else?Regards

Why don't you just create a separate collection for every Task Sequence?

Yes that was what I was looking at. Setting a Task Sequence for Deployment on different collections to build each department machine.e.g. 3 departments (these are detected from OU based Collection in AD):Member ServicesClient ServicesFinanceAnd then assign a different Task Sequence for each as they have different desktop builds.Was just wondering that's all if you could select a task sequence from a WinPE menu on PXE boot asking which Task Sequence you would use. This would enable you to just drop any new machine into one collection and then select which Task Sequence you would use on PXE boot

Well why do not use simplicity ;) ? I always try to make dynamic TS that will acomodate to businness needs accordingly. In your case I would have a variable on the collections department for instance Finance collection - variable DEPARTMENT with value FINANCE And a group that executes in TS if the variable DEPARTMENT=FINANCE In this case you would have just one TS :) And during reimaging you would not have to worry about choosing the correct TS. This is only of course for refresh scenario. In scenario new computer I do not know what is your approach but you could just import it into SCCM with correct variable for DEPARTMENT Hope it helps Blog at http://www.rpieniaz.wordpress.com