SCCM - PXE Password for unknown

[ReadTheNetwork]

Hey all,

 

A little background of my current position:

I have AD groups such as "os-win7-x64-force", "os-win10-x64-force". If I add machines to this group, the device collection relating to those AD groups has the task sequence forced to those machines. This works well.

 

However, here's my problem - is it possible to have a variable in the groups (relating to the os-win#-x64-force groups) to bypass the PXE boot password? Which would then still enforce other builds to require the password?

 

I've turned off PXE password during summer to help speed up the build process.

 

Thanks

[snagrat]

Hey all,

 

A little background of my current position:

I have AD groups such as "os-win7-x64-force", "os-win10-x64-force". If I add machines to this group, the device collection relating to those AD groups has the task sequence forced to those machines. This works well.

 

However, here's my problem - is it possible to have a variable in the groups (relating to the os-win#-x64-force groups) to bypass the PXE boot password? Which would then still enforce other builds to require the password?

 

I've turned off PXE password during summer to help speed up the build process.

 

Thanks

 

Wanted to do exactly same thing today.

 

But don't know how.....

[mukz]

I don't think you can, its either on or off.

Do you have dells? We turn off onboard nic on the boot sequence but can still choose this as long as you know the Bios Password. Not sure if that will help as it is the same thing really

[sparkeh]

AFAIK it's on or off

[Steve21]

It depends on how you're planning to deploy your known machines.

 

If they're already deployed once, and you just want to reinstall them with the same images, you don't need to use pxe you could just use a deployment via ConfigMgr etc so they won't need to bypass the pxe boot as it's using the already installed OS just refreshing it.

 

If it's a brand new machine (whether known or not) you'd have to put the pxe password in.

 

The other option would be to move the pxe password entirely, and have a script (vbs or hta) as part of the TS build that checks something like the group you mentioned, and if it's not within it it asks for password, or boots you out of the TS, and if it is it continues.

 

Personally I'd be very careful with removing the PXE password though as that'd allow anyone to rebuild your machines (if known) themselves

 

Steve

[ReadTheNetwork]

Thanks for your input, decided not to bother. I did see you can run a password script on the task sequences, but for now I'm happy just to run it as it is. But I guess it doesn't really matter all that much .