Host:
Host Kernel: 4.2.0-x32
Host Primary Disk: /dev/mmcblk0
Image:
Image Type: Your choice 
Links (for anyone who wants them):
bzImage32: 4.2.0 (x86) https://mega.nz/#!sQZFTCaY!aw23zMF9uY2g4Ep0W5kJP2sdrknshlGfrNR7mDCvgoY
Init_32.xz: SVN 3504 https://mega.nz/#!JEgWgCxa!KbTTSswOX4havJ4nb6b3UX25REZ3TWZg9BXL3_Q67Vw
@AsGF2MX Ok, I uploaded my image as Single Disk - Multiple Partitions and it still wouldn’t deploy. I then tried my oldest init_32.xz (SVN 3504) and it works.
Nope, I still use the 64-bit .efi files for these larger Asus EFI tablets we have.
On Monday I’m gonna experiment some more…I’m confident that with the right init_32.xz Single Disk - Resizable can work.
@AsGF2MX Ok, so I spoke too soon. I can’t deploy my resizable image, it seems to be a mount issue on the client.
I’m re-deploying my WDS image, then I’ll upload it as Single Disk - Multiple Partitions and see if that helps.
My init_32.xz is dated 09/18/2015 (SVN 4700).
Also, there’s a much easier way to handle these 32-bit EFI devices…
Go to: https://rom-o-matic.eu
Choose Advanced, for experienced users
Choose EFI PXE bootstrap 32-bit (.efi)
Check these boxes:
CPUID_SETTINGS
IMAGE_PNG
PARAM_CMD
CONSOLE_CMD
Lastly, paste this in the embedded script box at the bottom:
#!ipxe
dhcp
cpuid --ext 29 && set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://FOG-IP-or-Hostname/fog/service/ipxe/boot.php##params
(obviously replacing FOG-IP-or-Hostname with your FOG server’s IP or hostname)
Click Proceed and save that EFI file, I usually call mine ipxe-x32.efi.
Copy it to /tftpboot and set your DHCP server to use ipxe-x32.efi for 32-bit EFI clients and you won’t have to mess with them ever again!
I’d recommend keeping a few copies of that 32-bit .efi bootfile you made so you don’t have to re-make it in the future.
Also, if you regularly update to the latest SVN/Git…in the root of either SVN/Git directory, copy the 32-bit .efi bootfile into /packages/tftp and the file will always end up in the new /tftpboot directory whenever you update
@Wayne-Workman And yes, you are correct regarding the fixed size with a resizable image.
This is just nice because I can stay with Single Disk - Resizable exclusively for all of my images.
@AsGF2MX I didn’t have much time yesterday to tinker but I simply uploaded all four image types, starting with raw and working my way up. Once I saw the upload working I forced the tablet off and tried the next image type until I finished with Single Disk - Resizable.
I’m actually gonna deploy my WDS image I’ve been using for these onto my image tablet and upload it to FOG before the OOBE can commence. I’ll report any findings…
@Tom-Elliott No need to apologize brother! Thanks again to you and everyone who helped get these working
IT WORKS!!! You guys are amazing!
I did have to set Host Primary Disk to /dev/mmcblk0 but that was it
Single Disk - Resizable works!
I’ll give the kernel a whirl tomorrow at work and report back if anything’s changed.
This may or may not work:
service "FOGImageReplicator" stop && service "FOGScheduler" stop
You could always use SolarWinds Free TFTP Server on two separate servers (assuming you have them) or two regular old computers would even work.
Just configure both and copy your FOG server’s /tftpboot into both TFTP server’s root folder for their TFTP directories.
Of course this isn’t completely fail-safe…but this may do the trick:
Hostname: TFTP-Server01 (10.0.0.5)
Hostname: TFTP-Server02 (10.0.0.6)
Set option 66 to point at TFTP-Server01.
Add static DNS entries:
TFTP-Server01 (10.0.0.5)
TFTP-Server02 (10.0.0.6)
TFTP-Server01 (10.0.0.6)
As you can see, TFTP-Server01 has two entries, the second being TFTP-Server02’s IP.
This works in a Windows environment as long as the second IP for the specific host is numerically higher (e.g. 10.0.0.6/10.0.0.7/10.0.0.8/etc.)
The only way hosts would be stuck waiting for their PXE bootfile is if both TFTP servers went down…you could even add a third server (TFTP-Server03 (10.0.0.7)) and just add another entry for TFTP-Server01 (10.0.0.7).
This is how I have FOG setup in one of my environments. This way I can freely reboot my FOG server and only need to worry about it being up when I want to image.
@Wayne-Workman said:
@d4rk3 I’m thinking that the correct one will not be any of the “ram” ones.
You’ve tried these?
/dev/mmcblk0
/dev/loop0
Unfortunately, yes. I’ve tried everything from my partition table on my OP.
However, fdisk actually being able to see anything is progress. Tomorrow I’ll try some different kernels, maybe I’ll luck out…
Side note…I set the primary disk to /dev/ram0 with a raw DD image and it uploaded lol…
@Tom-Elliott said:
fdisk -l | more
Thanks Tom
Every disk looks like this (/dev/ram0 - /dev/ram15)
Kind of disappointing because the mmcblk0rpmb is still blocking me from seeing the mmc partitions.
If anyone has any ideas I’m all ears
Update:
I’m on SVN 3504 and just deployed a debug task to see if fdisk would show anything this time around…and it does!
The problem is, the screen fills up and I can only see the last disks which are all /dev/ram*.
How can I slow down the list or scroll up?
@ch3i said:
@d4rk3 I manage 800 stations in two domains without using sysprep, only FOG client.
It’ll be hard to disable raid in a server lol not sur you can emulate ahci/IDE.
You would have to do it in the BIOS on every station.
Like I said, you don’t have to Sysprep. I manage 1000 stations in 3 buildings, every station Sysprepped. To each their own
@DrouillardQ said:
Hello everybody.
Being actually on a training in a enterprise for my scholarship, I have for mission to make an server with Fog for creating and deploying some Windows ’ images.
After some researches, I found that I need to use sysprep for a OS on Windows 7. So again after some researches ans thanks to this site ( I did the same file answer as him) I had finally making an image of my first PC and deploy it correcfully.
After finishing thing my tutor ask me to image an R320 server By Dell running on Windows 7 and which is in RAID1. So thinking it was the same as a normal PC i did the same manipulation as before, my file answer in the repertory of sysprep and I run on a command line: sysprep /generalize /oobe /shutdown /unattend:unattend.xml. Then sysprep run itself and once finish close my windows session for shuting down the server.
And there is my problem, when the session is closing, the server freeze and I must shutdown the server manually. And so, when i’m restarting the server, the system told me that he can’t finish the installation and I have to reboot. I managed to override this and when I’m restarting sysprep, the freezing problem rehappen.
Can it be due to the fact that it is a RAID server and it is not compatible with sysprep ? Or it is a bad manipulation of mine ?
Sorry if i’m not precise enough and for the gramatical mistake i’m french.
Thanks for your answers
And yes, it’s probably the RAID that’s causing Sysprep to freeze. Are you able to disable RAID, temporarily use AHCI or IDE, then Sysprep without it freezing?
If so, just do that to upload it, then turn the RAID back on after it uploads. You will more than likely have to do this when deploying the image onto any additional RAID stations.
It is, however, highly recommended to Sysprep your images. Especially in any environment with more than a few stations.
I used 14.04 for about 6 months on two FOG servers, then fresh installed 14.10 on both of them.
I’ve been running 14.10 for over 8 months on both now with no issues. Don’t sweat it, IMO…