Share a mapped drive

[Samson]

Right here's the situation.

The county council wont fund more HD space to be installed into our curriculum server, nor do I have the nescessary skills to add it to the existing RAID array.

Im getting the long-overdrawn task of putting all installations onto the network done, and there isnt enough space on the server to do it.

So I'm making use of 70gb worth of free space on the mailserver, but this is only going to confuse people.

What im wondering is, if I map the //dhmail/Shares/Installs folder to drive I: on dhserve (the server) can I then share drive I: so that when it comes to installing, I can browse to \\dhserve\i$

Yay? Nay?

Thanks in advance.

[StewartKnight]

yes that should work, if you share a drive, you will be able to create a map to it.

[BKGarry]

Can i just ask, what is wrong with using //DHMAIL/Installs$?

[Samson]

yes that should work, if you share a drive, you will be able to create a map to it.

Other way round, I want to share a mapped drive

Can i just ask, what is wrong with using //DHMAIL/Installs$?

Continuity, everything else is //DHSERVE/<whatever>

Continuity and simplicity for the end user really, theres nothing wrong with using //DHMAIL, but its easier to know everyhting is //DHSERVE

[apeo]

Use DFS maybe? That way your users wont know any change has been made regardless of what you change in the background.