Jump to content

Recommended Posts

Posted

Afternoon,

 

We have taken delivery of a number of laptops for our staff and we would like to use SCCM to image them. previously we have only used SCCM on existing devices already in AD. So, what I was wondering was, is there a way to add these devices to SCCM to image them without having to go through each device and set up windows 11 to get into windows to install the client?

 

Any advice would be much appreciated?

 

Thank you

Posted

If you have deployed your task sequence to unknown computers collection with the (pxe) then when you pxe boot them you’ll get into SCCM and have the option to install it from there

 

Steve

  • Thanks 1
Posted
We used to have SCCM (Intune Autopilot now) we used to deploy to all unknown PCs via PXE. This would mean any device connected to the network can PXE boot to the SCCM Task Sequence. Obviously password it down!
  • Thanks 1
Posted

SCCM has 2 built in devices, x64 Unknown computer and x86 Unknown Computer. There should be a collection with these 2 devices in. Deploy your imaging task sequence to the Unknown Computer collection and once a new PC PXE boots a computer it doesn't recognise it will attempt to apply the image.

 

Your task sequence may need modification to allow for things like an unknown host name and joining the PC to a domain. You might want a separate task sequence just for new PCs.

 

You also need to be careful if your boot images aren't password protected as anyone could plug a device in to the network and get an image.

  • Thanks 1
Posted

We used to add the devices manually to SCCM - using their MAC address, assign them to a collection with a deployment on it, and then pxe boot the device.

 

Now, we swapped to deploying all our task sequences to the All Unknown Computer devices, with the boot image password protected, and then have a HTA window that pops up during the first step of the image - where you pop in the desired PC name, and specify which OU and collection the device should be in by default. The rest is then automatic.

Posted
How do you set that up with the PC name? that would be ideal.

 

thanks

 

You add a step in the TS to set device name during the setup. Ours was

 

1) Boot device to PXE

2) Put in Password

3) Select Relevant TS

4) Name Device

5) Leave to build - Job done

Posted (edited)
You add a step in the TS to set device name during the setup. Ours was

 

1) Boot device to PXE

2) Put in Password

3) Select Relevant TS

4) Name Device

5) Leave to build - Job done

 

Thanks have managed to do it using OSDCOMPUTERNAME variable.

Edited by donkeymusic
Posted

We have a HTA app that sets variables via VBScript. Its in a Package in SCCM, which you add to the task sequence.

 

The environmental variables we set are

 

env("OSDComputerName")

env("osdjoindomainouname") - this is then %OSDJoinDomainOUName% in the Domain OU box in Apply Network Settings.

env("StationGroup") - this is then used in a separate script step via another VBS script to add it to an AD Group, which links to a Device Collection.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...