Best practice for advertising TS
Can someone please explain the best practice for advertising TS to a rebuild clients? Do i need to manually add every client i am rebuilding to a collection? Is there a way to get around that? Thank you.
October 19th, 2012 2:26pm

Given that you target collections with adverts, yes. However, collections can have dynamic query rules also. If you are wipe and loading the systems, then you can also use unknown computer support. The golden question though is how are you determining what systems to "rebuild"?Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2012 4:25pm

I currently created a collection based on the subnet. I can see some clients in that collection but not the one i am looking for. I checked default gateway on the client and it has the ip i defined in the collection. I am trying to boot from USB. Maybe its not reporting to SCCM? Not sure if am clear...... If i enter client by MAC then i can see the advertisement. I am trying to avoid manually adding clients to a collection. Thanks for the help.
October 22nd, 2012 11:53am

Hey, seems like you're confident that you want the advertisement to be directed at a collection that contains all computers of a certain subnet, right? what query did you use ? my subnet queries look like this (mind the .x.x.): select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.IPSubnets = "10.x.x.0"
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2012 1:03pm

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.IPSubnets = "x.x.x.x"
October 22nd, 2012 3:24pm

If computers move around, they can pick up more than one subnet, so it's not a super clean way sometimes, to get a accurate set of computers. What does your collection query look like? Default gateways don't always match an IP subnet exactly.
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2012 6:08pm

The question is, can SCCM see the subnet information when client in winPE stage? Or client needs to log in to windows for proper inventory and only then can see the subnet? I am trying to accomplish the following scenario: tech gets a client from a user, brings its to a location with a isolated sunbet. I would like the tech to pxe boot and get TS advertisement and rebuild. I would like to eliminate the need of manually adding the client to a collection. Is there a way to create a dynamic collection for that? Thank you.
October 23rd, 2012 8:45am

No, this will not work. There is no active ConfigMgr agent while in WinPE and thus no inventory data is passed to ConfigMgr. You can design your TS to key off of the IP gateway though as this is indicative of client subnet/location. This is what MDT does -- or you can just use MDT.Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 11:16am

No, this will not work. There is no active ConfigMgr agent while in WinPE and thus no inventory data is passed to ConfigMgr. You can design your TS to key off of the IP gateway though as this is indicative of client subnet/location. This is what MDT does -- or you can just use MDT.Jason | http://blog.configmgrftw.com
October 23rd, 2012 11:16am

Jason thanks for reply. So if i am not getting the full use of advertisement i am better of with just MDT. I dont need to create adv and collections. If client just would like to pxe boot then tney can get same result with just MDT. Not sure if they'll go for dropping SCCM OSD :)
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 1:44pm

Jason's right, I have a suggestion instead, if you can install a server in that subnet with PXE point + DP + unknown computer support - and advertise the TS to "All unknown computers" collection (make sure the TS is enabled for PXE and boot media), then in DHCP make scope option for that subnet with options 066 and 067 (boot server / boot loader path) that way only from that subnet computer booted by technician will have the option to boot to PXE with F12 and initiate a rebuild, inside the TS you can give them tools for Lite Touch Installation or completely unattended with Zero Touch, MDT will also get you a long way with that solution like jason mentioned.
October 23rd, 2012 1:45pm

Another option could be the following: Look at the properties of the TS and go to the Advanced tab. Select "This task sequence can only run on the specified client platforms" and select an OS that you don't run beneath it. Hardly anyone runs Windows 2000 SP4, so if you're confident that you don't have any in your environment, this can act as a safeguard. Then advertise the TS (do NOT make it mandatory - another safeguard!) to as many clients as you'd like. When the technician use PXE to boot the computer, the PXE environment won't care what OS is running. WinPE will kick in, the PSP will find the advertisement for the TS and voila - you can image from there. (Note: Big ups to Chris S. for dropping this little trick on me!)
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 2:01pm

I think this is the setup i have right now. If there is no issues with new/unknown client. However all rebuilds must be added manually to a collection that has TS advertised to it. I am trying to find a solution avoiding manual step of adding client to a collection. Trying to figure out if its possible to create a dynamic collection?
October 23rd, 2012 2:42pm

I am sorry, but i am not clear. How will the client see the advertisement? advertisement has to be to a collection and clients must get to that collection somehow?
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 2:44pm

My suggestion would advertise the TS to ALL clients, but they would only be able to see the advertisement if: 1) They were pressing F12 and launching into PXE or 2) They were running Windows 2000 SP4 as their operating system.
October 23rd, 2012 2:48pm

Got it. Dont think this is very secure :) Any user might have the ability to rebuild if there is no password. However if the PXE is only on separate subnet that might work :) Will test it Thank you,
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 3:10pm

Sorry, I didn't mean to drop OSD -- I would never suggest that -- I meant to incorporate MDT into OSD. This is what most folks do.Jason | http://blog.configmgrftw.com
October 23rd, 2012 10:47pm

I have not testing it yet, but i dont think the PXE will get the advisement. Windows 2000 condition should prevent PXE getting it since the condition is false. Also the only place where i can select an OS requirement is on the program level in the package. Where is possible can you condition the advertisement? Will test it.
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2012 7:51am

I do have MDT integrated in SCCM. But with MDT there is no need to advertisements and collections. If the goal to use PXE only then i think its easier with MDT only.
October 24th, 2012 7:53am

I have not testing it yet, but i dont think the PXE will get the advisement. Windows 2000 condition should prevent PXE getting it since the condition is false. Also the only place where i can select an OS requirement is on the program level in the package. Where is possible can you condition the advertisement? Will test it. PXE will not care what the OS the cilent is running because PXE knows that OS won't be operating when you hit F12 and get into PXE. You can select the OS requirement if you look at Task Sequences. Find the Task Sequence that you want to advertise, right-click it and go to Properties. Look at the Advanced tab and near the bottom, you can select the OS requirement. :)
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2012 12:53pm

I have not testing it yet, but i dont think the PXE will get the advisement. Windows 2000 condition should prevent PXE getting it since the condition is false. Also the only place where i can select an OS requirement is on the program level in the package. Where is possible can you condition the advertisement? Will test it. PXE will not care what the OS the cilent is running because PXE knows that OS won't be operating when you hit F12 and get into PXE. You can select the OS requirement if you look at Task Sequences. Find the Task Sequence that you want to advertise, right-click it and go to Properties. Look at the Advanced tab and near the bottom, you can select the OS requirement. :)
October 24th, 2012 12:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics