Hello again,
we all wonder about compatibility when we update FOG to the last version and we don’t all have the time to search the forum for our brand or just inform people on forum of our solutions.
Could it be possible to add a “send anonymous data” that would bring back usage of tftp files and boot exit type with which computers brands and series of the FOG users ?
This could be store to a database that would give us a list of what tftp file choose and what boot exit type ?
Thank you.
Tom is a wonderful contributor to the project (with Junkhacker from what i saw), a great support technician and very professional worker.
I have nearly the same daily work as him (i’m work in 3 college with around 500 computers in total, maybe more) and i couldn’t spend the tenth of his time on FOG (testing, debugging, improving, solving, etc.).
Everybody should understand that FOG is free and so, people working on the project doesn’t earn money for the time spend on it.
They only earn, other than the last added “Donate” advances task, is thankfulness from us (computer user, technician, administrator and company owner) and a bit of our time for testing, and bring them back the few bugs we could see.
Again, Tom, thank you. 
Hello,
could you display the list of deployed computers on the main page graph when we go over the dot ?
We could easily see what we have deployed the past few weeks without going to the report management.
Thank you.
I don’t activate Windows when the image will work for different brand of computer unless i would have buy an amount of licence but i will keep note of the amount used at the same time in this case.
I use OEM key from the brand of the computer after deploying this “multi system” image.
I only backup keys when image will stay on the same computer brand and serie.
For me, using brand installed OS then remove ALL unwanted and useless software and configuration or install Windows from the DVD and use the same OEM key, end at the same things.
The 1st way can create unstable OS, unused files and unused reg key and will ask you to spend days to clean it.
The 2nd way reach the minimal size possible.
The question is if the OEM licence is for Windows itself or for Windows with the brand software layer.
[quote=“Tom Elliott, post: 36441, member: 7271”]What is this?[/quote]
A drunk user ? haha
I don’t think there is link with the topic.
.pxe and .kkkpxe does exist on fog 1.x ?
In the updates, i only remember that it was write kpxe and kkpxe.
I see that services were not running when you run the stop command.
Does it change something after you started them manually ?
When i have strange things, i run install.sh and fog takes it as an update (no db drop or image deleted).
In fact, i do it for each new svn version.
Maybe this could fix something ?
This depend of your hardware, how you work and what you want to do.
My image were not working and i had to deploy some before this was fix by Tom so i had no choice than build a second server and keep the old one ready to deploy.
I’m under 1.2 and log should be somewhere else.
Try to find it with this command :
[CODE]
locate fogreplicator.log
[/CODE]
Hello,
i had to change “undionly.kpxe” to “undionly.kkpxe” to be able to boot on pxe with my laptop.
What are the difference between them ?
Would it be possible to see computer boot fine with the “undionly.kpxe” then not work with the “undionly.kkpxe” ?
Thank you.
All logs should be in /opt/fog/log/
I was thinking that the gui option wasn’t enable during update between theses versions.
Thank you for this information Tom.
Image from 0.32 are not supported on 1.x unless you activate support in the FOG option and then set image type as partimage.
So it depends with what version of FOG you made them.
Images made with 0.32 must be set to partimage and 1.x images set to partclone
If this can help, here are my conf even if FOG should have doe it itself during install :
/etc/dhcp/dhcpd.conf
[CODE]
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 192.168.10.5;
subnet 192.168.10.0 netmask 255.255.255.0 {
interface eth1;
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.10.10 192.168.10.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 192.168.10.5;
option routers 192.168.10.5;
filename “undionly.kpxe”;
}
[/CODE]
/etc/network/interfaces
[CODE]
auto eth1
iface eth1 inet static
address 192.168.10.5
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
[/CODE]
As i did this only once and one month ago and all worked fine,
maybe i’ll say ask or say things but i hope this would at least helpa bit to find what is not working.
Are you sure that you don’t have an other DHCP on your network ?
How your PC’s IP are configured then ? Are they all done manually ? Do you get IP from FOG DHCP under OS ?
Is your FOG IP configuration is set as static ?
Hello,
I’m not sure if you have 2 servers now or just a fog server with a node storage.
Yesterday, I have added my fog 1.2 as new storage under my old fog 0.32 to do a replication and it worked fine.
I learn from Tom that it’s the master that send image. I was thinking it was working also the other way (that the slave will retrieve the image) but it doesn’t.
Are they in the same group and the server as master ?
If you have two server like me, it must be configurated on the server that have the image.
You can also check TTY 3 and look what is write about the replication or stop and restart the replicator service and see if this change anything :
[FONT=arial][COLOR=#222222]Sudo service FOGImageReplicator stop[/COLOR][/FONT]
[FONT=arial][COLOR=#222222]Sudo service FOGImageReplicator start[/COLOR][/FONT]
Right, i have reserved position of storage. I’ll set my FOG 0.32 storage as master on my Fog 1.x
When start the replication and will it consume all my bandwidth ?
Have you reboot your VM before and after sysprep to see if this happen ?
At first boot and before Windows make it self optimization ?
I always used this way many time and once again last week and never had that certificate request or any error.
I find out that it was a proxy problem but I don’t know what they made different here on the proxy…
I uncommented and edited in “/root/.subvertion/servers” the following lines :
[QUOTE]http-proxy-host = 10.121.0.1
http-proxy-port = 3128
http-proxy-username = lyc-liegeard.fr\administrateur
http-proxy-password = **********[/QUOTE]