lawrence
(Fresh Scripter)
2002-03-27 07:20 PM
Cannot see custom scripts

After "launching custom scripts" shows I do not see my custom scripts, yet I do not get an error. I can run the scripts from the cmd line and they run ok. Any tips as to where to look for the problem???

NTDOCAdministrator
(KiX Master)
2002-03-27 07:25 PM
Re: Cannot see custom scripts

Lawrence,

I really hate to be a pain, but... you don't supply back the information for people to help you.

Case in point your previous post...
error reading config.ini file

No one here knows your system or specifics. You really need to supply much more detail on your issues in order for anyone to help you. Until you can supply this information we won't be able to help you. [Frown]

lawrence
(Fresh Scripter)
2002-03-27 09:16 PM
Re: Cannot see custom scripts

My first post: error reading config.ini file, I resolved by correcting some syntax errors.

I am running kix 2001 and my logon script runs ok with no errors, however I cannot see my custom scripts run. I'm running W2000 advance server and I'm running my script manully from the cmd line (DOS window)at the server. I have all of the kix files togeather in the winnnt\sysvol\sysvol\scripts folder. I hope this helps.

Bryce
(KiX Supporter)
2002-03-27 09:31 PM
Re: Cannot see custom scripts

I think he is refering to my modular logon script...

Lawrence is this what you are talking about/trying to get to work?

Modular logon script?

lawrence
(Fresh Scripter)
2002-03-27 10:02 PM
Re: Cannot see custom scripts

Yes I am using the modular logon script. [Big Grin]

NTDOCAdministrator
(KiX Master)
2002-03-27 10:19 PM
Re: Cannot see custom scripts

Thanks Bryce.. [Smile] That helps... Lawrence, I'll beg off now and let the Master Bryce help you with this. Your in good hands with Bryce.

Guyver
(Lurker)
2002-03-27 10:52 PM
Re: Cannot see custom scripts

There are several policy settings referring to scripts and whether or not they are visible while running.

Have you check this in the group policy?

lawrence
(Fresh Scripter)
2002-03-27 11:12 PM
Re: Cannot see custom scripts

Yes I have check my group policy and I enabled them to run startup scripts visible. This is really puzzleing! [Frown]

Les
(KiX Master)
2002-03-28 01:10 AM
Re: Cannot see custom scripts

Have you checked "RunLogonScriptSync"?

Bryce
(KiX Supporter)
2002-03-28 03:39 AM
Re: Cannot see custom scripts

Ok Lawrence,

i am going to assume that the Modular logon script is mapping drives, and doing everything else that it should be doing is this correct?

and that for some reason, it is not executing any custom scripts that you have instructed it to do.

1. the custon scripts are in the \scripts folder of the netlogon share right?

2. the config.ini file under [Other_Scripts] look some thing like this.

code:
[Other_Scripts]
	;This is where you can tell your logon script launch other KiXtart scripts
	;set status  to ON if you want to run this Module
	status = on

	:Script library
	ScriptLib = scripts\

	;Set TotalActions to equal the total number of Scripts actions
	TotalActions = 3

	; you can specify by OS Type and Group Membership, to run only specific Scripts
	; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
	; action# = OS Type | Group Membership | script name

	action1 = all|G!Domain users|inventory.kix
	action2 = off|G!Domain users|xmas.kix
	action3 = win9x|G!Domain users|mcafee.kix
Be sure to make Totalactions equal the total number of action/scripts that are to be ran.

if you could post this part of your config.ini... that could help.

Bryce

lawrence
(Fresh Scripter)
2002-03-28 11:31 PM
Re: Cannot see custom scripts

Hey Bryce,

My config.ini looks like this:
;You may Modify the following parameters to select how your logon scipt will
;function.

[Module_run_order]
;Module Library
ModuleLib = modules\

;Set TotalModuleNumber to equal the total number of Modules
TotalModuleNumber = 8

; you can specify by OS Type and Group Membership, to run only specific Modules
; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
; Modue# = OS Type | Group Membership | Module

Module1 = all|l!Administrators|CTRL_C
Module2 = all|l!Users|legal_notice
Module3 = all|l!Users|Welcome
Module4 = all|G!Domain Users|PWExpire
Module5 = all|G!Domain Users|Set_Clock
Module6 = ALL|l!Users|Drives
module7 = ALL|G!Domain Users|Path
Module8 = All|G!Domain Users|Other_scripts

[ctrl_c]
;set status to ON if you want to run this Module
status = on
break = on

[legal_notice]
;set status to ON if you want to run this Module
status = on
force = yes
notice = "You are loggin on to the Edwards Air force Base Computer network.|Only authorised personell are allowed to access this system."

