login Script not working

[techie08]

Hi

 

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?

 

Many Thanks

[techie08]

Update: sometimes a reboot of the station will work but other times it wont!

[interele]

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 ?

[techie08]

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?

[interele]

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

 

M

[techie08]

I know this may not help but i have recreated the gpo for the students and i will see if thats had an effect.

[interele]

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

 

Ta

 

M

[techie08]

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!!!

[ChrisH]

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?

[interele]

the login script is in windows/sysvol/blah/blah/staff.bat and is replicated around

[lukeod]

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:

 

md c:\logs

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:

 

----------------

Mon 13/09/2010

01:59 PM

Edited September 13, 2010 by lukeod

[ricki]

HI

 

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

 

Richard

[Azhibberd]

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!

[interele]

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 ;-(

 

M

[Azhibberd]

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?

[interele]

Once you have logged in you can surf, ping and connect drives to your hearts content !

It's just the net use in the login script

 

M

[interele]

No, I take that back. If I try and map a drive once the failure has occurs it say my workstation service isn't running. Looking in the services shows it as stopped

 

What's killing it I wonder

 

M

[techie08]

I know you moved your home dirs to a new server like i did but have you run the latest microsoft updates on the machines? we did in the summer and im wondering if this may be something to do with it? I may be barking up the wrong tree!!! Im going to reboot my 3 DCs in half an hour and ill see if that has any effect.

 

Ive also notice today that sometimes even a restart of the station doesn't sort it. it may even take about 4 or 5 restarts!!

[interele]

Don't bother restarting your servers - I did that Friday and it made no difference

 

I am now 99.9% certain it's the workstation service falling over

I just don't know why - It could be set to just restart it but that

wouldn't explain why

 

We are doing some new images with SP2, SP3 from the CD and SP2 upgraded to SP3

It only started after we started using the SP3 install disk rather than using the SP2

install disk and running the update

 

M

[techie08]

with mine the workstation service is running but just isnt running the script!

[Azhibberd]

You say the workstation service is falling over, Is there anything in the event logs to show this? Never had this problem before tbh with you, And Techie "isnt running the script!" Does your batch script run then? Just can't find the correct Network share? Its not the firewall on the new server is it?

[techie08]

It appears that the batch script for the students just doesn't run all the time. Ive tried the suggestion to alter the script to log an entry in C:\log but nothing appears.

 

Ive also made sure windows firewall was off on the new file server and it is.

[Azhibberd]

Are you using one of the replicated areas? Is so are you sure replication is working accross everywhere fine? i know one problem we hit once was that we enabled software restrictions to disallow all apart from a white list and the new server hadn't been added to the students white list

[interele]

The workstation service seems to die quietly. I've been through the event log and there is nothing. If I log in and out repeatedly ( sometimes it takes 20-30 )

goes everything work fine then on the next login I get system error 67 and the services show that the workstation isn't running any more

 

I could just set it to restart on failure ( which works ) but it wouldn't get to the bottom of the issue and it would takes ages ( unless you know

a way of pushing that change out via group policies )

 

M

[techie08]

Ive tried 3 student logins on a pc and one of the student login always fails to apply the login script, so i think our situation may be user related. So the next thing im going to try is recreating the problem account.