Re: Mapping a drive automatically
- From: Ann <Ann@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Jan 2009 10:00:00 -0800
I think I got what you're saying. Just use net use with UNCs to get to the
server and then move the file over.
"Lanwench [MVP - Exchange]" wrote:
Ann <Ann@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
I have a need to map a drive between two servers, one is in a domain
the other is not. I also would like the drives to map if the server
gets rebooted but no one logs into it.
Here's what I've done so far.
I've created a .bat file with the appropriate net use commands. I've
scheduled a task to execute that batch file on system startup. Once
I reboot the server the drives never map. I check the Scheduler log
and it shows an exit status of 2.
The batch file will process and map the drives if I use other options
through Scheduler.
Is there a way to have the drives map without actually logging in to
the server?
Drive mappings are for the convenience of people, not computers. For
computers to communicate, you need to use UNC paths. Why do you think you
need to use a mapped drive? If you are going to set it up in the batch file,
a) you will need to run the scheduled task with a domain account and b) you
will need to specify credentials in the batch file.
- Follow-Ups:
- Re: Mapping a drive automatically
- From: Lanwench [MVP - Exchange]
- Re: Mapping a drive automatically
- References:
- Mapping a drive automatically
- From: Ann
- Re: Mapping a drive automatically
- From: Lanwench [MVP - Exchange]
- Mapping a drive automatically
- Prev by Date: Testing future dated processing using system clock, resets too soo
- Next by Date: Re: Mapping a drive automatically
- Previous by thread: Re: Mapping a drive automatically
- Next by thread: Re: Mapping a drive automatically
- Index(es):
Relevant Pages
|