RHunrath Posted May 10, 2012 Report post Posted May 10, 2012 I have a PXE issue and I may have found a pattern to at least my issue. I am using SCCM 2012 RTM, fully installed (based on windows-noob.com instructions of course). I have 4 PC's I have been able to reboot and PXE for weeks, even up to 10 PXE installs of an OS a day, but I have 4 other PC's I cannot get to PXE boot at all. I noticed that if I moved a PC between Collections that had a Deployment TS attached to them, they no longer PXE booted, permenantly. Let me clerify, if I had a PC that I manually imported into a collection that had a TS that deployed an OS and PXE'd into that TS it would work, but the minute I moved that PC to another collection with another TS that deployed an OS the PC would no longer PXE boot. This is still the case even if I deleted the PC out of SCCM and re imported it. Am I wrong, or is the new SMSPXE.log file is about as uninformative as possible. It no longer has ANY of the great information displayed in any of the RC's or even 2007. Sample below. Unsuccessful PXE Boot: PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Getting boot action for unknown machine: item key: 2046820352 SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set media certificate in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Client Identity: 0f35797a-771e-4381-a8f1-bb1a321da430 SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set media certificate in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:07:12 PM 6420 (0x1914) Successful PXE Boot: PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Set media certificate in transport SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Set authenticator in transport SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777226" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:53B0378A-0EBF-4610-AC95-1884ED926C74</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="L012000D" OfferIDTime="5/7/2012 4:10:00 PM" PkgID="L0100028" PackageVersion="" PackagePath="http://SMS1/SMS_DP_SMSPKG$/L0100002" BootImageID="L0100002" Mandatory="0"/></ClientIDReply> SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Client Identity: 0f35797a-771e-4381-a8f1-bb1a321da430 SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) PXE::CBootImageManager::FindBootImage: L0100002 SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) Looking for bootImage L0100002 SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) PXE::CBootImageCache::FindImage SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) PXE::CBootImageInfo::UpdateAccessTime SMSPXE 5/9/2012 4:10:12 PM 6420 (0x1914) The info is just as bad even for a successful PXE install. I have tried everything that made sense on the web, but this inconsistency is beyond me. The only thing I could find on this issue was in the SQL Database under the ImportedMachineIdentity table. PC's that would not PXE boot, the ItemKey referenced is not in the table. PC's that work, the ItemKey referenced are in the Table. I don’t know if this has anything to do with anything, but it was the only correlation I could find. ItemKey SMSID IdentityKey 16777222 GUID:936DC80E-A294-4521-9A2E-FB65C82BF1C9 {0D9E235D-EF10-488A-900D-DB520DE87324} 16777223 GUID:17D9EB3B-F9ED-488F-B212-589912753DAA {3DD7F2D8-A167-41A0-8C9B-3FF692E21E32} 16777225 GUID:6C25E3D0-3C68-4F78-8AED-71E1D35785E7 {90878CAA-9E70-4718-B9E5-07CF900D1384} 16777226 GUID:53B0378A-0EBF-4610-AC95-1884ED926C74 {3F4FFE47-276F-4FCE-9535-DF24014E804F} 16777227 GUID:6C73B48E-A85F-4610-BEBE-6D7067D02D1E {32948FE2-1239-478E-A6EA-EB4C6B083D7D} 16777228 GUID:EC980146-CE48-454B-B81F-BFD7C19D9E40 {335FA586-EBD4-4937-80D8-18ECFB0DFAB0} 16777229 GUID:19FC1959-4E10-425E-9783-F5A8E7470DB9 {A18EDDD7-5445-4818-90DC-10BE085E0DBE} I still have 4 PS’s I cannot PXE boot at all. Any ideas on how to rectify this? Quote Share this post Link to post Share on other sites More sharing options...
deployzilla Posted July 17, 2012 Report post Posted July 17, 2012 Hi, The unsuccessful PXE boot is an Unknown machine, do you have a TS deployed to the Unknown Computers Collection? Quote Share this post Link to post Share on other sites More sharing options...