Posts Tagged ‘PXE’

SCCM 2012 PXE not working after failed OSD TS

April 8, 2012

When i was doing my first OSD TS with SCCM 2012, the TS failed at first. Of course 🙂

I got a nice error 0x80004005 during a “Build and Capture” sequence, at the point where it was supposed to start installing windows 7 x64 to my VM.

When opening the smsts.log file it told me that i had made a bad combination of Boot image (x86) and the Windows  7 version i wanted to install (x64)

Well that made perfect sense, so i changed the boot image, and was ready to retry the operation.

But hey, after rebooting, i would no longer get a PXE boot.


I had advertised the TS to the “All unknown computers” collection, but i suspected that even though this TS had failed pretty fast, somehow a record of the new computer had been made in SCCM.

And when a record has been made for the copmuter, it is of course no longer an “Unknown Computer”.

And yes, in the Collection “All Systems”, there was a new Computer object, called “unknown computer”

Hey, that’s a new one. An Unknown Computer, which is in itself no longer an unknown entity, because there is a record for it in SCCM.

And therefore, it has become a member of the “All Systems” collection, and is no longer a member of the “All Unknown Computers” collection.

Can anyone still follow me? 😛

To make a long story short, just delete this object, update the collection membership, and PXE is working again for the new computer

SCCM 2012 RTM PXE not working… Warning: Matching Processor Architecture Boot Image (0) not found

April 8, 2012

So, i am working on setting up a System Center 2012 RTM test environment, all in VMware Workstation, on a 16 GB Dell Precision M4600 laptop.
After setting up a 2008 R2 SP1 DC and a 2008 R2 SP1 CU4 SQL Server, i started with my favourite product, Configuration Manager.
After the initial installation and some basic configuration of Boundaries, Service accounts, and Server Roles, i was ready for my first OSD TS.

However, when booting my test client (vmware workstation) for PXE boot, i didn’t receive any boot file name.

Into the logs then! The smspxe.log logfile on the SCCM 2012 server showed the following error:

Okay, that’s weird. After checking that the 2 default boot images (x86 and x64) were properly distributed to the DP, i opened the boot images themselves.
Clicking around on them i found this setting:
So, that’s a new one. Appearantly you have to explicitly enable a boot image to be used on a PXE service point.

Lets see the documentation on Technet about this new feature:Click here and then expand the item “To Modify the Properties of a Boot image”.
Here we see the option mentioned.
And some more information here, in the section “Distributing Boot Images to the Distribution Point
Basically when you make the Boot Images availiable to a DP, they are only copied to the DP folders, and not to the Reminst share, which is used for PXE deployment.

SCCM – An error occurred while trying to initialize the Windows Deployment Services image server. Error Information: 0xC1030104

February 17, 2012

Got the above error after updating the SCCM boot images with some network drivers.
The PXE service wasn’t running, because the Windows Deployment Service service had stopped.
When starting this service manually, the above error occured
Usually people remove and re-install the PXE Point sccm Role, and/or the WDS Windows role.
What worked for me was just to refresh the boot image packages on the server. Nothing more.
Then the WDS service would start properly, and PXE worked again.
So, if you get this error, first simply try refreshing the packages containing your boot images.

SCCM: No Boot Action for Device (number) found

August 25, 2011

I had a computer on which the OS was damaged so it would not boot, and using PXE boot it would just get the “” so it could be reimaged.

How do we know what collection it is in, so that we can find out why is doesn’t have any PXE advertisements?
– There is no label on the computer with a computername
– The OS won’t boot, so we cannot see the computername within windows.

That leaves us with only the MAC Address and the GUID to search with.

When you do a search in the SCCM Console in a collection , you can not search on either of these values.
So we have to use a query or a Report for this.
You can do this by using a standard report, within the folder Network, called MAC – Computers for a specific MAC Address:

But only if the system is known within SCCM.
So what if this does not show any results?

Then the system is unknown within SCCM, and therefore automatically is a member of the collection “Unknown Computers”
So any advertisements targeted to that collection should also apply to this computer.

But what if it still gets the “” stuff?
Then it’s time to get into PXE.
Open the file smspxe.log which is located on the sccm server in \SMS_CCM\Logs
Search in there for the mac address and for any messages.
In this case, it showed that sccm thought this computer was a known computer, with no active advertisements.
These are the messages in the log:

Executing LookupDevice..
CDatabaseProxy :: LookupDevice succeeded:
Device found in the database. MacCount=1 GuidCount=0
Executing GetBootAction
No Boot Action for Device (5292) found]
ProcessDatabaseReply: No Advertisement found in Db for device]

So, the device was foun din the database, on the basis of its MAC Address.
Strange, because I could not find the computer anywhere in the SCCM Database.
Now there is some caching of the SCCM database in the PXE part, so maybe it was once a known computer, but it was deleted recently.
So, a restart of the PXE service (or rather the Windows deployment Services – WDS ) on the sccm server should fix this.

This didn’t help either, still getting the
Well, if SCCM thinks it doesn’t know the computer, but PXE thinks it does, let’s tell either one of them something else.
So I added the computer to SCCM manually, by creating a new Computer Association.
Then added the “new computer” to a collection with the correct advertisements, and voila, we have working PXE boot again.

But the question remains: how can PXE/SCCM “find” the computer in the database, while I cannot find it anywhere?