SOLVED PXE boot Image deployment SCCM 1511

[apsenn]

Layout of my system

Hyper-V running with

1 VM = DC, DNS, and DHCP
1 VM = SCCM (WSUS / WDS)
Multiple clients being created and deleted

I have enabled PXE on the SCCM server, verified that the WDS role got installed and see the folders under

E:\RemoteInstall (SMSBoot, SMSImages)

On the DHCP server I have set the following options

66 = 192.168.2.51 (IP Address of SCCM Server)
67 = SMSBoot\x64\wdsnbp.com

PXE is enabled, Allow Distribution point to respond to incoming PXE requests, Enable unknown command support. Respond on all network interfaces

What I am seeing, is PXE is not booting constantly, seems it only wants to boot for known machines, even though it is set to Enable Unknown Computer support

I tried with multiple fresh VMs and PXE fails, in the quick info I see it get a DHCP address and Lists Server address of the SCCM Server. On HyperV I am testing with 2 different VM Types Generation 1 and Generation 2 (Seems Gen 2 is UEFI) Gen 1 appears to do nothing it just fails to boot never see DHCP request or anything.

I have a machine that was running Windows 10 and is in SCCM and had the client, I deployed an available image to it and booted it from a Bootable media I created, and it went to image but failed with error 0x8004242C after or during the Format of Hard drive for UEFI.

After that it rebooted and successfully PXE'ed except I had to Press Enter to continue for network boot, which I don't want. It still failed with the same error for the image.

I then made a Required Image deployment and deployed to the same machine and one 1 try saw PXE go without asking and booted and tried to image, but failed with same error again. Now it is back to failing to PXE at all, and I am not sure what is causing these errors.

Goal is to get PXE working to where I can create new VMs and kick off the images on them without them having to be in SCCM at all first, and they will get domain joined and get sccm client after that.

Also just tried this machine with the bootable media and it boots and tries to apply image but fails with same error, (Fails at Running Action Partition Disk 0 - UEFI)

Truthfully I would probably want to get this working without UEFI at all, and just use Legacy mode.

Thanks

 

[Prajwal Desai]

For the new VM's when you PXE boot, at what stage does it restarts ?. Do you have a screenshot of it ?.

 

[apsenn]

I have attached 2 pictures

Legacy = Error I get when trying to PXE a Hyper-V Legacy network adapter
UEFI = Error I get when trying to PXE Gen 2 which is UEFI (That boot has worked sometimes but image then fails)
Image Fail = The errors on the Task Sequence

PXE errors are confusing on the legacy as it doesn't even seem to try, on UEFI as it boots sometimes not sure but trying to figure out where to look for more troubleshooting.

Thanks

 

[apsenn]

Think I have solved part of this, the computers I was trying to PXE are unknown comps, as that is my goal is to be able to PXE any machine with prestage. I found that I did not deploy the task sequence to all computers, as I did not know this was required. I also as part of my testing have moved the VMs from Hyper-V to VMWare Workstation, going to test back on Hyper V

But a new VM on Vmware workstation was able to PXE just now, after deploying the Task Sequence I have to all unknown computers.

But part 2 of the issue still exists, the Task Sequence still fails with error 0x8004242C as mentioned before. PXE also works on the UEFI machine after deploying to the unknown computers group (Which I had thought this machine was known, but understand it may not be as its been erased for a bit)

But hopefully can now find the issue with the Task Sequence

Thanks for any assistance.

 

[apsenn]

Another update

No longer getting the 0x8004242C error, changed the size of the HD on the VM I was trying to install and it worked, not sure why when the wim is only 3 gigs or so (Seems small going to recapture) But hard drive was 20 GBs now 50 GBs and the new error is

