Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 164

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 167

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 170

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 173

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 176

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 178

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 180

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 202

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 206

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 224

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 225

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 227

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 49
Unable to PXE boot after Configuration Manager 2012 R2 CU1 Upgrade | Trailing Reboot

I recently came across this issue when upgrading a customers Configuration Manager 2012 R2 environment with cumulative update 1. After completing the update we were unable to PXE boot any image across all distribution points in the site. We did follow the steps in CU1 upgrade which asked for updating of boot images across all distribution points

Here’s a link to the CU1 update – http://support.microsoft.com/kb/2938441

Environment I’m referencing is as follows:

System Center 2012 Configuration Manager R2 CU1

Windows Server 2012 Standard R2

SQL Server 2012 Standard (local)

Management Point is on the site server

Distribution Points are on Windows Server 2012 R2

 

The first place I looked was SMSPXE on a few of the DPs. The errors were identical on all of them.

pxe01

This led me to a few articles on Technet and other various tech blogs referencing similar issues when updating ConfigMgr 2012 RTM to SP1. The troubleshooting workflow suggested removing WDS from the DPs, deleting any reference of boot images and then adding everything back again. Unfortunately, this didn’t work for our situation.

Next, I tried building a set of new x86 and x64 boot images and attaching them to my existing task sequences. No joy here either.

Finally, I came across the MPSetup.log file on the Management Point server which had the following errors

pxe02

This set of errors was repeating hourly since the CU1 upgrade.

This part caught my attention – “D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe” /UpgradeWithServer:mp failed with error code 193

For fun, I navigated to the above path and tried to run ccmsetup.exe and received the following Window Server 2012 error

pxe03

I tried a few different methods….run as admin, check permissions on the parent folder… None of it worked. So, I went back to the installation media, grabbed the ccmsetup.exe  from it and pasted it into my ConfigMgr Program Files path. Then I waited for the MP setup process to kick off again.

pxe04

 

Success. The command above reinstalls the client and MP which was required for successful communication with downstream distribution points and PXE.  A quick test of PXE boot on the distribution points showed things to be in working order again.

Bit of an odd one. I wasn’t able to find any articles in the community that fixed this so hopefully this one saves someone out there a few hours of their time.

 

Leave a Reply

Your email address will not be published. Required fields are marked *