#129779 - 2004-11-17 08:33 PM
@UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
first of all, kix rules, keep up the good work! on to the issue at hand ...
we've been having trouble mapping drives recently. it doesn't happen all the time, and usually if the user logs off and logs back on it works fine. the reason they aren't mapping is because the @UserID macro is blank. so our line in the script 'USE H: "\\server\@userid"' is basically being sent as 'USE H: "\\server\'. I know this because I am also opening a file and logging user names to it. the user names comes up blank in the file sometimes. /so far/ it only seems to happen on windows 98 computers logging in to a windows 2000 domain. i've also tried using the @WUserID macro with the same results. we are currently using kix v4.02 and i haven't upgraded because i didn't see anything in the release notes that pertained to this issue.
thanks in advance
-syn
|
|
Top
|
|
|
|
#129782 - 2004-11-17 09:06 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
just a note, we just had it happen on a windows 98 machine logging in to a NT4 domain as well.
thanks
|
|
Top
|
|
|
|
#129783 - 2004-11-17 09:10 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
Quote:
It can also be a timing issue. THat is why it is important to optimize protocols and provider order. Some people have been known to add a SLEEP in the script to give it time. When KiX encounters a macro or function that calls for a round trip to the DC, it does a pre-fetch of several attributes. You might want to force a call very early in the script so that it may be available later.
well the map drive line actually happens very early in the script and all subsequent @UserID calls are still blank.
here is the script: Code:
CALL "script_news.kix"
USE F: "\\ash2\courses" USE G: "\\asd\Warehouse" USE H: "\\ash1\@userid" USE J: "\\ajh2\gqapps" USE K: "\\ash1\abingtonian" USE L: "\\seclib1\data" USE P: "\\seclib1\prog" USE M: "\\ash2\musiclab" USE R: "\\ash2\arithmetic" USE S: "\\ash1\shared" USE T: "\\ash2\teachers" USE Y: "\\asd\SpecialEd" SETTIME "\\AsH1"
CALL "script_run_extra.kix" CALL "script_av.kix"
script_run_extra.kix -- Code:
$SERVER = "ASH1"
IF @ProductType = "Windows XP Professional" $Result=WriteValue("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\CleanupWiz", "NoRun", 1, "REG_DWORD") ENDIF
IF (@ProductType = "Windows 98") IF (@UserID = "") OPEN (1, "\\" + $SERVER + "\login\check\_blankusers.txt", 5) WRITELINE(1, "PC: " + @WKSTA + " -- Operating System Build: " + @BUILD + " -- Date: " + @Date + " @@ " + @Time + @CRLF) CLOSE (1) ENDIF ENDIF
SELECT CASE @ProductType = "Windows 95" GOTO run_it CASE @ProductType = "Windows 98" GOTO run_it CASE @ProductType = "Windows XP Professional" IF EXIST ("C:\Program Files\IBM\Java141\bin\java.exe") MD "%USERPROFILE%\.java" COPY "\\" + $SERVER + "\login\properties141" "%USERPROFILE%\.java\properties141" ENDIF ENDSELECT GOTO end
:run_it shell "\\" + $SERVER + "\login\regedit\update.bat"
:end
|
|
Top
|
|
|
|
#129784 - 2004-11-24 02:09 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
anyone else have any ideas? this happens pretty often for us (this is a log of all the machines for one domain that kix couldn't read the user id):
Code:
PC: ASS4A-1 Operating System Build: 1998 Date: 2004/11/15 @ 07:27:34 PC: AS205-1 Operating System Build: 1998 Date: 2004/11/15 @ 07:33:29 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/15 @ 07:35:32 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/15 @ 09:00:48 PC: ASS101A-2 Operating System Build: 1998 Date: 2004/11/15 @ 09:33:09 PC: AS207-1 Operating System Build: 1998 Date: 2004/11/15 @ 12:34:16 PC: ASS4A-1 Operating System Build: 1998 Date: 2004/11/15 @ 12:48:33 PC: AS110-16 Operating System Build: 1998 Date: 2004/11/15 @ 13:45:04 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/15 @ 13:50:09 PC: ASL4-2 Operating System Build: 2222 Date: 2004/11/15 @ 14:04:09 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/15 @ 14:39:52 PC: ASLIB-25 Operating System Build: 1998 Date: 2004/11/16 @ 07:18:08 PC: ASS4A-1 Operating System Build: 1998 Date: 2004/11/16 @ 07:21:47 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/16 @ 07:24:04 PC: ASLIB-25 Operating System Build: 1998 Date: 2004/11/16 @ 08:19:17 PC: AS139-1 Operating System Build: 2222 Date: 2004/11/16 @ 08:33:27 PC: AS207-1 Operating System Build: 1998 Date: 2004/11/16 @ 09:02:59 PC: ASS101A-2 Operating System Build: 1998 Date: 2004/11/16 @ 09:44:54 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/16 @ 10:26:43 PC: ASS101A-2 Operating System Build: 1998 Date: 2004/11/16 @ 10:30:47 PC: AS205-1 Operating System Build: 1998 Date: 2004/11/16 @ 11:14:22 PC: ASS101A-2 Operating System Build: 1998 Date: 2004/11/16 @ 13:02:53 PC: AS210-1 Operating System Build: 1998 Date: 2004/11/16 @ 14:38:31 PC: ASLIB-6 Operating System Build: 1998 Date: 2004/11/16 @ 14:40:06 PC: AS222-12 Operating System Build: 2222 Date: 2004/11/17 @ 07:33:24 PC: AS110-16 Operating System Build: 1998 Date: 2004/11/17 @ 08:57:41 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/17 @ 09:40:31 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 10:00:16 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/17 @ 10:25:35 PC: ASL4-2 Operating System Build: 2222 Date: 2004/11/17 @ 10:49:32 PC: AS205-1 Operating System Build: 1998 Date: 2004/11/17 @ 10:55:38 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 13:43:48 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/17 @ 13:44:19 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/17 @ 13:50:23 PC: ASLIB-7 Operating System Build: 1998 Date: 2004/11/17 @ 14:40:57 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 14:44:52 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 14:46:03 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 16:27:26 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/17 @ 17:36:21 PC: ASLIB-7 Operating System Build: 1998 Date: 2004/11/18 @ 07:11:13 PC: ASLIB-24 Operating System Build: 1998 Date: 2004/11/18 @ 07:26:32 PC: AS224-17 Operating System Build: 2222 Date: 2004/11/18 @ 09:32:45 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/18 @ 10:16:02 PC: ASL4-2 Operating System Build: 2222 Date: 2004/11/18 @ 10:27:30 PC: ASLIB-25 Operating System Build: 1998 Date: 2004/11/18 @ 10:30:20 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/18 @ 10:31:52 PC: ASP215-3 Operating System Build: 1998 Date: 2004/11/18 @ 11:13:25 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/18 @ 11:45:20 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/18 @ 13:44:39 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/18 @ 13:46:26 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/18 @ 13:52:37 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/18 @ 14:02:59 PC: ASLIB-16 Operating System Build: 1998 Date: 2004/11/18 @ 14:28:43 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/19 @ 07:32:04 PC: ASP215-2 Operating System Build: 2222 Date: 2004/11/19 @ 07:49:12 PC: ASS103-1 Operating System Build: 1998 Date: 2004/11/19 @ 08:03:05 PC: AS240-1 Operating System Build: 1998 Date: 2004/11/19 @ 08:10:31 PC: AS110-25 Operating System Build: 1998 Date: 2004/11/19 @ 08:36:22 PC: ASLIB-27 Operating System Build: 1998 Date: 2004/11/19 @ 08:53:54 PC: ASLIB-3 Operating System Build: 1998 Date: 2004/11/19 @ 12:42:02 PC: AS110-25 Operating System Build: 1998 Date: 2004/11/19 @ 13:45:27 PC: ASLIB-3 Operating System Build: 1998 Date: 2004/11/19 @ 13:49:58 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/19 @ 14:31:20 PC: AS233B-1 Operating System Build: 1998 Date: 2004/11/19 @ 15:29:49 PC: AS233B-1 Operating System Build: 1998 Date: 2004/11/22 @ 06:50:31 PC: AS233B-1 Operating System Build: 1998 Date: 2004/11/22 @ 06:54:23 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/22 @ 07:31:13 PC: AS213-4 Operating System Build: 1998 Date: 2004/11/22 @ 07:43:33 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/22 @ 07:40:29 PC: AS224-17 Operating System Build: 2222 Date: 2004/11/22 @ 09:23:24 PC: AS222-21 Operating System Build: 2222 Date: 2004/11/22 @ 09:33:03 PC: AS213-4 Operating System Build: 1998 Date: 2004/11/22 @ 10:11:14 PC: AS222-24 Operating System Build: 2222 Date: 2004/11/22 @ 10:28:17 PC: ASS102-1 Operating System Build: 1998 Date: 2004/11/22 @ 10:30:41 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/22 @ 11:26:42 PC: AS222-24 Operating System Build: 2222 Date: 2004/11/22 @ 11:58:48 PC: ASP215-2 Operating System Build: 2222 Date: 2004/11/22 @ 12:00:31 PC: AS201-1 Operating System Build: 1998 Date: 2004/11/22 @ 12:47:40 PC: AS250-1 Operating System Build: 2222 Date: 2004/11/22 @ 13:26:12 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/22 @ 13:43:31 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/22 @ 14:33:09 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/22 @ 14:40:26 PC: ASP215-2 Operating System Build: 2222 Date: 2004/11/22 @ 15:21:27 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/23 @ 07:26:58 PC: AS224-17 Operating System Build: 2222 Date: 2004/11/23 @ 08:09:06 PC: AS224-17 Operating System Build: 2222 Date: 2004/11/23 @ 08:33:55 PC: AS110-21 Operating System Build: 1998 Date: 2004/11/23 @ 08:34:08 PC: AS110-25 Operating System Build: 1998 Date: 2004/11/23 @ 08:37:53 PC: AS213-8 Operating System Build: 1998 Date: 2004/11/23 @ 08:43:26 PC: AS249-1 Operating System Build: 1998 Date: 2004/11/23 @ 08:48:55 PC: AS110-18 Operating System Build: 1998 Date: 2004/11/23 @ 09:00:00 PC: AS249-1 Operating System Build: 1998 Date: 2004/11/23 @ 09:01:00 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/23 @ 10:24:01 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/23 @ 10:42:30 PC: AS213-4 Operating System Build: 1998 Date: 2004/11/23 @ 11:12:30 PC: AS201-1 Operating System Build: 1998 Date: 2004/11/23 @ 11:12:48 PC: AS213-17 Operating System Build: 1998 Date: 2004/11/23 @ 11:16:29 PC: AS110-17 Operating System Build: 1998 Date: 2004/11/23 @ 11:17:25 PC: AS222-9 Operating System Build: 2222 Date: 2004/11/23 @ 11:27:37 PC: AS222-9 Operating System Build: 2222 Date: 2004/11/23 @ 11:31:14 PC: AS110-18 Operating System Build: 1998 Date: 2004/11/23 @ 11:43:36 PC: AS249-1 Operating System Build: 1998 Date: 2004/11/23 @ 12:45:47 PC: AS213-11 Operating System Build: 1998 Date: 2004/11/23 @ 12:47:29 PC: AS213-22 Operating System Build: 1998 Date: 2004/11/23 @ 12:52:20 PC: AS222-9 Operating System Build: 2222 Date: 2004/11/23 @ 13:12:08 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/23 @ 15:32:33 PC: AS245-1 Operating System Build: 1998 Date: 2004/11/24 @ 07:26:10 PC: AS213-17 Operating System Build: 1998 Date: 2004/11/24 @ 07:40:29
|
|
Top
|
|
|
|
#129786 - 2004-12-02 07:46 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
Quote:
Hmmm ... and you have done all 3 things Les suggested with his first reply ? The manual (kix2001.doc) will give you instructions on how to accomplish the tasks
three things being... (1) optimize provider order, (2) protocol order, and (3) adding sleep command to script??
i did try adding... "$x = @USERID" SLEEP 5
...at the start of the script and that didn't help. as for the provider order, the kix2001.doc only talked about switching the provider order when using Novell, which we are not. we are seeing this happen on about 40 logons a day just between the two domains we are monitoring.
|
|
Top
|
|
|
|
#129788 - 2004-12-03 04:00 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
I am in the process of setting up the RPC service on our domain controllers but I'm slightly confused by the install procedures--
Currently we do not copy any files to our clients for Kix. All the files are in the netlogon share and we execute kix and the scripts from there. All of the RPC instructions say we need to "install" kx95.dll onto the 9x clients. However, when I was trying to figure where exactly to install that file (wasn't sure if it was windows or system dir) i see a lot of people copying all of the kix files to the local clients and executing kix from there. At the same time, I see a lot of people executing their scripts how we do. The kix installation instruction don't make it clear which method is right or wrong or better or worse. So my questions are ...
a) does the install of kx95.dll just mean the file needs to be placed in the same directory as kix32.dll? We could just place the kx95.dll in the netlogon share and it will work?
b) or should we be copying all of the kix files to the clients and executing from there?
c) or do we just need to copy kx95.dll to the client and continue to execute kix from the netlogon share?
Thanks, matt
|
|
Top
|
|
|
|
#129790 - 2004-12-03 04:10 PM
Re: @UserID empty / blank
|
Howard Bullock
KiX Supporter
   
