@george1421 said in [PXE-E32 error:
@Tom-Elliott said in [PXE-E32 error:
@george1421 I try to make them not care really but for 1.3/trunk I’d say 14 or higher for Ubuntu 8 of higher for Debian 6 or higher for rh based and 22 or higher fedora. I don’t think arch really cares lol.
@Wayne-Workman is ^^ this something that should be noted in the wiki pages? (at least on the upgrade to trunk page)
https://wiki.fogproject.org/wiki/index.php?title=Installation#Requirements
@Arrowhead-IT can you make a git repo with your two scripts in it, with a read me and a GNU GPLv3 license?
@Sebastian-Roth The real issue was Ubuntu 12 with FOG Trunk. Solved by Ubuntu 14 with FOG Trunk.
@Quazz I’ve not done that, everything seems fine. I wonder what potential issues there could be? I’m not copying the default user’s registry entries, just the files I believe.
@MattPayerle In the picture you posted, it appears normal. It takes a really long time to write zeros across a big drive. If anything, it would indicate an issue with full-wipe, because full-wipe should take x4 longer than normal wipe. @Tom-Elliott.
If FOG isn’t running DHCP, then there are no DHCP settings to change on the FOG server besides to use DHCP or not. If it’s utilizing DHCP - its taking whatever offer comes in first from whatever DHCP server. This is not specific to FOG, this is how all devices that use DHCP work.
If your wanting to change what DNS server the FOG server is actually using, that’d be in your interface’s configuration file. On red hat/fedora/centOS that is in /etc/sysconfig/network-scripts/ifcfg-interface and on Debian/Ubuntu it’s in /etc/network/interfaces
However, if your utilizing DHCP on the fog server, the DNS settings are normally specified by the DHCP server.
@Twilems I work in a school as well. I’m not concerned about the students customizing what they are allowed to customize. A great deal of things are locked down via group policy, to include wallpaper, screensavers, themes, resolution, control pannel, access to the command prompt, numerous file extension screenings and rules, no access to the c:\ drive. However, if they want to re-arrange the tiles in the start menu I don’t care about that, also re-arranging or customizing the task bar icons, that’s fine with me. Maybe they have a good reason for it, maybe it makes their life easier.
./installfog.sh # Requires Input
can be replaced with
./installfog.sh -y # Does not require input.
And if you move to CentOS 7, you can go to PHP 7.
And, if you wish to stay on CentOS 6, you can replace that line with
php_ver='5.5' php_verAdds='55u' ./installfog.sh -y
Or, simply update your packages list inside of /opt/fog/.fogsettings with the ones you want to use, and also update php_verAdds and php_ver while you’re in there too.
@george1421 said in FOG `Kernel panic - not syncing' error after entering quick host registration:
Plus when you ask for FOG support it will confuse the person helping you because they are not suspecting this non-standard setup.
Going to quote you on that 
@Quazz That definitely needs integrated into the script.
Probably - but not without a mega-ton of re-coding. Fog is focused completely around utilizing a network to accomplish imaging.
Conezilla is better suited for what you’re wanting - it already can do imaging from a local flash drive.
@Quazz In 8.1 and later, windows becomes un-activated when it detects it’s hardware UUID changed. MS Office is the same way now.
@Satheesh That means your boot order goes to network first. It’s not WOL causing that. You just need to change your boot order.
If you can’t do that easily, you can just hide the boot menu, it’s a setting in FOG Configuration -> iPXE boot menu.
@Gary-Kulovics said in Windows 8 image fails:
When trying to image a Win 8.1 pc get the following error
Starting to clone device (/dev/sda2) to image (/tmp/pigz1)
Reading Super Block
ntfsclone~ng.c: NTFS Volume ‘/dev/sda2’ is scheduled for a check or it was shutdown uncleanly. Please boot Windows or fix it by fsck
Wiki excerpt:
ntfsclone-ng.c: NTFS Volume ‘/dev/sda4’ is scheduled for a check or it was shutdown uncleanly. Please boot Windows or fix it by fsck.
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit
@Chris-Shipley Then perhaps you didn’t copy over all of the image files? Please give us the output of ls -lahRt /images/Win7Image on the new fog server.
Also, it’s possible you ran out of space while copying the images over. What is the output of df -h ?
@jes6309 I think that’s a separate issue, but easy enough to fix. The FTP credentials used for that are here:
Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD
If you have only one fog server in your setup, those credentials will be the same as these:
Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password
Both of these things and a lot more can be found in the “Troubleshoot FTP” article here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
@Tom-Elliott From my experience, on current fog trunk, you don’t even get to partclone when fast startup is turned on.
Also, that command must be ran from an elevated command prompt.