[THIN] Re: Kix
- From: "Jim Hathaway" <JimH@xxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 12 Oct 2004 11:37:46 -0700
Bill, The Windows 2000 group policy login script field can only take *.cmd, *.bat, *.wsh, and *.vbs login script arguments by default. In cases where I want to call out a Kix based login script from group policy I personally use a launcher CMD file. IE = the group policy calls the TSlogin.cmd file Contents of TSlogin.cmd: kix32 \\servername\share\tslogin.kix HTH J ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Beckett Sent: Tuesday, October 12, 2004 11:10 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Kix Ahh, that might help. No I've only turned it on in the policy linked to the OU. I'll give it a try. -----Original Message----- From: Jonathan.Carr@xxxxxxxxxxxxxxxxx [mailto:Jonathan.Carr@xxxxxxxxxxxxxxxxx] Sent: Tuesday, October 12, 2004 2:07 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Kix Bill, Have you turned loopback processing on the Local Group Policy on the Terminal Server itself? We've just been fighting with a GPO that wouldn't run and it turned out that we needed loopback processing on the terminal server too. Hope this helps, Jon........... -----Original Message----- From: Bill Beckett [mailto:Bill.beckett@xxxxxxxxxxxxxxxxx] Sent: Tuesday, October 12, 2004 18:56 To: 'windows2000@xxxxxxxxxxxxx'; 'thin@xxxxxxxxxxxxx' Subject: [THIN] Kix Completely new to kix but I am doing some testing at the moment. I have a W2K terminal server in a 2000 domain. The terminal server box is located in a separate OU called Terminal Servers. I have a GPO called Terminal Server policy linked to this GPO. I ahve loopback processing turned on. I am creating a simple logon script for the Terminal Server Policy. I have the script name set to kix32.exe and the script parameters as the kix logon script (tslogon.kix). The problem is that it appears that the script is not being run, none of the drives are being mapped. However, if I run the script manually from a command prompt it does run. Do I have the script parameters set up incorrectly? Notice: This transmission contains confidential information intended only for the use of the individual or entity to whom it is addressed. Any disclosure, copying, distribution, or action in reliance on the contents of this transmission is strictly prohibited by anyone except the party to whom it is addressed.