SVN 2389 can see the hard drive when I try to upload! However, it gets to the point where it would start checking partitions before uploading and then it reboots.
So close!!!
SVN 2389 can see the hard drive when I try to upload! However, it gets to the point where it would start checking partitions before uploading and then it reboots.
So close!!!
It’s a 64GB EMMC SSD.
I know it’s possible to get this to work, the latest builds of Clonezilla let me upload the image…
The device I’m referring to is the Asus T100TA tablet. UEFI PXE booting exclusively on these,
which isn’t an issue anymore!
I can access the FOG menu. I can get inventory to send if I set the “Host Primary Disk” to:
/dev/mmcblk0
However, I still cannot upload an image due to the partition layout of these tablets.
No matter what I set the “Host Primary Disk” to FOG always errors with “Can’t find the hard disk!”
Here is the partition layout for the EMMC drives on these:
/dev/loop0
/dev/mmcblk0rpmb
/dev/mmcblk0boot0
/dev/mmcblk0boot1
/dev/mmcblk0
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3
/dev/mmcblk0p4
From the research I’ve done (and I may be wrong) but a kernel with the proper MMC settings
embedded within could be all I need to get FOG to recognize the partition layout and find the hard drive.
If anyone can help me I’d be extremely grateful! Thanks in advance.
Download Windows ADK for Windows 8.1. Run it, only check the Deployment Tools box, then install.
Follow steps 1-8 here to create a new answer file:
[url]http://theitbros.com/sysprep-a-windows-7-machine-start-to-finish-v2/[/url]
Then follow steps 12-13 to sysprep your station.
Finally, open FOG from in your browser, find the host you ran sysprep on and click the upload button.
I’d appreciate any details you can provide…what type of devices are these? What USB–>LAN adapter are you using? USB 2.0 or USB 3.0? etc…
I’m jealous that you can even get the menu to display during a UEFI boot…I have yet to get that far with any .efi file I’ve tried :0
If you haven’t already, run:
[CODE]sudo service tftpd-hpa restart[/CODE]
I experienced this too. I liked it
As long as you installed the FOG service into your image, nope. Once your hosts hit the login screen they should start rebooting within 30 seconds or less to change their host names. Then, another 30 seconds or less and they’ll be rebooting to join your domain.
Well, I have gotten one step closer…kinda. I found a bootia32.efi file that successfully boots me into Grub 2.
Here it is if anyone would like to experiment…
[url=“/_imported_xf_attachments/1/1372_bootia32.zip?:”]bootia32.zip[/url]
This error happens if I image a station on our domain and I forget to delete the computer from AD before it re-joins the domain post-imaging.
I’ll be running more tests today at work, I’ll report back if I get anywhere…
I moved the WDS UEFI boot file to my FOG server, and I’m able to get a bit further, but it times out because it’s waiting for WDS commands from the FOG server which obviously don’t exist…
Try these if you haven’t already:
[url]http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/[/url]
chmod 755 them once they’ve been moved into /tftpboot
I should clarify, the farthest I’ve came is downloading the boot file successfully, then continues booting into Windows.
I’m in the exact same boat with the exact same devices, lol.
Currently using awful WDS to deploy…once we are finally able to boot to the FOG menu I’ll probably start screaming hysterically lol.
At work we purchased approximately 140 of these. We eventually gave up on FOG and turned to WDS. If you want to save yourself lots of time and stress I would go this route. Good luck!