You can store install images on another server (not a Windows Deployment Services server) using DFS and still install the images by using Windows Deployment Services. Using DFS for install images provides two main benefits:

• Load balancing. Clients can be directed to computers other than the Windows Deployment Services server to download the image.
  
  
• Simplified administration. When you use DFS replication technology, you can modify images on a single server and propagate changes to other distribution points.
  
  

	Note
	You cannot redirect the boot directory (that is, \\<server>\reminst\boot) using DFS. If you do, Windows Deployment Services will not start.

To configure DFS namespaces for install images:

1. Install and configure Windows Deployment Services.

2. Install the DFS role service from the File Services server role in Server Manager. For more information about DFS, see Distributed File System (http://go.microsoft.com/fwlink/?LinkId=108012)

3. Create a file share on a secondary server. Grant permissions to the Windows Deployment Services server’s computer account. For example, if the server is called MyWDSServer, grant read/write permissions to MyWDSServer$.

4. Create a new namespace in DFS Management. For example, \\fileserver\MyNamespace for a stand-alone namespace or \\corp.woodgrovebank.com\MyNamespace for a domain-based namespace.

5. Add a new folder to the namespace and create an image group on the Windows Deployment Services server as the target folder. For example, create \\MyServerOrDomain\MyNamespace\ImageGroup in DFS Namespaces, and specify \\MyWDSServer\RemoteInstall\images\DFSImageGroupName as a target folder for that folder.

6. Add images to the Windows Deployment Services server.

7. Verify that the content appears when you connect to \\MyServerOrDomain\MyNamespace\ImageGroup.

8. Repeat this procedure for additional image groups.

DFS Replication is a server technology that you can use to replicate images between Windows Deployment Services servers. DFS Replication can decrease the total cost of ownership by making it possible for you to manage images from a single server in the environment. Changes can then be propagated to other servers without requiring interaction. A best practice is to create a single, master Windows Deployment Services server that clients do not connect to. Make all modifications to images on this server by using the Windows Deployment Services management tools and the image maintenance tools included in the Windows AIK. Next, replicate changes from this server to other servers in the topology. To prevent replication conflicts, avoid modifying or servicing the same image from multiple servers at the same time.

For more information, see Distributed File System Replication: Frequently Asked Questions (http://go.microsoft.com/fwlink/?LinkId=111023).

To configure DFS Replication for install images:

1. Install and configure Windows Deployment Services.

2. Install the DFS role service from the File Services server role in Server Manager. For more information, see Distributed File Systems Step-By-Step Guide (http://go.microsoft.com/fwlink/?LinkID=111021)

3. Create and configure a replication group for the RemoteInstall folder or its subfolders. If you are replicating RemoteInstall subfolders, you must exclude the \Mgmt and \Tmp folders. These folders contain server-specific information that cannot be used by remote Windows Deployment Services servers.

4. Configure the BCD refresh policy by running the following command (see below for details about the options): WDSUTIL /set-server /BcdRefreshPolicy /Enabled:yes /RefreshPeriod:<time in minutes>