"Richth" <Ric***@discussions.microsoft.com> wrote in message
news:AB232E4A-8821-4FC0-A263-F82C0DB228C5@microsoft.com...
> On Win2003 Srvr assigning a login script via Group Policy that maps a
> drive
> as follows:
>
> Set objNetwork = CreateObject("WScript.Network")
> objNetwork.MapNetworkDrive "M:" , "\\srvr1\mt4"
>
> To assign I do the following:
> 1. Right-click on container and choose "Create and link a GPO here..."
> 2. Give name "mapdrive" and press OK.
> 3. Right-click "mapdrive" GPO object and choose Edit.
> 4. Navigate to UserConfiguration->WindowsSettings->Scripts->Logon
> 5. In Logon Properties click Add, then click Browse and navigate to
> srvr1.local\scripts and choose "mapdrive.vbs" file, then OK out.  (The
> script
> is located in the \\srvr1\netlogon\scripts folder.)
>
> Am I assigning the login script correctly?
> The container is a list of users
>
> Need ideas on what to do to figure out why the script is not running
> during
> login for users.  If I run the script from the Run cmd line while logged
> in
> as the user, the script runs perfectly.
>
> Rich

"Jeremy" wrote:

> Login to a windows XP workstation with one of the users who is should be
> getting the script and run RSOP.msc
>
> This will show you the resultant set of policy.  This will confirm that the
> user should be running the policy.
>
> Policy processing wont run scripts if a slow link is detected.
> Scripts might run but might not do what you want if the "Always wait for the
> network before logon" isn't set to Enabled.
>
> Basically Windows doesn't care what the result of a logon script is, it just
> runs it and moves on, so if the script fails and doesn't perform its own
> error handling then you will never know what is going on.
>
> Since Windows is woefully inadequate when it comes to logging problems with
> policy processing (especially scripts), then I suggest that you add another
> script to the same policy that is a simply CMD script that spits out some
> output into a log file.  Something like this:
>
> date /t > "%TEMP%\logon.log"
> time /t > "%TEMP%\logon.log
>
> Ever since I have been using AD I have had different sites where logon
> scripts intermittently didn't run and it has been typically difficult to
> troubleshoot.  At one site I even gave up an moved the command to "Run this
> Command after logon"  In the Administrative templates part of the GPO.
>
> Cheers,
> Jeremy.
>
> "Richth" <Ric***@discussions.microsoft.com> wrote in message
> news:AB232E4A-8821-4FC0-A263-F82C0DB228C5@microsoft.com...
> > On Win2003 Srvr assigning a login script via Group Policy that maps a
> > drive
> > as follows:
> >
> > Set objNetwork = CreateObject("WScript.Network")
> > objNetwork.MapNetworkDrive "M:" , "\\srvr1\mt4"
> >
> > To assign I do the following:
> > 1. Right-click on container and choose "Create and link a GPO here..."
> > 2. Give name "mapdrive" and press OK.
> > 3. Right-click "mapdrive" GPO object and choose Edit.
> > 4. Navigate to UserConfiguration->WindowsSettings->Scripts->Logon
> > 5. In Logon Properties click Add, then click Browse and navigate to
> > srvr1.local\scripts and choose "mapdrive.vbs" file, then OK out.  (The
> > script
> > is located in the \\srvr1\netlogon\scripts folder.)
> >
> > Am I assigning the login script correctly?
> > The container is a list of users
> >
> > Need ideas on what to do to figure out why the script is not running
> > during
> > login for users.  If I run the script from the Run cmd line while logged
> > in
> > as the user, the script runs perfectly.
> >
> > Rich
>