There were some changes made by Tom in the last days. I guess he fixed things for you as well. Marking this solved. Please report back if you see the issue coming up again or if you have other problems.

Fix pushed. Basically if there’s any “bad” characters, I replace them (for the html attributes) with _, this way the attribute is setup properly and can be edited.

no problem, i’ll update trunk later on this week and try again.

@x9rok Is there any way I could get you to help me with the working and installation process involved to get clam av to work…I’ve got it installed on server at this point.

The global settings appear to be working now that the sloppy domain pre-fix has been removed and the cert issue was cleared up. It still appears to be a bug that the extra erroneous slashes are added, but if the expected input is wrong then that is fair enough really!

Thanks for the help, much appreciated.

@Tom-Elliott Didn’t have “join domain after image task” checked under host, and apparently didn’t allow enough reboots ( 2 by fogservice) for it to re-domain itself with new name. **Also had to make sure the gpo package (which I use to push client) was NOT set to “uninstall package when no longer managed”.

Remoted in and found that the files in /opt/fog/{service,etc} were having problems for some reason. Deleted them and installed again and all appears to have worked properly.

Thanks for the picture. Do you see anything after that or is it sitting there forever? From your first post I guess that you see more FOG messages after that. It all finishes without ever showing the blue partclone window? I am just guessing here. Feel free to upload a video and post a link here.

The errors on the picture should not be a show stopper AFAIK!

@need2 Imaging across the internet would be one good reason… Imagine that!

@ChrisJ said:

[quote=“Uncle Frank, post: 42587, member: 28116”]There are a couple of examples here in the forums. e.g.: [url]http://fogproject.org/forum/threads/boot-menu-iso-file-size.12442/[/url][/quote]

Thanks. That worked. Got the AVG ISO booting now.
If anyone is interested In Fog 1.2.0, in the fog configuration in the advanced config options text box I have this :

menu
item --gap – ---------------- iPXE boot menu ----------------
item AVG AVG Antivirus scan
item Sophos Sophos Antivirus scan
item shell ipxe shell
item return return to previous menu
choose --default AVG --timeout 5000 target && goto ${target}

:AVG
initrd http://${fog-ip}/${fog-webroot}/iso/avg_arl_cdi_all_120_141126a8645.iso
chain memdisk iso raw ||
goto MENU

:Sophos
initrd http://${fog-ip}/${fog-webroot}/iso/sophosbootable.iso
chain memdisk iso raw ||
goto MENU

:shell
shell ||
goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot[/CODE]

Next task is to customise that iso so its got up to date definitions, sets the network and proxy appropriately and has 2 options “scan” and “custom” where scan just gets on with it (if nothing is selected) without asking loads of questions and custom gives access to the original ARL menu…

Very helpful @ChrisJ, thank you!

@Tom-Elliott Many thanks for going through the effort of remoting into my system and getting FOG_trunk installed. Really - my best gratitude.

I have now thoroughly tested the FOG_trunk version. And, most unfortunately, I can confirm that I still have the original issue of the Win7 image just booting to classpnp.sys. I basically went through all the steps listed below again.

Nonetheless, I’ll keep my eye on this project and give it a few tries in the future as more versions become available.

Thanks, now it works!

Here is a step by step for rhel 6 distros
https://forums.fogproject.org/topic/6074/extending-a-file-system-on-redhat-base-distros

@Tom-Elliott Hi Tom, updated to latest git release now and indeed its working again. I did only update a few days ago after your last fix re the flashing issue.

regards Kiweegie.

@jimmmmmmah We need people like you who try out the most current version of FOG and report bugs. Otherwise we wouldn’t be able to find and fix all the issues. Please give it another go and hopefully we can figure things out together. See my first answer on where to find the apache error log file.

From my point of view it’s not a bug. Save to ignore. There is no stable build newer than 1.2.0 at the moment. But Tom has reworked the scripts and you are more than welcome to upgrade to the latest trunk and test things.

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

@Wayne-Workman roger that. Appreciate the input.

@george1421 That might work for getting imaging done in UEFI mode for this weird hardware, but I think that @tj.krause 's original problem is simply an exit to HDD issue in BIOS network booting mode. The OS is installed under UEFI / GPT but the network boot is Legacy - and things are not jiving.