Completed 2012 SP2 Upgrade and MDT 2013 - next steps?

[nry]

Hi all,

 

Following your guides on here a few years ago we got SCCM 2012 up and running and last year upgraded it to SP1.

 

I recall at the time having to re-do some of the boot images etc.

 

We've just upgraded to SP2 which all went fine, however we can no longer PXE boot - we have installed/upgraded to MDT 2013 and moved to the Windows 10 ADK...the point of the upgrade was to allow us to look at Windows 10 deployment which I believe needed these two additional steps. I assume(s) we can also still roll out Windows 7 which we were successfully doing before.

 

What are the expected next steps I should be doing to ensure the Win7 PXE boot still works? At the moment no boot image is being sent out when I try a PXE boot on a networked computer, but all the boot images still exist in the SCCM console as before.

 

Hopefully I can get this bit sorted as at the moment it all looks fine within the console but I'm guessing I've missed a step

 

Thanks,

 

Chris

[ZeZe]

Hi all,

 

Following your guides on here a few years ago we got SCCM 2012 up and running and last year upgraded it to SP1.

 

I recall at the time having to re-do some of the boot images etc.

 

We've just upgraded to SP2 which all went fine, however we can no longer PXE boot - we have installed/upgraded to MDT 2013 and moved to the Windows 10 ADK...the point of the upgrade was to allow us to look at Windows 10 deployment which I believe needed these two additional steps. I assume(s) we can also still roll out Windows 7 which we were successfully doing before.

 

What are the expected next steps I should be doing to ensure the Win7 PXE boot still works? At the moment no boot image is being sent out when I try a PXE boot on a networked computer, but all the boot images still exist in the SCCM console as before.

 

Hopefully I can get this bit sorted as at the moment it all looks fine within the console but I'm guessing I've missed a step

 

Thanks,

 

Chris

Hi Chris,

 

I think it'll depend in the order how you install things.

 

I've done like this and didn't had any issues, nor have to add the boot images manually or change PXE settings:

 

- remove adk 8 and install adk 10 rtm

- install CM SP1/CUxx

- Restart server

 

Doing like this, the upgrade package should add automatically the boot images and you shouldn't have any problems. Nevertheless, I've read in some forums where something went wrong and people had to add manually the boot image, change PXE, etc. But keep it simple like this and you should be fine!

 

Regarding MDT I think you need to recreate the images (using the MDT to create a new boot image, new packages and settings). Don't forget to distribute the content.

 

P.s. use ADK 10 RTM and not 10.0.10586.0

[nazimb]

Hi Chris,

 

I think it'll depend in the order how you install things.

 

I've done like this and didn't had any issues, nor have to add the boot images manually or change PXE settings:

 

- remove adk 8 and install adk 10 rtm

- install CM SP1/CUxx

- Restart server

 

Doing like this, the upgrade package should add automatically the boot images and you shouldn't have any problems. Nevertheless, I've read in some forums where something went wrong and people had to add manually the boot image, change PXE, etc. But keep it simple like this and you should be fine!

 

Regarding MDT I think you need to recreate the images (using the MDT to create a new boot image, new packages and settings). Don't forget to distribute the content.

 

P.s. use ADK 10 RTM and not 10.0.10586.0

Hey Zeze,

 

are you saying that my current MDT Boot Images have to be recreated ?will it affect my current OSD task sequences?

[ZeZe]

If you have installed a new ADK, yes you've to recreate MDT boot images. And yet, you can still used the old ones, but I'm pretty sure that if you try to used them with Windows 10, the TS will fail.

 

The current Tasks Sequence will continue to work as they are. If you add a new TS to build and capture or to install Win10 image, then you have to use a boot image from the ADK10 and not from the old.

 

Got it?

[nry]

Thanks all, I did ADK 10 after the SP2 install...which I now regret as the boot images won't import into SCCM, I'll check the error I get and post it up as nothing I've tried from answers I've found get it going. I can't PXE boot from the original images either...

[ZeZe]

I would guess that maybe the PXE is missing the boot images... At least wait until you have the boot images and distributed them. Let us know what errors are you having with the import

[nry]

OK, the boot images are now importing and distributing OK, I noticed that removing Windows ADK for 8.1 had left some of the folders behind and all I have done is rename them, leaving just the 10 ADK ones...

 

However now, checking the SMSPXE.log I am getting the following, trying to PXE Boot a client results in this error in the client:

 

PXE-E53 not boot filename

 

SMSPEXE.log:

 

Prioritizing local MP http://MYSCCMSERVER. SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
RequestMPKeyInformation: Send() failed. SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
Failed to get information for MP: http://MYSCCMSERVER. 80004005. SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
reply has no message header marker SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
Failed to send status message (80004005) SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
Failed to send the status message SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
38:60:77:8F:6C:68, D78C0F00-FE1A-81E0-2F8F-3860778F6C68: Not serviced. SMSPXE 22/02/2016 11:30:05 10116 (0x2784)
File C:\RemoteInstall\SMSTemp\2016.02.22.11.08.18.03.{A9385315-B1C7-4B10-BC12-239B7CBDB84D}.boot.bcd deleted. SMSPXE 22/02/2016 11:38:24 11016 (0x2B08)
File C:\RemoteInstall\SMSTemp\2016.02.22.11.08.18.03.{A9385315-B1C7-4B10-BC12-239B7CBDB84D}.boot.bcd.log deleted. SMSPXE 22/02/2016 11:38:24 11016 (0x2B08)

 

It was all working nicely before SP2

 

Chris

[nry]

Curiously, I checked the MP log and it says this:

 

<02/22/16 14:24:32> Installing pre-req using command line "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp<02/22/16 14:24:47> Pre-req installer "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 1

 

Then:

 

<02/22/16 14:24:47> Failed to Install Pre Req CcmSetup. Return Code is 1

 

Does the CCM Client on the SCCM server itself need upgraded for the PXE to work again? It seems to be trying this before failing each time I try a PXE boot but I may be misinterpreting things.

[nry]

Still the same error though I believe the upgrade to the client is now complete according to the logs...it failed on a Silverlight dependency...strange.

[ZeZe]

PXE: if the boot images are there, then just disable the PXE from the DP, wait until you see the the PXE it has been removed. Add the same configuration again and check the distmgr.log;

 

The other error seems pretty much the same I had once and you simply have to wait because it will fix by itself.

 

but read my post regarding my issue and check if it's not the same:

 

https://www.windows-noob.com/forums/topic/13243-boot-image-x64-error-loading-task-sequence/

 

Please note that I had two missing keys that should have some information and in my case they were empty. If you have that, in my opinion it will fix by itself (for me 24h).