Mapped network drive always requires user login after reboot

We have 1 server that is a domain controller/exchange server that has some
folders that need to be shared for client access. I setup a mapped network
drive to this shared folder on a windows vista client computer and set it to
auto login each time he reboots with the admin credentials. However each
time he reboots it requires him to manually put in the admin user name and
PW. How do we get around this problem without joining his computer to the
domain? We obviously don’t want to give out the admin login info to every
user and they are hesitant to add them to the domain because they take there
laptops home each night and don’t want any problems with there internet at
home.

dath <dath@discussions.microsoft.com> wrote:
> We have 1 server that is a domain controller/exchange server that has
> some folders that need to be shared for client access. I setup a
> mapped network drive to this shared folder on a windows vista client
> computer and set it to auto login each time he reboots with the admin
> credentials. However each time he reboots it requires him to
> manually put in the admin user name and PW. How do we get around
> this problem without joining his computer to the domain? We
> obviously don't want to give out the admin login info to every user
> and they are hesitant to add them to the domain because they take
> there laptops home each night and don't want any problems with there
> internet at home.

Questions/comments -

Why is the user connecting using administrative credentials to map the
drive? Can't this folder be accessed by a non-admin user account in the
domain? This doesn't sound like an ideal setup.....

You can set up a domain account & password that matches the local
workstation credentials and they ought to be passed through (I'm not a Vista
person, note).

I'd use a login script on the desktop rather than telling Windows to map the
drive automatically - have the user run it manually when they're in the
office.

net use x: \\server\share /persistent:no


All that said, I would recommend that *all* your users' computers be joined
to the domain - and use login scripts, group policy, to manage them. Their
internet access at home shouldn't be disrupted by this, but honestly, if
these are company owned computers, they should be locked down sufficiently
that the users can't (in)advertently make any systems changes or install
software.

"Lanwench [MVP - Exchange]" wrote:

> dath <dath@discussions.microsoft.com> wrote:
> > We have 1 server that is a domain controller/exchange server that has
> > some folders that need to be shared for client access. I setup a
> > mapped network drive to this shared folder on a windows vista client
> > computer and set it to auto login each time he reboots with the admin
> > credentials. However each time he reboots it requires him to
> > manually put in the admin user name and PW. How do we get around
> > this problem without joining his computer to the domain? We
> > obviously don't want to give out the admin login info to every user
> > and they are hesitant to add them to the domain because they take
> > there laptops home each night and don't want any problems with there
> > internet at home.
>
> Questions/comments -
>
> Why is the user connecting using administrative credentials to map the
> drive? Can't this folder be accessed by a non-admin user account in the
> domain? This doesn't sound like an ideal setup.....
>
> You can set up a domain account & password that matches the local
> workstation credentials and they ought to be passed through (I'm not a Vista
> person, note).
>
> I'd use a login script on the desktop rather than telling Windows to map the
> drive automatically - have the user run it manually when they're in the
> office.
>
> net use x: \\server\share /persistent:no
>
>
> All that said, I would recommend that *all* your users' computers be joined
> to the domain - and use login scripts, group policy, to manage them. Their
> internet access at home shouldn't be disrupted by this, but honestly, if
> these are company owned computers, they should be locked down sufficiently
> that the users can't (in)advertently make any systems changes or install
> software.
>
>
>
The problem is that he does not want to join the domain he is the owner of
the company so he just wants the mapped drive to work without logging in each
time. Why would you use a script when you can just setup a shortcut on his
desktop to the mapped drive?

Are there any vista experts out there that have had experience with setting
up a user on the DC with the same name and pw as the user on a laptop that is
not part of the domain? I know I could do this with my 2000 network and XP
but I dont want to show up at his office only to find out it wont pass
through using Vista.

dath <dath@discussions.microsoft.com> wrote:
> "Lanwench [MVP - Exchange]" wrote:
>
>> dath <dath@discussions.microsoft.com> wrote:
>>> We have 1 server that is a domain controller/exchange server that
>>> has some folders that need to be shared for client access. I setup
>>> a mapped network drive to this shared folder on a windows vista
>>> client computer and set it to auto login each time he reboots with
>>> the admin credentials. However each time he reboots it requires
>>> him to manually put in the admin user name and PW. How do we get
>>> around this problem without joining his computer to the domain? We
>>> obviously don't want to give out the admin login info to every user
>>> and they are hesitant to add them to the domain because they take
>>> there laptops home each night and don't want any problems with there
>>> internet at home.
>>
>> Questions/comments -
>>
>> Why is the user connecting using administrative credentials to map
>> the drive? Can't this folder be accessed by a non-admin user account
>> in the domain? This doesn't sound like an ideal setup.....
>>
>> You can set up a domain account & password that matches the local
>> workstation credentials and they ought to be passed through (I'm not
>> a Vista person, note).
>>
>> I'd use a login script on the desktop rather than telling Windows to
>> map the drive automatically - have the user run it manually when
>> they're in the office.
>>
>> net use x: \\server\share /persistent:no
>>
>>
>> All that said, I would recommend that *all* your users' computers be
>> joined to the domain - and use login scripts, group policy, to
>> manage them. Their internet access at home shouldn't be disrupted by
>> this, but honestly, if these are company owned computers, they
>> should be locked down sufficiently that the users can't
>> (in)advertently make any systems changes or install software.
>>
>>
>>
> The problem is that he does not want to join the domain he is the
> owner of the company

I understand what you're talking about - but I tell business owners "no" all
the time when they have dumb requests. And they still call me to do work for
them.

> so he just wants the mapped drive to work
> without logging in each time.

And I want a pony. :)


> Why would you use a script when you
> can just setup a shortcut on his desktop to the mapped drive?

Because he shouldn't have it try to maintain a persistent connection. What
about when he's not at work? What if you move a share or add a server?

You haven't explained why he's using any sort of administrative
credentials - maybe I'm not following....
>
> Are there any vista experts out there that have had experience with
> setting up a user on the DC with the same name and pw as the user on
> a laptop that is not part of the domain? I know I could do this with
> my 2000 network and XP but I dont want to show up at his office only
> to find out it wont pass through using Vista.

I don't use Vista (ptui!) so I can't advise you there, sorry.