@Tom-Elliott ok it works for working branch, sorry 
Do I have to stay with working banch or move to dev ?
Posts
-
RE: installlang reset to ='' after each upgradeposted in Bug Reports
-
RE: installlang reset to ='' after each upgradeposted in Bug Reports
No, Iâm using dev-branch, I make change and test once again
-
RE: installlang reset to ='' after each upgradeposted in Bug Reports
Just tested, I change installlang to =â1â before upgrade, and after installation installlang is reset to =ââ
-
installlang reset to ='' after each upgradeposted in Bug Reports
Server
- FOG Version: 1.4 RC3
- OS: Debian 8.7
Client
- Service Version: 0.11.11
- OS: Win10
Description
Hi,
Each time I upgrade git, intalllang parameter in /opt/fog/.fogsettings reset to standard value (=ââ) so I have to set it to =â1â before upgrade.
Thanks
Matthieu -
RE: language frenchposted in Bug Reports
@Wayne-Workman Ok, upgraded to 1.4-RC3 and itâs fine ! But I still prefer english language

Is it normal I have to modify .fogsettings for installlang=ââ=â1â after each upgrade ? -
RE: change color of icon "upload"posted in Feature Request
@Tom-Elliott ok thanks, you made this on dev branch ? git pull and update in working branch but no change
-
RE: change color of icon "upload"posted in Feature Request
I agree with that, better differentiation will be fine ! For example on hosts management page, icons are : first => deploy, seconde => capture. But on Tasks management - List all hosts itâs the opposite : first => capture, seconde => deploy
-
[1.3.4 + Client 0.11.9] No hostname changer, AD integration and snapins after deploymentposted in Bug Reports
Server
- FOG Version: 1.3.4 (svn 6064)
- OS: Debian 8.5
Client
- Service Version: 0.11.9
- OS: Win10
Description
Hi,
Since last update to official 1.3.4 and 0.11.9 client, when I deployed PC (3 this morning), image deployment is ok but after nothing else occurs :
- no hostmane changer and no AD integration (I hadto do this manually on each computer)
- snapins stays with âcheked inâ status
No problem friday with previous 1.3.4 RC and 0.11.8 client.
Even after git pull and fog isntlal, Iâm still with svn 6064 (I saw in announcements thread that 6066 was last svn ?)I think itâs because client wonât upgrade (on all computers, even those already deployedâŠ)
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 30/01/2017 08:36 Client-Info Version: 0.11.8 30/01/2017 08:36 Client-Info OS: Windows 30/01/2017 08:36 Middleware::Authentication Waiting for authentication timeout to pass 30/01/2017 08:36 Middleware::Communication Download: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt 30/01/2017 08:36 Data::RSA FOG Server CA cert found 30/01/2017 08:36 Middleware::Authentication Cert OK 30/01/2017 08:36 Middleware::Communication POST URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&authorize&newService 30/01/2017 08:36 Middleware::Response Success 30/01/2017 08:36 Middleware::Authentication Authenticated 30/01/2017 08:36 Bus Registering ParseBus in channel Power 30/01/2017 08:36 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&configure&newService&json 30/01/2017 08:36 Middleware::Response Success 30/01/2017 08:36 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&mac=B0:83:FE:94:79:40&newService&json 30/01/2017 08:36 Middleware::Response Success 30/01/2017 08:36 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?clientver&newService&json 30/01/2017 08:36 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?newService&json 30/01/2017 08:36 Service Creating user agent cache 30/01/2017 08:36 Middleware::Response Module is disabled globally on the FOG server 30/01/2017 08:36 Middleware::Response Success 30/01/2017 08:36 Middleware::Response Module is disabled globally on the FOG server 30/01/2017 08:36 Service Initializing modules ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 30/01/2017 08:36 Client-Info Client Version: 0.11.8 30/01/2017 08:36 Client-Info Client OS: Windows 30/01/2017 08:36 Client-Info Server Version: 1.3.4 30/01/2017 08:36 Middleware::Response Success 30/01/2017 08:36 Middleware::Communication Download: http://192.168.10.60/fog/client/SmartInstaller.exe 30/01/2017 08:36 Data::RSA FOG Project cert found 30/01/2017 08:36 ClientUpdater Update file is authentic ------------------------------------------------------------------------------ 30/01/2017 08:36 Bus { "self": true, "channel": "Update", "data": "{\r\n \"action\": \"start\"\r\n}" } 30/01/2017 08:36 Bus Emmiting message on channel: Update 30/01/2017 08:36 Service-Update Spawning update helper 30/01/2017 08:36 UpdaterHelper Shutting down service... 30/01/2017 08:36 UpdaterHelper Killing remaining processes... 30/01/2017 08:36 UpdaterHelper Applying update... 30/01/2017 08:37 UpdaterHelper Starting service... 30/01/2017 08:37 Main Overriding exception handling 30/01/2017 08:37 Main Bootstrapping Zazzles 30/01/2017 08:37 Controller Initialize 30/01/2017 08:37 Zazzles Creating main thread 30/01/2017 08:37 Zazzles Service construction complete 30/01/2017 08:37 Controller Start 30/01/2017 08:37 Service Starting service 30/01/2017 08:37 Bus Became bus server 30/01/2017 08:37 Bus { "self": true, "channel": "Status", "data": "{\r\n \"action\": \"load\"\r\n}" } 30/01/2017 08:37 Bus Emmiting message on channel: Status 30/01/2017 08:37 Service Invoking early JIT compilation on needed binaries ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 30/01/2017 08:37 Client-Info Version: 0.11.8 30/01/2017 08:37 Client-Info OS: Windows 30/01/2017 08:37 Middleware::Authentication Waiting for authentication timeout to pass 30/01/2017 08:37 Middleware::Communication Download: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt 30/01/2017 08:37 Data::RSA FOG Server CA cert found 30/01/2017 08:37 Middleware::Authentication Cert OK 30/01/2017 08:37 Middleware::Communication POST URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&authorize&newService 30/01/2017 08:37 Middleware::Response Success 30/01/2017 08:37 Middleware::Authentication Authenticated 30/01/2017 08:37 Bus Registering ParseBus in channel Power 30/01/2017 08:37 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&configure&newService&json 30/01/2017 08:37 Middleware::Response Success 30/01/2017 08:37 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&mac=B0:83:FE:94:79:40&newService&json 30/01/2017 08:37 Middleware::Response Success 30/01/2017 08:37 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?clientver&newService&json 30/01/2017 08:37 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?newService&json 30/01/2017 08:37 Service Creating user agent cache 30/01/2017 08:37 Middleware::Response Module is disabled globally on the FOG server 30/01/2017 08:37 Middleware::Response Success 30/01/2017 08:37 Middleware::Response Module is disabled globally on the FOG server 30/01/2017 08:37 Service Initializing modules ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 30/01/2017 08:37 Client-Info Client Version: 0.11.8 30/01/2017 08:37 Client-Info Client OS: Windows 30/01/2017 08:37 Client-Info Server Version: 1.3.4 30/01/2017 08:37 Middleware::Response Success 30/01/2017 08:37 Middleware::Communication Download: http://192.168.10.60/fog/client/SmartInstaller.exe 30/01/2017 08:37 Data::RSA FOG Project cert found 30/01/2017 08:37 ClientUpdater Update file is authentic ------------------------------------------------------------------------------ 30/01/2017 08:37 Bus { "self": true, "channel": "Update", "data": "{\r\n \"action\": \"start\"\r\n}" } 30/01/2017 08:37 Bus Emmiting message on channel: Update 30/01/2017 08:37 Service-Update Spawning update helper 30/01/2017 08:37 UpdaterHelper Shutting down service... 30/01/2017 08:37 UpdaterHelper Killing remaining processes... 30/01/2017 08:37 UpdaterHelper Applying update... 30/01/2017 08:37 UpdaterHelper Starting service... 30/01/2017 08:37 Main Overriding exception handling 30/01/2017 08:37 Main Bootstrapping Zazzles 30/01/2017 08:37 Controller Initialize 30/01/2017 08:37 Zazzles Creating main thread 30/01/2017 08:37 Zazzles Service construction complete 30/01/2017 08:37 Controller Start 30/01/2017 08:37 Service Starting service 30/01/2017 08:37 Bus Became bus server 30/01/2017 08:37 Bus { "self": true, "channel": "Status", "data": "{\r\n \"action\": \"load\"\r\n}" } 30/01/2017 08:37 Bus Emmiting message on channel: Status 30/01/2017 08:37 Service Invoking early JIT compilation on needed binaries -
RE: Deployement failed on smaller drive (message "Target partition size smaller")posted in FOG Problems
@Tom-Elliott YES !!! Thanks Tom
It seems working, deployement begins after adding â1â in d1.fixed_size_partitions (which was empty).And I will remember Georges advice to prepare image on the smaller disk

