@Jbob We use adminfog.

@Jbob It’s working.

I found something else.
In the MSI détails, I don’t have the right version displayed.
It’s write : {16B0BCD7-423F-49A9-B757-E457D7312A33}

Can you display version during install ?

Shouldn’t we be able to update client from tray or from GUI ?
I didn’t find how do this without overwriting.

@Jbob I will look stupid but how update it ? It’s directly in SVN ?

edit : It seems to be… lol

* Downloading inits, kernels, and the fog client..............

Task is still here.

Hello,
I have disabled shutdown for a computer but it keeps to shutdown.
In log it’s right detected

------------------------------------------------------------------------------
-----------------------------------GreenFOG-----------------------------------
------------------------------------------------------------------------------
 08/12/2015 17:27 Client-Info Version: 0.9.7
 08/12/2015 17:27 GreenFOG Running...
 08/12/2015 17:27 Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=greenfog&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
 08/12/2015 17:27 Middleware::Communication Response: Module is disabled on the host
------------------------------------------------------------------------------

I don’t have this morning logs of FOG log about this shutdown at this time.

My script launch edition didn’t solved the problem.
I try again with fog service disabled.

I have called for help from a old fellow worker.
He as said to try to replace the “timeout” command by a “ping 127.0.0.1”.
But, I think i have find a way to avoid this reboot during the script process.
I call my script in the unattend.xml like this “cmd /c start /wait Myscript.cmd”.
I wasn’t on site and I wanted to test it in the same condition (with the same fog server) in case it’s the fog client that makes this unwanted reboot (it’s Tom Elliott only idea to my problem).
I run few last test today and i keep you update.

Is the fog client use this exe to reboot the computer ?

Thomas use kinda the same script without problem but disable the fog service and that the only thing that I see that could explain a reboot.
Yet, i don’t see what a simple “pause” can change from a “timeout” to avoid this reboot.

I’ll test again with fog service disabled or the client remove to find if it comes from the fog client.
I can also try with a fresh OS install in case Windows Update did something.

Since I don’t know what trigger this reboot, I don’t even know where to start to dodge this reboot.
I don’t know if there is other way to run a script after a sysprep.
I only know with the setupcomplete.cmd or adding call of commands in the unattend.xml.

What do you mean ?

I did but the script never reach this line as it’s forced to stop for the reboot during the 60 seconds of the timeout command.

I know you’ll look for basic reason but I have tested so many things that I’m out of idea.

Reboot appears during

timeout /t 60 /nobreak 

When i say only pause, it’s only a pause

pause

lol

I have just make a test with only a “pause” in the script and there is no unwanted reboot.

Thank you for your reply.

I’m sure drivers install is not related to the reboot problem because, as i said, the timeout command is stopped before the 60 second.

I’ll repeat in case i wasn’t clear :

• Case 1 with the timeout command : countdown is stopped before reaching 0.
• Case 2 without the timeout command : SDI is forced to closed during install.

I have tested most of the posibilities possible during few days (this script was in setupcomplete.cmd at first) such as removing the timeout command, reducing it, adding or removing some “start /wait” or “cmd /c” in the xml.
I ended adding the %time% and the %date% to check system event and i see clearly a message saying that “wmiprvse.exe has initiated the restart of computer” but there is no more details.

I start to think that the computer doesn’t see that there is a script running so here my last test left, just set a “pause”.

Hello,
I run cmd script called from the unattend.xml of Windows sysprep.
This script makes a 60s break to wait network to start then run SDI (Snappy Driver Installer) that works perfectly when run manually.
During the script process, i have a reboot requested by wmiprvse.exe (WMI Provider Host).
This happen during the 60s, or during driver installation when i remove the 60s delay.
I have run SAD (Stand Alone Driverpack) for a year using the same way without any reboot during the process.

The only change made are that i was running SAD directly in the unattend.xml but now i call a cmd to run SDI.

Does anyone have idea why I have this reboot, if i can avoid it or if i have made a stupid mistake somewhere ?

Thank you.

Here is all the details i can provide.

Content of unattend.xml

<FirstLogonCommands>
	<SynchronousCommand wcm:action="add">
		<CommandLine>C:\SDI.cmd</CommandLine>
		<Order>1</Order>
		<RequiresUserInput>true</RequiresUserInput>
	</SynchronousCommand>
	<SynchronousCommand wcm:action="add">
		<CommandLine>cmd /c del C:\SDI.cmd</CommandLine>
		<Order>2</Order>
		<RequiresUserInput>true</RequiresUserInput>
	</SynchronousCommand>
	<SynchronousCommand wcm:action="add">
		<CommandLine>cmd /c rmdir C:\Users\Administrateur\Desktop\sysprep /s /q</CommandLine>
		<Order>3</Order>
		<RequiresUserInput>true</RequiresUserInput>
	</SynchronousCommand>
</FirstLogonCommands>

The cmd script

