I cant upgrade.
i’m stuck at
Running Version 1.3.4
SVN Revision: 6066
And when i try to upgrade here is the result :
cd /home/svn/trunk
[root@Fog] /home/svn/trunk # svn up
Mise à jour de ‘.’ :
À la révision 6065.
I cant upgrade.
i’m stuck at
Running Version 1.3.4
SVN Revision: 6066
And when i try to upgrade here is the result :
cd /home/svn/trunk
[root@Fog] /home/svn/trunk # svn up
Mise à jour de ‘.’ :
À la révision 6065.
Once deploy task finished, hostname changer failed with this error message :
13/02/2017 15:20 Client-Info Version: 0.9.12
13/02/2017 15:20 HostnameChanger Running...
13/02/2017 15:20 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:21:85:71:BD:8E||00:00:00:00:00:00:00:E0&newService=1
13/02/2017 15:20 Middleware::Communication Unknown Response: {"error":"ng"}
Does someone could help me ?
@x23piracy
It’s no more possible. I havent the computer with me and for my tests i had to remove logs
@Joe-Schmitt
Thanks for your answer.
But yesterday it didn’t works even i reset encryption data. I had to install manually the new client version
@Duncan
Do you think the solution could be to use Snapins to install new version of the client from 0.9.12 to 0.11.5 ?
As this page show SmartInstaller Switches
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options
@Duncan said in FOG 1.3 and old clients:
Hope this helps
It’s just the exact answer to my question !!! 
For information :
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options
Hello,
i just updated my fog server to 1.3.
Today i had to image an old pc with old client (0.9.12) installed. (client present into the image)
Then i activated hostname changer (active directory settings) but nothing happened.
I had to manually upgrade client version. (0.11.5)
After that hostname changer worked fine.
Is it normal ?
Does that means fog 1.3 is not compatible with old client version ?
Is there a way to upgrade all client automatically?
@plegrand
how can i upvote the thread (what means upvote) 
how can i solve a thread ? 
@george1421
Hello
i made some tests with these informations :
https://wiki.fogproject.org/wiki/index.php?title=IPXE#rom-o-matic.eu
the keymap is quite correct ( i cant use “{” “}” for example)
http://forum.ipxe.org/printthread.php?tid=7554
but the procedure is OK
Thanks for your help
i dont know how to solve the thread
@x23piracy said in Problem on HP ProBook 650g2:
Then have you got problem with computer with Realtek RTL8168D/8111D NIC (if you have some)
Thanks for your answer
@x23piracy
“we have a lot of this probook’s 650 G2 and they are working fine for me.”
Just to be sure :
you havent this message :
Warning using legacy NIC wrapper on 00:00:00:00:00:00
Are you using ipxe.pxe or undionly.kpxe ?
If you use “undionly.kpxe”, have you got problem with computer with Realtek RTL8168D/8111D NIC
Thanks for your answer
@Tom-Elliott i 'm making a lot of tests with my new configuration (ipxe) and it seems everything works fine except : Warning using legacy NIC wrapper on 00:00:00:00:00:00 message.
Then everything it’s ok !!
Just for information here is my new menu for ipxe (default.ipxe)
#!ipxe
# Variables utilisables : http://ipxe.org/cfg
# Commandes utilisables : http://ipxe.org/cmd
# --------------------------- VARIABLES ----------------------------------------
# TimeOut de 5 secondes
set TimeOut 5000
set fog-proto http
set fog-ip 192.168.39.243
set fog-webroot fog
set fog-url ${fog-proto}://${fog-ip}/${fog-webroot}
set tftp-proto tftp
set tftp-ip 192.168.39.247
set tftp-url ${tftp-proto}://${tftp-ip}
set ghost-directory ghost
set memdisk-bin memdisk
# ------------------------------------------------------------------------------
# Test du processeur : si ext 29 alors 64 bits sinon 32 bits
# && : Si Oui
# || : Si Non
cpuid --ext 29 && set arch x86_64 || set arch i386
# Image de fond
console --picture http://192.168.39.243/fog/service/ipxe/bg.png --left 100 --right 8
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
# S'il existe une seconde carte réseau alors le paramètre mac1 correspondra à son adresse mac. Sinon branchement sur MENU.
# S'il existe une troisième carte réseau alors le paramètre mac2 correspondra à son adresse mac. Sinon branchement sur MENU.
isset ${net1/mac} && param mac1 ${net1/mac} || goto MENU
isset ${net2/mac} && param mac2 ${net2/mac} || goto MENU
:MENU
menu
item Local Boot local
item Fog Fog
# item HostInfo Informations sur cette machine
item Shell IPXE shell
item Ghost Ghost Drivers Universels
choose --default Local --timeout ${TimeOut} target && goto ${target}
:Local
sanboot --no-describe --drive 0x80 ||
prompt
goto MENU
:Fog
chain ${fog-url}/service/ipxe/boot.php##params ||
prompt
goto MENU
:HostInfo
echo This computer : ||
echo MAC address....${net0/mac} ||
echo MAC address....${net1/mac} ||
echo MAC address....${net2/mac} ||
echo IP address.....${ip} ||
echo Netmask........${netmask} ||
echo Serial.........${serial} ||
echo Asset number...${asset} ||
echo Manufacturer...${manufacturer} ||
echo Product........${product} ||
echo BIOS platform..${platform} ||
echo ||
echo press any key to return to Menu ||
prompt
goto MENU
:Shell
shell ||
goto MENU
:Ghost
kernel ${tftp-url}/${memdisk-bin} keeppxe floppy
initrd ${tftp-url}/${ghost-directory}/universels.img
boot memdisk
prompt
goto MENU
autoboot
Tanks again
@Tom-Elliott
Hello
do you want i solve this thread ?
@Tom-Elliott
i think also is the bluetooth adapter
The thread is solved for me except “Fatal Error, unable to find size data out on”
But i think this problem come from the original partitionning (new HP computer with a lot of partition)
I have to reinstall it with the good number of partition.
As we saw that before i think it will solve the problem ?
Big, enormous thanks again for Fog and your precious help .
@Tom-Elliott
For the moment here is the tests i made :
I use ipxe.pxe
Then for the “ProBook” Computer i always have this message :
Warning using legacy NIC wrapper on 00:00:00:00:00:00
Configuring NET0 00:00:00:00:00:00
error 040ee119
Configuring NET1 98:e7:f4:e8:2b:bd
...
But the computer is well registered, than i can say that it works
For the computers with realtek nic it boot fine also.
Then i keep use ipxe.pxe for the moment and not “undionly.kpxe” (problem with realtek nic)
I continue my tests.
thanks again for your help
@Tom-Elliott
Hello Tom, now this computer (HP ProBook 650g2) boot fine and is well registered, but all the others olds computers, which booted fine before, hang now on :
ipxe initialising devices...
For the moment, computer having this problem has same NIC :
Carte réseau Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet (NDIS 6.20)
As i’m very new to “ipxe”, could you tell me what is the best to use : undionly.kpxe or ipxe.kpxe?
If i understand :
undionly.kpxe is universal driver
ipxe.kpxe contain a lot of nic drivers
The 2 uses the default.ipxe config file ?
What is the difference between ipxe.pxe, ipxe.kpxe, ipxe.kkpxe?
On the probook the only problem is on capture task :
An error has been detected
(ShrinkPartition)
Args passed : /dev/sda2 /images/98e7f4e82bbd/d1.original.fstypes :4:1
Fatal Error, unable to find size data out on /dev/sda2. Cmd: ntfsresize -f -i -v -P /dev/sda2
But i think the problem come from the original partitionning.
The last question is : before i used this kind of configuration file for pxelinux.0 :
DEFAULT vesamenu.c32
KBDMAP fr.kbd
MENU BACKGROUND splash.jpg
menu color title 1;37;40 #ffffffff #00000000 std
menu color timeout_msg 37;40 #80ffffff #00000000 std
menu color timeout 1;31;40 #ffff0000 #00000000 std
menu color border 30;44 #00000000 #00000000 none
TIMEOUT 300
ALLOWOPTIONS 0
PROMPT 0
MENU TITLE MENU
LABEL BootNormal
MENU LABEL Boot local
MENU DEFAULT
COM32 chain.c32
APPEND hd0
TEXT HELP
Boot sur le disque local.
Valider pour ne pas attendre 30 secondes.
ENDTEXT
LABEL Drivers_Universels
MENU LABEL Drivers Universels
KERNEL memdisk
APPEND keeppxe floppy initrd=ghost/universels.img
LABEL FOG_ETUDIANTS
MENU LABEL Clonage de postes avec FOG pour les postes ETUDIANTS
KERNEL fog/ipxe.krn dhcp && chain http://192.168.39.243/fog/service/ipxe/boot.php?mac=${net0/mac}
is there a way to configure default.ipxe to make the same ?
thanks again for your help
@Tom-Elliott
then :
copy of undionly.kpxe from fog server to tftp server :
scp /tftpboot/undionly.kpxe 192.168.151.247:/var/lib/tftpboot/
Change of dhcpd.conf configuration :
next-server 192.168.39.247;
filename “undionly.kpxe”;
i test
I had to copy also default.ipxe on my tftp server
scp /tftpboot/default.ipxe 192.168.151.247:/var/lib/tftpboot/
It seems that it boot fine with fog
then here is my differents configurations :
dhcpd.conf of my own dhcp server:
subnet 192.168.39.0 netmask 255.255.255.0 {
range 192.168.39.36 192.168.39.230;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.39.255;
option routers 192.168.39.254;
option domain-name-servers 192.168.39.253;
option netbios-name-servers 192.168.39.237;
.../...
next-server 192.168.39.247;
filename "undionly.kpxe";
}
configuration of my own tftp server
LABEL FOG_ETUDIANTS
MENU LABEL Clonage de postes avec FOG pour les postes ETUDIANTS
KERNEL fog/ipxe.krn dhcp && chain http://192.168.39.243/fog/service/ipxe/boot.php?mac=${net0/mac}
may be i could copy also an up to date ipxe.krn file ?
i test capture task
@Tom-Elliott
you mean on my dhcp server configurationi change pxelinux.0 by undionly.kpxe ?
then this file has to exist on my dhcp server ? i have to copy it ?
@Tom-Elliott
dhcp/tftp server : 192.168.39.247
fog server : 192.168.39.243
I use my own dhcp and tftp server on 192.168.39.247
Then i dont use the dhcp and tftp option on fog server. (192.168.39.243)
I use an intermediary tftp server for the moment
The host i registered appears in the fog app with the good mac address.
I program a basic task (capture)
and when i reboot it doesnt start task and told me that host is not registered.
It seems that it see 2 nic net0 and net1