Roaming user profiles seems like such a good idea at first, but it causes a myriad of problems in practice. One of these problems stems from the fact that the master copy of each profile is stored on a central file share. That file share needs to be accessible over a fast connection from all machines a user is logging on to, or logons tend to become very slow. This proximity requirement is easy to meet if only one site is involved, but what if users roam between different locations, or if terminal servers are distributed across several data centers? Unfortunately, there is no easy answer to this question.
Filtered articles: "Replication"
Filtered articles: "Replication"
Replicating User Profiles Between Sites (With or Without DFS) - Why it Should be AvoidedPublished by Helge Klein on 07/30/2009 | 4 Comments | 9,148 Views |
![]() |
Most Viewed Posts
| 155,450 Views |
Where is the Hosts File on Windows x64?by Helge Klein (06/04/2009) |
| 83,171 Views |
Deleting a Local User Profile - Not as easy as one Might Assumeby Helge Klein (10/16/2008) |
| 53,149 Views |
Printer Driver Isolation in Windows 7 and Server 2008 R2by Helge Klein (04/08/2009) |
| 44,285 Views |
How to Reduce the Size of Roaming Profilesby Helge Klein (11/17/2008) |
| 32,176 Views |
Aufbau einer KMS Infrastrukturby Thorsten Christoffers (03/19/2009) |
Most Popular Tags
Blog Categories
64-Bit Windows (x64)
Application Delivery
Citrix
Citrix / Terminal Services / Remote Desktop Services
Community
Configuration Manager
Infrastruktur
Presentation Server / XenApp
Profile Migrator
Scripting
sepago
System Center
System Management
Terminal Services
User Profiles
Windows 7
Windows General
Windows Internals
Windows Server 2003
Windows Server 2008





