Our environment uses a fairly slick OSD task sequence that is applied to a large number of collections. For the next step in it's feature development I have been tasked with detecting which Collection in SCCM the advertisement was received from. The purpose is to detect if the advertisement came from a collection named "Windows XP Only" and to use a windows xp image. I need some guidance on how to detect that originating collection from inside my OSD task sequence. Thanks in advance!

I don't think there's an easy way to figure that out. An easy thing to do though would be to set a collection variable on each possible collection and then query the variable or use it as a condition in the TS itself.Jason | http://blog.configmgrftw.com

I don't think there's an easy way to figure that out. An easy thing to do though would be to set a collection variable on each possible collection and then query the variable or use it as a condition in the TS itself. Jason | http://blog.configmgrftw.com Thanks! I didn't realize I could do it that way. I will try this tomorrow and mark this as an answer if it works. Thanks again Jason. :)

I don't understand. If you advertise your TS "Install Windows XP" on collection with name like "OSD Windows XP" when you will receive only this TS. If you're add your computer to three collections such as "Install Windows 7", "Install Windows XP" and "Install Windows Vista" when you will receive three advertisements. And you can't detect from which collection you run task sequence advertisement because you can't do it.

Very true. It really depends upon a lot of factors. To handle this scenario, you could also set another TS variable in the task sequence itself and based on some basic logic deduce which collection is being used. Clients simply don't know which collections that they are members of so you have to devise a scheme to let them know. Jason | http://blog.configmgrftw.com

Very true. It really depends upon a lot of factors. To handle this scenario, you could also set another TS variable in the task sequence itself and based on some basic logic deduce which collection is being used. Clients simply don't know which collections that they are members of so you have to devise a scheme to let them know. Jason | http://blog.configmgrftw.com Yes, exactly. Thanks again, this saved the day. We are using a single advertised image to deploy everything from Windows XP 32-Bit to Windows 7 32-bit / 64-bit. With a lot of logic to analyze your machine and your current location. We have a large school district with a LOT of requirements for the older XP OS. Thanks to the variables on the Collections we are able to add an even more support for customizing image selections. Thank You again Jason. :)