@lschnider if you are doing a golden image (one image for multiple models), then I strongly suggest doing sysprep for Windows 10. I sysprep mine from “audit mode”, which became necessary when trying to remove windows store apps from being created when a new user gets created. There are other reasons we had to go that route as well, but my memory is a bit hazy as to what we had to do. I will get to build the golden image from scratch again once the next spring update comes out.

If you aren’t doing much customizing, you may not need audit mode, but I think you need sysprep for the driver injection to work correctly (assuming you are going for a zero-touch installation).

@george1421 @Sebastian-Roth what about a compromise? Is it possible to have accounts for logging into the fog web UI that have limited access? Like only the hosts tab and image / capture from the list of clients. You can protect certain images from being written over already, so he can protect anything he doesn’t want modified and unlock as needed for his lower tier staff.

I think it was back in 1.4.x that FOG had limited user accounts that could deploy images, it seems they were removed though.

@george1421 virtualbox does not. @lschnider make sure you don’t turn off EFI in virtualbox until after the VM has shut down and just before uploading. Otherwise you have to go back to your snapshot do the sysprep again.

Then, as @george1421 said, you get to play musical chairs with your boot files, using undionly.kpxe for uploading and ipxe.efi for deploying.

I set up the DHCP rules on one of our dhcp servers (only one that was 2012…) and I can vouch that it saves a LOT of headaches.

@Sebastian-Roth awesome, thanks! I’ll give it a while on my VM’s tonight.

@Sebastian-Roth No worries, I know you guys have a lot on your plates. I just wanted to make sure it got noted that there was a bug.

I can confirm that your workaround works, thanks. The group printer page still doesn’t reflect the settings applied, but it I go into the members it does seem to have the correct settings. I will use this until a patch can be made. Thanks!

@george1421 said in Dell Latitude 5590 issues after imaging:

change drive controller from raid-on to ahci mode.

Hey George, I noticed that when deploying my UEFI Win10 images, that it didn’t seem to matter if the client was raid-on or ahci. I’m guessing because my image is sysprepped and uses your driver install, but yeah… doesn’t seem to care anymore for me at least. ¯\ _ (ツ)_/¯

in virtual box machine go to settings>system>extended features and check enable efi(special OSes only) correct?

Yes, I have that box enabled. If you created your image with that box unchecked, then your Windows install is set up to install on a legacy BIOS. I had my images set that way initially but ran into BIOS exit type issues from the FOG PXE menu, so started over as EFI. As a side note, I do have to switch the EFI setting back off right after I run sysprep and shutdown, as FOG only picks up up my VM for uploading with EFI off. Virtualbox won’t pxe boot when EFI is on.

where do you enable IPv4 in UEFI

@lschnider I couldn’t find a 5590 nearby, but here is the BIOS settings on a 7040:

Settings -> System Configuration -> Intigrated NIC
Check the box that says “Enable UEFI Network Stack” with Enabled w/PXE selected.

Also… you may need to switch your SATA Operation to ACHI instead of RAID if you have it in legacy mode.

@lschnider was your image created with a UEFI or Legacy BIOS? I believe you need to match the format your image came from. Our district has imaged quite a few 5590 laptops with a golden image created in virtualbox using the EFI bios setting.

If your image is UEFI based, you need to use ipxe.efi as your boot file and have the laptop set to UEFI with secure boot off. Don’t forget to enable IPv4 UEFI so you can PXE boot in UEFI mode.

@Sebastian-Roth okay, thanks. I’ll do some research and see which route seems best. I still have a lot to learn about linux and wasn’t sure if there was a “new” way of adding storage to a FOG server since the wiki didn’t mention LVM and I was am not familiar with that yet.

@Sebastian-Roth

[root@fog-master ~]# df -h
Filesystem                             Size  Used Avail Use% Mounted on
/dev/mapper/centos_fog--master-root     20G   14G  6.8G  67% /
devtmpfs                               3.8G     0  3.8G   0% /dev
tmpfs                                  3.8G     0  3.8G   0% /dev/shm
tmpfs                                  3.8G  169M  3.6G   5% /run
tmpfs                                  3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/sda1                             1014M  334M  681M  33% /boot
/dev/mapper/centos_fog--master-images  902G  233G  669G  26% /images
tmpfs                                  766M   12K  766M   1% /run/user/42
tmpfs                                  766M  4.0K  766M   1% /run/user/0

[root@fog-master ~]# lsblk
NAME                          MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                             8:0    0   931G  0 disk
├─sda1                          8:1    0     1G  0 part /boot
└─sda2                          8:2    0   930G  0 part
  ├─centos_fog--master-root   253:0    0    20G  0 lvm  /
  ├─centos_fog--master-swap   253:1    0   7.8G  0 lvm  [SWAP]
  └─centos_fog--master-images 253:2    0 902.2G  0 lvm  /images
sr0                            11:0    1  1024M  0 rom