For those that are wondering, here are my brief instructions for installing ChromiumOS onto the Elitebook.

Arnold The Bat - latest special build (x86 or x64)
http://arnoldthebat.co.uk/wordpress/chromium-os/

Burn to flash drive or hdd per his instructions:

Linux:
Extract with p7zip
burn to drive using:
dd if=ChromeOS.img of=/dev/sdX bs=4M

Windows:
extract using 7zip
burn to drive using https://launchpad.net/win32-image-writer/

Boot

Go into chros shell with:
Ctrl + Alt + F2

Username is chronos
password is password

Install OS:

/usr/sbin/./chromeos-install --dst /dev/sda

Please let me know after updating…again. I say again because I found I had one thing being encoded where it shouldn’t have been which would cause the failure because it’s passing the password that will NOT be decoded. When it’s performed on command line, however, it needs to be encoded.

Confirmed and fixed,

Thanks for reporting.

@Tom-Elliott I’m kidding. I’ll use the group method to get them all set correctly again. Automagic would be nice huh

@sudburr filename detection should now be fixed too, sorry 😞

@Tom-Elliott Thank you!

This has now been fixed/added/updated.

@Tom-Elliott Thanks Tom. Confirmed fixed.

@Tom-Elliott This is resolved. Thanks very much Tom.

@Tom-Elliott
Updating to 6152 seems to have resolved the issue of not saving the assigned image during registration. Thanks!

@Tom-Elliott This is true, it is indeed fixed because Tom is the best

@ch3i they are part of the installer and a few additional things so the symlinks that are created are refreshed with the proper things as well.

@Wayne-Workman Pretty sure this is fixed.

Solved the thread as the issue wasn’t something the installer or bug in fog…directly. It was apparently related to firewalld? Of course more confirmation could be useful.

Pretty sure this is fixed, (though again confirmation would be great. We are up to 0.9.11 now, and if it wasn’t fixed maybe we need to let someone know more directly?)

Solving this thread as the bug was user created. Don’t use GPO to enforce a client version is the quick answer.

I’m solving this thread as the issue involved was not caused by fog at all.

You’re absolutely correct. It’s chinese if it’s any help. It is not set until you set it, though I’m pretty sure I’ve made sure it defaults (now) to English.

I’m fairly sure this has been addressed and fixed, though please let me know if I’m wrong.

I’m fairly sure this is fixed now.