I will be deploying two servers at two different offices (80 Mbps dedicated\nconnectivity between offices). Both server builds are identical (Dell head\nservers and DAS enclosures) and will be installed with "Storage Server 2003\nR2 SP2 64-bit". These will be used purely for storing user folders (~1500\nusers) which will be configured in Active Directory (Home Folder drive\nletter) for each user. The directory structure on the server will be simple:\n\nE:\USERS\username\ (USERS will be the shared folder with each username\nrestricted by NTFS so only the user, SYSTEM and administrator accounts have\naccess to his/her own folder).\n\nThe plan is for "Server_A" to be the main server and "Server_B" to be the\nbackup server in the event of a primary failure. We plan to use the updated\nDFS included with R2 to replicate the Users folder data to Server_B. In the\nevent of a failure users would fail over to Server_B (using DFS namespaces).\n\nSome questions I hope you folks may be able to answer for me regarding\nDFS-R:\n\n1) Are there any issues with using VSS and DFS together? Will the VSS data\nbe replicated across to "Server_B" as well and would VSS need to be enabled\non this server also?\n\n2) Is it possible to use Single Instance Storage (SIS -natively available in\nStorage Server 2003 R2) with DFS? If it does the common store (in the root\ndir) need to get replicated across or do you simply enable SIS on the second\nserver as well?\n\n3) Would it be better to configure DFS to replicate the "Users" folder or\nthe actual root drive "E:\" as it will only be used for the users folders?\n\n4) Do the NTFS and share settings get replicated across also (I assume so)?\n\n5) I will be implementing quotas on the user folders using the "File Server\nResource Manager" in R2. How would these Quotas be affected with DFS at the\ntarget server? Would they get carried over or would they need to be manually\nset on Server_B?\n\n6) All clients will be Windows XP SP2, so is it recommended to use the\n"Client failback" hotfix [WindowsXP-KB898900-v2-x86-ENU.exe\n([URL]http://go.microsoft.com/fwlink/?LinkId=53202[/URL])] so that user computers can\nrevert back to the original server once it is back online?\n\n7) In the event that Server_A is down and users are accessing and editing\ntheir files on Server_B, what happens when Server_A comes back online and\nclients revert back to it? The files they have edited on Server_B would not\nbe available on Server_A since it was down when the files were changed My\ninitial plan was for DFS to replicate one way, from Server_A to Server_B but\ntaking this situation into consideration I realize this strategy is not\nsufficent. What is the recommended way to implement DFS Replication in this\ncase?\n\n8) If I add Server_A and Server_B to the same namespace, can I ensure that\nusers only go to "Server_A" to access files (given that it is up and\navailable)?\n\n*note: our DCs are running Server 2003 SP1but I made the necessary AD schema\nupdate (adprep.exe /forestprep) to support the update R2 version of DFS\n\nAppreciate any feedback or advice that any of you may be able to offer on\nthe above questions. Thanks very much.