Re: SBS2003 rename a share

however, I do not believe KJ is proposing either moving or copying the data.

A folder (say D:\) on a server (say SBS) can have multiple shared names (say "D Drive" _and_ "DDRIVE", or maybe just "D"). You don't actually copy or move anything, you simply assign the folder a 2nd share name (and maybe different share level permissions).

People accessing \\SBS\D Drive would in fact be accessing the exact same files as people accessing \\SBS\DDRIVE, or \\SBS\D.

You then change your drive mapping GPO:
from "M: = \\SBS\D Drive"
to "M: = \\SBS\DDRIVE"

and while people continue to be able to use the 'old' method of access until GP updates (or if you don't wish to use GP you can do it manually, possibly via either startup or login script) they eventually move to the new name without realising it (or so the theory goes :-).

From the server you can then see if anyone is accessing the share via the
old name and when you are sure the old name is no longer in use it can be removed.

"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message news:Ois4QWafJHA.5244@xxxxxxxxxxxxxxxxxxxxxxx
Liam wrote:
Thanks KJ,

I will try that one.

if I move data to a new folder does it retain permissions or is it
with a copy that it retains permissions.

Different methods give different results. ie, moving to same disk, or different disk, and how permission inheritance is configured.

http://support.microsoft.com/kb/310316



They want to redesign their data tree....

"kj [SBS MVP]" wrote:

Liam wrote:
I inherited a system where the main data share is called "D Drive".

The space is casuing me some grief when I try to map it in scripts
and on Sharepoint.

So, I would like to rename it but I am not sure of the consequences
of doing that.

Any insight?

Liam

Probably the easiest and safest is to just create another (2nd)
share for the same directory using the same permissions except name
it "DDrive" or whatever you want. Then begin chaning all the
mappings in your login scripts, etc. When you no longer observe any
connections to the old share then you can just delet the old share
and everyone will be using the new share name.



--
/kj

--
/kj


.

Relevant Pages

  • Re: SBS2003 rename a share
    ... I don't think the restructure of the file system was mentioned up ... A folder on a server can have multiple shared ... share name (and maybe different share level permissions). ... possibly via either startup or login script) they ...
    (microsoft.public.windows.server.sbs)
  • Re: File access rights in Windows Server 2003
    ... > When I am moving files among servers, I usually create a backup files with ... > process will also restore a file and folder permissions. ...
    (microsoft.public.windows.server.security)
  • Re: file sharing and permission on xp Pro?
    ... > Here are the basic rules when copying vs moving files on NTFS partitions: ... > of the file or folder takes on the permissions of the destination. ...
    (microsoft.public.windowsxp.network_web)
  • Re: SBS2003 rename a share
    ... The only thing I saw wrong with the whole things was 'sharing a root folder'. ... you simply assign the folder a 2nd share name (and maybe different share level permissions). ... and while people continue to be able to use the 'old' method of access until GP updates (or if you don't wish to use GP you can do it manually, possibly via either startup or login script) they eventually move to the new name without realising it. ... From the server you can then see if anyone is accessing the share via the old name and when you are sure the old name is no longer in use it can be removed. ...
    (microsoft.public.windows.server.sbs)
  • Re: trust issues when connecting a member server
    ... When i look at the NTFS settings all setting are for domain ... permissions, if the program needs to write to that directory (or sub ... permission in that folder, attempt to create and save a simple text file ... The shares comes as a part of a login script, ...
    (microsoft.public.windows.server.sbs)
Quantcast