ekainyah
(Getting the hang of it)
2005-07-06 09:23 AM
kixtart on a windows 2003 server platform

I have try serveral times to get kixtart 4.22 to map a driver for some group of user in a department (on a 2003 server platform) but it seems to work for me. I will be grateful if somebody give me a helping hand.
Cheers

Edmund


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 09:29 AM
Re: kixtart on a windows 2003 server platform

can't map drivers... can load them and install but not map... as far as I know.

ekainyah
(Getting the hang of it)
2005-07-06 09:39 AM
Re: kixtart on a windows 2003 server platform

Sorry not drivers but map a drive on a file server

LonkeroAdministrator
(KiX Master Guru)
2005-07-06 09:45 AM
Re: kixtart on a windows 2003 server platform

k, lets start with what you got.
could you show what you have tried.


ekainyah
(Getting the hang of it)
2005-07-06 09:59 AM
Re: kixtart on a windows 2003 server platform

I have these 3 files logon.bat, logon.kix and the kix32.exe.
the content of the logon.bat is:
kix32.exe logon.kix.
The content of the logon.kix is:

use "g:" "\\server\everyone"

If InGroup("Finance")
use "h:" "\\server\Accounts"
EndIf

If InGroup("Plant")
use "i:" "\\server\Maintenance"
EndIf

Then i have place all these 3 files in the %systemroot%\Sysvol\sysvol\domain.com\scripts.
Then in group policy,under User Configuration, then windows settings then in Scripts(Logon), i have place all the 3 file s in there. But still not working.


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 10:05 AM
Re: kixtart on a windows 2003 server platform

da, this is ad issue.
boys?


ekainyah
(Getting the hang of it)
2005-07-06 10:12 AM
Re: kixtart on a windows 2003 server platform

Active directory issue?????????

LonkeroAdministrator
(KiX Master Guru)
2005-07-06 11:17 AM
Re: kixtart on a windows 2003 server platform

in english, I can't help no matter how much I know about kix as I have no experience of kix in AD...

hmm... I probably should try that out though.
anyone willing to send me some hardware to run AD on?
I performed last test on P2 ~300MHz and it was ok.
anyone?


ekainyah
(Getting the hang of it)
2005-07-06 12:02 PM
Re: kixtart on a windows 2003 server platform

B'cos i am running a windows 2003 server domain and it will just not map the drive but if i run kix32.exe logon.kix /d from the command prompt, it map the drive. Anyway thanks for ur idea.
Need this to work badly. Hope somebody can come to my rescue.
Cheers

edmund


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 12:18 PM
Re: kixtart on a windows 2003 server platform

like said, the script seems ok and thus, the problem is not the script but your config to get it running on each logon.
that is AD issue.


ekainyah
(Getting the hang of it)
2005-07-06 12:21 PM
Re: kixtart on a windows 2003 server platform

Thanks man

ShawnAdministrator
(KiX Supporter)
2005-07-06 02:16 PM
Re: kixtart on a windows 2003 server platform

Stick a tracer message after your map, that will show you why its failing ...

use "h:" "\\server\Accounts"
? @SERROR

-Shawn


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 02:39 PM
Re: kixtart on a windows 2003 server platform

shawn... are you sure it's running at all?

ShawnAdministrator
(KiX Supporter)
2005-07-06 02:46 PM
Re: kixtart on a windows 2003 server platform

No I'm not - but this should help prove that theory too. Edmund, if you see no tracer message at all, then you will know its the InGroup that isn't working.

-Shawn


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 03:05 PM
Re: kixtart on a windows 2003 server platform

no.
if you have tracer messages all over your script, then you know your script is not running at all.
right?


ekainyah
(Getting the hang of it)
2005-07-06 06:14 PM
Re: kixtart on a windows 2003 server platform

When i run the command kix32.exe logon.kix /d at the command prompt,
you goes through, map the drive for me and tells me "The operation completed successfully" .But when i logon, it doesn't map the drive.


ekainyah
(Getting the hang of it)
2005-07-06 06:16 PM
Re: kixtart on a windows 2003 server platform

