I fixed my problem. I had the IP address pointing to the wrong place. D’oh. Noobie mistake.

Thanks MLX,
I’ll mention the requirements to others - 🙂

I quick Google search for “Throttle Linux network connection” came up with this result - even if Fog can’t throttle, if you can slow down the speed of the server’s NIC it should accomplish the same result. You also might ask whoever the network is outsourced to if some form of QoS can be setup (so it can run at full speed unless someone else needs it).
[url]http://superuser.com/questions/66574/how-to-throttle-bandwidth-on-a-linux-network-interface[/url]

not without heavy modifications to the code. When uploading or deploying images, NFS is used to to access the image files.

The # is the prompt indicator. If I told you to run a command in windows like c:>ipconfig /release, would you type the c:>? o_O

Actually it was pretty straightforward to get working on FC17 -

Follow instructions found in other posts for Fedora Core 16 (Remove php-gettext from the install file, fix the NFS-server start so it won’t break the install process) Replace &$tmp with $tmp Start the NFS-server / enable the nfs-server

I just successfully re-imaged a computer 😄

OK, I’m an idiot, I’d somehow overwritten the ramdisk image with the kernel, turning off quiet produced an error that made that clear (unreadable ramdisk image, essentially).

Now I can load the kernel, but I eventually just end up at a command prompt. If I type “acronis” there, it does some stuff (something with network interfaces then enumerating my drives) but then just dumps me back to the prompt. Do I need to run it from a graphical environment? Is there any way to automate whatever the solution to getting it to run is?

[quote=“pjcard, post: 8665, member: 2528”]This discussion is about booting hirens over the network, russed, I think you’re talking about something else.[/quote]
Maybe you’re right, but as I stated at the start of my post, I had something to say about booting Hiren’s boot CD from it’s ISO image file and running its menus and programs.
I only had the hope that this can be useful for someone.

run chkdsk /f 😄
defrag
seatools for dos maybe?

Use proxyDHCP so you don’t have to worry about what the DHCP server config looks like.

Incase anyone else has this problem - It seems to have resolved it self.

The image I mention above was never sysprepped. I sysprepped it, uploaded it as multiple partition - single disk, and it worked fine multicast. After that I noticed the hidden partition shrunk from 500mb to 100mb. I figured I’d try uploading it as NTFS resizable - and go figure, it works fine multicast now.

Odd

hahaha thanks for the award. I checked the cabling and switching, things seem fine. I had to reboot the machine for some OS updates to take effect and that ended up fixing the issue for now. I’m still curious as to why it was happening. I will definitely poke around in syslog like you suggested next time.

Yeah, I could see 12.04 being the cause of our problems.

To be honest, if the virus messes up the computer badly enough to need a pxe boot scan to actually remove it, I’ve found it saves time to just reimage the machine (we make use of a lot of network storage, so losing files is almost never an issue).

I’m actually not sure about how well ClamAV works in regards to detecting and removing viruses, but maybe that’s for a different thread.

FOG doesn’t like to image most OEM recovery partitions. I used GParted to remove the Fujitsu recovery partitions and expand/rearrange the remaining partitions.

When you installed Ubuntu, did you make a “fog” user account? Did you set the IP address of the FOG server static before you installed FOG? Are you using FOG for your DHCP?

Is this a new problem? Has it worked in the past and just quit?

Ask your local computer resellers or support companies. One of them may be familiar with FOG.

For reference, the ONLY time you use FOGCrypt on a password is when setting the user credentials for joining computers to AD. All the other passwords in the FOG settings and config files are in plain text. I know some of them look encoded, but they are just random strings made complex enough so they are not easily guessed from 1 FOG install to the next.

All you really needed to do what reset the password for the “fog” user in the WEB ui, which you can do through mysql command line if you can login to the fog server.

You need to set the passwords in the /var/www/fog/commons/config.php and the web UI.
[LIST=1]
[]open /var/www/fog/commons/config.php
[]set the TFTP_FTP_PASSWORD, doesn’t have to be complex, but write it down.
[]set the STORAGE_FTP_PASSWORD to the same value as TFTP_FTP_PASSWORD.
[]save the file.
[]from the command line: sudo passwd fog
[]Enter the same value you used for TFTP_FTP_PASSWORD and STORAGE_FTP_PASSWORD
[]open the FOG web UI.
[]login as user: fog
[]go to other information, FOG Settings
[]Go down to the TFTP Server section, make sure the FOG_TFTP_FTP_PASSWORD value matches the TFTP_FTP_PASSWORD value from step 2
[]Save changes
[]Schedule a task and see if it works.
[/LIST]
In FOG 0.32, some settings are duplicated between the config files and the database. So you have to make sure both spots are updated or you have weird problems. It’s getting cleaned up for the next version I think, but for now, change the values in both the web UI and the config files.

After hours upon hours of trying to figure out a config file parameter I may be missing, that dummy file workaround is music to my ears. Thanks a lot!

You set it in the fog settings, pxe boot menu settings. You have to enter a master password before you can set any of the sub-passwords.