[welcome]
;set status to ON if you want to run this Module
status = off
timeout = 5
welcome = "Welcome to Civil Engineering|Have A Nice Day||We Really Mean It!!"

[PWexpire]
;set status to ON if you want to run this Module
status = off

;X number of days till Password Expire(start showing a notice)
days2PWE = 5

;how old a pasword is allowed to get
PWE = 90

;message box timeout
timeout = 10

[set_clock]
;set status to ON if you want to run this Module
status = on
timeserver = \\houston

[drives]
;set status to ON if you want to run this Module
status = on

;set the TotalActions to equal the total number of drive mappings action

TotalActions = 44

; The drive mapping entires should be in this format.
; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
; action# = OS Type | Group Membership | UNC path | Drive letter

action1 = all|G!ce_admin|\\testserver2k\admin|G:
action2 = all|G!95trans.ce|\\testserver2k\95trans|G:
action3 = all|G!command.ce|\\testserver2k\command|G:
action4 = all|G!eng_general.ce|\\testserver2k\eng_general|G:
action5 = all|G!contracts.ce|\\testserver2k\contracts|G:
action6 = all|G!environmental.ce|\\testserver2k\environmental|G:
action7 = all|G!ops.fire.ce|\\testserver2k\fire|G:
action8 = all|G!heavy_repair.ce|\\testserver2k\heavy_repair|G:
action9 = all|G!infrastructure.ce|\\testserver2k\infrastructure|G:
action10= all|G!labor_pool.ce|\\testserver2k\labor_pool|G:
action11= all|G!logistics.ce|\\testserver2k\logistics|G:
action12= all|G!maintenance.e|\\testserver2k\maintencae|G:
action13= all|G!manpower.ce|\\testserver2k\manpower|G:
action14= all|G!operations.ce|\\testserver2k\operations|M:
action15= all|G!readiness.ce|\\testserver2k\readiness|G:
action16= all|G!real_property.recs.ce|\\testserver2k\rea_propertyl|G:
action17= all|G!work_order.ce|\\testserver2k\workorder|G:
action18= all|G!shopmanager.ce|\\testserver2k\shopmanager|G:
action19= all|G!tech_service.ce|\\testserver2k\fire|G:
action20= all|G!briefings.ce|\\testserver2k\briefing|I:
action21= all|G!A76_team.ce|\\testserver2k\A76team|I:
action22= all|G!fire_restricted.ce|\\testserver2k\fire_restricted|J:
action23= all|G!eng_programs.ce|\\testserver2k\engineering\division\plans\programs|J:
action24= all|G!eng_design.ce|\\testserver2k\engineering\division\plans\design|J:
action25= all|G!com_planing.ce|\\testserver2k\engineering\division\plans\com_plan|J:
action26= all|G!eng_saber.ce|\\testserver2k\engineering\division\saber|T:
action27= all|G!eng_managment.ce|\\testserver2k\engineering|J:
action28= all|G!operations.ce|\\testserver2k\engineering\division\maintenance|K:
action29= all|G!ops_maint_programs.ce|\\testserver2k\engineering\division\maintenance|K:
action30= all|G!logistics_ro.ce|\\testserver2k\logistics|K:
action31= all|G!acquisition.ce|\\testserver2k\contracts_acquisition|K:
action32= all|G!bce_briefing.ce|\\testserver2k\bce_briefing|L:
action33= all|G!drawing.ce|\\testserver2k\dangerous|I:
action34= all|G!standby.ce|\\testserver2k\standby|M:
action35= all|G!slides.ce|\\testserver2k\slides|P:
action36= all|G!standup.ce|\\testserver2k\standup|P:
action37= all|G!networking.ce|\\testserver2k\networking|S:
action38= all|G!southbase_rp.ce|\\testserver2k\southbase_rp|S:
action39= all|G!ccas.ce|\\testserver2k\ccas|S:
action40= all|G!water.ce|\\testserver2k\water|W:
action41= all|G!division.ce|\\testserver2k\division|Y:
action42= all|G!fedlog.ce|\\testserver2k\volumes|O:
action43= all|G!afepl.ce|\\testserver2k\volumes|O:
action44= all|G!cbt_access.ce|\\testserver2k\volumes\access97|T:


[Path]
;**********************************************************
;---===this module is broken for win9x users....sorry.===--
;**********************************************************

;This is where you can tell your logon script add or remove statments from the Path
;set status to ON if you want to run this Module
status = off

;Set TotalActions to equal the total number of Actions
TotalActions = 4

; you can specify by OS Type and Group Membership, to add or remove the selected paths
; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
; action# = OS Type | Group Membership | A!path to add
; action# = OS Type | Group Membership | R!path to remove