And i didn't get any tracer messages when i added the @SERROR

NTDOCAdministrator
(KiX Master)
2005-07-06 07:00 PM
Re: kixtart on a windows 2003 server platform

In a command prompt (DOS Console) type SET

C:\SET <hit the enter key>

You should find a variable set for LOGONSERVER

Then type START \\the server name\NETLOGON

That should open a window with all your scripts, if you don't find WKIX32.EXE or KIX32.EXE and your script there then you don't have them in the correct location.
 
If they are there, then you have your LOGON script GPO setup incorrectly.
 


ekainyah
(Getting the hang of it)
2005-07-06 07:36 PM
Re: kixtart on a windows 2003 server platform

When i type C:\set then enter, i see the logonserver=\\SerPlant
Then when i type the START \\SerPlant\netlogon,
it opens up an explorer showing all the 3 files.
I am going to check with the GPO setup.
I have it under user configuration in the GPO. Should it be under the machine configuration or what?


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 07:40 PM
Re: kixtart on a windows 2003 server platform

Quote:

If they are there, then you have your LOGON script GPO setup incorrectly.



Quote:

i have place all the 3 file s in there. But still not working.



hmm...
I think this one needs to be taken one step at a time.

remove everything from your logonscript setting except that bat.


NTDOCAdministrator
(KiX Master)
2005-07-06 07:46 PM
Re: kixtart on a windows 2003 server platform

What do you have specifically set for the GPO?

ekainyah
(Getting the hang of it)
2005-07-06 07:55 PM
Re: kixtart on a windows 2003 server platform

NTDOC,in the GPO, under the user configuration\windows settings\Scripts(logon/logoff), then i go into the logon properties and add all the 3 scripts from the netlogon folder. So that is what i have in there

Les
(KiX Master)
2005-07-06 08:02 PM
Re: kixtart on a windows 2003 server platform

Edmund,
There are several topics and at least one FAQ dedicated to running KiX as a GPO script. I suggest you have a go at the board search.


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 08:05 PM
Re: kixtart on a windows 2003 server platform

ekainyah, like said, you should only have that bat there.

Les
(KiX Master)
2005-07-06 08:07 PM
Re: kixtart on a windows 2003 server platform

Quote:

ekainyah, like said, you should only have that bat there.



Huh?
Just the opposite... put the BAT in the GPO GUID folder and leave KiX and the script in NetLogon.


LonkeroAdministrator
(KiX Master Guru)
2005-07-06 08:11 PM
Re: kixtart on a windows 2003 server platform

Quote:

Quote:

ekainyah, like said, you should only have that bat there.



Huh?
Just the opposite... put the BAT in the GPO GUID folder and leave KiX and the script in NetLogon.




huh huh?
Quote:

NTDOC,in the GPO, under the user configuration\windows settings\Scripts(logon/logoff), then i go into the logon properties and add all the 3 scripts from the netlogon folder. So that is what i have in there




Les
(KiX Master)
2005-07-06 08:17 PM
Re: kixtart on a windows 2003 server platform

GPO scripts like to run from the current dir, which is under the \\domain.tld\SYSVOL\domain.tld\Policies\{GUID}\User\Scripts\Logon folder

Kat
(Fresh Scripter)
2005-07-07 09:00 AM
Re: kixtart on a windows 2003 server platform

