#206393 - 2012-12-07 12:23 AM
Placement of kix32 file for windows 2008 R2
|
Tony
Getting the hang of it
Registered: 2001-11-04
Posts: 55
Loc: LA
|
I am currently using kixtart on a domain wide based (placement on netlogon directory) with policies, etc.
I am building a terminal server which I want to place it locally. Where do I place the file for Windows 2008 R2 64bit?
TIA, tntrac
|
|
Top
|
|
|
|
#206400 - 2012-12-07 11:38 PM
Re: Placement of kix32 file for windows 2008 R2
[Re: Lonkero]
|
Tony
Getting the hang of it
Registered: 2001-11-04
Posts: 55
Loc: LA
|
C:\Users is fine then?
I want to keep the same layout as what we used before on the con2prt scripting. So can you lead me to the syntax if possible. The Group name is not from AD. It explicitly define on the script.
IF @userID = JohnDoe goto Group_Name1
EndIF
'Below I specify share name and printers Group_name1 use z: "\\fs1\all$ AddPrinterConnection("\\PS1\HPb")
Group_name2, Next sample
Edited by Tony (2012-12-07 11:38 PM)
|
|
Top
|
|
|
|
#206402 - 2012-12-07 11:57 PM
Re: Placement of kix32 file for windows 2008 R2
[Re: ShaneEP]
|
ShaneEP
MM club member
   
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
However, using GOTO's is considered by many to be poor scripting. It results in code this is difficult to follow, troubleshoot, and edit.
Here is one of numerous alternatives to achieve the same task without using GOTO's...
Select
Case @UserID = "JohnDoe"
Group1()
Case @UserID = "Betty"
Group2()
Case 1
; If It Get Here Then User ID Was Not In List
EndSelect
Function Group1()
use z: "\\fs1\all$
$nul = AddPrinterConnection("\\PS1\HPb")
EndFunction
Function Group2()
use y: "\\fs1\none$
$nul = AddPrinterConnection("\\PS1\HPc")
EndFunction
|
|
Top
|
|
|
|
#206404 - 2012-12-08 12:44 AM
Re: Placement of kix32 file for windows 2008 R2
[Re: ShaneEP]
|
Tony
Getting the hang of it
Registered: 2001-11-04
Posts: 55
Loc: LA
|
However, using GOTO's is considered by many to be poor scripting. It results in code this is difficult to follow, troubleshoot, and edit. Here is one of numerous alternatives to achieve the same task without using GOTO's... Select
Case @UserID = "JohnDoe"
Group1()
Case @UserID = "Betty"
Group2()
Case 1
; If It Get Here Then User ID Was Not In List
EndSelect
Function Group1()
use z: "\\fs1\all$
$nul = AddPrinterConnection("\\PS1\HPb")
EndFunction
Function Group2()
use y: "\\fs1\none$
$nul = AddPrinterConnection("\\PS1\HPc")
EndFunction
Thanks shane. I haven't worked with Kixtart that much. I thought it has to be placed in a system directory of a local server if I want to go that route.
So how does it know where the executable file of kix? I am guessing you specify in the file itself or the local policy of logon script?
Note: Users who are logging in will be AD user.
Edited by Tony (2012-12-08 12:47 AM)
|
|
Top
|
|
|
|
#206408 - 2012-12-08 02:23 AM
Re: Placement of kix32 file for windows 2008 R2
[Re: Lonkero]
|
Glenn Barnas
KiX Supporter
   
Registered: 2003-01-28
Posts: 4402
Loc: New Jersey
|
In our domain, we have just one copy of Kix for logon processing - in the NETLOGON share. It services the login script for workstations, servers, and the RDP farm. The Kix login script itself is there as well. Same deal at our clients - we never place Kix32 or scripts on local systems for login processing.
We do, however, install Kix32 on every server for admin scripting unrelated to logon. We NEVER place it into the Windows folder or any subfolder. If it isn't part of Windows, it doesn't belong in that directory structure. We create a folder under Program Files (32-bit on x64 platforms) called "ITCG" - our company initials - and place all config files there.. Kix and any scripts or other tools go into a BIN subfolder, and that folder is added to the system PATH. Thus, we can run any system tools, BAT or KIX files, utilities, etc - directly from the command line or the RUN option of the start menu.
Glenn
_________________________
Actually I am a Rocket Scientist!
|
|
Top
|
|
|
|
#206435 - 2012-12-10 08:38 PM
Re: Placement of kix32 file for windows 2008 R2
[Re: Lonkero]
|
Tony
Getting the hang of it
Registered: 2001-11-04
Posts: 55
Loc: LA
|
I am thinking that I might put it on the netlogon directory. For the current kixstart script we have it there (also the kix32.exe). It is for the students who log into the student terminal server. I might just create a separate file called staff_terminal.kix (apply to group policy under the OU). I like to keep them separated instead of one large file.
If @WKSTA = "staff_terminalmachine"
Ideally, I am trying to avoid MS group policy integration as much as possible.
Edited by Tony (2012-12-10 09:19 PM)
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 1045 anonymous users online.
|
|
|