Posts made by BryceZ

Using current functionality, you could probably do this with Snapins and the DeepFreeze command line options.

I’ve seen reboot=bios solve some cases of machines failing to reboot after completing the image task, but I’ve had better luck with reboot=pci.

Are you using sysprep when building your image? Not using sysprep could be the cause of the failed first boot of Windows.

If you’re using Ubuntu 12.04/12.10 then it’s a known issue with rebooting. The “solution” is to use an older version of Ubuntu, such as 10.04.

FOG image files cannot be “opened” due to the way they’re designed, but you can image a VM or test machine and pull the files that way.

I’m pretty sure you need TCP 20 open as well. One of them is used for control while the other is for data. The username and password being used are the linux username and password, which need to match the FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD listed under FOG Settings in the web UI.

The error about the TFTP server is actually referring to FTP. When a task is created the web server FTPs a MAC address specific task file to the TFTP server. What you need is TCP ports 20 and 21 open to the web server. If this is all on the same server then you can just make it open to localhost.

It does sound like a RAID driver issue. Most likely you’ll need to use a different kernel or [URL=‘http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel’]build your own[/URL].

We don’t have a release date for FOG 0.33 at this point. FOG 0.33 isn’t just a collection of bug fixes or feature updates, it’s a complete rewrite of the underlying code structure, so it’s not like we can say “feature X will have to wait until next time”. The standard response is “it’ll be released when it’s ready”.

During the install process for FOG it asks if you would like to have FOG manage your DHCP. If you don’t have any images or a long list of hosts added to FOG already, it might be easiest to just set it up one more time from scratch on an isolated switch, making sure to let FOG handle DHCP.

Thanks Jesus, the more testing the better. The thread for beta testing 0.33 is [url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631[/url], feel free to document your test results there.

Windows 8 support is being tested.

Have you tried:
[CODE]sudo stop tftpd-hpa
sudo start tftpd-hpa[/CODE]

There is a major difference between what FOG does and what DeepFreeze does. FOG actually images the disk sector by sector (unless you’re doing a RAW image which is bit by bit), while DeepFreeze adds it’s own driver that redirects file writes to a temporary space that gets dropped on reboot. Currently there is no way to schedule FOG to reimage on every reboot (and even a small XP image (about 5GB) would take time and wear down the drive faster.

Dealman, non-sysprep’d images have worked in the past, and there are plenty of people that for whatever reason choose not to sysprep, so we want to insure that functionality still exists. We’ve already encountered some issues while testing non-sysprep’d images, but more tests with detailed step by step documentation can help us track down the bug a lot faster.

Falko, give it a try. I haven’t tested that functionality myself, and I haven’t heard of anyone else testing it, and I know the database schema changed with 0.33, so go ahead and try.

Always looking for more testers

The Full Wipe uses [URL=‘http://linux.die.net/man/1/shred’]shred[/URL]:
[CODE]shred -f -v -z -n 3 ${hd}[/CODE]
Full Wipe is more secure than the DoD Short option in DBAN. The DoD 5220.22-M option is more secure than one pass of Full Wipe, but two passes of Full Wipe would be more secure.

There is already a wipe function built into FOG. It’s listed under advanced tasks. There is also a tutorial on adding ISOs to the FOG boot menu [URL=‘http://fogproject.org/forum/threads/how-to-modify-the-pxe-boot-menu-to-allow-the-booting-of-iso-files.154/’]here[/URL].

FOG 0.32 was released a while ago (over a year). 0.33 is still in beta.

The quick way to delete multiple hosts is to add them to a group and then delete the group.

The database is different and there is no easy way of reverting back to 0.32 ( you might be able to do it manually, but I wouldn’t suggest it to anyone). The images are compatible as we are still using Partimage to collect and deploy images. Running FOG 0.33 in a VM is just a suggestion; 0.33 is still n beta and not really ready for production use (you can use it in production, but again I wouldn’t suggest it to anyone), so the idea is that people wanting to help with bug testing or get a feel for what’s coming will pull down 0.33 and test it in an isolated environment.