What is your normal data transfer rate through the IPSec tunnel using FTP, outside of FOG. If it’s slow doing a normal FTP, HTTP, or SMB file transfer from site to site, then you might try troubleshooting it from a VPN IPSec performance angle instead of FOG.

So after a while, I found a solution.

Before installing the OS, I wipe (normal, not fast) the DD with fog advanced task, next I installed XP + sysprep + deploy.

The image works perfectly on 5 PC (in multicast)

Franckb67

I get that behavior also. I just search for * and they all show up, and from that point on, they all show up. Wierd…

Snap-ins run in the context of the FOG Service user. Which I believe runs as the system user by default. Snap-ins themselves do not add anything to the c:\fog.log. The snap-in manager may add when a snap-in is executed, but I’m not sure.

While just calling the exe with no path may work now, it’s not the safest approach to take. Try using your system variables if you don’t want to hard code the path. %systemroot%, %comspec%, %windir%, etc.

Thank you for your help. I’m hoping to dig up some spare time in the next month or so to start moving on this. I will let you know how it goes.

It is possible that the image uploaded is corrupted. Run into similar problems with Dell 390 & 790. Usually stops during deploying the largest partition. However it doesn’t happen consistently, nor at the same point. It has nothing to do with partition size, since larger partition size would deploy fine. Try upload the image again from the same host. I am guessing it has something to do with the way data are compressed. Will test image out without using compression & see if it makes any difference.

I just came across this myself, and although you probably fixed it by now looking at the date of your post,for future reference for others I found my problem was down to some stale computer accounts in my AD, I removed these and all good.

Can you boot the computer into debug mode from FOG, run an fdisk -l, and then report the results here?

Not at this time. But you can modify the web scripts to do it.

Have you tried newer kernel? I am lazy, please check this page and try this method [url]http://community.spiceworks.com/how_to/show/1951[/url]. You can download kernel from here [url]http://sourceforge.net/projects/freeghost/files/Kernels/[/url]

No, just normal troubleshooting techniques. Could not find a way to drop a pc for an active multicast

install webmin on your Ubuntu Server

Unfortunately I’m not very familiar with the source code for the client, but there is the Additional MAC Address field on the host edit page. Adding the wireless NIC MAC address might take care of this, but again I’m not 100% sure without seeing what the client code is doing. Worth a shot though.

Yes our fog servers are either Windows 2003 Server or Windows 2008 Server and they all work well as storage nodes.

Sorry all, just found a fix for this in the bug reports forum - didn’t look there! All working perfectly now.

[quote=“kirksec, post: 2469, member: 289”]Then i wonder what my issue could be, because my Value is none but yet the session didn’t start[/quote]

did you get this resolved?

so multicasting to two machines today the log had no timeouts.

so i multicast to 10 machines and the log would receive timeouts in it (multicast speed at 600mbs roughly)

any ideas on what i should be troubleshooting?

After more troubleshooting…problem still not resolved but do notice something.

Issues is with Dell Optiplex 390

Tried on Dell Optiplex 780 it boots fine…

THOUGHTS???

Something is causing it to not exit the pxe boot.

I noticed on the 780 that once the pxe boot screen exits I see a screen that says something like…

Booting from local disk
Exiting pxe

I do not get that prompt or screen on the 390…imediately get the blinking cursor?

Need more information. What type of Image? NTFS Resizeable I’m guessing?

If so your filesystem must be 100% tiptop or you will get lost files during the NTFS partition resize, delete and recreation.

This is outside of FOG’s control and is down to the badness of NTFS.

Always chkdsk /x 😄 multiple times, reboot in between.