------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 20/03/2017 16:38 Client-Info Client Version: 0.11.11
 20/03/2017 16:38 Client-Info Client OS:      Windows
 20/03/2017 16:38 Client-Info Server Version: 1.3.5
 20/03/2017 16:38 Middleware::Response Success
 20/03/2017 16:38 SnapinClient Snapin Found:
 20/03/2017 16:38 SnapinClient     ID: 272
 20/03/2017 16:38 SnapinClient     Name: WSUS ID
 20/03/2017 16:38 SnapinClient     Created: 2017-03-20 15:38:00
 20/03/2017 16:38 SnapinClient     Action: 
 20/03/2017 16:38 SnapinClient     Pack: False
 20/03/2017 16:38 SnapinClient     Hide: False
 20/03/2017 16:38 SnapinClient     Server: 
 20/03/2017 16:38 SnapinClient     TimeOut: 0
 20/03/2017 16:38 SnapinClient     RunWith: cmd.exe
 20/03/2017 16:38 SnapinClient     RunWithArgs: /c
 20/03/2017 16:38 SnapinClient     Args: 
 20/03/2017 16:38 SnapinClient     File: SusClientId.cmd
 20/03/2017 16:38 Middleware::Communication Download: http://fogserver/fog/service/snapins.file.php?mac=4C:CC:6A:32:E5:4B||00:00:00:00:00:00:00:E0&taskid=272
 20/03/2017 16:38 SnapinClient C:\Program Files (x86)\FOG\tmp\SusClientId.cmd
 20/03/2017 16:38 Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"Installation de WSUS ID\",\r\n  \"message\": \"Ne pas éteindre l'ordinateur tant que la tâche n'est pas terminée\"\r\n}"
}
 20/03/2017 16:38 Bus Emmiting message on channel: Notification
 20/03/2017 16:38 SnapinClient Starting snapin...
 20/03/2017 16:38 SnapinClient Snapin finished
 20/03/2017 16:38 SnapinClient Return Code: 0
 20/03/2017 16:38 Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"WSUS ID installé\",\r\n  \"message\": \"L’installation est terminée, prêt pour l'utilisation\"\r\n}"
}
 20/03/2017 16:38 Bus Emmiting message on channel: Notification
 20/03/2017 16:38 Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=272&exitcode=0&mac=4C:CC:6A:32:E5:4B||00:00:00:00:00:00:00:E0&newService&json
------------------------------------------------------------------------------

Server

• FOG Version: 1.3.5
• OS: Ubuntu

Client

• Service Version: 0.11.11
• OS: Windows 10 pro 64 bits

Description

I run a script that write on a network share and use reg query.
It was working fine on 1.3.4 but since i have updated to 1.3.5, some commands doesn’t look to work.
I can write in local (such as c:) but not using \aComputerName\Myshare even using a “net use”.
Reg query doesn’t return anything neither.

These are the test I have done writing localy

echo 1. blablabla >> C:\logs.txt
REG QUERY %KEY_NAME% /v %VALUE_NAME% >> C:\logs.txt
echo 3. %KEY_NAME% >> C:\logs.txt
echo 4. %VALUE_NAME% >> C:\logs.txt
echo 5. titi;toto;tata >> C:\logs.txt
echo 6. %COMPUTERNAME%;%ValueValue% >> C:\logs.txt

Here are the results :

1. blablabla 
3. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate 
4. SusClientId 
5. titi;toto;tata 
6. console; 

Problem remain the same with version 1.3.5.

I have also run as Thomas asked :

truncate table snapinJobs;
truncate table snapinTasks;
delete from tasks where taskTypeID IN (12,13);

but without success

Server

• FOG Version: 1.3.4
• OS: Ubuntu 14.04.5 LTS

Description

I have a group of 260 hosts, I try to deploy a “Single Snapin” task.
More than 250 host had image associated.
None has snapins associated (it’s my first snapin).
Only 64 hosts hast task created at the end.

Cancel from GUI all task or run :

DELETE FROM `tasks` WHERE `taskStateID` IN ("1","2","3");
DELETE FROM `snapinTasks` WHERE `stState` in ("1","2","3");

only end to create the same amount of task each time.

Thank you

@sourceminer Hello, I never tested using a channel but using a private message works fine with test token.
You can also create your bot : https://my.slack.com/services/new/bot

Here is my conf :

Hello,

I have speak of this with Thomas but I don’t want to make him spend too much time on my problems.