@echo off
echo %date% %time% Fichier de log cree >> C:\imageresults.txt 2>&1
echo %date% %time% Demarrage du script >> C:\imageresults.txt 2>&1
echo %date% %time% Attente de 60 secondes pour activation du LAN >> C:\imageresults.txt 2>&1
timeout /t 60 /nobreak >> C:\imageresults.txt 2>&1
echo %date% %time% Montage du partage samba de fog >> C:\imageresults.txt 2>&1
NET USE z: \\fogserver\Drivers
Z:
if not %cd% == Z:\ goto nofog
echo %date% %time% Installation drivers via SDI >> C:\imageresults.txt 2>&1
FOR /F "tokens=*" %%G IN ('DIR /B *.exe') do start /wait %%G -autoinstall -nologfile -autoclose -license
C:
NET USE /delete /yes Z:
:nofog
::echo %date% %time% Activation Windows >> C:\imageresults.txt 2>&1
::cscript C:\Windows\system32\slmgr.vbs /ato >> C:\imageresults.txt 2>&1
shutdown -r -t 30
exit

[FONT=Tahoma][COLOR=#000000]Here are the rights of the directory :[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#000000][CODE]drwxrwxrwx 20 root root 4096 2014-03-17 17:26 images[/CODE][/COLOR][/FONT]
and the sub directories
[CODE]drwxr-xr-x 2 root root 4096 2014-03-17 08:25 7pro32
drwxrwxrwx 2 root root 4096 2011-04-11 15:03 7-pro-32-sysprep-vauban
drwxrwxrwx 2 root root 4096 2011-04-04 12:56 7-pro-64-sysprep-vauban
drwxrwxrwx 2 root root 4096 2012-06-11 15:56 acer-m480
drwxrwxrwx 2 root root 4096 2012-06-11 16:45 admin-lenovo-1577-7-64
drwxrwxrwx 2 root root 4096 2010-02-02 11:49 cdi-acer-veriton-m410
-rw-r–r-- 1 root root 4628810288 2012-04-02 16:08 cdi-dell-optiplex-210L
-rw-r–r-- 1 root root 9685721343 2014-03-17 17:25 dell210Liaca
drwxrwxrwx 2 root root 4096 2013-12-09 17:57 dellcdi
drwxr-xr-x 2 root root 4096 2012-09-17 15:17 dell-optiplex-390
drwxrwxrwx 2 fog root 4096 2014-03-17 17:26 dev
drwxrwxrwx 2 root root 4096 2012-06-25 14:00 h22-acer-m480-32bits
drwxrwxrwx 2 root root 4096 2012-07-02 11:41 h22-acer-veriton-m410
-rw-r–r-- 1 root root 3546020335 2012-06-25 13:57 h22-nec-ml7
drwxrwxrwx 2 root root 4096 2012-11-12 16:24 h27dell390
drwxrwxrwx 2 root root 4096 2013-12-03 19:09 h27dell39001
-rw-r–r-- 1 root root 5333007375 2012-04-16 10:10 h27-dell-gx620
drwxrwxrwx 2 root root 4096 2012-06-11 14:29 lenovo-1577-7-64
-rw-r–r-- 1 root root 2825225992 2011-11-07 17:33 master-h22
-rwxrwxrwx 1 root root 3176718665 2010-07-05 15:36 nec-h22
-rw-r–r-- 1 root root 2575353559 2012-06-25 12:17 nec-ml7
drwxrwxrwx 2 root root 4096 2013-01-28 08:54 opti39032bit
-rw-r–r-- 1 root root 2586100327 2012-06-11 13:10 profs-acer-m410
drwxrwxrwx 2 root root 4096 2012-07-02 16:27 profs-acer-m480
drwxrwxrwx 2 root root 4096 2010-05-03 15:19 salleh27
drwxr-xr-x 5 fog fog 4096 2014-03-13 17:48 systemes-vierges
-rw-r–r-- 1 root root 1744269556 2011-11-02 14:13 xp-corp-sysprep-2011-11-03 [/CODE]

And what are the “normal” rights ?
Do you have a list of rights that must be set for images directory, sub folders and images files ?

Some links say fog user and root group and others say fog user and fog group.
Some links says 755 and others 777.
And on my own server, it’s root user with root group with chmod 777.

I don’t have fog as owner on my default installation.

[CODE]drwxrwxrwx 11 root root 4,0K sept. 30 10:23 images
[/CODE]

Hello,

We have just update a FOG 0.32 to version 1.2.
Local default storage works fine but the old system administrator added a 2nd storage manually.
I mean that he made a directory called “images” on a linux server (it’s a backuppc server in fact), add line for NFS on “exports” and create a local fog user.
I have check SSH login with fog account using the password write for this storage on GUI and it works fine.
FTP is running and works fine too. I have check connection from the FOG server.
We read fine this storage “Hardware Information”.

Is there need package to read image size ?

Thank you.