action1 = NT|G!Domain Admins|a!w:\ntreskit
action2 = win2k|G!Domain Admins|a!w:\w2kreskit
action3 = NTx|G!Domain Admins|a!w:\ntsec
action4 = off|G!Domain Admins|a!w:\ntsec

[Other_Scripts]
;This is where you can tell your logon script launch other KiXtart scripts
;set status to ON if you want to run this Module
status = off

:Script library
ScriptLib = scripts\

;Set TotalActions to equal the total number of Scripts actions
TotalActions = 2

; you can specify by OS Type and Group Membership, to run only specific Scripts
; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
; action# = OS Type | Group Membership | script name

action1 = all|G!all_users.ce|dod.kix
action2 = off|G!all_users.ce|alphare.kix

Bryce
(KiX Supporter)
2002-03-28 11:34 PM
Re: Cannot see custom scripts

set the status for Other_scritps to be on

[Other_Scripts]
;This is where you can tell your logon script launch other KiXtart scripts
;set status to ON if you want to run this Module
status = on

lawrence
(Fresh Scripter)
2002-03-28 11:37 PM
Re: Cannot see custom scripts

Sorry... this is what you requested.
[Cool]
L

[Other_Scripts]
;This is where you can tell your logon script launch other KiXtart scripts
;set status to ON if you want to run this Module
status = on

:Script library
ScriptLib = scripts\

;Set TotalActions to equal the total number of Scripts actions
TotalActions = 2

; you can specify by OS Type and Group Membership, to run only specific Scripts
; please see logon-readme.txt for a full explanation on "OS type" and "Group membership".
; action# = OS Type | Group Membership | script name

action1 = all|G!all_users|dod.kix
action2 = all|G!all_users|alphare.kix

Bryce
(KiX Supporter)
2002-03-29 12:01 AM
Re: Cannot see custom scripts

yep, that should fix things. [Wink]

lawrence
(Fresh Scripter)
2002-03-29 12:05 AM
Re: Cannot see custom scripts

I still do not see my scripts. Could it be something on my box?? If I run the scripts manually from the cmd window it works. Go figure!

[Confused]

Bryce
(KiX Supporter)
2002-03-29 01:13 AM
Re: Cannot see custom scripts

how are you running manualy....

kix32 \\server\netlogon\scripts\dod.kix

lawrence
(Fresh Scripter)
2002-03-29 04:34 PM
Re: Cannot see custom scripts

Almost - from the scripts folder I'm running:
kix.exe\dod.kix [Cool]

Any ideas Bryce??

Bryce
(KiX Supporter)
2002-03-30 01:45 AM
Re: Cannot see custom scripts

ok do this from a command line

dir \\server\netlogon /s

and show us what it gives you.

Kdyer
(KiX Supporter)
2002-03-30 04:09 AM
Re: Cannot see custom scripts

Bryce/Lawrence,

Mind if I chime in here?

Lawrence - It appears that the execution is very close..

Try this, if the files are in the same directory:
Option (1)
kix.exe dod.kix

Option (2)
\\Server\share\kix.exe \\Server\share\dod.kix

Option (3)
%logonserver%\netlogon\kix.exe %logonserver%\netlogon\dod.kix

Option (4)
%0\..\kix.exe %0\..\dod.kix

One of these options should get your Kix file running via batch.

HTH,

- Kent

lawrence
(Fresh Scripter)
2002-04-01 10:24 PM
Re: Cannot see custom scripts

Bryce - when I run dir \\server\netlogon /s I receive "the network name cannmot be found" any clue??

Kent - option 1 works I did not try the other options, I'm also using modules in my script

Sealeopard
(KiX Master)
2002-04-01 10:27 PM
Re: Cannot see custom scripts

Lawrence:
'\\server\netlogon' is a generic statement. You will need to replace 'server' with the name of any of your domain controllers and 'netlogon' with the name of your netlogon share, by default 'netlogon'.

lawrence
(Fresh Scripter)
2002-04-01 10:37 PM
Re: Cannot see custom scripts

Bryce- I typed in "\\terserver2k\netlogon", when I should have typed "\\testserver2k\scripts" I gor the directory list.

Sealeopard
(KiX Master)
2002-04-01 10:42 PM
Re: Cannot see custom scripts

Now try
code:
%logonserver%\scripts\kix.exe %logonserver%\scripts\dod.kix
This will only work against the server that autneticated you.

code:
\\testserver2k\scripts\kix.exe testserver2k\scripts\dod.kix
This will only work with the server TESTSERVER2K

[ 01 April 2002, 22:44: Message edited by: sealeopard ]

lawrence
(Fresh Scripter)
2002-04-01 11:02 PM
Re: Cannot see custom scripts

When I type "%testserver2k%\scripts\kix.exe %testserver2k%\scripts\dod.kix" I get "the system could not find the path specified" I think my problem is the default logon share.

