login Script not working
Im having a very strange problem where the students login script doesn't get applied to all students despite the batch file being in the user account profile.
It only seems to happen occasionally and not to everyone.
The batch just maps a share to the students shared directory.
During the summer i added a 2008 R2 DC to my existing 2 2003R2 DC's so not sure if this it causing problems.
Has anyone else had the same problems?
Update: sometimes a reboot of the station will work but other times it wont!
Yes, Mine only has 2003 servers. Sometimes the mapping works and sometimes it doesn't - With students it's about 1 in 50 logins , with staff it's about 1 in 10
Same thing, reboot and the first login works OK. Have you got XP SP3 ?
Yes. It seems strange that its only happened after I installed a 2008 r2 dc and I migrated the students home dir and share to 2008 r2 server.
Have you any ideas?
Mine started happening after I moved staff home directories to a new 2003 R2 server
I am running a test today as I had an inspiration this morning ... I'll let you know what happens
I know this may not help but i have recreated the gpo for the students and i will see if thats had an effect.
I have tried:-
Recreating the user account - improves it but doesn't completely fix it
Delete all the users Documents and settings and their application data - doesn't do a whole lot
Use IP addresses in the login scripts instead of names - also doesn't do a lot either
I am now trying sync login scripts and don't detect slow networks
When it doesn't work I just get 'network name could not be found' even if I'm useing IP addresses. A reboot and it works again
Let me know if you get any more ideas please
i dont get any errors just the drive not appearing. I recreated the students GPO and it made things better although i still get the odd on or two that dont get the network drive. Very Strange and doing my head in!!!
In my experience when this sort of thing happens it is a performance issue. It just isn't able to map the drive and the time with everyone logging on. Our old file server was like that and when we upgraded the problem disappeared.
Where exactly are you storing the batch file?
the login script is in windows/sysvol/blah/blah/staff.bat and is replicated around
I think you need to establish if it's an error starting the script, or if it's an issue mapping the drive.
Try re-writing the script to have the first line just dump the current date/time to a text file. You can then check to see if the script runs at all, or if it does and is not mapping the drive for some reason.
An example batch script is:
echo ---------------- >> c:\logs\loginscript.txt
date /t >> c:\logs\loginscript.txt
time /t >> c:\logs\loginscript.txt
net use j: \\someserver\someshare
this outputs a file 'c:\logs\loginscript.txt' looking like:
If you are on a windows 2008 server have a look at this. You can map drive in group policy Group Policy related changes in Windows Server 2008 - Part 3: Introduction to Group Policy Preferences
When you say 'network name could not be found', Is this the batch script causing that error to say the shared drive isn't available or is that windows throwing that error up to say it couldn't find the batch script? I know before i've seen domains getting this error when a dc wasn't correctly removed and the login was trying to run batch script from old dc that is no longer available!
System error 67 The network name could not be found
The batch file is running as the 'echo' I put in and the pause so
I could read the messages are there - it's just my 'net use' bits don't work
Then if I reboot the box it'll work fine ;-(
On the machines that fail to connect to the share, Can they actually ping the server your trying to connect to? Not something like your hitting your max connections on that server?