You can simply put it in the user's Startup folder.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"David" <(E-Mail Removed)> wrote in message
news:FAFB9DBE-A563-400F-8706-(E-Mail Removed)...
> That's what I had thought. But with W2K3 in WG mode, where do I put logon
> scripts? All the examples assume to use Group Policy, etc...
>
> DT
>
> "Doug Sherman [MVP]" wrote:
>
> > The conventional way is to simply create a user account on SRVB called
USERA
> > with the same password used for the corresponding account on SRVA. If
you
> > really want to map the drive using an account other than the logged on
user,
> > create a logon script:
> >
> > net use x: \\SRVB\sharename /user:SRVB\USERB password <enter>
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "David" <(E-Mail Removed)> wrote in message
> > news:348C8A05-745B-4368-9ADE-(E-Mail Removed)...
> > > I have two W2K3 servers SRVA and SRVB, both running in Workgroup mode,
in
> > > different Workgroups WGA and WGB respectively.
> > >
> > > USERA on SRVA maps drive X to a share on SRVB, checks "Reconnect at
Logon"
> > > and specifies to login as a different userid. Gets prompt for userid
and
> > > password, enters USERB (defined on SRVB) and password, and the drive
is
> > > then mapped and accessible.
> > >
> > > When USERA logs off/on, drive X appears to get mapped, but when the
drive
> > is
> > > accessed, the user is again prompted for userid and password.
> > >
> > > How can I prevent the need to supply the userid and password on first
> > access
> > > after a login?
> > >
> > > Would putting both servers in the same Workgroup help?
> > >
> > > This is a really pressing problem, and any help would be
appreciated...
> > >
> > > DT
> >
> >
> >
|