I am deploying Vista64 and have a kix logon script. When a user logs on the script runs but does not map drives. What is wierd is that if you manually run the script after they logon it will map the drives.
USE X: "\\$SITEFS1\corp" USE Y: "\\$SITEFS1\data"
I have displayed the error codes and it returns a 0 but no mapped drive. seems to work fine on Vista32 and XP It also works most of the time logged on as a domain admin. I have tried version 4.6 and 4.53 Any suggestions? Anyone else come across this?
If i use a net use command in the script it will map correctly too I would just prefer using the Kix command
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
About 70% of my workstation environment is x64 w/ Vista and I haven't run into the problem. I can run a simple test when I get back to the office later today and tell you what I find.
Glenn
_________________________ Actually I am a Rocket Scientist!
The problem only occurs running the logon with the group policy. If after I log on as the user I run the logon script it will map all of the drives correctly! Thanks for replying!
For anyone else that may have this issues. The issue has to do with the UAC and permissions. Microsoft has a script to delay running the logon script allowing it to run with the proper security token. In the following artical look for launchapp.wsf. I have tested this and it is working for me. Although i did have to comment out a few lines so it would run without user interaction.
but sadly, this issue was found way before vista RTM (around the time I tested it) and has never got fixed. I think that proves, not even microsoft wants organizations using vista. it's ment for home users who don't care that much of the slowness of the computer, etc.
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
Oh - one thing.. I do configure my Vista systems with a reg hack, but don't think it's related. It simply sets the delay of the graphic login screen to 0 seconds. Without that hack, the login script runs behind the Windows logo image, which is usually displayed for 30 seconds. The login script runs in 2-3 seconds so I don't see it work without setting the screen delay to 0.
Glenn
_________________________ Actually I am a Rocket Scientist!