(Fresh Scripter)

2014-02-03 04:59 PM

kix32.exe 4.63 and Windows 8.1 - script doesn't run

I have been using Kixtart for about 5 years. It has worked great with Windows XP and Windows 7. My login.kix file is called from logon.cmd and I use it to map drives, printers, and run a few other programs.

I updated to version 4.63 since I have a few Windows 8 computers. The script does not appear to run on these Windows 8 computers when the users log in using their domain credentials. However, after they are logged in, I can go to the SYSVOL share and run the logon.cmd manually (which calls the kix32.exe) and the script runs and does everything correctly.

What is the issue? Is it because the Windows 8 computers (both are Surface Pro 2 tablets) boot up so fast?

Glenn Barnas Administrator

Administrator

(KiX Supporter)

2014-02-03 05:42 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Question - do you not SEE the script run, or does it not map the drives?

I deployed a Windows 8.1 Pro workstation this weekend and our login script runs as always. I did set the DelayedDesktopSwitchTimeout value on the workstation to Zero, though.. our script runs fast - 4-5 seconds - and the timeout of 30 seconds was both annoyingly slow and blocked the login script from running visibly during login.

We're running Kix 4.62 - I can verify 4.63 tonight.

The boot time is generally not an issue - things happen in a specific sequence.. BUT!!!
It's possible that you are not defining the Wait for Network at Startup setting in GPO.

This delays the presentation of the login screen until the workstation can see AD when connected to a domain network. With the setting disabled, the computer can log you in with cached credentials, and login scripts and GPOs will not run at that time. The net effect of enabling this setting is a few second delay between BOOT and the display of the C-A-D login screen. This issue is usually only seen after a computer cold boot because the login can be made available before all networking is initialized. A cold boot will fail but a logoff/logon will usually work properly if this setting is not defined and the cause of the problem.

Glenn

(Fresh Scripter)

2014-02-03 05:50 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Glenn, thanks for the reply.

I know the script is not running on the Windows 8 computers, because it doesn't map the drives, the printers, or run the few programs I have setup.

However, after login, if I browse to SYSVOL and run the logon.cmd batch file, a command prompt window will pop up and the script is run because the drives get mapped, etc.

Yes, I have had the Wait for Network setting enabled in GPO for many years.

Administrator

(KiX Supporter)

2014-02-03 06:04 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I have 4.63 running at all my customer locations. They have a mix of XP, Win7, Win8, and Win8.1. No problems with the logon script.

I was going to suggest making sure the Wait for Network GPO is enabled, but it sounds like you have it.

Is this a traditional logon script or GPO startup script?

(Fresh Scripter)

2014-02-03 07:35 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Allen - sorry, I guess I'm not sure what you mean by traditional vs GPO startup.

But, here is an excerpt:

Code:

;if user is a DHHS Employee, then map drives and printers
IF INGROUP("Dhhs Employee")

	;If DHHS user doesn't have a P: Drive, make one
	IF NOT EXIST("\\fileserver\dhhs\users\%USERNAME%")
		MD "\\fileserver\dhhs\users\%USERNAME%\"
	ENDIF

	;Map Network Drives that all DHHS users get
	USE H: /DELETE /PERSISTENT
	USE N: /DELETE /PERSISTENT
	USE P: /DELETE /PERSISTENT		
	USE H: "\\fileserver\dhhs\apps" /PERSISTENT
	USE N: "\\fileserver\dhhs\common" /PERSISTENT
	USE P: "\\fileserver\dhhs\users\%USERNAME%" /PERSISTENT

	;Map Specific Network Drives and Printers Based upon DHHS AD Groups
	SELECT	
		
		;Map for Corporation Counsel
		CASE INGROUP("CorpCounUsers")

			IF NOT PRIMAPSTATE("\\trouble\econdev-hp")
				ADDPRINTERCONNECTION("\\trouble\econdev-hp")
				SETDEFAULTPRINTER("\\trouble\econdev-hp")
			ENDIF

			IF NOT PRIMAPSTATE("\\trouble\econdev-ricoh")
				ADDPRINTERCONNECTION("\\trouble\econdev-ricoh")
			ENDIF			

		;Map for ADRC
        	CASE INGROUP("ADRCusers")

			IF NOT PRIMAPSTATE("\\trouble\adrc-mfp")
				ADDPRINTERCONNECTION("\\trouble\adrc-mfp")
				SETDEFAULTPRINTER("\\trouble\adrc-mfp")
			ENDIF

			IF NOT PRIMAPSTATE("\\trouble\adrc-hp")
				ADDPRINTERCONNECTION("\\trouble\adrc-hp")
			ENDIF