Sealeopard
(KiX Master)
2002-04-01 11:26 PM
Re: Cannot see custom scripts

%TESTSERVER2K% will try to resolve a variable that has been set with the DOS SET command. If the variable is empty, it'll return the error you just specified.

Lawrence, it seems you are very, very new to administering Windows NT/2000 domains. I would suggest you take a break and go back to square one.

I assume you do have a clean install of your Windows 2000 domain controller. Now, start with the most simple login script, e.g. LOGIN BAT
code:
ECHO Running login script
The login script must be set up in the user manager as LOGIN.BAT. The script should run when a user logs into the testserver2k domain.

The next step is to put KIX32.EXE and a clean LOGIN.KIX into the same directory where you already have LOGIN.BAT. Modify LOGIN.BAT to read
code:
%0\..\KIX32 %0\..\LOGIN.KIX
and modify LOGIN.KIX to read
code:
? 'Running Kixtart login script'
Once you get that running, start implementing gradually more complicated scripts.

Finally, if you try to implement our tips from the board, make sure that you type it incorrectly, w.g. I never suggested to use %TESTSERVER2K% but wrote %LOGONSERVER%.

I would also suggest to read the Windows manuals about implementing logon scripts and about command line usage like variable syntax and so on.

[ 01 April 2002, 23:26: Message edited by: sealeopard ]

Bryce
(KiX Supporter)
2002-04-01 11:46 PM
Re: Cannot see custom scripts

quote:

Bryce- I typed in "\\terserver2k\netlogon", when I should have typed "\\testserver2k\scripts" I gor the directory list.
Laurance,

could please post what you got for a directory listing?

and i am a tad bit confused about it being \scripts when it should be \netlogon.

The modular logon script looks for custom scripts in the \\server\netlogon\scripts\ folder.

here is am example of how/where your files should be

quote:

C:\>dir \\server\netlogon /s/b /a-d

\\server\netlogon\config.ini
\\server\netlogon\kix32.exe
\\server\netlogon\Kix_Logon_script.zip
\\server\netlogon\kx16.dll
\\server\netlogon\KX32.dll
\\server\netlogon\KX95.dll
\\server\netlogon\Logon-ReadMe.txt
\\server\netlogon\logon.bat
\\server\netlogon\logon.kix
\\server\netlogon\logon.zip
\\server\netlogon\wkix32.exe
\\server\netlogon\Applications\winset.exe
\\server\netlogon\Functions\Custom_Variables.kix
\\server\netlogon\Functions\kix_functions.kix
\\server\netlogon\Modules\ctrl_c.kix
\\server\netlogon\Modules\Drives.kix
\\server\netlogon\Modules\Legal_Notice.kix
\\server\netlogon\Modules\Module_template.kix
\\server\netlogon\Modules\Other_Scripts.kix
\\server\netlogon\Modules\Path.kix
\\server\netlogon\Modules\pwexpire.kix
\\server\netlogon\Modules\set_clock.kix
\\server\netlogon\Modules\welcome.kix
\\server\netlogon\Scripts\inventory.kix
\\server\netlogon\Scripts\mcafee.kix
\\server\netlogon\Scripts\xmas.kix
if you notice my custom scripts inventory.kix, mcafee.kix and xmas.kix are in the \\server\netlogon\scripts folder.

This is where you need to put your custom scripts if you are using the modular logon script I made.

[ 01 April 2002, 23:49: Message edited by: Bryce ]

lawrence
(Fresh Scripter)
2002-04-01 11:59 PM
Re: Cannot see custom scripts

Bryce - Thank you and everyone else for all of your help. I am going to back off, read up on logon scripts, and reinstall my server(it is a test box)Please close out this posting.

[Cool]

lawrence
(Fresh Scripter)
2002-04-04 06:00 PM
Re: Cannot see custom scripts

Ok now you can close this posting. My scripts are working and I know now where I went wrong. Thanks everyone for all of your help! Life is GOOD! [Razz] I will continue to work with Kix and hopefully get better at using it. I'll be back.

Bryce
(KiX Supporter)
2002-04-04 06:43 PM
Re: Cannot see custom scripts

glad to hear it!

if i may ask for future reference, what was wrong?

Bryce

lawrence
(Fresh Scripter)
2002-04-04 10:46 PM
Re: Cannot see custom scripts

Well... The first thing I did wrong was move the logon share and give it a share name "scripts" when I should have named it "netlogon" then I did not have my custom scripts in my sub folder "scripts", I had them in my sciprt folder with all of the other kix files. But because of the problem I created, I learned more about Kix and W2K. My next challenge is to learn the scripting language (any tips)so I'm not so dependant on modules, I could then be more creative and effective.

-Lawrence [Cool]