Issue when pupils logging in

[faza]

I am having a big issue when pupils are logging. We have a script that connects two network drives. Also within AD Users and Computers we have the H:\ mapped as the home drive. We have a mandatory profile setup %logonserver%\pupils. We also have a printer script that connects the appropriate printer according to the room.

 

The big issue we are having is that some times pupils log in and everything works, they get the correct printer, network drives and home folder. Then the same pupil will login to another machine and lose the network drives or home folder, but he will login to that machine later in the day and everything will work.

 

It is weird i have checked permissions, AD everything

 

Hope you can help

 

faza

[tomscaper]

have you checked the event viewer of when the pupils log in, do any errors come up when trying to run login scripts.

[faza]

No but the strange thing why does it work sometimes and not others. Also the H;\ does not come from a script does it?

[Colditzz]

I would suggest checking your group policy settings relating to how the computer processes the scripts (timings mainly). Check that "wait for network"is set & that scripts are run synchronously... Apologies for the vague information, but I'm away from work atm.

 

Edited: PS, the "wait for network" setting should fix the H:\ issue...

[faza]

I have just tried that Colditzz and it is still doing it.

[Colditzz]

Hmmm, have you tried the RSOP (Start - run - rsop.msc) tool to check that all the GP settings are being applied correctly, I have only come across this issue twice, both times the fix above was the cure...

[faza]

Is it always wait for the network at computer start-up and logon do i need to enable this is that all?

[Colditzz]

Is it always wait for the network at computer start-up and logon do i need to enable this is that all?

Yes, set that/those options. But, also ensure (under the logon scripts section I think) that the run scripts synchronously is enabled. I'm pretty sure that that is the correct name, but not 100%, but if it is wrong, it is very close . Then, wait for fifteen minutes or so and refresh the policy on the workstations, reboot & try again...

[Ric_]

If you use the Group Policy Management Console to check whether group policies are being applied it should shed some light on the subject.

 

As suggested earlier, the event logs on the clients should contain some info too.

 

Also check DNS (use netdiag and dcdiag for this).

[Colditzz]

If you use the Group Policy Management Console to check whether group policies are being applied it should shed some light on the subject.

This is less effective than running rsop.msc on the workstation. Running this on the workstation will show you exactly what is being applied and if not, why not...

[mrforgetful]

If you use the Group Policy Management Console to check whether group policies are being applied it should shed some light on the subject.

This is less effective than running rsop.msc on the workstation. Running this on the workstation will show you exactly what is being applied and if not, why not...

 

As will GPMC...

[Colditzz]

Hmmm, not exactly, it will show what's going on if you select the correct settings, if you have perfect connectivity to the workstations... However, if you run rsop.msc from the workstation when logged in as the correct user, you will get the exact current session information. This is where you are more likely to find the errors. If you find that there are policies not applying that should be, run gpresult from a command line, this will then give you a text based on/off type list for the policies that apply to user & machine.