Registered: 2000-09-15
Posts: 5809
Loc: Harrisburg, PA USA
|
|
|
Top
|
|
|
|
#129791 - 2004-12-03 04:21 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
Quote:
I'm not sure what you mean with not being clear:
Quote:
Installing KiXtart
KiXtart consists of five executable components:
· Kix32.exe, the main program file
· Kx16.dll, a 16-bit DLL used to connect to Netapi.dll on Windows 9x clients
· Kx32.dll, a 32-bit DLL used to connect to Netapi.dll on Windows 9x clients
· Kxrpc.exe, a Windows NT service to support Windows 9x clients
· Kx95.dll, a 32-bit dynamic link library (DLL) used by Windows 9x clients to connect to the KiXtart RPC service
All executable components can be installed on and run from the network or from the local hard disk of the client systems.
ah, i didn't notice the "All executable components can be installed on and run from the network or from the local hard disk of the client systems." line
|
|
Top
|
|
|
|
#129794 - 2004-12-08 07:37 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
Quote:
Copy the KXRPC.EXE file to the System32 folder of a DC and install it as a service as per the manual.
Add a line to your logon.bat to point to the DC with the KXRPC service.
copy KiX32.exe and all the DLLs to the windows folder of the Win9x clients.
Adjust your logon.bat to call KiX from the path instead of from the DC. You can still reference the script in NetLogon.
Make sure that you don't have unnecessary protocols installed on the PCs. Look for IPX/SPX/NetBEUI, etc. If you have additional protocols that are necessary change the binding where you can.
Make sure that there is no other provider that stole top billing. Stuff like IBM Client Access will do that.
HTH
P.S. I hate wintendos and have banned them from my network so am going on memory. If all of the above fails or you need furter help, find someone else to help as I wash my hands of them.
i have updated kix to v4.22, installed the RPC service on both domain controllers, and we are now executing Kix from the client machines themselves. unfortunately the problem still exists . we do have netbeui loaded on all of our machines as well as tcp/ip. is there some way to make tcp/ip override that? here is one of our logon batch files (note none of our machine had kix on them before doing this, that's why im not checking for version and/or overwriting the files on every logon):
Code:
@ECHO OFF CLS if (%OS%) == (Windows_NT) goto NT_XP
:9x SET KXRPC=\\AJH1,\\AJH2 IF EXIST C:\WINDOWS\SYSTEM\KIX32.EXE GOTO skip COPY /Y %0\..\KX16.DLL C:\WINDOWS\SYSTEM >NUL COPY /Y %0\..\KX32.DLL C:\WINDOWS\SYSTEM >NUL COPY /Y %0\..\KX95.DLL C:\WINDOWS\SYSTEM >NUL COPY /Y %0\..\KIX32.EXE C:\WINDOWS\SYSTEM >NUL :skip C:\WINDOWS\SYSTEM\KIX32.EXE %0\..\teacher.kix goto end
:NT_XP kix32.exe teacher.kix
:end
please advise, this problem is rather annoying, heh.
|
|
Top
|
|
|
|
#129796 - 2004-12-08 07:54 PM
Re: @UserID empty / blank
|
syntax53
Fresh Scripter
Registered: 2004-11-17
Posts: 33
Loc: Pennsylvania
|
Quote:
now, the batch looks "cool" going forward, is the only problem still the one descriped in the subject field?
yes, the only problem we have is the @userid returns an empty string.
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
1 registered
(Allen)
and 781 anonymous users online.
|
|
|