Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 622
  • Last Modified:

AD integrated DFS

This is more of just an assurance of what i think i know.  So, as of now we deploy msi files via a single server..i.e. \\servername\share.  Clients boot up and should that GPO be applied to an OU where the comptuer account resides, that computer will get the application.  My question is this, since this is a physical server should that server die, even though we add a new server with the exact same name and share location, the application will get intalled again (looking for documentation on this but can't find any).  Now, if we use AD integrated DFS teh path is virtual.  So should a server in the DFS fail, everything will still be groovy.  We just need to add a new server and integrate it with the AD DFS.  No comptuers will get the application installed again.

More to this, is AD integrated DFS is site savy and can load balance.  Just seeing what others are doing and if i understand the benefits of DFS (\\domain.com\share) vs \\servername\share).

Many Thanks
0
esbfern
Asked:
esbfern
1 Solution
 
Joseph DalyCommented:
First I would think that the sever dying and being replaced with another server with the same name and paths etc would not cause the software to be reinstalled. I believe that AD handles all of the software push via GPO. As long as you didnt move the computer out of its existing GPO I would bet that the software policy would not get pushed again.

I would also reccomend doing the DFS method just for the benefits it has. Like you said the DFS path is virutal and if one server dies the others will pick up the slack. Also if you have a distribute network with several sites in different locations the machines will pull from their closest server in the DFS replication. If there is a DFS member server onsite it will go to that one. This should reduce the amount of traffic you are putting over the network.
0
 
AmericomCommented:
You use GPO to deploy the msi files and the \\servername\share is just a path where the GPO can locate the install files.  After GPO applying to client machines, it does not get pushed again simply you the UNC path has refresh. It gets pushed again when you modified/reconfigured/updated/deleted/removed&linked the GPO again. It also get pushed again when you move computer out/in the OU where you applied the GPO to.

It would be best to use DFS name instead of a servername as msi files can be replicated to two or more servers for better redundancy and performance. But for user to be able to install from their local server will require site design.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now