#3152 - 2000-05-30 05:25 AM
NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Hi,i`ve a Master Domain concept. My NT4.0 Workstations runs fine, but my Win95/98 make trouble. On my Login Domain i run a "start.bat" from Netlogon. --- Start.bat ---- @ECHO OFF net use x: \\srv1\netlogon x: %0\..\Kix32 login.kix EXIT The Kix-script runs fine, but the "NT-Logon Windows" doesn`t close (only under Win95/98). Has anyone a idea ? Thanks from Germany (sorry for my english) :-)
|
|
Top
|
|
|
|
#3153 - 2000-05-30 05:38 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Hi,First of all, you should run the Kix program from the netlogon share that is automaticaly connected at drive letter Z:. Then start a batch file like you're start.bat with the following code in it. %0\..\Kix32 %0\..\Login.kix Good Luck,
Jos. ( From The Netherlands )  [This message has been edited by Jos (edited 30 May 2000).]
[This message has been edited by Jos (edited 30 May 2000).]
|
|
Top
|
|
|
|
#3157 - 2000-05-31 02:23 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Hi Both, Jochen And BoxKite.I have to disagree about that. The KXRpc service is only needed when you want to use extended functions like @FullName and group membership. Please refer to the manual ( page 8 ). Jos  Sorry Jochen
|
|
Top
|
|
|
|
#3158 - 2000-05-31 02:47 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Thanks too all, but it`s doesn`t run.I think it`s better to tell you more of the Domaim. There a many Domains, the login domain is in Netherlands (PDC) and the BDC is in Germany. On PDC & BDC in the share "NETLOGON" is the Start.bat, on a Trusted Domain in Germany (PDC & BDC)is the Kix32 (in the Share NETLOGON). I think Win95/98 can`t go back to end the "Start.bat", so the "NT Login Window" hangs. Greetings. Ralf
|
|
Top
|
|
|
|
#3159 - 2000-05-31 03:03 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Hi RalFre,This is what you should do. Keep the Kix Program and the Kix Scripts all on the same NETLOGON Share. Why spread them over different logon shares at different domains?. I doubt that win9X can deal with that properly. Even NT WS. ( Sorry Jochen ). But it's a hard thing to do such things over trusted domains because of the user privilages etc. Jos.
[This message has been edited by Jos (edited 31 May 2000).]
|
|
Top
|
|
|
|
#3160 - 2000-05-31 03:22 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
HI Jos,first thaks for your answer. I spread them over differend domains, because there a differend Admins, one from Netherlands and one from Germany <smile> and the Logon Domain must be the "Netherlands". Ralf
|
|
Top
|
|
|
|
#3161 - 2000-05-31 04:00 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Hi Ralf,If i'll understand that correct you logon to the Netherlands domain and want to run a login script from youre own server ? In that case youre start.bat should look like this. Net use X: \\localserver\share %0\..\Kix32 X:\login.kix ; %0\..\ is youre path to the netlogon share. exit Jos.
|
|
Top
|
|
|
|
#3163 - 2000-05-31 06:04 AM
Re: NT Loginscript
|
Jochen
KiX Supporter
   
Registered: 2000-03-17
Posts: 6380
Loc: Stuttgart, Germany
|
Ralf (Jos Boxkite),here's another suggestion (referring to the Master Domain Concept!) I don't know what level of 'solutionproviding' You have Ralf , but wouldn't it be natural to place the logon-script in the repl$-folder of Your Master PDC ? -> setting replication to his own Netlogon-folder and to every single Resource-Domain-Controler (setting replication interval accordingly to the WAN-Speed).... Think i remember it correctly when i say that the Resource-Domains trusts the Master Domain?!?!?! (->Years and day since i thought bout that) Next step would be ammending the Script that it fits all of Your login requests! (in every Domain)... ok that will grow the script to a pair of kbytes , but this is the easiest way to handle. -> Think of dividing it into several Sections where You can hop to from the start , after deciding 'where the User is.... hope this gives a little hint! Greetings Jochen P.S.:this Solution must be well-implemented and thought-through
_________________________
|
|
Top
|
|
|
|
#3165 - 2000-06-01 07:44 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Okay everyone keeps talking about where the scripts are running from, I don't think it has anything to do with this problem. I am experiencing the same problem using the exact same scripts and scenario as from another large enterprise NT setup. The users login batch file and all scripts are in the netlogon share of the BDC, Kix32.exe and the two dlls (kx16 $ kx32) are copied into c:\windows along with kix32.exe. I have two script files, they are both pretty much the same, just one is for Win95 and one is for WinNT (different paths, windows vs. winnt is pretty much the only difference) The script works fine on Windows NT, but the window titled NT Login script with the cancel button doesn't close when the script completes on Windows 98 (don't know about Windows 95 not using it anymore). It has Exit in the end of the Kix script. The only thing I have come up with so far is that the lmscript emulation is coming into play (as documented in the manual ?? But don't really understand that and have never had a problem with login scripting in this way before) I don't have the third DLL or the RPC service installed on NT servers (have never needed it and frankly don't like screwing with my servers) I can get users fullname homedrive .. all the info I need from the Kix scripts without it.. dunno.. any ideas would be appreciated.. thanks.------------------ Steve Agnew MCSE since 1997 SteveAgnew@aol.com [This message has been edited by SteveAgnew (edited 01 June 2000).]
|
|
Top
|
|
|
|
#3166 - 2000-06-01 08:55 AM
Re: NT Loginscript
|
Anonymous
Anonymous
Unregistered
|
Okay I found out what the problem was on Windows 95 / 98. KixTart hangs during login(at least did in my environment) I mean by hanging when it does not exit the 'NT Login Script' (the window with the cancel button that appears above the login script window as you log into Windows 95/98) This behavior is caused by the login.bat file not exiting out while in the same directory as kix32.exe (or in c:\windows which is where kix32.exe is in my environment) Thus the following lines were put into the login.bat file:C: CD %WINDIR%
------------------ Steve Agnew MCSE since 1997 SteveAgnew@aol.com
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 671 anonymous users online.
|
|
|