Re: Logon scripts can't access network home drive

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Jessica,
unless you are using Loopback Group Policy processing, settings under User
Configuration node in the GPO are not relevant if you link it to the OU
containing computer objects - so I assume that this is the reason for the
behavior you are describing.
Can you clarify how you create user home drive mapping? While this can be
done via logon script, a more common approach (at least based on my
experience) involves specifying drive letter and path as part of user's AD
object attributes (Profile tab of the user's account Properties dialog box
in ADUC). Is there a particular reason that you decided to use logon script
instead?
I'm also not clear on what exactly you want to accomplish via your logoff
script - but, as with logon script, that's part of the user configuration
node, so you would need to apply it to the OU containing user accounts or
use Loopback Group Policy (but keep in mind that in such case, logon/logoff
scripts will apply to all users who log on to/logoff from these computers).

hth
Marcin

"Jessica Hamilton" <JessicaHamilton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:DDF9BFE9-F6B3-4E51-97B1-A5836BED65F3@xxxxxxxxxxxxxxxx
Hi,

I have a problem trying to set up user logon/logoff scripts using GPO.

I'm using the User Cfg > Windows Settings > Logon/Logoff scripts settings,
and putting my scripts in here.

The problem is that the user's home drive doesn't appear to be mapped
during
the logon script, and the logoff scripts that access the home drive don't
seem to work either (though my diagnostics said the home drive was
mapped).

My GPO is attached to OU containing computer objects, as our team does not
have access rights to attach GPOs to user containers, and the GPO is
computer
specific, rather than user specific.

Also, we're using a profile management tool that redirects the user
profile
to a custom profile on the local machine, so I'm not sure if this has
anything to do with it.

If I set the logon scripts to use the Administrative Settings > System >
Logon to launch the script, it then has access to the home drive.

However, this doesn't resolve the issue with the logoff script, and
there's
no System > Logoff option like there is with the Logon one.

How do I resolve this? I thought the home drive should be mapped before
the
logon/logoff scripts run....

Oh, the clients are Windows XP SP2 clients in a Windows 2003 AD domain.

Thanks,

Jessica


.

Relevant Pages

  • Re: Applying Computer Settings Slow
    ... try to not apply the script or any other gpo with different settings, I don't believe in some kind of magic, so you probably are running some tool gpo or script that is affecting the user's logon. ... >>> default domain policy does not have any configuration changes. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Disabling a GPO logon Script
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... you can easily jump out of the script by ... But a GPO would be nicer. ... disable it by not specifying a logon script? ...
    (microsoft.public.windows.terminal_services)
  • Re: Disabling a GPO logon Script
    ... you can easily jump out of the script by ... MCSE, CCEA, Microsoft MVP - Terminal Server ... disable it by not specifying a logon script? ... GPO, and to which OU the GPO is linked. ...
    (microsoft.public.windows.terminal_services)
  • Re: Install Windows Patch via GPO
    ... I did gpresult on the PCs and the GPO is showing up now. ... Browse when you want to add a new script or put the ... only reply to Newsgroups ... Ethernet adapter Local Area Connection 1: ...
    (microsoft.public.windows.group_policy)
  • Re: GPOs not applying
    ... > settings for both user and computer configuration. ... >> I have a two deep OU structure with one GPO per OU. ... >> Folder redirection, which is crucial as my start menus, ... >> are mapped despite there being a script which does this. ...
    (microsoft.public.win2000.group_policy)