kix script not running all the time

[kubasa]

Hi everyone,

 

I have been working on a problem with Microsoft since about October of 2007 and I've pretty much given up that I will get it solved so I'm turning to you all for suggestions.

 

Here's the problem. Our students (10,000+) logon and some students find out that they are missing their mapped drives and/or printers and/or homepage setting. This happens to about 5 - 10 students per site (21 sites) per day. If you do the math, this isn't happening to that many students percentage-wise but it is very annoying and frustrating for students and staff. As a part of the logon process, we setup a Group Policy that calls out a bat file that runs the kix script that assigns mappings, printer and homepages based on group memberships. There aren't any problems with the kix script or it wouldn't work for anyone.

 

All of our students use mandatory profiles. We have 4 domain controllers running W2K3SP2. The kix executable, kix config file and bat files resides in the netlogon share that is replicated amonst all 4 domain controllers. The mandatory profile also resides in the netlogon share. The last bit of information is that the workstations are XPSP2 and the workstation are all Dell Optiplex 260-755 models.

 

Again, I've been working with Microsoft on this issue since last October. If anyone has any ideas, I would be very grateful. Thanks in advance for any ideas.

[craiglay]

Windows implementing a slow logon? Whats the network infrastructure like? Could it be overloading?

 

Try a solution like a super mandotary profile that will log the user off if the profile cannot be properly loaded.

 

Craig

[MkII]

Welcome kubasa

 

Big question!

 

Have you any evidence like errors produced on the bad logons?

 

A break in communication can cause some GPOs to not apply is all I can think. 5 sites per server - what's the geographical spread/ network quality like?

 

Don't suppose you can list the blind alleys you've already found?

[GlennT]

How many DC's are we talking about?

How many DNS servers?

Definately look at network traffic for bottlenecks. I presume this happens at the busiest times?

Seem to recall there is a "wait for network" registry fix that we applied here to solve a similar problem.

[boomam]

Whats that fix called? Ive been told about that fix in the past, but could never find it?

[GlennT]

Erm.... rummaging through notes....

 

Pretty sure it was this.....

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

"TcpTimedWaitDelay"=dword:00000300

 

Save as "whatever.reg"

[srochford]

Is the logon script running in a visible window? A problem we used to have when we used a logon script similar to yours was that people would think logon was slow, not know what the command window was for and just close it - leading to random drives not being mapped.

 

The other thing you could do is add some debugging logic to the script so it writes a log of the steps it's following - if you then have a failure you can try and find out if the script is not running at all or failing at a particular point. One of the things which I *think* we sometimes have is that if a server is busy, it won't respond to the mapping request quickly enough and so it fails.

 

Another thing you could try is:

 

attempts=1
do
 Map drive
 attempts=attempts + 1
loop until drive mapped or attempts > 3

- choose a number to suit. It obviously slows down even a "good" logon a bit (but it wouldn't be horrendous) and might help to fix the odd problems

[JamesC]

Is there anything at all in the event log on the clients that this is happening with?

[GlennT]

Is the logon script running in a visible window? A problem we used to have when we used a logon script similar to yours was that people would think logon was slow, not know what the command window was for and just close it - leading to random drives not being mapped.

 

If it's Kixtart, you can add "Break On" to stop them closing the script window.

[boomam]

Erm.... rummaging through notes....

 

Pretty sure it was this.....

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

"TcpTimedWaitDelay"=dword:00000300

 

Save as "whatever.reg"

 

Thanks.

I'll have a play with that when i get the time. .

[sahmeepee]

I would be tempted to make the batch and kix files both do some basic logging in the short term to see if either or both are running at all. I suspect that if they sometimes get some, but not all, settings set then the kix script is running for everyone.

 

In kix, you can run an action and assign the return code to a variable. I think the syntax is:

 

$ErrCodeDefPrint=SetDefaultPrinter($strPrinter)

You can also write events to the Windows event log, so you could follow each line as above with something like:

 

$ErrCodeDefPrint = "Default printer mapping result: " + $ErrCodeDefPrint
$RC = LogEvent(4,1004,$ErrCodeDefPrint,'KiXtart')

 

You can use this dll to make the events a bit easier to read, but it should work ok without.

 

Then you just need to examine the event viewer for an affected session to see what failed and how.

[kubasa]

Hello and thanks for all the replies. I was out of town and unable to check what suggestions had been made. In any case, the problem has been resolved. The problem was with one of our 5 domain controllers. When students would login and authenticate against this particular domain controller, it wouldn't run the kixscript for whatever reason. Everything appears fine and there were no errors on the DC but when we shut it off and then just let the other 4 take over, we didn't have any errors. It seems pretty obvious now (after the fact....). Again, thanks for all of the suggestions.