Thanks for the reply. We have chainloading implemented. The problem turned out to be a missing file or files that weren’t copied correctly during the setup phase. Re-copying the files fixed the issue. Thanks again.
You really should be using FOG 0.32 and sysprep’ing your images.
I would be using 1 image for all rooms, as long as they are from the same hardware set.
Simply enable / disable the ‘Hostname Changer’ service per Host.
In regards to the Hostname Changer not working:
[LIST=1]
[]Open or preferably ‘tail’: c:\fog.log
[]Look for: HostnameChanger
[/LIST]
Are there any errors reported? It may take a few minutes for errors to appear.
Adding a row in the images table is not hard. But, there is currently there is no way to determine if the image is empty or not. This will be addressed in coming versions.
In the future, please create your own thread for your questions.
[quote=“rixter, post: 474, member: 168”]Blackout, are you sure this isn’t an initrd issue? I was thinking I had some issue where I changed out my init file and it took care of something similar to this.[/quote]
No Its just my best guess
Am I reading this right, you have windows and debian on the same pc, and on that pc you have fog installed and you want to ghost the windows partiton from the same pc that fog+debian is on? Maybe pulling your hard drive from the other pc, installing it in the pc with windows 7 on it, booting to debian (not windows) and learning how partimage works would be your best option here… You really need fog on a seperate PC than you are trying to pull a ghost from…
Thanks! but turns out my WOL wasn’t working because I had to update the driver of the NIC card, and then it only works during standby and hibernate… also, my switches were of the unmanaged type, so i didn’t have problems
Hi
I just upgraded to the latest and it worked. i dont think there was something wrong with the old version coz it was working before. may be installing the new version has fixed some error in my old installation.
regards
Thanks - I’ve been studying the code. Looking forward to the next release. FOG’s already been a game changer for me over using just an old copy of ghost and pxe/bartpe.
You need to make sure you have a valid gateway. Use ‘route -n’ to look at your routes.
There should be a default route (0.0.0.0) to your gateway IP (What ever that is)
i.e. mine
[code]fog-2:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 bond0
0.0.0.0 10.10.10.10 0.0.0.0 UG 0 0 0 bond0[/code]
I have static IP settings for my FOG servers, you will probably want this too.