sccm 2007 SP2 R3 Up to this point I've been having users send me their MAC and Name so I can prestage the computer association for a barebone deployment. Works fine but kind of a pain for end users so I'm looking into the PXE boot to unknown computers feature, so far the only problem I see is that I have 128 task sequences for 50 different physical locations. Is it possible to use unknown support to their specific boundaries or subnets and their specific tasks?

That's a lot of task sequences. You are able to have a single Task Sequence for all of your locations with and without use of unknown computers. Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

yes, each location has roughly 3 so collectively its 128 plus. Are you're talking about MDT?

no, this can also be done without MDT. Just advertise the TS to a parent collection and sure you have the newly imported computers in child collections. You can either use the customsettings.ini file (if you have MDT) to assign variables that control diferent values for the different locations etc. or if you do not have MDT, configure variables pr. collection.Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

Just advertise the TS to a parent collection and sure you have the "newly imported computers in child collections" This is how I do it now, I don't want to have to create the association. For barebones I want them to be able to PXE but only to their TS.

Hi jamicon, As Kent said "Just advertise the TS to a parent collection and sure you have the newly imported computers in child collections." means: Create a parent collection "Bare Metal", this collection contains sub-collections for your clients in different locations. So when the task sequence was advertised to this parent collection and a new bare-metal computer is added to SCCM, make sure this newly added bare-metal computer is added one of sub-collections of this parent collection "Bare Metal". "For barebones I want them to be able to PXE but only to their TS." What's difference between task sequences for different location clients? Why they need to be separated? In SCCM OSD task sequence, such as time/domain settings, different advertised programs, etc. can be configured in one task sequence for different clients. Hope this will help. Thanks

yes these collections are good for many thing but maybe I'm just not saying it correctly... Right now I advertise my OSD/TS's to the unknown group, works great but I don't want every location to see everyone elses TS. Simply making a parent collection with child location collections and then advertising the TS's does not achieve this.