Christopher D. Clausen wrote: > Actually, that is pretty much all it is. Its a namespace for CIFS > shares. The replicas work with the File Replication Service (frs) and > can operate even without a domain controller, although most places will > want the data hosted in active directory. The file replication can be > more advanced than one to many replication. Active Directory has a > concept of "sites" and this can be utilized to save data transmission > time over WAN links between branch offices. Group Policy can be used to > point different sets of machines at different servers by default, > failing over to other sites when needed.
With Windows 2003 R2, incremental propagation of replicated data for files and active directory entries can be performed either in real time or in batch modes. The data exchange can either use socket connections or message based transports such as e-mail. This is a major boon for branch offices that have only a small number of machines or are in locations without dedicated high speed networks. The model is last write wins. This is sufficient for many application models. Note that this model makes it impossible to use file locking to protect files from overwrites. This is a conscious decision that is made by the administrator when a share is replicated. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
