tim.cummings@juhsd.net Posted February 27, 2018 Report Share Posted February 27, 2018 We recently received 10 Dell Latitude 7490, we are having trouble deploying the image on them, it cannot seem to see the SSD. Anyone have trouble with this or resolve this before? Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 27, 2018 Report Share Posted February 27, 2018 If you are using SmartDeploy 2.0.2097, then you need to ensure you've built your boot media with the platform pack for this device selected. Otherwise, if you are using SmartDeploy 2.0.3000, then it should work out of the box. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 27, 2018 Author Report Share Posted February 27, 2018 using 2.0.3000, Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 27, 2018 Report Share Posted February 27, 2018 Are you using the beta release by chance? Can you check Add/Remove programs and verify that SmartDeplloy Enterprise is 2.0.3000.8154? If it's not, then uninstall that version and download the current version from our website, and re-create your boot media. If it is, then boot your 7490 to SmartDeploy and on the splash screen click Collect Logs. Save the resulting .zip to USB or Network and email it to us at support @ smartdeploy .com Thanks! Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 27, 2018 Author Report Share Posted February 27, 2018 Yes it is 2.0.3000.8154, i will try to grab logs Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 27, 2018 Author Report Share Posted February 27, 2018 logs https://1drv.ms/u/s!AhwoICTP_02ug_URVLAl9mIbqXaZYg Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 27, 2018 Report Share Posted February 27, 2018 It looks like the Deploy Wizard could see the disk... DeviceID:\\.\PHYSICALDRIVE0 Caption:SK hynix SC311 SATA 256GB So, what was the exact error you we're receiving? It actually looks like from the logs that the deployment was successful. Is it just that the machine is auto rebooting to the USB drive? If so, you'll need to remove it and reboot the machine. Or, Deploy Wizard, Advanced Options, and choose shutdown instead of reboot so that you'll know when the deployment is finished and to remove the USB stick. Unfortunately, some UEFI devices write a firmware boot entry for the USB drive, and will try to boot to it on reboot, even if we clear out the firmware boot entries before rebooting. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 28, 2018 Author Report Share Posted February 28, 2018 after it looks like the image loads, the computer reboots and has no bootable device other then network nic. We were using pxe by the way not a usb boot disk. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 28, 2018 Author Report Share Posted February 28, 2018 I was able to load the the OS from factory with t he DELL recovery usb, so not sure what the issue is here. Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 28, 2018 Report Share Posted February 28, 2018 That is probably due to a mismatch between UEFI and Legacy. The way the machine is configured, and the boot option need to match. I.e. if the machine is in UEFI mode, then you need to ensure you are selecting a UEFI boot menu option. If the machine is in Legacy mode, then you have to select a Legacy option. Ensure that once booted to SmartDeploy, the lower right hand corner shows the correct setting UEFI or BIOS. Looks like you we're booting the machine in BIOS, but it was configured UEFI. It looks like by default on these devices the "Enable UEFI Network Stack" isn't checked. So, in order to UEFI PXE boot this machine, you'll need to go into the BIOS, System Configuration, Integrated NIC, and check the Enable UEFI Network Stack" option. Also, put the machine back into it's default settings, if you changed it to Legacy... General, Advanced Boot Options, Enable Legacy Option ROMs = unchecked Secure Boot, Secure Boot Enable, Secure Boot Enable = checked Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted February 28, 2018 Author Report Share Posted February 28, 2018 They were not in UEFI mode from the factory. I ended up factory reseting them and loading the recovery media, then install the smartdeploy agent, and deploy a package and that worked. But I will have to test further, the image was created in a vm, so uefi or legacy shouldnt matter. Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 28, 2018 Report Share Posted February 28, 2018 On the F12 screen, it will say "Boot mode is set to:" either UEFI or Legacy. Based on what that says, you have to select an option from the menu that matches, otherwise you will end up with no bootable device found. Here is a spreadsheet we made to try and illustrate all the different scenarios and outcomes. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted March 1, 2018 Author Report Share Posted March 1, 2018 I got Sorry, there is a problem The page you are trying to access is not available for your account. Error code: 2C171/1 when clicking that link Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted March 1, 2018 Report Share Posted March 1, 2018 Ok, changed the link. Thanks. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted March 1, 2018 Author Report Share Posted March 1, 2018 Okay, I am checking now to see if this helps. I had some techs working on this for way too long and i found they changed a lot of settings all wonky in the bios. Link to comment Share on other sites More sharing options...
tim.cummings@juhsd.net Posted March 2, 2018 Author Report Share Posted March 2, 2018 Thanks for your help, with the one test machine I had it looks like not having "secure boot" enabled was causing the issue. Not sure if it was enable or disable from dell. Link to comment Share on other sites More sharing options...
allenturnage Posted March 27, 2018 Report Share Posted March 27, 2018 I'm currently having this same problem. I don't understand the fix here. Link to comment Share on other sites More sharing options...
Jeff Harris Posted March 27, 2018 Report Share Posted March 27, 2018 45 minutes ago, allenturnage said: I'm currently having this same problem. I don't understand the fix here. Are you able to enter the system settings and enable Secure Boot? Link to comment Share on other sites More sharing options...
allenturnage Posted March 27, 2018 Report Share Posted March 27, 2018 Yes, with no luck. Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted March 27, 2018 Report Share Posted March 27, 2018 Can you ensure you've followed this please? On 2/28/2018 at 10:18 AM, SmartDeploySupport said: That is probably due to a mismatch between UEFI and Legacy. The way the machine is configured, and the boot option need to match. I.e. if the machine is in UEFI mode, then you need to ensure you are selecting a UEFI boot menu option. If the machine is in Legacy mode, then you have to select a Legacy option. Ensure that once booted to SmartDeploy, the lower right hand corner shows the correct setting UEFI or BIOS. Looks like you we're booting the machine in BIOS, but it was configured UEFI. It looks like by default on these devices the "Enable UEFI Network Stack" isn't checked. So, in order to UEFI PXE boot this machine, you'll need to go into the BIOS, System Configuration, Integrated NIC, and check the Enable UEFI Network Stack" option. Also, put the machine back into it's default settings, if you changed it to Legacy... General, Advanced Boot Options, Enable Legacy Option ROMs = unchecked Secure Boot, Secure Boot Enable, Secure Boot Enable = checked Link to comment Share on other sites More sharing options...
allenturnage Posted March 27, 2018 Report Share Posted March 27, 2018 Yes. I did however find the issue. My option67 in the DHCP scope was still set to work with Legacy and not UEFI. Once I changed it, it successfully booted and imaged the system and booted into Windows. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now