Well Not quite sure if I understood it right: you got the .bat and the scripts in the netlogon folder - should be fine I got this as well and my mapping works fine.
so have a look on the policy: how did you pur in the logon.bat? edit the policy and ad the logon.bat by browsing to the netlogon folder. (if you don't do that the default location is in the policy it self) If there is nothing else in the .bat file than calling the kix32.exe than don't use the .bat file at all and put in the logon script kix32.exe logon.kix in (again navigate to the right place and check if the path is OK) this will call your kix script instandly. I am not sure with the drive mapping as I use e newer version and don't know the syntax in the older one - I just assume that it is right.
(in mine is just use o: \\servername\share) I am running it an mixed plattform 2000/2003 and it works fine. (got it as a logon policy as well)
Hope this helps.
Kat


Kat
(Fresh Scripter)
2005-07-07 09:01 AM
Re: kixtart on a windows 2003 server platform

Oops forgot:
all my scripts and kix files are netlogon as well


ekainyah
(Getting the hang of it)
2005-07-07 09:43 AM
Re: kixtart on a windows 2003 server platform

Kat,
Now i have only the logon.bat in the GPO and then have the kix32.exe and the logon.kix in the netlogon folder.


ekainyah
(Getting the hang of it)
2005-07-07 10:25 AM
Re: kixtart on a windows 2003 server platform

Guys,
Where should the logon.bat be physically be place? Is it in the netlogon folder or it can be anywhere on the server?


Kat
(Fresh Scripter)
2005-07-07 10:27 AM
Re: kixtart on a windows 2003 server platform

did you the specify the path where kix32.exe is in the batch file? It will look for it in the same folder if you don't tell to look in a different (netlogon) location. and why don't you type the kix32.exe dicrectly into the logon instead of the batch file?

ekainyah
(Getting the hang of it)
2005-07-07 10:37 AM
Re: kixtart on a windows 2003 server platform

can you explain a little bit further

sixdoubleo
(Starting to like KiXtart)
2005-07-08 04:21 AM
Re: kixtart on a windows 2003 server platform

Go to your GPO screen. Go to User Configuration, Windows Settings, Scripts, Logon.

Remove what you have. Then click Add. Now, do NOT browse to the script. This wont work because your clients to not see the same thing you do. Microsoft shouldnt have even put the option in there.

Instead, type %logonserver%\netlogon\logon.bat as your script name. Leave the parameters field blank.

Save this. Then drop to a command line and do a gpupdate. Then go log off and back on. Should work.

And by the way, for simplicity's sake, I find it best to put EVERYTHING in the "scripts" root directory. Not taking anything away from Les as his method works fine...but when you get multiple GPO's going it can get hard to figure out which script is beneath which GUID directory. So for the above to work you'll need all three files in the scripts root (where you had them to begin with).


sixdoubleo
(Starting to like KiXtart)
2005-07-08 04:24 AM
Re: kixtart on a windows 2003 server platform

Also, as kat suggested, I would eliminate the batch file altogether (once you have this working.)

To do that you would put the script as: %LOGONSERVER%\NETLOGON\kix32

and the script parameters as: %LOGONSERVER%\NETLOGON\mylogon.kix

This is how I run mine and it works fine.


NTDOCAdministrator
(KiX Master)
2005-07-08 07:06 AM
Re: kixtart on a windows 2003 server platform

Okay guy ONE of these links has got to get you going. Please take your time and read up on this and you should be up and going well in no time.

 
GPO Change-over

Frequently Asked Questions About Logon Scripts

How to assign scripts in Windows 2000

Batch-less (or remove NTLOGON.BAT) Login script

Sequence of events during logon

Use of %0\..\ to launch KiX

Description of the Windows XP Professional Fast Logon Optimization feature

W2k+ - Keep the Window visible on login?

Windows NT Login Script Tricks and Tips

How to apply System Policy settings to Terminal Server

Group Policy may not be applied to users belonging to many groups

Environment variables in Windows NT

How To Assign a Logon Script to a Profile for a Local User in Windows 2000

Assigning Scripts Using Group Policy in Windows 2000

How to run a logon script one time when a new user logs on

Understanding Group Policies on Windows Server 2003

Step-by-Step Guide to Understanding the Group Policy Feature Set

 


LonkeroAdministrator
(KiX Master Guru)
2005-07-08 11:17 AM
Re: kixtart on a windows 2003 server platform

that many?
doc, do you expect us to read them all?
huh, can't be that hard.

and just like sixdoubleo said, clean for everyone's sake the logonscript value and set it like it should be.


StarwarsKid
(Seasoned Scripter)
2005-07-08 06:08 PM
Re: kixtart on a windows 2003 server platform

Ekainyah,
If you're having trouble setting up your logon script via GPOs perhaps you should look at an alternative method for deploying this script.

For example:

Logon script and KIX executable file locations should be..
File Location: C:\WINNT\SYSVOL\sysvol\damain.name\scripts\

Place the following text in your User Account's Properties
User Account properties>Profiles TAB>Logon Script>"kix32.exe logon.kix"

When logging in, your user's accounts will automatically run the "kix32.exe logon.kix" command from the closest domain controller's NETLOGON share.

If you have many user accounts that you need to change this value on and want to automate the process, you can use a kix script on your Domain Controller that will make the appropriate change for you. (be sure to test this in your environment before running on production servers)

Code:
 CLS
BREAK ON
; change DomainString to match your organization's NetBIOS domain name
$DomainString='Domain'
; change GroupString to equal the appropriate security group to affect
$GroupString='TEST'
$GroupObj = GetObject('WinNT://' + $DomainString + '/' + $GroupString)
For each $UserObj in $GroupObj.Members
;Look for the word NTLOGON in case of NTLOGON OR NTLOGON.BAT
;(change NTLOGON string if different in your environment)
IF $UserObj.AccountDisabled<>'True' AND INSTR($UserObj.LoginScript,'NTLOGON')
?$UserObj.Name
?$UserObj.FullName
$UserObj.LoginScript = 'WKIX32.EXE LOGON.KIX'
$UserObj.SetInfo
$error=@error
$logshare='H:'
$logfile=$logshare+'\'+$DomainString+'CHANGESCRIPT.CSV'
$logdata=$UserObj.Name+','+$UserObj.FullName+','+$error+@CRLF
LOGGER($logfile,$logdata)

ENDIF
Next
?'--'
?'Script complete'
SLEEP 4

FUNCTION LOGGER($logfil,$logdat)
$result=0
$n=0
DO
$result=Open(1, $logfil, 5)
IF $result<>0
IF $n=0
;First wait
?'Please wait'
ELSE
;follow waits
'.'
ENDIF
SLEEP 3
ELSE
$result=WriteLine(1, $logdat)
$result=Close(1)
ENDIF
$n=$n+1
UNTIL $result=0 OR $n=5
ENDFUNCTION



NTDOCAdministrator
(KiX Master)
2005-07-08 08:50 PM
Re: kixtart on a windows 2003 server platform

Quote:

that many




Quote:

Okay guy ONE of these links




No you don't have to read any of them. There not for you as you understand already. There for those that DON'T understand and are asking for help.

Personally I think this link explains it as well or better then most.
http://www.rlmueller.net/LogonScriptFAQ.htm

Just posted those links so that if he has trouble understanding one, maybe another would help.

Not sure you know or have noticed but many teachers in the World don't have the same results with all students, some students learn better from other methods or other teachers. That doesn't mean the teacher is not good, only that some have different learning needs.
 


LonkeroAdministrator
(KiX Master Guru)
2005-07-08 09:13 PM
Re: kixtart on a windows 2003 server platform

and that some are bad teachers

doc, don't get sad, I wasn't really picking on you.
just tried to lift up the atmosphere with some little "picking"


ekainyah
(Getting the hang of it)
2005-07-21 11:15 AM
Re: kixtart on a windows 2003 server platform

Hi Guys,
Thanks for the help. I have tried almost all the suggestion given out here but till didn't get this going for me. I entered the script directly into my profile and then when i logon, it mapped the drive according to the group i put myself in but when i put the script into the sysvol and the GPO, it doesn't and i just don't understand. Might have to try another script.Thank you all for.


Sealeopard
(KiX Master)
2005-07-22 05:16 AM
Re: kixtart on a windows 2003 server platform

Go back to the basics. Create a simple script that consistes just of a messagebox displaying a notice that the script is running. the place the script as per instructions below. Check the user ACLs to ensure they have acess. Try calling the script from a user's computer. Then strart enterign the script call into a GPO.

I've doen such things and it's easy as long as permissions and paths are set up correctly. Otherwise, you'll have to troubleshoot, e.g. enable file-level auditing or use other tools to see why the script is not being started. That's the stuff you really get paid for.