SCCM 2012 R2 : Deploying an image

[CapnPugwash]

I'm just starting to play with SCCM 2012 R2 & I'm not having much joy deploying an image.

 

I've enabled PXE. Added an OS image, pushed the boot image and the OS image to the distribution point successfully

Created a basic task sequence and deployed it to a test collection that contains one machine

 

On my DHCP server I've set option 66 to the IP of my SCCM server and option 67 to \smsboot\x86\wdsnbp.com

 

When I F12 the machine that I want to put the image on (and select boot from network) the on-screen text shows the message "Message from Administrator : Configuration manager is looking for policy"

 

Looking at the SMSPXE log I can see that the job is initiated, it finds the target device and verifies that it is in the database. It doesn't actually seem to throw any errors and the last two lines of the log are:

 

Looking for bootImage P0100002

SMSPXE 12/05/2016 15:47:06 2824 (0x0B08)

Prioritizing local MP http://SCCM.mydomain

SMSPXE 12/05/2016 15:47:06 2824 (0x0B08)

 

P0100002 is the correct resource ID of the Boot image

 

Is there any other log files I can look at that might give me a hint as to what's going on?

I've got a lot of machines to rebuild!

[CapnPugwash]

Just to add to this: On the target machine, when I reboot / Press F12 / Select boot from NIC, the machine boots & on-screen I see 'Downloaded WDSNBP from [sCCM IP]'

 

After it says "Message from Administrator : Configuration manager is looking for policy"

 

It contacts the SCCM server & quits.

 

From some online documentation I've seen I would expect to see a message like : TFTP Downloading smsboot\x86\wdsnbp.com

 

...

[localzuk]

Is it a 32bit machine you're using? We have the bootfile set to SMSboot\x64\wdsnbp.com here, as all the images are 64bit.

[CapnPugwash]

Turns out it was just me being an idiot... Hit F12 again (just like all the documentation told me to!) & I'm in business

[sparkeh]

If you are just starting out then I would advise upgrading before you get too far in.

 

SCCM has moved to a SaaS approach. The latest version of Config Manager Current Branch is v1602 (which adds Win 10 servicing support) but you have to install v1511 and use the in console upgrade to v1602.

[markwilfan]

+1 for upgrading to 1602. Makes following the current branch much less painless as upgraded are done in the console.