(Fresh Scripter)

2014-02-03 07:37 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

And in my logon.cmd file, this is what calls kix program:

@echo off
\\DOMAIN\netlogon\kix32.exe \\DOMAIN\netlogon\login.kix

-----where DOMAIN is replaced with my domain name

Administrator

(KiX Supporter)

2014-02-03 07:48 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I stand corrected... still using 4.62. I have not tested 4.63 in those environments. I'm actually waiting for 4.64 to come out of beta and I was going to use that.

Do you have a @producttype statement in your script? There is a bug in 4.63 that causes it to display the wrong info.

(Fresh Scripter)

2014-02-03 10:56 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Okay, thanks. No, I don't use the @producttype statement.

I'm really at a loss at this point. I'm hoping it is something simple or stupid, but again, everything works perfectly fine with Windows XP or Windows 7 clients. It is only with the Window 8 client where it doesn't work.

Administrator

(KiX Master)

2014-02-04 02:48 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I don't have any Windows 8.1 in production but I do know that there are quite a few applications that work in Windows 8 that do not work in 8.1 - MS made quite a few more security changes under the hood that seem to lock out some programs that don't do things the approved MS way I'm guessing.

(Fresh Scripter)

2014-02-04 05:07 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Would UAC being ON or OFF matter one way or the other in regards to the script not running?

Administrator

(KiX Supporter)

2014-02-04 05:09 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Just for grins have you tried a different version of kix and/or with a very simple script?

(Fresh Scripter)

2014-02-05 03:21 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Yes, I was originally running version 4.60 with Window 8 when the script wouldn't run, so that is why I upgraded to 4.63.

In my Windows 2008 R2 group policy, I enabled the wait time for login script to 50 seconds, and I am waiting to test that out.

Administrator

(KiX Supporter)

2014-02-05 03:23 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Just to make sure we are talking about the same GPO, see

http://www.kixtart.org/forums/ubbthreads.php?ubb=showflat&Number=112428#Post112428

(Fresh Scripter)

2014-02-05 04:22 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Allen - yes, I have had the "Always wait for the network at computer startup and logon" enabled for years.

Then, just yesterday, I found out there was another policy called "Startup policy processing wait time" under Computer Configuration\Administrative Templates\System\Group Policy node. I set it to 50 seconds for testing.

Even with these 2 settings enabled in GPO, the Windows 8 tablet still does not run the script. However, after tablet is logged into domain with user and I goto desktop, I can immediately browse to SYSVOL and run the logon.cmd and the script runs perfectly.

Also, I can confirm UAC enable/disable had no effect.

Administrator

(KiX Supporter)

2014-02-05 04:49 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Anything in the the Eventviewer?

Administrator

(KiX Master Guru)

2014-02-05 05:36 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

hmm... is your "mydomain" part of local intranet?

(Fresh Scripter)

2014-02-05 05:55 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Yes, my domain is local. I will check out Event Viewer for clues. Also, I just found out you can run the command "rsop.msc" at command prompt to see which group policy settings have been applied on a client, so I'll check that out, too.

I believe my domain and DNS are set up correctly, because Windows XP and Windows 7 clients have no issues with login script.

Glenn Barnas Administrator

Administrator

(KiX Supporter)

2014-02-05 06:04 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I have the office all to myself today due to the snow, ice, sleet, and other frozen concoctions. I'll push 4.63 up and try the Windows 8 and 8.1 systems this afternoon.

Glenn

(Fresh Scripter)

2014-02-05 09:47 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I'm having sort of the same issue running on Windows 8.1, everything runs fine on Windows 7.

"WKIX32.EXE - Entry Point Not Found"
The Procedure entry point RtlConvertUiListToApiList could not be located in the dynamic link library \\<domain controller>\netlogon\NETAPI32.dll

This is running WKIX32.exe directly from the DC, When I modified the batch file to copy the wkix32.exe and .kix file to the C Drive on the Win8.1 machine and then run, it was working.

Anyone seen this issue before?

Thanks in advance!

Administrator

(KiX Master Guru)

2014-02-05 09:59 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

when you say you copy to c-drive, where in c-drive you copy the executable?

