Re: Can I move a UNC share to DFS?
OK, first off we're talking about DFS here. I don't know what CNAMEs
have to do with DFS.
Sammy, theoretically, yes you can use DFS to do what you want.
However, your going to have to make some changes BEFORE you start
moving things around. So the first thing you're going to need to do
is set up a DFS namespace. This is where you'l probably run into your
first problem. Your currently connecting to \\netserver2003\d. It's
giong to be difficult for you to use the current servername in your
namespace. One of the big points to DFS is getting away from directly
addressing servers when connecting to shares. Essentially what your
doing is setting up a share of shares. So you'll need to creat a
namespace with a more generic name. So it'll be something like \
\yourdomainname\Data. Now you have a namespace, you can start linking
actual data shares to that namespace. In this example the d share on
netserver2003 would be linked to \\yourdomain\Data crating a new unc
path \\yourdomain\Data\d. Unfortunately you will have to point all
those other computers to the new DFS path. Once you have that done,
you can set up dfs replication to sync \\netserver2003\d to some other
location. Once that is done you should be able to turn off \
\netserver2003 and your clients will be redirected to wherever the
valid link is.
Bit of a pain to set up initially, but once your there makes moving
data around seamless.
Dean
On Sep 24, 2:36 pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "SammyBar" <sammy...@gmail.com> wrote in message
>
> news:uIjVL4lHJHA.1156@TK2MSFTNGP04.phx.gbl...
>
> > Hi all,
>
> > I have the following problem: I have the following share on a Windows 2003
> > R2 server
> > : \\netserver2003\d
> > Now I need to shutdown the netserver2003 server. It will be susbstituted
> > by a new server with a new name. But I need to preserve the above
> > mentioned share because it is used by many computers.
> > Can Dfs do that?
>
> No.
>
> > For a short time both server will coexists.
>
> ...an even bigger NO.
>
> You create a CNAME in your DNS that uses the Old Name. The CNAME then
> points to the A Record of the "new" Server. The CNAME and the old server
> cannot co-exist at the same time.
>
> What you should have done from the beginning was create a CNAME called
> "fileserver" or something equally generic. Access the resources with the
> "generic" name. If the file server ever gets replaced you just repoint the
> CNAME.
>
> Even if you never use the CNAME you can still use a Shortcut and then rename
> the Shortcut to whatever you want it to be. If the server gets replaced you
> just delete and recreate the Shortcut and name it back to the correct name.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------