Re: logon script not working - need hlep
From: John Leonard - Sage (sagegrp_at_adelphia.net)
Date: 12/28/04
- Next message: Bob I: "Re: PASSWORD IN OUTLOOK EXPRESS"
- Previous message: Helen of Joy: "Re: PASSWORD IN OUTLOOK EXPRESS"
- In reply to: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Next in thread: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Reply: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Dec 2004 16:31:56 -0500
Thanks - I found my problem.
I had installed Windows 2003 development tools on the client and it changed
the environment path.
"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:egsDk3B7EHA.2012@TK2MSFTNGP15.phx.gbl...
>
> "John Leonard - Sage" <sagegrp@adelphia.net> wrote in message
> news:uqxYvpB7EHA.4028@TK2MSFTNGP15.phx.gbl...
>> I am trying to use the properties in the Profile of an account. logon
>> script.
>>
>> Having a problem with Net Use with Windows 2003 Server NETLOGON.
>> > >>
>> > >> I share the psdata folder on the server
>> > >>
>> MY bat files are in %windir%\SYSVOL\sysvol\<Domain Name>\scripts.
>>
>> > >> I have roaming profiles (they show up ok) and have setup the logon
>> script as folows:
>> > >> pslogon.bat.
>> > >>
>> > >> My pslogon.bat is: ( located in %windir%\SYSVOL\sysvol\<Domain
>> > >> Name>\scripts.)
>>
>> > >> @echo off
>> > >> net use s: \\gateway\psdata
>> > >> exit
>> > >>
>> > >> I am expecting to see the mapped dive S: on the client, after
>> > >> logon..
>> > >> This will not work?
>> > >>
>>
>> I can see the NETLOGON from the client MY Network ... and from the server
>> using NET SHARE
>>
>> If I run the net use command on the client - it works great.
>>
>> > >> What am I doing wrong???
>
> There are a few things you need to become aware of:
> 1. The physical location of your logon script is not important.
> What matters is that the logon script resides in the "netlogon"
> share of your server. Does it?
> 2. Did you specify pslogon.bat in your users' profiles?
> 3. Placing the "exit" command after the "net use" command is not
> only unnecessary; it also deprives you of any diagnostic feedback.
> A far better way would be to code the script like so during
> the debugging phase:
> @echo off
> echo Starting the logon script
> net use s: \\gateway\psdata
> pause
>
> You will now have plenty of time to watch what's going on.
>
>
>
- Next message: Bob I: "Re: PASSWORD IN OUTLOOK EXPRESS"
- Previous message: Helen of Joy: "Re: PASSWORD IN OUTLOOK EXPRESS"
- In reply to: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Next in thread: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Reply: Pegasus \(MVP\): "Re: logon script not working - need hlep"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|