I am even further thinking this is an issue of trust. your unc is not recognized as local intranet zone and thus gets blocked. might be way of this, but nobody has checked on this yet.

Glenn Barnas Administrator

Administrator

(KiX Supporter)

2014-02-05 11:08 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

OK - I updated Kix to 4.63 on the netlogon share..

Code:

Windows 7     - works
Windows 8     - works
Windows 8.1   - works
Server 2008   - works
Server 2008r2 - works
Server 2012   - works

I'll be able to test Server 2012r2 in the next couple of days.

This is calling the login script in the user profile as "kix32.exe kixtart.kix". The Kix script is our Universal Login Script. The ULS default display shows the version of Kix and the version of the script, so I can confirm that it is running 4.63. Everything runs from the Netlogon share.

I tested the Windows 8.1 preview system and saw the script run just as the banner telling me that my eval period had expired and the system would reboot in 1 hour.. $;\)$

So - it does not appear to specifically be a Kix issue.

I do set the DelayedDesktopSwitchTimeout value to 0 on all systems so I can see the scripts run. I don't know that I have anything too special in the GPOs. I am using Kix32 and not WKix32.

Glenn

Administrator

(KiX Master Guru)

2014-02-05 11:14 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

you are not pointing to an UNC path when calling kixtart and the script.
this is a difference worth noting.

Administrator

(KiX Supporter)

2014-02-06 12:14 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

I have a batch file called logon.bat and it contains a unc path to the kix32.exe and to the script. So my config should be very similar to the original poster. Only difference is, mine works and his doesn't.

(Fresh Scripter)

2014-02-06 03:44 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Originally Posted By: Lonkero

when you say you copy to c-drive, where in c-drive you copy the executable?

I am even further thinking this is an issue of trust. your unc is not recognized as local intranet zone and thus gets blocked. might be way of this, but nobody has checked on this yet.

in the batch file i just run a copy command that copies the exe and the .kix file to a folder on the C drive from the DC. where might the trust setting be on windows 8.1?

(Fresh Scripter)

2014-02-06 03:47 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Originally Posted By: Allen

I have a batch file called logon.bat and it contains a unc path to the kix32.exe and to the script. So my config should be very similar to the original poster. Only difference is, mine works and his doesn't.

i'm running the same thing, a logon.bat file that points to the netlogon on the DC, but i'm getting the error i posted above for Windows 8.1, but not for Windows 8 or Windows 7.

btw, i'm running Windows 8.1 Enterprise x64 on a Server 2012 DC.

it works on Windows 7 Enterprise x64 and Windows 8 Pro.

Administrator

(KiX Master Guru)

2014-02-06 04:29 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

alka, in your case I would look do you even have NETAPI32.dll

Administrator

(KiX Supporter)

2014-02-06 05:28 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Quote:

in the batch file i just run a copy command that copies the exe and the .kix file to a folder on the C drive from the DC. where might the trust setting be on windows 8.1?

Have you verified that this is happening correctly? Curious why you bother with copying to the local machine anyway?

(Fresh Scripter)

2014-02-06 05:49 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Originally Posted By: Lonkero

alka, in your case I would look do you even have NETAPI32.dll

there is a NETAPI32.dll file located in the netlogon folder. however, it seems to be a older version. can anyone tell me which version of NETAPI32.dll i should have?

it would work fine for Windows 8 Pro, and Windows 7, but not Windows 8.1

(Fresh Scripter)

2014-02-06 05:52 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Originally Posted By: Allen

Quote:

in the batch file i just run a copy command that copies the exe and the .kix file to a folder on the C drive from the DC. where might the trust setting be on windows 8.1?

Have you verified that this is happening correctly? Curious why you bother with copying to the local machine anyway?

running the wkix32.exe directly from the DCs using a UNC path causes that error i posted above, but changing the logon.bat file and having the kix32.exe copy to the c drive first and then running it, works. now, it could be the version of NETAPI32.dll i have on the dc. just bothers me that it works on Windows 8 pro and Windows 7 without any issues.

Administrator

(KiX Supporter)

2014-02-06 06:01 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Well... my next logical question is... why is the NETAPI32.dll in the netlogon directory? Have you tried just renaming the file to see if the problem corrects itself? In my logon folders I have nothing but the kix32.exe and the scripts.

Also of note, I do not use wkix.exe.

I'm not sure how this relates, but here is a (very old) thread that shows what Kix is looking for in terms of DLLs. http://www.kixtart.org/forums/ubbthreads.php?ubb=showflat&Number=96858#Post96858. I have never once added these files to a machine, so obviously they are part of a standard Windows release.

