[windows2000] Re: Poll

  • From: Greg Reese <gareese@xxxxxxxxx>
  • To: windows2000@xxxxxxxxxxxxx
  • Date: Wed, 1 Sep 2004 14:34:47 -0400

no.  Just drop the kix32.exe into the script directory along with the
.kix file you create and you are good to go.

all my users were already setup for logon.bat to be thr login script. 
I just edited that to have two lines: @ECHO OFF
%0\..\kix32.exe kixtart.kix

it's been working great for three years now.  All my clients are thin
clients with mandatory profiles running on Win2K3 terminal servers.  I
map all their printers, set default printers, setup outlook settings,
drives etc through kix at login.


----- Original Message -----
From: Bill Beckett <bill.beckett@xxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2004 08:52:01 -0400 
Subject: [windows2000] Re: Poll
To: "windows2000@xxxxxxxxxxxxx" <windows2000@xxxxxxxxxxxxx>

Quick question on kixtart...does it have to be installed on each client? 
-----Original Message-----
From: Sullivan, Glenn [mailto:GSullivan@xxxxxxxxxxxxxx] 
Sent: Tuesday, August 31, 2004 11:22 AM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Poll

My logon script is a VBS file, with a mix of some of the others. 
Let me explain: 
There is an identical copy of the VBS file both in the netlogon shares
of the DC's (for down-level clients) and in a GUID directory for the
"logon script" GPO.
Anyone Win2K or higher runs the script from the GPO.  There is 90% of
the workstations.
But, I had to deal with the other 10%. 
So, I created a .BAT file (since that is the only one that I can
guarantee will run on any system from Win95 up) executes a Kixtart
script.  This script:
1. Checks to see if the OS is Win2K or above... if so, exit, since the
script will run from the GPO.
2. Assuming we are on a down-level client, it checks to see if the
Windows Script Host 5.6 is installed.  If not, it installs it.
3. The it checks to see if the Directory Services client is installed.
 If not, install it.
4. If either 2 or 3 were installed, reboot. 
5. If neither 2 or 3 were installed, call the .VBS login script. 
This batch file is assigned to everyone in ADU&C in the "Login script"
Now, no matter which machine they log onto, the same script is run. 
And once my last Win9X/NT4 machine goes away, I just remove the "Login
script" setting from the user properties, and the GPO script takes
over as normal.
All of this was to take advantage of GPO Login scripts.  That and I
had a user who was creatively using CMD.exe on my terminal services to
do things that I didn't want him to, but when I restricted the
permissions on CMD.exe, the original, .BAT only login script did not
work anymore.

Glenn Sullivan, MCSE+I  MCDBA
David Clark Company Inc. 
 From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Beckett
Posted At: Tuesday, August 31, 2004 10:16 AM
Posted To: Windows 2000
Conversation: [windows2000] Poll
Subject: [windows2000] Poll

If I may bother the list for a quick poll. What do you use for
scripting (logon, etc)...
Shell Scripting 
This Weeks Sponsor StressedPuppy.com Games
Feeling stressed out? Check out our games to
relieve your stress.
To Unsubscribe, set digest or vacation
mode or view archives use the below link.


Other related posts: