Initiating kixtart-script via GPO. Bat(ch)-less. - KiXtart.org - official site

You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Lounge » Initiating kixtart-script via GPO. Bat(ch)-less.

Page 2 of 2

2

Topic Options

#163274 - 2006-06-16 08:45 AM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Björn Björn Korg Regular Registered: 2005-12-07 Posts: 953 Loc: Stockholm, Sweden.	Is there a reason for that? _________________________ as long as it works - why fix it? If it doesn't work - kix-it!
Top

#163275 - 2006-06-27 08:50 AM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1895 Loc: Hilversum, The Netherlands	It's not really neccesary to use GPU to deploy new loginscripts. I package wkix32.exe together with the loginscript using KixScript Editor and put that .exe in the netlogon share. Then in the AD under the user's properties you fill in the name of the .exe (without path) under the loginscript bar and your done. this way you can also replace the exe when it's needed without extra hassle.
Top

#163276 - 2006-06-27 10:24 AM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Richard H. Richard H. Administrator Registered: 2000-01-24 Posts: 4946 Loc: Leatherhead, Surrey, UK	My experience is that using "\\mydomain.com\netlogon" is really flaky as clients frequently cannot access the share for no good reason. Using "\\mydomain.com\sysvol\mydomain.com\scripts" is very much more reliable. BTW, this is not script language specific - VBS login scripts are just as problematical.
Top

#163277 - 2006-06-27 10:30 AM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1895 Loc: Hilversum, The Netherlands	Well you don't specify a path at all, just put in the name of the .exe for instance "start.exe" in the user's properties. On more then 20 different networks it has never failed me once. Here's an example: Edited by apronk (2006-06-27 10:45 AM)
Top

#163278 - 2006-06-27 10:49 AM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1895 Loc: Hilversum, The Netherlands	Don;t mind the profilepath or anything else just look at the "Logon Script"
Top

#163279 - 2006-06-27 12:16 PM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Richard H. Richard H. Administrator Registered: 2000-01-24 Posts: 4946 Loc: Leatherhead, Surrey, UK	Quote: Well you don't specify a path at all, just put in the name of the .exe for instance "start.exe" in the user's properties. On more then 20 different networks it has never failed me once. You're talking about configuring the logon script in user properties, while the thread topic is about using GPOs. Two very different things.
Top

#163280 - 2006-06-27 12:30 PM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1895 Loc: Hilversum, The Netherlands	Quote: You're talking about configuring the logon script in user properties, while the thread topic is about using GPOs. Two very different things. Look at my first post in this thread.
Top

#163281 - 2006-06-27 01:09 PM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Richard H. Richard H. Administrator Registered: 2000-01-24 Posts: 4946 Loc: Leatherhead, Surrey, UK	Quote: Look at my first post in this thread. How does that help in specifying the login script via GPO?
Top

#163282 - 2006-06-27 01:19 PM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1895 Loc: Hilversum, The Netherlands	I just tried to point out that doing it the way I specified doesn't require GPO, therefore it works after the GPO is applied and can't run too early. This way works the way it was intended.
Top

#163283 - 2006-06-27 03:31 PM Re: Initiating kixtart-script via GPO. Bat(ch)-less.
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Quote: My experience is that using "\\mydomain.com\netlogon" is really flaky... If Netlogon is not available on a DC, that indicates a problem with FRS. A DC will "offline" the Netlogon share when there is replication problems. The client should then look to DNS and resolve the "\\mydomain.com\netlogon" to another DC. _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

Page 2 of 2

2

Previous Topic

Previous Topic View All Topics

View All Topics

Index Next Topic

Next Topic

Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart

Hop to:

Shout Box

Who's Online

0 registered and 918 anonymous users online.

Newest Members

rrosell, PatrickPinto, Raoul, Timothy, Jojo67
17877 Registered Users

Generated in 0.085 seconds in which 0.037 seconds were spent on a total of 12 queries. Zlib compression enabled.

click tracking