Registered: 2005-06-10
Posts: 9
Loc: Seattle, WA, USA
When I browse Shared Folders/Open Files on the domain controller, I see lots of users that have not released kix32.exe. About half of users in the office. Cannot figure out why. All users are running same OS (Windows 7) and same script - there is only one script for the entire office. THANKS
I've been doing a little eyeball research on this. It appears this is only happening with Window 7 64bit clients. I've seen the kix32.exe file listed in the open files on both Server 2003 DC, and Server 2008 DC, with kix32.exe versions 4.53 and 4.61.
Here are my results so far:
I have access to Vista x32 with Server 2003, but it will be a week or so before I can test it. If anyone has the other environments, please post your results.
We have the same problem since months. The problem is with Startup-/Logon-Scripts from GPO and Logon-Script for Users.
For our students we habe about 300 Win7-64vit PCs, which only use the Startup-Script ( cmd ) which started a KIX-Script. Every mornning we have some PCs which have kix32 opened every time, and othe PCs chaning each day.
But its not a KIXtart-Problem. It must be something like timing or so.
A little more info. The kix32.exe process does not show up in the process list on the computer that is holding the file open on the server.
One office that I checked on the other day, had a number of kix32s open, but now has none. The only thing that has changed is the installation of SP1. Maybe its fixed now. I'll try to do some more confirmation myself, but if anyone else can confirm this, it would be helpful.
I found something new. On 2 DCs I disabled SMB2. Now no open kix32.exe where found. Can this a problem with sm2 function durable_handle? But I didn't find a Reg-Key to disable only this function.
I've not applied any myself. I run a few server 2008 R2 boxes but for applications - not user access stuff and so far I'm not having any of these issues.
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
Aha! No wonder I can't replicate this issue. The first thing I do at any client is set DelayedDesktopSwitchTimeout to zero on every system at build or deploy time.
I do it just because it is annoying as all getout!
Glenn
_________________________ Actually I am a Rocket Scientist!
after more testing. I found that starting from our Netapp-Filer the problem was gone. On the filer the option: cifs.smb2.durable_handle.enable was disabled. After disabling smb2 on DCs kix32.exe also not opened.
From a german AD maillinglist i got the answer to test the following registry key: HKLM\System\CCS\Services\LanmanServer\Parameters Type: REG_DWORD Name: DisableLeasing Value: 1
After setting this key on all DCs tomorrow only 3 PCs ( from 300 ) holds kix32 open.