PXE Boot didn´t find Task Sequences to Deploy

[HRoegener]

Dear all,

We use SCCM 2012 R2. Since the weekend our deployments don´t work anymore. When we start a PC in PXE mode and we insert the password the PC don´t recognize Task Sequences.

 

At Friday everything was working fine.

 

Task Sequences are deployed to the All Systems Collection. Unknown Computer Support is enabled and it doesn´t matter, if the Computer is known or not. Certificate is valid, as I can see in Distribution Point.

 

I´ve also tried to create a new task sequence and deployed this to the Unknown Computer Collection, to the All Systems Collection and to a collection where the PC is insert.

 

Had somebody else something like this or have an idea where I can look why it doesn´t work?

 

Best Regards

 

HRoegener

 

smsts.log

[HRoegener]

This happens on one of our Primary Sites. On our other Primary Site everything is working fine.

 

Has somebody an idea, where I can look in which Log to find a failure?

[rddvls1999]

you say you have two primary sites, are they independant, or are you using a CAS? If on a CAS, have you advertised from the CAS? On the site where it's not working, have you reviewed the smspxe.log file to see what it's logging when that mahcine pxe boots?

[HRoegener]

Hi, yes we have a CAS above. The Tasks I have created and deployed from the Primary Site where it is not working.

 

We didn´t had the CAS as I have created the tasks etc. the task and the second Primary Site came later. But everything was working fine. It´s was already working a couple of month.

 

Here are the last rows from smspxe.log

 

]LOG]!><time="09:28:15.790-120" date="07-03-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6346">

<![LOG[18:A9:05:F9:6E:C5, 816A6538-BB0B-11DF-BBDA-05F96EC518A9: device is in the database.]LOG]!><time="09:28:15.790-120" date="07-03-2014" component="SMSPXE" context="" type="1" thread="4532" file="database.cpp:483">

<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777313" ServerName=""><Machine><ClientID>GUID:7C3B28C1-070A-4BFE-9A81-4D0BC989D9D5</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CAS20051" OfferIDTime="01.07.2014 14:45:00" PkgID="CAS00038" PackageVersion="" PackagePath="http://LER-SCCM-1.BBC.LOCAL/SMS_DP_SMSPKG$/BBC00004" BootImageID="BBC00004" Mandatory="0"/></ClientIDReply>

]LOG]!><time="09:28:15.884-120" date="07-03-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6544">

<![LOG[18:A9:05:F9:6E:C5, 816A6538-BB0B-11DF-BBDA-05F96EC518A9: found optional advertisement CAS20051]LOG]!><time="09:28:15.884-120" date="07-03-2014" component="SMSPXE" context="" type="1" thread="4532" file="database.cpp:483">

<![LOG[Looking for bootImage BBC00004]LOG]!><time="09:28:15.884-120" date="07-03-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1774">

Looks nearly same in the log on our other primary site

[rddvls1999]

The following line from the smspxe.log file indicates that the machine is already known to SCCM, which will prevent it from being imaged again until you delete it from the console (assuming the MAC below is tied to the machine in question):

 

MAC: GUID: Status:

18:A9:05:F9:6E:C5, 816A6538-BB0B-11DF-BBDA-05F96EC518A9: device is in the database.]LOG]!><time="09:28:15.790-120" date="07-03-2014"

 

Try deleting the device from the SCCM console and see if it then allows you to image.

[HRoegener]

Same with new devices. It doesn´t matter if they are known or unknown. Its deployed to all systems but I have checked both.

[rddvls1999]

have you advertised to the "All Systems" collection, or "Unknown Computers" collection?

[HRoegener]

Tried both. Also we have now the problem that no Client will get deployments. I can see in System Center that the Clients are getting the policy but they don´t start installation of software.

 

So seems something with management point or distribution point is wrong but I can´t find anything.

[HRoegener]

Just for Info, Microsoft fixed it last week. There were some policy deployments hanging in SQL which were wrong. After they had deleted them, everything was fine.

[anyweb]

how did they discover them, can you share that info

[HRoegener]

That´s what I got from Microsoft about it:

 

They´ve done it on the SQL Database from the primary site

 

 

ran SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

 

MachineID PADBID LastUpdateTime TargetSourceID IsTombstoned

0 16777231 2014-06-27 22:26:14.107 NULL 0

0 17164446 2014-06-27 22:26:14.080 NULL 0

 

Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)