Announcement

Collapse
No announcement yet.

Setting up a DFS namespace on a single server (no replication)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Setting up a DFS namespace on a single server (no replication)

    I have been tasked with redoing our file server. The requirement is to setup a dfs namespace . The issue is we have only one file server and i was wondering if it is worth doing if there is no replication being used. Would there still be an advantage?

  • #2
    Yes! The advantages are that you can collect many shares beneath a single namespace - for example, one of our namespaces contains links to 28 shared folders. Secondly, if you need to move your data to a different server or rename your existing one, you simply need to update the info in DFS. This means that your staff don't need to re-map the namespace as once the changes have been made they will not know anything has changed. DFS makes life simpler.
    A recent poll suggests that 6 out of 7 dwarfs are not happy

    Comment


    • #3
      100% agree with Blood. The biggest pain IME of doing file server migrations is the number of shortcuts people have on their desktops pointing to things. Fixing drives assigned by GPO or script is trivial, manual mappings are a PITA and if the name doesn't change then neither does the mapping.

      Having the namespace also allows the later addition of more servers E.g. if you open a branch office.
      BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
      sigpic
      Cruachan's Blog

      Comment


      • #4
        Originally posted by cruachan View Post
        100% agree with Blood. The biggest pain IME of doing file server migrations is the number of shortcuts people have on their desktops pointing to things. Fixing drives assigned by GPO or script is trivial, manual mappings are a PITA and if the name doesn't change then neither does the mapping.

        Having the namespace also allows the later addition of more servers E.g. if you open a branch office.

        What he said.
        Cheers,

        Daniel Petri
        Microsoft Most Valuable Professional - Active Directory Directory Services
        MCSA/E, MCTS, MCITP, MCT

        Comment


        • #5
          Think of DFS Namespace as you are future proofing your environment. The only thing which can be a pain with namespace is if you have a load of namespace folders and you need to make a change to them all. You then need to start thinking about using powershell to make mass updates or it can take a while.

          Comment

          Working...
          X