Topics created by klasikrkade

Have you tried the information in this thread?

[url]http://fogproject.org/forum/threads/many-will-want-to-rollout-win-8-1-on-new-hardware-well-before-the-expiry-of-xp-in-april-2014.9871[/url]

I’m running into the same problem.

Using Fog 1.2.0
Optiplex 3020, BIOS A05
No matter which kernel I use (official or unpublished) I can’t upload my image.
It gets stuck at “Using Hard Disk: /dev/sda”

And really, only kernels 3.14.2 and 3.16.0 have let me get this far. I let it go an hour yesterday hoping it would work but it just freezes at this point.

Any help would be appreciated.

Thanks

Please refrain from posting similar questions in multiple forums, this makes it hard for users to find answers when using the search system, and it makes it harder on those of us dedicating our time to try to help others.
Someone will be happy to assist you when someone with the expertise becomes available.

similar post -> [url]http://fogproject.org/forum/threads/is-flog-able-to-clone-windows-server-2008-with-raid-1-configuration.4470/#post-12886[/url]

Try to register your host again, look for what the last line displayed is.

After you attempt to register the host, check the log on the server in /var/log/daemon.log

Don’t post the whole thing just what is most recent and include it in code brackets.

Next check /var/log/syslog, again only paste the most recent concurrent event, if you attempted register at 11:35 paste that section for 11:35.

Look here for some information regarding pxe/tftp over vpn.

[url]http://fogproject.org/forum/threads/tftp-issues.823/#post-4112[/url]

This is all corrected for in 1.x.x Since moving to partclone, we’ve removed the need for sysprep, and even added the ability to have ntfs resize without sysprep for windows 7.

Try to check the command file for the machine in question.
/tftpboot/pxelinux.cfg/01-XX-XX-XX-XX-XX-XX (The file is named after the MAC of the machine)

Within that file check to make sure all settings are correct. Like DNS=(should be your DNS on Your network and not the remote DNS)

Another thing to check: is there something broadcasting on the remote network that could interfere with the traffic?

So I have been experimenting with limiting the TFTP block size to 1024 but I don’t think it is working. The way I am testing is this: I am observing a normal PXE boot with WireShark and looking at the size.

What I did in an attempt to limit the block size was this:

Edit [FONT=Times New Roman]/etc/default/tftpd-hpa and include [/FONT][FONT=Times New Roman]“-B 1024” under the OPTIONS line so the entire tftpd-hpa file looks like this:[/FONT]

[CODE]# /etc/default/tftpd-hpa

FOG Modified version

TFTP_USERNAME=“root”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“0.0.0.0:69”
TFTP_OPTIONS=“-s -B 1024”
[/CODE]

What am I missing?

I have a bunch of these ST250LT007 Seagate drives (the same Momentus line of drives, but with no encyption) and they work just fine. However, 4K advanced format drives are not supported in FOG yet. You’d have to use FOG .33 (beta still) to image those drives. That is what I am using now and it is working. The beta is not “feature complete” yet, but 4K drive imaging works.

I’d recommend downloading the beta release to a spare system and doing a few image tests. You could report your success/failures to this forum post:

[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/page-4#post-3691[/url]

If you need help getting the latest beta release down, just let me know.

If i may ask why is the machine set to logon with the Admin account ?

please use the CODE tags.

I may be wrong here, I haven’t worked with Fog in a while and may not be familiar with any new features, but here goes.

If you don’t specify a computer name in your answer file windows will always stop and ask you for a name. If you put a * in for the name, one will automatically be generated by windows and you will not be asked for a name. When the computer reboots, the fog service will kick in and automatically rename the computer to whatever it is in your database.

Your quick reg should be set to 0 unless you are actually using quick registration. Ex, you have 10 new computers but don’t want to give them all names manually. Quickreg will automatically do this for you, but as far as i know it has anything to do with sysprep.

Is your computer name really set to PC-*. If it is that’s not right. The start should be replaced with a number if quick reg worked correctly.

Early name changer - I have not worked with this yet. As far as I know it has to do only with registry and not sysprep. Maybe you have this setting on and the pc’s registry is updated to the name in your database, then sysprep is just getting the name from that.

In summary, turn off quick reg, turn off name change early, and change your answer file computer name to a * You should be fine then.

Try putting in a * and windows will give it a random name, and after that fog will rename it accordingly