We have received 3 type of Acer computer this year X2640g, X4640G and N4640G.
Both X are working fine with undionly.kkpxe but N isn’t.
N is only working with ipxe.pxe.
Thomas asked us to use the 10s delay pxe boot file since he thinks it’s because RSTP that is disabled on switches but problem remain the same.

Here are the 2 screenshot using undionly.kkpxe.
First is normal one, second is 10s delay one.

@Tom-Elliott Sorry Thomas. I am running 7001.

I have the same problem on my side (under Win 10 too).

@Tom-Elliott you are wonderful. lol

Hello,
could it be possible to send, as the Pushbullet plugin, messages to Slack account ?
Here is the site of Slack if someone want details : https://slack.com/

https://api.slack.com/methods/chat.postMessage

Thank you.

@FlowLive
I think you are right about the start /wait of the cmd.
But I have this on the .bat of SDI :

 start /wait "Snappy Driver Installer" /d"%~dp0" "%~dp0%SDIEXE%" %1 %2 %3 %4 %5 %6 %7 %8 %9

The web access of SDI is to check driver packages update.
Fog service name depend of the version you use on the OS of the image you are going to make.

@Jbob Thank you for your help too.

@Tom-Elliott That’s what i was thinking. Thank you.

@Wayne-Workman It’s set on computer startup. I can’t restart all my network like this… I fixed only a few manually.

@Tom-Elliott
I live in loops… lol

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 18/12/2015 16:25 Client-Info Version: 0.9.9
 18/12/2015 16:25 SnapinClient Running...
 18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 18/12/2015 16:25 Middleware::Communication Response: Success
 18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/snapins.checkin.php?mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 18/12/2015 16:25 Middleware::Communication Response: Success
 18/12/2015 16:25 SnapinClient Snapin Found:
 18/12/2015 16:25 SnapinClient     ID: 201
 18/12/2015 16:25 SnapinClient     RunWith: 
 18/12/2015 16:25 SnapinClient     RunWithArgs: 
 18/12/2015 16:25 SnapinClient     Name: Upgrade Client FOG
 18/12/2015 16:25 SnapinClient     File: upgradefogclient.bat
 18/12/2015 16:25 SnapinClient     Created: 2015-12-18 15:21:44
 18/12/2015 16:25 SnapinClient     Args: 
 18/12/2015 16:25 SnapinClient     Reboot: 0
 18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/snapins.file.php?mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=201
 18/12/2015 16:25 Bus {
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"Upgrade Client FOG\",\r\n  \"message\": \"FOG is installing Upgrade Client FOG\",\r\n  \"duration\": 10\r\n}"
}
 18/12/2015 16:25 Bus Emmiting message on channel: Notification
 18/12/2015 16:25 SnapinClient Starting snapin...
 18/12/2015 16:25 Service Stop requested
 18/12/2015 16:25 SnapinClient ERROR: Could not start snapin
 18/12/2015 16:25 SnapinClient ERROR: Le thread a été abandonné.
 18/12/2015 16:25 Service ERROR: Le thread a été abandonné.
 18/12/2015 16:25 Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 18/12/2015 16:25 Bus Emmiting message on channel: Status
 18/12/2015 16:26 RegistryHandler ERROR: Could not retrieve Software\Wow6432Node\FOG\Server
 18/12/2015 16:26 RegistryHandler ERROR: Null key
 18/12/2015 16:26 RegistryHandler 32 bit registry detected
 18/12/2015 16:26 Middleware::Communication URL: http://fog-server/fog/management/other/ca.cert.der
 18/12/2015 16:26 Bus Became bus server
 18/12/2015 16:26 Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 18/12/2015 16:26 Bus Emmiting message on channel: Status

@Wayne-Workman If he releases a new version that remove all old version (under 0.9.9) and upgrade the last (0.9.9), won’t it solve my problem ?
Will 0.9.7 client will download a 0.9.9+ version and clean the multiple install ?

My current script remove the 3 clients (old, 0.9.7 and 0.9.9) before installing the 0.9.9.
But this is not great since it will do this in loop.

@Tom-Elliott So a check looking for newer version was forgotten in 0.9.7 install to avoid such install ? Client shouldn’t have been installed if 0.9.9 was already installed.

@Tom-Elliott If I understand well, i have kept deloying the 0.9.7 when 0.9.9 was already installed automatically ?

@Wayne-Workman Nevermind.