![]()
It may have only affected PXE Boot in hyper-v based on some of the comments in the below technet articles. #Bluebeam revu download keeps failing update#Let me give the BIOS update a whirl and see how that goes. It looks like it can't find the boot image. Prioritizing local MP SMSPXE 3:36:17 PM 7340 (0x1CAC) Looking for bootImage SMSPXE 3:36:17 PM 7340 (0x1CAC) Prioritizing local MP SMSPXE 3:36:16 PM 7340 (0x1CAC) Looking for bootImage SMSPXE 3:36:16 PM 7340 (0x1CAC) Looking for bootImage SMSPXE 3:36:15 PM 7340 (0x1CAC) Getting boot action for unknown machine: item key: 2046820353 SMSPXE 3:36:14 PM 7340 (0x1CAC) Is there anything else I can try or a log I can view that will tell me why the download is failing? Any suggestions on what would assist to fix this issue? None of these settings have helped to download the WIM file and the error persists. I've tried the steps in this MS KB which says to set the MaximumBlockSize to 1456 for the WDS service, I've tried Modifying: #Bluebeam revu download keeps failing driver#It sounds like a driver issue, but it's not even loading WinPE at this point. #Bluebeam revu download keeps failing drivers#I've updated the drivers in the boot image, deployed it to the DP's and it works for the majority of laptops I have in the environment, but this one particular model isn't working. Info: A required device isn't connected or can't be accessed. The PXE process starts, loads the boot.sdi and it starts downloading the boot.wim file but then stops at about 5% with the below error: I've had OSD deployed for about 2 months now and for some reason it doesn't work for a specific model of laptop. As a general rule, if someone has flair, they almost definitely know what they're talking about.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |