How can I deploy a Hidden task sequence in Configuration Manager 2012 SP1

[anyweb]

<![LOG[Provided preferred deployment CR320028 is not found among the available deployments.]LOG]!><time="07:59:12.365+240" date="08-12-2014" component="TSPxe" context="" type="3" thread="964" file="tsmediawizardcontrol.cpp:1502">

 

 

there you go !

 

so is this computer in a collection targeted by that depoyment above and is the deployment deployed with a purpose of hidden

[P@docIT]

I have it deployed to the "All Unknown Computers" collection. It is set to media and pxe only (hidden), purpose is available. The weird thing is it did work a few times before it stopped working and i changed nothing in CM.

[P@docIT]

So I deleted the deployment to all unknown computers and created a new deployment pointing to the All Systems collection it's now working. Very weird since these devices are brand new out of the box and definitely unknown. Anyway working as I need it to now. Thanks.

[anyweb]

check Devices under assets and compliance,

 

do you see a whole bunch of UNKNOWN objects (please do NOT delete the UNknown Computers collections)

 

you can delete all the unknown devices (not the collections) then try again, 1 shown below but i've seen up to 91 in our production environment....

 

 

 

[P@docIT]

I had done that already. What I found is that the two built in Unknown Computers (x64 and x86) are also in the All Systems Collection. Not sure if that collection is taking precedence or what. The machines are definitely unknown, brand new out of the box. Very strange but deploying to All unknown just won't work, only All systems.

[mikeyp]

If you use/have PowerShell built into your WinPE image, you could avoid using any files at all with this one-liner in the "Prestart command settings">"Command line" box:

powershell.exe -noprofile -command "$TSEnv = New-Object -ComObject Microsoft.SMS.TSEnvironment;$TSDeploymentID = Read-Host 'Enter the TS Deployment ID: ';$TSEnv.Value('SMSTSPreferredAdvertID') = $TSDeploymentID"

Partly leaving this here so I can find it in future. ?

[Abnrangerx67]

 Great post, thanks will give this a try because now that we are deploying win11, but want to keep a win10 ts but have it restricted to "as requested". By hiding it, a ticket would need to be submitted and the deployment ID provided. Is there a way to use another form of "id" that we can rotate let's say monthly? Maybe overkill, but just trying to find a way to keep this as restricted as possible, because I suspect someone will get wise and know the deployment ID is not changing so they won't ask for it anymore. Now that I think of it, maybe we can just create a new deployment every month so the ID get changed. I will see how that works, but definitely open to some ideas.

Edited Wednesday at 09:53 PM by Abnrangerx67

[Abnrangerx67]

Apologies, so with the boot image in place and used by our main TS. how would have an additional boot image for the hidden TS work or affect the unknown computers collection when it is time for OSD? My concern or wonder is what happens when a new/BareMetal computer is PXE booted, how is the "correct" boot image selected to be presented for the correct imaging process?

[Abnrangerx67]

I gave this a try but it did not work. Not sure if it is because I used the x64. However, it did raise a concern that I was afraid would happen. When I PXE booted, the correct WIM did come down, but as mentioned in my other post, what if this was someone else and they wanted to access the visible TSes? Aside from assigning to a known collection, how do you use this on the unknown computers collection for baremetal imaging while still using the other normal boot images for traditional imaging?

[anyweb]

5 hours ago, Abnrangerx67 said:

I gave this a try but it did not work. Not sure if it is because I used the x64. However, it did raise a concern that I was afraid would happen. When I PXE booted, the correct WIM did come down, but as mentioned in my other post, what if this was someone else and they wanted to access the visible TSes? Aside from assigning to a known collection, how do you use this on the unknown computers collection for baremetal imaging while still using the other normal boot images for traditional imaging?

you can deploy multiple task sequences to the same collection with a purpose of Available, some hidden, some not, the hidden ones just 'won't appear' unless acted upon using my script or a modern version of it (Powershell), the thing that matters here (for hidden task sequences) is the deploymentID