You just need a vbscript, or similar, to query wmi for the ip address which will then determine which ts it receives. You don't need to have the interaction.
Basically the hook runs a custom action, like a script, before the client in the winpe image retrieves policy from sccm. It is embedded in the boot image. Because the policy has not yet been retrieved you can use it to set the preferred TS like in this example. I use it to trigger webservices and orchestrator runbooks. Does that help? The other option you mentioned is using the single TS. Then use a script to get the ip address and set as a TS variable. Then run or skip groups depending on the ip address, or subnet. To get the ip address out of wmi you'll probably need a script because this info is stored in wmi as arrays. Andrew Von: [email protected] [mailto:[email protected]] Im Auftrag von Stuart Watret Gesendet: Dienstag, 24. September 2013 13:48 An: [email protected] Betreff: RE: [mssms] sense check pxe stuff Hi Craig, yes I saw that this morning - if the pre-execution hook (which I'm not familair with..) requires some interaction (in this example it does) then that wouldn't be the first choice I don't think. Maybe the script could be the subnet identifyer? I'll have to read up on "hooks"....... Thanks feel free to explain pre-execution hooks in english and a couple of sentences - that would help :) Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected] [[email protected]] on behalf of Craig Andrew (OIZ) [[email protected]] Sent: 24 September 2013 12:40 To: [email protected] Subject: AW: [mssms] sense check pxe stuff You can deploy both TS to all computers, as hidden deployments. Then you need a pre-execution hook to determine which site the machine is in and then set the preferred TS as a TS variable accordingly. Check this post on deploying hidden TS http://www.windows-noob.com/forums/index.php?/topic/6456-how-can-i-deploy-a-hidden-task-sequence-in-configuration-manager-2012-sp1/ Von: [email protected] [mailto:[email protected]] Im Auftrag von Stuart Watret Gesendet: Dienstag, 24. September 2013 13:29 An: [email protected] Betreff: RE: [mssms] sense check pxe stuff That would probably solve the problem, I want to run a separate custom usmt process mainly for that particular site; I shall chew on that....... Thanks. Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected] [[email protected]] on behalf of Jason Wallace [[email protected]] Sent: 24 September 2013 12:17 To: [email protected] Subject: RE: [mssms] sense check pxe stuff No you advertise a task sequence to a collection. The only thing that sits on the PXE Service Point is the boot image. Now I wonder if it is possible for you to have a single task sequence but with a query against IP information of the WinPE client directing you into different groups within the task sequence? ________________________________ From: [email protected] To: [email protected] Subject: [mssms] sense check pxe stuff Date: Tue, 24 Sep 2013 10:10:22 +0000 Is this possible? Currently we advertise one rebuild job availale to all our clients, from one pxe point. This works well, as users just F12 and nothing else. I have a new site, they need a different job; I don't want a choice forced upon the existing sites. Was thinking: New local pxe point on their subnet, ip helpers adjusted for them to point there. But can I advertise a TS to a specific pxe point? Ta Stuart Watret Offshore - IT Ltd