-
RE: Deployement failed on smaller drive (message "Target partition size smaller")posted in FOG Problems
@george1421 Hi,
On computer with SSD 128 just deployed : 32GB used

On a 60GB SSD computer, deployed few months ago : 35GB used

-
RE: Deployement failed on smaller drive (message "Target partition size smaller")posted in FOG Problems
Iâve just test with another image and itâs okâŠ
so problem on my image, but I tried an older save (image from november) and same problem, while it works 2 weeks ago⊠Weird ! -
Deployement failed on smaller drive (message "Target partition size smaller")posted in FOG Problems
Server
- FOG Version: 1.3.4-RC2 (SVN 6063)
- OS: Debian 8.5
Client
- Service Version: 0.11.8
- OS: Win10
Description
Hi
Iâve got a âbigâ problem, Iâve just deployed image on 20 computers, and those who have a smaller drive failed with this message.


And after that computer is unusable (Windows broken).
Image prepared on dell optiplex 3020 with SSD 128GB, deployed successfully on dell latitude 3350 or dell optiplex 3040 (always with SSD 128, but not same reference), and even on a computer with HDD500Gb.
But on 4 PC with SSD smaller (Kingston v200 or v300 60GB), it fails with same errorâŠ
And I deployed same image 2 weeks ago on these same 4 computers and everything was fine !Thanks for help !
Matthieu -
RE: [HELP WANTED] Client Internationalizationposted in General
ok first try !
First french and english :
### SHUTDOWN PROMPT ### {company} a besoin de rĂ©aliser une opĂ©ration de maintenance sur cet ordinateur. {company} needs to perform maintenance on this computer. Merci de sauvegarder votre travail et de fermer tous les programmes. Please save any work and close all programs. Annuler Cancel Cacher Hide RedĂ©marrer maintenant Restart Now Ăteindre maintenant Shutdown Now Reporter dans Postpone for X heure(s) Y minute(s) Z seconde(s) X hour(s) Y minute(s) Z second(s) ### NOTIFICATIONS ### ArrĂȘt annulĂ© Shutdown Aborted LâarrĂȘt a Ă©tĂ© annulĂ© Shutdown has been aborted ArrĂȘt reportĂ© Shutdown Delayed LâarrĂȘt a Ă©tĂ© reportĂ© dans {time} Shutdown has been delayed for {time} Lâordinateur sâĂ©teindra dans {time} Shutdown will occur in {time} Vous allez ĂȘtre dĂ©connectĂ© You are about to be logged off Vous serez dĂ©connectĂ© si votre session reste inactive You will be logged off if you remain inactive Installation de {snapin name} Installing {snapin name} Ne pas Ă©teindre l'ordinateur tant que la tĂąche n'est pas terminĂ©e Please do not shutdown until this is completed {snapin name} installĂ© {snapin name} installed Lâinstallation est terminĂ©e, prĂȘt pour l'utilisation Installation has finished and is now ready for useThen just french
### SHUTDOWN PROMPT ### {company} a besoin de rĂ©aliser une opĂ©ration de maintenance sur cet ordinateur. Merci de sauvegarder votre travail et de fermer tous les programmes. Annuler Cacher RedĂ©marrer maintenant Ăteindre maintenant Reporter dans X heure(s) Y minute(s) Z seconde(s) ### NOTIFICATIONS ### ArrĂȘt annulĂ© LâarrĂȘt a Ă©tĂ© annulĂ© ArrĂȘt reportĂ© LâarrĂȘt a Ă©tĂ© reportĂ© dans {time} Lâordinateur sâĂ©teindra dans {time} Vous allez ĂȘtre dĂ©connectĂ© Vous serez dĂ©connectĂ© si votre session reste inactive Installation de {snapin name} Ne pas Ă©teindre l'ordinateur tant que la tĂąche n'est pas terminĂ©e {snapin name} installĂ© Lâinstallation est terminĂ©e, prĂȘt pour l'utilisation -
RE: Cannot change language of management webpageposted in FOG Problems
Hi, I canât help you, Iâm French but Iâm prefer to stay with english language
I tried to choose French on mamagement login page and in fog settings - General settings change FOG_DEFAULT_LOCALE with French also, but any change on display language. -
RE: [HELP WANTED] Client Internationalizationposted in General
Hi Joe, I can try to make french translation

-
RE: Group deploy - Theres no image definitions available on any node for the hosts in this groupposted in Feature Request
@Tom-Elliott Yes itâs ok for that.
But I still have this error when deploying several pc (for example 2 hours ago, deploy 14 pc and 3 of them didnât start and reboot)
https://forums.fogproject.org/topic/8994/rc-25-boot-error-when-pxe-booting (see docx)
Restart deployment when other pc were complete was ok -
RE: Group deploy - Theres no image definitions available on any node for the hosts in this groupposted in Feature Request
@Tom-Elliott I had sometimes same error so I did the trick, but now Iâve got error in fog.log :
Authentication error : Certificate is not from FOG CAEDIT : itâs ok, I have to restore management/other from backup

-
RE: IPXE boot HP X2 210 (hybrid)posted in Hardware Compatibility
@Tom-Elliott Yeah it works fine with this file !
Thanks, topic can be closed