Posts Tagged ‘OSD’

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:
Wait..wut?
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.

Advertisements

SCCM OSD Error 0×80040104 Failed to find CCM_SoftwareDistribution object

November 16, 2011

Scenario:
Added new drivers to SCCM driver database for hardware of a new pcmodel.
Made a new driver package containing these drivers, and put it on a distribution point.
Then ran the OSD Task Sequence, but after completion i noticed that none of the drivers had been applied to the windows installation.
So the Device Manager was still full of yellow questionmarks.

Then tried a different approach, instead of relying on the “Auto-Apply Device Drivers” step in the OSD TS, I specifically added a step for “Apply Driver Package”, specifying the newly created driver package containing the drivers.
Now when i rebooted the machine using PXE, and started the OSD TS, it failed immediately on the first step when it is checking the availability of all packages.

The smsts.log showed that it couldn’t find a DP location for the driver package.

The error:
Getting policy for CCM_SoftwareDistribution[AdvertID=””, PackageID=””,
FALSE, HRESULT=80040104 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2301)
Failed to find CCM_SoftwareDistribution object for AdvertID=””, PackageID=””,

So basically the SCCM Management Point could not provide the client with a location of a Distribution Point that holds a copy of the package.

A little googling turned up this posting which described the exact same error, and luckily, the solution.
So it turns out that sometimes a driver packages is not properly registered in the SCCM database, when the package version is “1”.
This is fixed when you update the package, and the version number is incremented.
Weird bug!