(Starting to like KiXtart)

2009-09-04 03:30 PM

Windows 7 and Kixtart scripts?

I just joined my Windows 7 Pro RTM to our Windows 2003 domain and logged in. Looks like the drive mappings don't work. What's the new syntax for mapping drive letters in Windows 7?

(KiX Supporter)

2009-09-04 04:25 PM

Re: Windows 7 and Kixtart scripts?

there is no new syntax

(KiX Supporter)

2009-09-04 05:01 PM

Re: Windows 7 and Kixtart scripts?

You got stuff like UAC disabled? Do your scripts run synch-ed? Is the Always wait for network setting set?

Al three of these can cause massive headaches when troubleshooting the things that should be "simple and easy".

To get you a little out of the woods just put the code below after each attempt to map a drive and run the script. This will display any errors that occurred while trying to map a drive.

Code:

?@error
?@serror

Administrator

(KiX Master)

2009-09-04 08:04 PM

Re: Windows 7 and Kixtart scripts?

Probably the INGROUP issue that I replied to on another post in beta that it was not working for me either. Then Ruud asked him to run some other test and it came back that the system is not trusted as I recall. I've not really looked further at mine as it's still RC1 and I don't use it enough to worry about it. It does seem to work for most of the rest of my script though.

(Just in Town)

2009-10-24 02:15 PM

Re: Windows 7 and Kixtart scripts?

I have the same situation with a new installed Windows 7 Professional.
All our WinXP and WinVista are running the login correctly. But on our new Win7 it doesn`t work.

-- snip --

Code:

MessageBox ("Willkommen bei"+chr(9)+": "+"C/S/G"+chr(10)+ chr(10)+
"Datum"+chr(9)+chr(9)+": "+@day+" "+@mdayno+" "+@month+" "+@year+chr(10)+
"Zeit"+chr(9)+chr(9)+": "+@time+chr(10)+ chr(10)+
"User ID"+chr(9)+chr(9)+": "+@userid+chr(10)+
"Privileges"+chr(9)+chr(9)+": "+@priv+chr(10)+ chr(10)+
"Prozessor"+chr(9)+chr(9)+": "+@CPU+chr(10)+ chr(10)+
"Speed"+chr(9)+chr(9)+": "+@MHZ+" MHz"+chr(10)+
"Speicher"+chr(9)+chr(9)+": "+MemorySize()+" MB"+chr(10)+ chr(10)+
"OS-Name"+chr(9)+chr(9)+": "+@PRODUCTTYPE+chr(10)+
"OS-Version"+chr(9)+": "+@dos+chr(10)+ chr(10)+
"Terminal-Session"+chr(9)+": "+$TS+chr(10)+
"Domain"+chr(9)+chr(9)+": "+@domain+chr(10)+
"Logon Server"+chr(9)+": "+@lserver+chr(9)+chr(9)+chr(10)+
"Computername"+chr(9)+": "+@wksta+chr(10)+
"Node adress"+chr(9)+": "+@address+chr(10)+chr(10)+
$greeting, "Anmelde Information", 4160, 10)

	; *********************************
	; * Laufwerke Client mappen Anfang
	; *********************************

	use * /Delete
	
	IF @TSSESSION <> 1

		if ingroup("Mapping_R_Exchange-Archive")
			use R: "\\SERVER\Exchange-Archive"
		endif

-- snip --

Messagebox appears. TSSESSION is not 1. It works on all the other installations of WinXP and WinVista with the same user. tried for debugging to change the servername with the IP, but it`s not working too.

If I start the script manually from Win 7 and not via ActiveDirectory-Login it works fine.

Any ideas?

Administrator

(KiX Supporter)

2009-10-25 04:13 AM

Re: Windows 7 and Kixtart scripts?

Please provide more information.

What version of Kix?
What is the @serror after the failed mapping?
Are there any errors in the Eventlog?
Is this a logon script or GPO Script?

(Just in Town)

2009-11-11 06:33 AM

Re: Windows 7 and Kixtart scripts?

I can second that. Kix script that has worked for years, can't map drives during logon on Windows 7. It goes through the routine like it worked, but in Explorer or CMD, the drive are not there. When the script is manually ran after login, the mapped drives shows up.

Kix 4.6 and 4.61
Windows 7 x64 Pro 6.1.7600
Windows 2003 AD

My script looks like this, which works fine for XP SP3

Quote:

cls
?
?
color w+/n
? "Default Domain GPO Logon Script"
?
sleep 5
?
color w/n
use x: "\\wind-dvr\photos"
? @error
? @serror
if @error = 0
? "Drive X mapped for Photos"
endif
use y: /d
use y: "\\wind-dvr\mp3data"
? @error
? @serror
if @error = 0
? "Drive Y mapped of MP3s"
endif
use list
?
sleep 20

and the output looks like this:

Quote:

Default Domain GPO Logon Script

0
The operation completed successfully.
Drive X mapped for Photos
0
The operation completed successfully.
Drive Y mapped of MP3s
Current redirections :

X: --> \\wind-dvr\photos
Y: --> \\wind-dvr\mp3data

This kix script is started off in my OU's GPO, by a CMD file that looks like this:

Quote:

@echo off
%logonserver%\netlogon\kix\kix32.exe %logonserver%\sysvol\dxb.lan\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\USER\Scripts\Logon\default.kix
rem net use x: \\wind-dvr\photos
rem net use y: \\wind-dvr\mp3data

(I rem-ed out the two "net use" lines. They were added once I discovered that the kix script was no longer mapping my x: and y: drive. They work. I rem-ed them out to retest the kix script.)

Administrator

(KiX Supporter)

2009-11-11 08:12 AM

Re: Windows 7 and Kixtart scripts?

See if the following Reg Setting fixes your problem.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLinkedConnections =(dword)1

(Just in Town)

2009-11-14 06:28 AM

Re: Windows 7 and Kixtart scripts?

Yup, that fixed it. Thanks. Since I skipped Vista and when right to W7, I missed all the information on access token. Guess it's time to dive into learning all the in's and out's of the new platform.

Thanks for the help.

(Fresh Scripter)

2009-11-19 08:47 PM

Re: Windows 7 and Kixtart scripts?

Kudos Allen, the EnableLinkedConnections registry entry worked for me as well. Do you know what is causing this issue? Or am I going to have to apply this to all of my win7 boxes?

Running win7 with 2008/2003 mixed domain.

thanks for your help

$\:\)$ this reg fix also allows InGroup to function as desired

Administrator

(KiX Supporter)

2009-11-19 10:43 PM

Re: Windows 7 and Kixtart scripts?

If you are running a GPO script, I believe you will have to do this on any computer with the UAC(Vista and Windows 7) enabled.

Couldn't this reg fix be applied pretty quickly with a gpo?

(Fresh Scripter)

2009-11-19 10:58 PM

Re: Windows 7 and Kixtart scripts?

Yes, not a problem with applying the fix with GPO. Thanks for answering my question about why we needed to add the entry. I just need to determine if we want to disable the UAC or use the reg fix.

thanks again