HY,

1st, we have about 8 pc's in company, most of them on win xp home. Some of
them have to map disk on server every day. How can we make them maped all
the time.

2nd, our server is supposed to copy disk c: to disk which I cant see, so in
case of trouble we just change disk's . If it does do I have to see the
second disk or not, until change?

Hope you understand my Q...

M M-N

Hey,

1. Make the mapping persistent. e.g.:

net use t: \\server\share /persistent:yes

You may need to include the username and password there if they differ
between the workstation and server.

2. It rather depends on what you mean. If you're using a mirrored pair you
won't see the second disk, it works beneath that level.

If you're literally copying files it simply won't work as a C: drive should
you try.

--
Chris Dent
MVP Directory Services


"dudum" <dudum@vip.hr> wrote in message news:g35qm5$ia2$1@ss408.t-com.hr...
> HY,
>
> 1st, we have about 8 pc's in company, most of them on win xp home. Some of
> them have to map disk on server every day. How can we make them maped all
> the time.
>
> 2nd, our server is supposed to copy disk c: to disk which I cant see, so
> in case of trouble we just change disk's . If it does do I have to see the
> second disk or not, until change?
>
> Hope you understand my Q...
>
> M M-N
>

"Chris Dent [MVP]" <chris@highorbit.co.uk> wrote in message
news:O%231wur7zIHA.4040@TK2MSFTNGP04.phx.gbl...
> Hey,
>
> 1. Make the mapping persistent. e.g.:
>
> net use t: \\server\share /persistent:yes
>
> You may need to include the username and password there if they differ
> between the workstation and server.

Put this in a script or?

>
> 2. It rather depends on what you mean. If you're using a mirrored pair you
> won't see the second disk, it works beneath that level.

It supposed to be mirrored

1. Entirely up to you, you can copy and paste it into the run box if you
wish.

The key is the /persistent:yes, it makes the profile (users profile)
remember the connection.

As it's Home edition you wouldn't be able to force it out as a logon script,
but that shouldn't stop you placing it in a batch (.bat) file if that makes
life easier.

2. Excellent. Any change between the disks should be transparrent. Any data
written to the first will be written to the second.

In essence though, you won't ever "see" the second disk as a drive in
Windows. To all intents and purposes it's C: as well.

Of course, if either disk fails you will need to replace it or you lose the
redundancy.

--
Chris Dent
MVP Directory Services

"dudum" <dudum@vip.hr> wrote in message news:g3615d$62i$1@ss408.t-com.hr...
>
> "Chris Dent [MVP]" <chris@highorbit.co.uk> wrote in message
> news:O%231wur7zIHA.4040@TK2MSFTNGP04.phx.gbl...
>> Hey,
>>
>> 1. Make the mapping persistent. e.g.:
>>
>> net use t: \\server\share /persistent:yes
>>
>> You may need to include the username and password there if they differ
>> between the workstation and server.
>
> Put this in a script or?
>
>>
>> 2. It rather depends on what you mean. If you're using a mirrored pair
>> you won't see the second disk, it works beneath that level.
>
> It supposed to be mirrored
>
>
>
>
>