[wpkg-users] reboot problem

[Nicolas Lepot]

Hello,

Thank you for your answer :)


>>>> if rebootCmd="special" in wpkg.js :
>>>> The startup is blocked indefinitely on the GUI of WPKG-Client and
>>>> nothing happens (no reboot).
>>> What do you mean by blocked? You can't login?
>> 
>> Yes, Exactly. Unable to login on Windows because the boot stop at WPKG moment. At startup, I see indefinitely the window of WPKG-Client. I waited 1 hour, but nothing happens. I still see the window of WPKG-Client.
> 
> This blocking (called "logon delay") will appear only as long as:
> 
> 1. wpkg.js runs commands, *AND*

 

--> This is not my case...



> 2. logon delay still didn't pass
> This means that if you have a broken installer that got stuck and hangs 
> for user input, and you set logon delay to 90 minutes, the logon delay 
> will block user for 90 minutes.
> On the other hand, if installation is quick and takes only 1 minute, it 
> will block logon only for 1 minute.
> 
> What's your logon delay in WPKG Client? I guess it's bigger than 1 hour? 
> And it hangs probably on psshutdown "accept window" you're talking about 
> earlier.

 

--> Aie! This is effectively my case.

I am really sorry to make you lose time for it. It's pity because I had read correctly the documentation.

Now, I define only one minute and the wait time is very short. 

Thank you.



> To debug it, set "show GUI" in WPKG Client, decrease logon delay, and 
> use /debug instead of /quiet for wpkg.js - you should see where it got 
> stuck.



OK. Now, in my settings.xml, I use for test :
...
/synchronize /debug
...
YES
...
1
...
 
And I loaded my file with : wpkginst.exe --SETTINGSFILE=\\server\WPKG\settings.xml
This is ok.
 
But, at startup of the computer, I see only the window of WPKG-Client and not the window of Command Prompt (with all traces of debug). However, I use the argument "/debug"... I thought that argument would display the window of Command prompt (Exactly as if I run the command "\\server\WPKG\wpkg.js /debug" in Command prompt in a session administrator)... So, when the computer starts, I see no difference between normal mode and debug. By contrast, in a administrator session, the debug mode gives me valuable informations in the command prompt.
 

This is normal ?
I made another error ?

 

> There are also some badly written applications which install fine from 
> Administrator account, but show errors or unexpected behaviour when 
> started from an account which has a name other than Administrator (other 
> administrator, SYSTEM user etc.), and that could be your other problem 
> (or, you accepted psshutdown license as Administrator, but not as SYSTEM 
> etc.).



I use only this package for searching my error of reboot :

    
    


 

>> In the local administrator environment, if I run manually the command : "CSCRIPT \\MAJ01\WPKG\wpkg.js /synchronize /debug", psshutdown.exe run. But it is blocked by the special licence "EULA" of Sysinternals because it is the first usage.
>> 
>> If I click "ok", the computer reboot correctly.
>> 
>> The psshutdown tool want a flag in the register key :
>> HKCU\Software\Sysinternals\PsShutdown\EulaAccepted=1.
>> 
>> 
>> With the user SYSTEM, psshutdown run well or is it blocked by the Eula Licence ?
> 
>
> I've no idea. I don't use that tool.
> When Microsoft acquired Sysinternals, they introduced this helpful 
> "accept license", which seems to confuse everyone.

 

I found a good solution for this case, simply copy in .reg file and run this :

Windows Registry Editor Version 5.00

' Usage of psshutdown.exe authorized for all profils
[HKEY_USERS\.DEFAULT\Software\Sysinternals\PsShutdown]
"EulaAccepted"=dword:00000001

' Usage of psshutdown.exe authorized for local SYSTEM
[HKEY_USERS\S-1-5-18\Software\Sysinternals\PsShutdown]
"EulaAccepted"=dword:00000001

' Usage of psshutdown.exe authorized for local service (nt authority)
[HKEY_USERS\S-1-5-19\Software\Sysinternals\PsShutdown]
"EulaAccepted"=dword:00000001

' Usage of psshutdown.exe authorized for network service (nt authority)
[HKEY_USERS\S-1-5-20\Software\Sysinternals\PsShutdown]
"EulaAccepted"=dword:00000001

 
--> Now, the reboot is OK if rebootCmd = "special" in wpkg.js. I'm very happy :-)
--> It is possible to add easely some lines in the function psreboot() of wpkg.js for to write these registry values automatically before the start of psShutdown.exe. If I can't restart the computer with  the "standard" mode, I will try that possibility.



> 
> With WPKG Client, you don't need to use this tool; WPKG Client can 
> reboot perfectly fine.
> 

 

Ok. 

I want continue to search the good solution if rebootCmd = "standard". 

Now, if rebootCmd = "standard", I don't have a reboot when the computer start. 

After the display of the window of WPKG-Client, Windows display the user logon and nothing happens (no reboot). The long wait with the GUI of WPKG-Client at startup is finished. The cause is found by you. Thank you again. 



For a install with WPKG-Client when the computer start, (I use only "/synchronize /quiet", and rebootCmd = "standard"), in event log of Windows, I see several messages :

WPKG Service trying start...
WPKG Service->RegisterServiceCtrlHandler: successfuly done
WPKG Service->SERVICE_START_PENDING: successfuly done
ServiceStart
Set script security context: successfuly done.
Network resource: successfuly connected
Script execution: successfuly done
Network resource: successfuly disconnected
WPKG Service->service_ctrlEx
WPKG Service->service_ctrlEx

--> What is it : "service_ctrlEx" ? a exception ?


I also tested the special log arguments in settings.xml : 

/synchronize /logfilePattern:'wpkg-[YYYY]-[MM]-[DD]-[HOSTNAME].log' /logLevel:31 /log_file_path:'C:\log' 

But without effect.
Now, I need ideas...

Thank you again,

Nico
_________________________________________________________________
Chattez, téléphonez et conversez par webcam GRATUITEMENT !
http://messenger.live.com