joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 I received 40 loaner gen 1 Surface demo machines yesterday and noticed I’m now getting a 0x80040005 error for only a few machines when I get into windows PE and attempt to start my task sequence. The odd thing is, they are all the same machine meaning no difference in make/model. It pops up right after putting in my credentials to view the list of available task sequences. It’s almost like it looks and see’s the machines don’t fall into any category, however I am deploying to the unknown collection, and these machines are all NIB. I don’t think it couldn’t be a driver issue if it seems to be completing the task sequence fine on other machines. I have already tested this deployment with 4 Surfaces prior (gen1/2). I also ran into an issue with using the same NIC dongles yesterday, but I resolved this by adjusting my task sequence to not record the network information, IE: MAC. That issue was causing the machines to not even PXE, as they were active clients, not unknown. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 So looking deeper I found that the machines are not matching any deployments. This leads me to think it still has something to do with reusing the same NIC's. This is going to be a huge issue because we are deploying over 1000 of these machines and moving towards 8000 of them over the next few years. Anyone have any advice on how I can somehow not capture the MAC address of these machines individually? It's a nice reference to be able to check the MAC of typical machines, but clearly that isn't going to work in this scenario. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 27, 2014 Report post Posted February 27, 2014 are you doing new computer scenarios only here or refrreshes ? Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 are you doing new computer scenarios only here or refrreshes ? New computer scenario. These are 40 devices that were sent to us NIB. Everything I am finding leads me to think it's MAC address related still. I only have 6 Surface USB dongles for imaging all devices. I found that deleting the machines from the console after imaging corrects the issue of getting into PE, and in most cases allows the machines to image because I've already boxed the previous machines up, in turn not allowing a hardware audit to run even if they are rediscovered. The issue at hand is getting into PE and from the logs I can see this: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16780947" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 2/27/2014 9:30:45 AM 3440 (0x0D70) 60:45:BD:F9:98:A9, 63898079-893F-74F0-892B-C860C64E9F88: device is in the database. SMSPXE 2/27/2014 9:30:45 AM 3440 (0x0D70) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16780947" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> SMSPXE 2/27/2014 9:30:46 AM 3440 (0x0D70) 60:45:BD:F9:98:A9, 63898079-893F-74F0-892B-C860C64E9F88: no advertisements found SMSPXE 2/27/2014 9:30:46 AM 3440 (0x0D70) 60:45:BD:F9:98:A9, 63898079-893F-74F0-892B-C860C64E9F88: No boot action. Aborted. SMSPXE 2/27/2014 9:30:46 AM 3440 (0x0D70) 60:45:BD:F9:98:A9, 63898079-893F-74F0-892B-C860C64E9F88: Not serviced. SMSPXE 2/27/2014 9:30:46 AM 3440 (0x0D70) I will next try to locate the machines that these dongles belong to, and I will delete them and re-attempt a deployment. I will update as I go. Thanks for the reply Quote Share this post Link to post Share on other sites More sharing options...
willisj318 Posted February 27, 2014 Report post Posted February 27, 2014 Yes you will need to delete the machines or use a unique dongle for them. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 Yes you will need to delete the machines or use a unique dongle for them. Any reasoning why some will skip past PXE because they are known, and the others I am noting get into PE and then fail? I just want to understand if it's random or what the reasoning is. Thanks for the reply Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 Deleting the machines that the NIC's were first associated with did not fix the issue. These two are still receiving a 0x80004005 after searching for available deployments. Quote Share this post Link to post Share on other sites More sharing options...
willisj318 Posted February 27, 2014 Report post Posted February 27, 2014 I don't know at this point without the log file, you will need to pull the smsts.log file to see what the problem is. If you can do that and post it here that would help. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted February 27, 2014 Report post Posted February 27, 2014 I don't know at this point without the log file, you will need to pull the smsts.log file to see what the problem is. If you can do that and post it here that would help. Still no luck. I attached the smsts log. Disregard the x.x. IP's smsts_clean.log Quote Share this post Link to post Share on other sites More sharing options...
Edenost Posted February 27, 2014 Report post Posted February 27, 2014 Generally the 0x80004005 error would be "access denied" or similar. Might sound a bit odd, but is the Bios clock set to the right time? (and date). That can cause this error apparently. Quote Share this post Link to post Share on other sites More sharing options...
