Posts made by sarge_212

@george1421 Sweet, doing the initial install now via git.

@george1421 So, I’m doing a brand new install to start afresh. I’ll need to do some work I assume to get on 1.5.2?

@george1421 Ok… how does one install to a certain version? I’d used git on the last one to update to current, but I’m not sure how to get 1.5.2 installed and then switch to the working branch? I’ll look on the forums but if you can point me in the right direction to get this installed, then 1.5.3 will be a simple upgrade.

@george1421 Any idea when 1.5.3 will be released?

Would it be a good idea to update FOG? I know you all have made TONS of improvements from the version I’m on. However, it doesn’t like a FOG issue per se but a UEFI issue. So, the process I would take to image is as follows:

Machine comes in RAID ON
Prep machine as I want it
Start a Capture task for the host
sysprep, then on reboot change to AHCI, Legacy mode and capture
After that, capture image
Deploy or just reboot
Before booting up, change back to RAID ON

?? Does that sound like the right process?

@george1421 I should be able to use any .efi file, correct? OR should it be a specific efi file? Right now I think I’m using a hacked together one from @Tom ages ago so I will most likely be upgrading FOG shortly.

@george1421 That is the process I was looking for. I’ll attempt that and let you know. Thanks @george1421 !!

Switched to RAID on and got an “inaccessible boot device” interestingly enough. This is a latitude 7490 from factory with a few tweaks and then me trying to upload to be able to deploy. I’m fine if I have to update FOG, that’s not a problem but wondering if this can be avoided in the future or what process I should take to capture and deploy with this UEFI/linux issue?

So,

Windows just booted up and I got the famous “windows cannot complete the installation, please reinstall” or some such. Thoughts? Would switching back to Raid On fix this issue and allow windows to boot properly?

@george1421 Very interesting. I just switched to legacy and captured the “master sysprepd” image as it were. BEFORE booting into the os, I changed from RAID-ON to AHCI. I’ll let you know what happens in a few minutes as I suspected the RAID-on vs AHCI deal. Thanks.

Hey all,

Using FOG 1.4.0 RC-8. I know, I know it’s outdated. However, I can’t get a 1709 UEFI image to capture, FOG can’t find the disk. I can however, do so on Legacy but wondering if I should be able to do so on UEFI, or if I have to use the Legacy boot option. Let me know what I can do to troubleshoot. Thanks.

Changing from RAID on in BIOS to AHCI fixed this issue for me. Thanks so much for the tip @FoSTerCyber !!

@george1421 thank you, I will certainly look into that on the Dell website, and post my findings. Appreciate it.

I also am seeing this. Here is the hardware:

Dell Optiplex 9020, Optiplex 7040 – Gets to the Window of cannot start windows, please reinstall

Any laptop I try the image on it works fine, this is windows 1607. Laptops are as follows:
Dell Latitude 7440, 7450, 7470
Also works on older models in our environment. I’m happy to do some debugging per any direction. We are using a sysprep’d image. It seems to only happen after I sysprep and then when it tries to boot on the desktops it struggles with finishing the windows install.

@Tom-Elliott Updated, on 8217, seems to be faster! W00t!

@Tom-Elliott not quite yet, taking a lil snapshot atm before doing so and then I’ll update.

@Tom-Elliott Tom,

How “snappy” should the web UI be? What factors go into that? Obviously reporting back from the host, but what other things?

@Tom-Elliott sorry, haven’ had time yet. Crazy work day and fog got back-burner’d. Will have to next week prolly. Thanks though Tom!

@Tom-Elliott hehe, no worries. I’ll try an update and report what turns out. Thanks Tom!

@Tom-Elliott So it’s not the imaging itself its the web UI. Imaging is very quick. I’m only noticing the slowness in the web UI when trying to first load things. After that, it works splendidly.