to populate the dropdown seperate your OU’s with | and whichever you want to be the default (if you want a default just add ;):
i.e OU=Workstations,OU=Domain,DC=domain,DC=com;|OU=Servers,OU=Domain,DC=domain,DC=com|OU=Servers,OU=Domain,DC=domain,DC=com
so workstations will be default and all 3 will be available in the dropdown.
thanks tom for the addition 
gone will be the days of temps/trainees uploading images when they should be downloading images… 
… that was a nice day to come in to… “what’s happened to all the images???”
also only shows for PartClone Images, not legacy PartImage - assume you’re using legacy PartImage?
unfortunately no you can’t simultaneously run UEFI and legacy boot it’s one or the other i’m afraid however you can run UEFI with legacy PXE… iPXE does not support UEFI PXE but iPXE dev team are working on developing this…
change the arch to amd64 and see if you get the same errors
you’re better of posting your unattend.xml file - what did you use to create ur unattend.xml? from examples or Windows AIK? what OS is it? and the OSArch?
also might be a good idea to read the fog wiki / user guide to see how fog actually works
fog doesn’t use .wim files, i’d recommend getting ur “build” machine/vm to the state ur happy with and then just upload to fog
[SIZE=14px][FONT=Arial][COLOR=#615f5f][COLOR=#000000]below is how i used to deal with the fog client rollout - there used to be a thread on the old forum explaining how to edit msi (freely) and get it rolled out and someone else has also posted the instructions externally:[/COLOR][/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Arial][COLOR=#615f5f] [/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Arial][COLOR=#615f5f][COLOR=#000000]thanks paul![/COLOR][/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Arial][COLOR=#615f5f][COLOR=#000000][/COLOR][/COLOR][/FONT][/SIZE]
[FONT=Arial][COLOR=#615f5f][SIZE=14px][url]http://www.bauer-power.net/2011/09/how-to-deploy-fog-service-client-from.html#.U4IkdvldW-4[/url][/SIZE][/COLOR][/FONT]
[SIZE=14px][FONT=Arial][COLOR=#615f5f] [/COLOR][/FONT][/SIZE]
[SIZE=14px][FONT=Arial][COLOR=#615f5f]In order to do this correctly, you will need to re-package the MSI file for the Fog Client Service[COLOR=#1b8ede]installation[/COLOR]. You can do that with a free tool called [URL=‘http://download.cnet.com/WinINSTALL-LE/3000-2094_4-10973399.html’][COLOR=#102741]Winstall LE[/COLOR][/URL].[/COLOR][/FONT][/SIZE]
[LIST]
[][I][COLOR=#0000ff]Open Winstall LE, right click on [B]Windows [COLOR=#1b8ede]Installer[/COLOR] Packages[/B] and select[B] Import Package[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Browse to the Fog Client MSI, and give it a description of [B]Fog Silent[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Right click [B]Fog Slient[/B] and Select [B]Decompress…[/B][/COLOR][/I]
[][I][COLOR=#0000ff]At the [B]Expand[/B] dialog, click [B]Expand[/B][/COLOR][/I]
[/LIST]
[SIZE=14px][FONT=Arial][COLOR=#615f5f][I][COLOR=#0000ff][IMG]http://lh5.ggpht.com/-iBRdFMi9jc/TmEaiP_XtXI/AAAAAAAAC1o/FIDvVb5Vhc8/%25255BUNSET%25255D.png[/IMG][/COLOR][/I][/COLOR][/FONT][/SIZE]
[LIST]
[][I][COLOR=#0000ff]Expand the [B]Fog Silent[/B] tree, and delete the following components because you don’t need them:[/COLOR][/I]
[/LIST]
[INDENT=2][SIZE=14px][FONT=Arial][COLOR=#615f5f][B][COLOR=#333399][I]{7A0D8B0C-D68A-E7BE-76B6-8D70577B4F38}[/I][/COLOR][/B][/COLOR][/FONT][/SIZE][/INDENT]
[INDENT=2][SIZE=14px][FONT=Arial][COLOR=#615f5f][B][COLOR=#333399][I]{A4389213-D1C5-59F6-260E-D84F4D4BE41A}[/I][/COLOR][/B][/COLOR][/FONT][/SIZE][/INDENT]
[LIST]
[][I][COLOR=#0000ff]Now browse to [B]\localhost\WinINSTALL\Packages\fog silent\etc[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Edit the [B]config.ini[/B] file so it has the [COLOR=#1b8ede]IP address[/COLOR] or FQDN of your fog server under[B]ipaddress=[/B] then save it[/COLOR][/I]
[][I][COLOR=#0000ff]Go back to Winstall LE, right click on [B]Fog Silent[/B] and select [B]Compress[/B], then press the[B]Compress[/B] button[/COLOR][/I]
[/LIST]
[SIZE=14px][FONT=Arial][COLOR=#615f5f][I][COLOR=#0000ff][IMG]http://lh5.ggpht.com/-XuAT9zcr8ek/TmEb7iXBD_I/AAAAAAAAC1s/OmKaJ6MkZaE/%25255BUNSET%25255D.png[/IMG][/COLOR][/I][/COLOR][/FONT][/SIZE]
[LIST]
[][I][COLOR=#0000ff]Now browse to [B]\localhost\WinINSTALL\Packages\fog silent\ [/B]and your [B]FOG ServiceInstaller.msi[/B] file is ready to deploy![/COLOR][/I]
[][I][COLOR=#0000ff]Place the new [B]FOG Service Installer.msi[/B] and the original [B]setup.exe[/B] in a fileshare that is accessible by everyone. I created a [B]deploy [/B][URL='http://en.wikipedia.org/wiki/Samba(software)'][COLOR=#102741]Samba[/COLOR][/URL] share on my Fog server.[/COLOR][/I]
[][I][COLOR=#0000ff]Now open [B]Group Policy Management[/B] on your domain controller and create a new Group Policy Object called something clever like [B]Fog Deploy[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Right click on [B]Fog Deploy[/B] and select [B]Edit[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Navigate to [B]Computer Configuration > Policies > Software Settings > SoftwareInstallation[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Right click on [B]Software Installation[/B] and select [B]New > Package[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Browse to your file share, and select your custom [B]Fog Service Installer.msi[/B] file and select[B]Open[/B][/COLOR][/I]
[][I][COLOR=#0000ff]Leave the [B]Assigned[/B] radio button checked and click [B]OK[/B][/COLOR][/I]
[/LIST]
[SIZE=14px][FONT=Arial][COLOR=#615f5f][I][COLOR=#0000ff][IMG]http://lh4.ggpht.com/-3Glte9p_ln4/TmEmK0J3CLI/AAAAAAAAC1w/qd6f1T6NTa8/%25255BUNSET%25255D.png[/IMG][/COLOR][/I][/COLOR][/FONT][/SIZE]
[LIST]
[][I][COLOR=#0000ff]Now link your new GPO to the OU where you keep the workstations you want to manage with Fog, and you’re good to go![/COLOR][/I]
[][I][COLOR=#0000ff]Users will get [COLOR=#1b8ede]the install[/COLOR] the next time they reboot, and even better it will be automatically configured![/COLOR][/I]
[/LIST]
[FONT=Arial][COLOR=#0000ff][SIZE=14px][I]Hope this helps…[/I][/SIZE][/COLOR][/FONT]
This was a feature in 0.30/0.31 and below if memory serves me well… the FOG Client used to check if host exists in fog (registered) if not then it would add the host, using minimum need info - mac & hostname nothing else was populated.
meaning you could roll out the fog client across your network and all your hosts would get registered with fog. Chuck/Blackout removed it going forward but can’t remember the reason behind it now but there was one (memory is awful!) i think it was because of compatibility as you said.
the simplest “manual” way to get around this until we are able to implement this feature would be to utilise something like rsync and crontab for the snapin “files” (and possibly samba) and have your snapin be a script that determines your machines location and uses/run the files from the node that is on site but if you have many branches this may be a pain to initially setup but if you set it up right you would only have to update the files on the one server/node and rsync and crontab will take care of the other “branches”.
Basically the software is stored on the storage node and gets copied down to the pc after image, also setup samba to the folder so its available as a software rep/share, we have a node on each site (any site that has more than 10 machines on site) so everything is “available” on the local network so no need to go down slow links etc… then the snapin is just a script n it determines what software is needed by hostname, model and location so once it determines what is needed jst installs them in order, i’ve used powershell in the past bt using autoit atm because its easier to be creative with GUI’s. Also got multiple tftps so the only “data” that is coming from “off” site is the snapin which is tiny 1.5MB n jst task n progress sent bk to server, so tiny tiny amounts 
so its jst as quick regardless of the remote site.
just my 2 cents, personally - i couldn’t recommend sysprep more, we have one image per OS (under most circumstances) rather than per hardware and had to find this solution because we have over 30 models on our network (don’t ask!) so to have nearly 60 images to look after wouldn’t be feasible… can you imagine just having to install windows updates on each one!?!.. cringes
just to give you an idea of how i’ve set it up here (i understand this way doesn’t suit/work for everyone)
our image is stripped down and has minimal on it as possible, so it basically just has company branding, microsoft office on it and all windows updates, nothing else (unless it’s software that takes a long time to install or doesn’t change frequently etc…) - this is all built in audit mode. to keep unnecessary drivers etc off the image and keep image size as small as poss, i build the base image in VM also meaning i can just use snapshots for the “before and after” sysprep and if i want to update the image just fire up VM and revert to snapshot rather than deploying etc.
Then when the image task completes and before fog reboots this is what i get the init.gz to do.
so when the machine then boots up into sysprep, it’s got it’s unique details already and the drivers get installed as part of sysprep, it also eliminates the needed reboots to change hostname, add to domain etc or run any scripts post sysprep (apart from snapin!:)).
machine is set to autologin so logs in and snapin is set to lowest sleep time possible so it kicks off pretty much instantly and the snapin is just a small script with a gui (a pretty progress bar!) doing little changes, removing autologin, adding shortcuts here or there and installing those software previously pulled down from the server/node things like, adobe, java, AV, remote tool etc etc etc then finishes by removing installers, cleaning up, updating bios and reboots and it is then ready for the user to use.
doing it this way means i barely have to update my images, only for windows updates really. When new software comes out like adobe, all i have to do is update the installer on the server (also synchronizes across nodes) which means minutes work rather than having to update the images.
same goes for a new model - all i do is add the drivers for that model to the driver folder and presto! new model supported
takes around 15-20mins to build new machine from start to finish (ready for user to use) and there’s nothing for our engineers to do once imaging starts, so all in all only take 2/3 minutes of their time (to register machine and kick off image)
sorry for the long post just thought i’d share my setup too!
p.s. chad i could help you with the driver setup if you want but with recent development within FOG and upcoming/future plans might not need the assist, watch this space…
[quote=“warp, post: 24094, member: 22860”]The all this is to stabilize something overcharged as changing constantly as the PXE boot, which worked very well, for having changed?
You still need to know that the 0.33 version is expected for almost 2 years![/quote]
FOG is not a paid service and you still need to know that nothing should be “expected” the devs spend their own personal time working very hard to improve and stabilize FOG and do not make any money from doing so. Tom has worked extremely hard and is adding excellent addtions to FOG and the reason for the changes are either to move away from products either outdated or no longer being actively developed i.e. partimage or their are big benefits and potential in doing so i.e. ipxe
this is obviously old and outdated but give you the idea:
[url]http://www.fogproject.org/wiki/index.php/Hook_System[/url]
you could potentially get fog to “look” how you want it to (within reason) without hard coding your changes and making changes to the core code of fog and for example when it’s time for a fog upgrade, it would be easier to implement your “hooks” back in and in “theory” wouldn’t have to do anything to do that.
latest svn version typo under image management image path shows /images/images just need to remove the second images from path
[IMG]http://s12.postimg.org/84riji5nx/typo.jpg[/IMG]
This is excellent because you can customize and change the look of fog without actually changing the base code of FOG and “shouldn’t” break when updating FOG or at least be easy to re-implement your changes rather than hard coding them back in.
it’s not just joining after imaging - the client service will join to the domain at the next time it checks in with the server as long as domain join is set/checked under host information and the client checks in as pretty instant the first time the service starts/restarts so the easiest way without you having to mess with code is to just restart the fog service on the remote machine as long as you have admin rights to that machine just run this from command line (a windows machine):
sc.exe \machine restart “FOG Service”