Administrator

(KiX Master Guru)

2014-02-07 05:26 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

removing that fixed it. :P

I do wonder too, why the file was copied there in the first place...

Administrator

(KiX Supporter)

2014-02-07 05:33 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Sadly... neither poster has come back to post their results. $\:\($

Administrator

(KiX Master Guru)

2014-02-07 11:31 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

too embarrassed?

(Fresh Scripter)

2014-02-08 04:14 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Allen and Lonkero - I think kixtart is working correctly. I believe my issue is now figuring out how to get wireless devices like laptop and tablets to make valid network connection before the domain user logs in.

In Event Viewer, on the Windows 8 tablet, I am seeing errors for "no domain logon servers available" - so that points to the wireless connection not being ready and connected before the user logs in. That also explains why the kixtart script can be run manually after login, since the wireless connection is then established.

Administrator

(KiX Supporter)

2014-02-08 04:20 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Good to know. Thanks for the update.

I have seen some wireless nics that do reconnect with no issues and some that do not. I think it really depends on the vendor and their drivers. Also, I have seen where the default drivers MS uses have less features than the manufacturers, so you might try updating the drivers if you have a stock Windows loaded.

(Fresh Scripter)

2014-02-08 04:26 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Allen - yes, I have found a few sites with info referring to accessing the advanced setting of wireless adapter and enabling Single Sign-on and other such settings, but my HP laptops with Windows 7 64-bit and Qualcomm Atheros drivers did not have those settings.

I have also seen a forum post where you can create a registry value in the Current Version\Run key to auto-connect wireless immediately, but that didn't work either.

I did look for updated drivers, but didn't find any yet. Any other suggestions.

Thanks for all the help.

Administrator

(KiX Master Guru)

2014-02-08 04:57 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

using the manufacturer supplied drivers usually brake stuff.
specially the linksys, zyxel and alike never work with them. uninstalling the bloatware and only installing the bare minimum driver and letting windows wireless zero configuration take care of the connectivity almost always fixes these issues.

Administrator

(KiX Supporter)

2014-02-08 05:08 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Yeah, I saw that post about adding the registry setting and running a profile. Too bad that doesn't work. Here is the only other one I found that might be useful.

http://answers.microsoft.com/en-us/windo...a9-0985de5da483

(Fresh Scripter)

2014-02-09 12:05 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Allen - okay, thanks, I hadn't see that webpage before. Unfortunately, the poster mentions changing encryption to WPA2-Personal to fix his problem, which is what I already use.

Also, he mentions having his Windows 7 computers set to All Users wireless profile or whatever, which I'm pretty sure I have set on my Win7 laptops, but I'm still having network connectivity problems before users login to domain.

I'm using HP ProBook 4540s laptops, Surface Pro 2 tablets, and Ubiquity Unifi Long Range wireless access points.

Administrator

(KiX Master Guru)

2014-02-09 01:08 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

oh and note about "Then, just yesterday, I found out there was another policy called "Startup policy processing wait time" under Computer Configuration\Administrative Templates\System\Group Policy node. I set it to 50 seconds for testing."

this is longer by default.
if you actually use start up scripts or if your logonscript actually does something important, setting it to something realistic like 10 minutes would be advisable. I have even had environments where the timeout has been disabled.

(Fresh Scripter)

2014-02-09 02:26 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Lonkero - I believe I read the default for that policy is 30 seconds. Either way, I think my GPO and login script is just fine, now. I just have to solve the "make sure the wireless connection is active before logging into domain" issue.

Administrator

(KiX Master Guru)

2014-02-09 05:50 AM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

uhm... you are correct. had something else in mind there.

(Fresh Scripter)

2014-02-10 02:21 PM

Re: kix32.exe 4.63 and Windows 8.1 - script doesn't run

Originally Posted By: Lonkero

removing that fixed it. :P

I do wonder too, why the file was copied there in the first place...

Sorry for the late reply, i don't have a test environment and i had to make sure that nothing else was using the NETAPI32.DLL in the netlogon folder. I went ahead and renamed that DLL in the netlogon folder to .OLD and it looks like KIX32.exe is working now. I'm not sure why that .dll is in there. We've upgraded the DCs over the last decades starting from Windows 2000 Server to Server 2012, and I was only around for the last 2 DC upgrades.

Thanks for all the help.