#25777 - 2002-07-25 10:19 AM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
Hello again,
some more information:
I use kix to prevent the user getting his desktop until he has done "something". If the user doesn't do the "something" he should be logged out directly !
This works fine with kix and RunLogonScriptsSync=1 and when the workstation is online more than 5 minutes !
The only thing that makes the desktop visible to the user anyway is, when kix didn't find the script and didn't logout the user in this case of error.
If the script is found and there is an error in the script kix will logout the user... (good)
Why isn't that happening when the "failed to find/open script" occurs ?
Therefore the run or runonce commands cannot be used.
|
|
Top
|
|
|
|
|
#25779 - 2002-07-26 12:09 AM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
Hi,
I've found a way without NETLOGON...
I put into the HKLM/Software/Microsoft/Windows NT/Winlogon/userinit string the "kix32 scipt.kix".
...that's it !
|
|
Top
|
|
|
|
#25781 - 2002-07-25 03:57 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
LH
Lurker
Registered: 2002-07-25
Posts: 1
Loc: FRANCE
|
I've the same problem with Windows XP
We use %0 in the script, but it's OK if we wait 3 minutes after we have the screen "press CTRL- ALT -SUPP ......"
Have you answer ??
I can't put the logon script in registry because if I change the script, we need to modify registry and it's not possible in 300 computers
The administration is on the server and not on stations
|
|
Top
|
|
|
|
|
#25782 - 2002-07-25 04:09 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
Jack Lothian
MM club member
Registered: 1999-10-22
Posts: 1169
Loc: Ottawa,Ontario, Canada
|
Lonkero,
This is a topic that I usually avoid for a number of reasons.
Yes, I knew there were 2 registry entries that change an NT Workstation into an NT server. I believe this is discussed in great detail on both the O'Reilly & Sysinternals sites. Unfortunately, the OS constantly monitors these 2 locations & it will reverse any changes that a user tries to enter. The Sysinternals site outlines a general procedure that could allow one to mask this area from the OS & trick it into letting you change it. The Sysinternals site does not provide an actual program to do this.
These 2 registry entries fundamentally change the character of the OS. Microsoft claims that the chain of changes resulting from these registry entries affects about 500 parameters in the OS. So while in theory they are same OS, in practice NT Workstation is a severely crippled version of NT server & it can't really do all the things the server version can.
That being said, you & I were really recommending the same type of solution. MG independantly found an equivalent 3rd solution. NT has 5 or 6 methods for initiating a program during bootup & any of these would work.
LH,
Your problem can not be the same as MG, I believe his problem derived from the fact he didn't have a server while you have one. I would recommend that you should post a separate question concerning your problem.
[ 25 July 2002, 16:15: Message edited by: JackLothian ]
_________________________
Jack
|
|
Top
|
|
|
|
|
#25784 - 2002-08-07 03:17 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
Hi,
some users who do not want a script to be started and with the knowledge of this way around will not wait 3 minutes to login....
In our company we do not want a user to get to the desktop without running their Kix scripts, but with this little problem it is not possible to prevent this, except if there is way for the developers to avoid this -in my opinion bug- !
We are now living starting scripts without NETLOGON and KIX32 being the shell for the user...
Regards !
|
|
Top
|
|
|
|
|
#25786 - 2002-08-07 03:36 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
Sealeopard
KiX Master
Registered: 2001-04-25
Posts: 11165
Loc: Boston, MA, USA
|
|
|
Top
|
|
|
|
|
#25787 - 2002-08-07 04:05 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
Hello again,
we use BREAK OFF and no batch, because a batch can be interrupted !
The HKLM\...\run is a workaround like my solution, but not completely satisfactory....
...interesting would be, why kix32.exe is started and not able to find the scipt unless the whole system is up and running, wouldn't it ?
Kix has a feature to prevent users from stopping a script, logging the user off if an error occurs... but nothing if the script is not found.
Why logging off when a script error occurs and not when the script isn't available out of any reason ?
|
|
Top
|
|
|
|
|
#25790 - 2002-08-07 04:21 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
This is not possible... only relative pathnames are accepted in User Environement Profile !
This is possible in a batch, but this would take away the advantage preventing ctrl+c during execution.
MG
|
|
Top
|
|
|
|
|
#25792 - 2002-08-07 04:31 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
...again sealeopard this is not working when a system is comming up without waiting a few minutes.
[ 07. August 2002, 16:32: Message edited by: MG ]
|
|
Top
|
|
|
|
|
#25793 - 2002-08-07 04:35 PM
Re: "failed to find/open script" on local NETLOGON share in NT4.0
|
MG
Fresh Scripter
Registered: 2002-07-24
Posts: 16
|
Lonkero, YES !
And as I told you this is working a few minutes after the system is up, but not if you logon as soon as NT give you the possibility to do so.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 837 anonymous users online.
|
|
|
![[Confused]](images/icons/confused.gif){kind=icon}
