For some reason when our servers were setup it was decided to setup shared folders and then share the subfolders located within those folders. Is this a good idea? And if not has MS put out any information as to why it may or may not be a good idea?
I agree with lemon13. Shares are really just "shortcuts" to a folder on the server, so just because one happens to be inside another, that shouldn't be an issue.
Thanks,
Andrew
Hard work often pays off over time, but procrastination pays off right now!
The reason I ask is because we are seeing an issue of when a users H: drive maps instead of mapping to \\server\sharename1\sharename2\username as it is setup in the users profile settings it will map to \\server\sharename1\sharename2 or if in the users profile the H: drive mapping is set \\server\sharename2\username the H: dirive will map to \\server\sharename2. Generally a simple logoff and log back on fixes it but sometimes I have to go so far as resetting up the users account.
C:\folder1 is shared as share1
c:\folder1\folder2 is shared as share2
If you want to map an H: drive for sally, you should just use \\servername\share2\sally, not \\servername\share1\share2\sally.
It is ok to use share folders that happen to be inside other shared folders, a share name inside a share name will not work properly, even though it may appear to work properly if your share names are the same as your folder names. If that is the case, the second folder in the path is actually using the folder name, not the share name.
I hope that makes sense.
Thanks,
Andrew
Hard work often pays off over time, but procrastination pays off right now!
Problems will occur in the future if decide to move your file shares off the Windows to a NetApp filer or a NFS share as shares under another aren't supported.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.