grjitdept
asked on
Domain login script not working for one user
Hi,
We have a network of XP machines, Win 2003 servers. We have a general vb login script setup in group policy that maps drives and printers. We've had no problems with it until recently it stopped working for one particular user, that is, the drives not longer mapped, so we assume it's stopped working. For other users on same machine it's no problem, it's just this one user. The script wasn't changed and we're at a loss to explain why it's jsut this one user.
What sort of error logging is available for vb login scripts that might point us to the cause. It does seem to be user specific - any ideas?
Fairly urgent so 500 points.
Thanks
We have a network of XP machines, Win 2003 servers. We have a general vb login script setup in group policy that maps drives and printers. We've had no problems with it until recently it stopped working for one particular user, that is, the drives not longer mapped, so we assume it's stopped working. For other users on same machine it's no problem, it's just this one user. The script wasn't changed and we're at a loss to explain why it's jsut this one user.
What sort of error logging is available for vb login scripts that might point us to the cause. It does seem to be user specific - any ideas?
Fairly urgent so 500 points.
Thanks
Check to see if this User is added to the Local Administrators of that machine..
ASKER
oriziv
- I know it's not a computer thing as other users on that same machine do not have the problem
- I've even tried other users in the same OU and it works for them as well
- I've run GP result, and nothing strange there - it's inherting all policies
- tips to how to create a log file? Actually I should mention that we have the parameter 'Resume on error' set in our login script, so it generally continues even if there is a problem...
speshalyst
- The user is not a local admin, but then neither are any of our other users or the test users I tried on the same machine...
- I know it's not a computer thing as other users on that same machine do not have the problem
- I've even tried other users in the same OU and it works for them as well
- I've run GP result, and nothing strange there - it's inherting all policies
- tips to how to create a log file? Actually I should mention that we have the parameter 'Resume on error' set in our login script, so it generally continues even if there is a problem...
speshalyst
- The user is not a local admin, but then neither are any of our other users or the test users I tried on the same machine...
Do all tasks of the script fail, or it just doesn't run period? Explain how this is run, does it pop up a box or is it run in silent mode, etc. Is drive mappings failing but printers working?
Is it a permissions issue for the user to the drives being mapped? double check the users NTFS permissions with those users that are working. If the user does not have permission to the drive, it will fail. Not sure how your NTFS permissions are set, but are they a member of the security groups they need to belong to?
Is it a permissions issue for the user to the drives being mapped? double check the users NTFS permissions with those users that are working. If the user does not have permission to the drive, it will fail. Not sure how your NTFS permissions are set, but are they a member of the security groups they need to belong to?
ASKER
Good question - I will check if the printers are mapped but not the drives...
The user is however definitely has permissions and is a member of the correct groups. In fact, our temporary solution has been to give her a copy of the script which she simply runs MANUALLY everytime she logs on! When she runs it manually it runs straight away no problem and all works...
The user is however definitely has permissions and is a member of the correct groups. In fact, our temporary solution has been to give her a copy of the script which she simply runs MANUALLY everytime she logs on! When she runs it manually it runs straight away no problem and all works...
What happens if this user login to a different PC?
ASKER
excellent question - I'll try now...
ASKER
OK I tried the user on a different machine and the script worked fine on that machine!
So we seem to have a problem with ONE user ONLY on ONE machine where the vbs login script is failing to run properly...
So we seem to have a problem with ONE user ONLY on ONE machine where the vbs login script is failing to run properly...
What happens if you login as admin and rename their existing profile on that machine? (c:\documents and settings\username) Next time they log in it will create a new profile, maybe the script will work then? If not you can always rename the old one back and you've lost nothing! if it works you can just copy the documents, wallpaper etc from the old profile.
I agree with robstacey.
It should work
It should work
ASKER
OK I'll try that - it's a roaming profile though so any corruption my be copied down from the server... having said that it did work on other machines so maybe this could be the cure - will try and let you know!
ASKER
Right I've done a lot of testing this lunchtime....
I renamed the cached local profile so a new copy was downloaded from the server, and no difference, the script still didn't run...
I tried other users on the same machine, the script does run
I checked the printers mapped by the script and they wern't mapped either, so it's almost as if the script just isn't running at all. How could I make it log or flag when it runs to see what stage, if any, it gets to before failing?
I renamed the cached local profile so a new copy was downloaded from the server, and no difference, the script still didn't run...
I tried other users on the same machine, the script does run
I checked the printers mapped by the script and they wern't mapped either, so it's almost as if the script just isn't running at all. How could I make it log or flag when it runs to see what stage, if any, it gets to before failing?
Hmmm, OK, that user's rights on that machine.. the same as everyone else?
ASKER
Yes, they are a domain user just like everyone else
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Well I gave up in the end and resorted to simply renaming the roaming profile local and server copies. Got the user to log in again which forced the creation of a new profile. Checked that the drives mapped OK (they did). Copied back files and set settings as required. Check drives still mapped (they did). So a strange one - something obviously got corrupted or 'stuck' somewhere. I'll keep this question open for a while in case anyone can suggest a cause, but rebuilding the profile was the eventual fix, albeit a slightly heavyhanded one!
before you do that try few easyer options:
1. Make sure the user and computer located in an OU not in a container
2. Make sure there is no block inheritance for the user's OU
3. Try to disconnect the machine for you domain and then re-register it