SCCM imaging - stupid question

[gerardsweeney]

All..

 

SCCM noobie here!

 

I've been tasked with creating imaging jobs for our recently installed SCCM.

I've created a Task sequence that installs Windows, injects drivers etc - all good.

 

Our main PXE deployment setup has a password to prevent anyone being able to run anything untoward.

So we hit F8, boot disk downloads and you get prompted for a password.

 

However.. I'm now trying to roll out the image deployment jobs to PCs (eg at midnight).

That obviously presents a problem, as it just boots to boot disk and sits asking for a password.

 

How can I have my boot disk/Task Sequence setup so that I get the best of both worlds?

 

Cheers,

Gerard

[Steve21]

Funny you say that as we were looking at this.

 

Seems the official answer is remove the password, and hide the task sequences. So even if they do boot into it they can't see it. However that caused the question of how to do a manual "in the room" build which we couldn't figure out, so never did enable the option

 

Be interested if you do find a way

 

Steve

[jaminben]

From memory I think you can set your task sequence to run as Required and then make it available only to Configuration Manager Clients rather than PXE (in the drop down).... it's been a few years since I've done it though so probably wrong.

[gerardsweeney]

Splendid..

 

I vaguely recalled seeing the consultant have a running PC pull down the PE boot disk without going anywhere near PXE.

Which - coming from Altiris DS 6 - looked like sorcery

 

This sounds like it might be how he did it..

 

I shall investigate ASAP, and get back to you.

[ReadTheNetwork]

If you're trying to do a ZTO (zero touch)_ deployment, then the machines need to be switched on. You deploy the OS to the machines and it installs the OS automatically with no password intervention.

If you boot and press F12 then this is LTE Light touch.