0x80070002 (Saw a whole post dedicated to this, but the Network access account is set and has been set on image, looking further and making a new wim for testing

 

[apsenn]

Update - Recaptured a new Windows 7 Image, added it to SCCM and created a Task Sequence for it.

This round the Install appeared to be going smoothly, got through Applying Image, and started Looking for drivers.

Then failed again with the same 0x80070002 error, there are currently no drivers installed or added into SCCM as I am only deploying to Virtual Machines that don't need drivers

Here are the smsts logs files

From C:\_SMSTaskSequence\logs\smstslog\ (Post Image Apply) https://dl.dropboxusercontent.com/u/59229956/smsts.log
From x:\windows\system32\smsts\ (During boot and such https://dl.dropboxusercontent.com/u/59229956/smsts-preapply.log

 

[Prajwal Desai]

Unsuccessful in finding a suitable device driver for device 'Generic Bus. Could you add the drivers to the boot image and test the OSD ? - http://prajwaldesai.com/import-vmware-drivers-to-your-sccm-boot-image/

 

[apsenn]

Added to Boot Image and got error again, but don't see the same output in log about drivers this time. Should those drivers also be deployed to the image, I currently have no drivers being applied to image, figure I am going to try with them

New Log

https://dl.dropboxusercontent.com/u/59229956/newlog/smsts.log

 

[Prajwal Desai]

Have you updated the boot images after adding the drivers ?. Is the updated version of boot image distributed to DP's ?.

 

[apsenn]

Hello, During the adding of those drivers, it gave me a message saying I would need to update the Distribution points and asked if I wanted it to do it. I said yes to that, and then checked on the boot image I do see that for the content it currently says

1 Targeted (Last Update 4/14/2016 7:54 AM)

If I understand that right, its saying the Boot image was updated to the distro point this morning, as the x86 one that I have not touched has a last update of back on the 6th.

I am not about to try adding the drivers to the task sequence, I currently have it set as a step after Applying Operating System, that it will Auto Apply Drivers and Install all Compatible drivers.

I will update if I still get the error or not.

Thanks

 

[apsenn]

Ran again and watched to see where it fails. It makes it through all the Applying Image, Computer Settings, and network settings. Then errors on

Running Action: Setup Windows and Configuration Manager

The Task sequence steps are as follows

(Folder Install Operating System)
Restart in Windows PE
Partition Disk 0 - Bios
Partition Disk 0 - UEFI
Apply Operating System
Auto Apply Drivers
Apply Windows Settings
Apply Network Settings
(Folder Setup Operating System)
Setup Windows and Configuration Manager
Install Applications

These were by default from creating a task, I decided to look at the task that fails

Setup Windows and Configuration Manager, that appears to be a task to install the SCCM Client or Package

It has (Configuration Manager Client Package) set, and you can choose other package, when I went to look at that package that I figure was made by SCCM itself, its there and has Datasource set to

\\SennCorp-SCCM.SennCorp.local\SMS_SEN\Client

But says it has no programs, and I dont see any commands on the package for how it will install the SCCM Client

Looking back at your guide for deploying windows 7, you show adding the smsmp line, but still confused a bit as I dont even see that Package having anything to run for those parameters to be passed to.

Thanks for any assistance

 

[apsenn]

Another update, I got the Task Sequence image to deploy

Couple changes I made that I think made it go

1) I found that my drivers that I had being applied in the Task Sequence had not been distributed to the DP, did this and that made drivers succeed
2) I removed the part of the task sequence that installs SCCM Client, I think that package has issues

With those 2 the computer images and restarts and comes up domain joined working well.

So I need to figure out how to get the Client to install, so that I can have a good setup and be able to also add apps into the sequence.

I tried making a sequence that didnt have sccm client but had an app I have at the end, (VMWare Tools) but it failed, and I figure that cause it probably cant install that app from Windows PE and doing reboot to production wouldnt help as it doesnt have the SCCM client yet.

Going to test, by deploying a machine and allowing it to get the SCCM Client via the Automatic install that I have setup, and then deploy app to it afterwards to ensure that the app deployment does work at least as I have not tested it yet as been focused on imaging.

 

[apsenn]

This can be marked as resolved. I have images deploying via PXE now, going to post new topic with separate imaging issue.

 

[Prajwal Desai]

Thank you. Marking the thread as Solved.