DFS replication and TS profiles

[Jeff]

If I am only allowing one terminal session, is there an easy way to setup DFS
replication of our roaming profiles for backup purposes? And if this is
possible is it not a good idea to point roaming profile locations to an
Active Directory share setup as a DFS namespace instead of to a direct server
share. If this is possible, on the event that the server housing the roaming
profiles goes down I could redirect to a server that was part of the
replication.

Any articles or ideas on this?

 

[Helge Klein]

You mentioned two different things - DFS Namespaces and DFS
Replication. Let's start with the easier one: DFS Namespaces:

It is no problem whatsoever and I even recommend building one single
DFS namespace which contains, among many others, the network shares
for your user's home and profile folders.

Now to DFS replication: You _can_ use DFS-R for backup purposes of
roaming user profiles as long as you make sure that profiles are not
changed on both sides simultaneously. As you want to use DFS-N for
redundancy you cannot restrict write access to the second (backup)
copy. I find it problematic, even if you restrict every user to one
session, to combine DFS-N and DFS-R for user profiles. I would not do
it.

For redundant file shares it is better to use a cluster.

I hope this helps.

Helge

On 18 Jul., 15:14, Jeff <J...@discussions.microsoft.com> wrote:
> If I am only allowing one terminal session, is there an easy way to setup DFS
> replication of our roaming profiles for backup purposes? And if this is
> possible is it not a good idea to point roaming profile locations to an
> Active Directory share setup as a DFS namespace instead of to a direct server
> share. If this is possible, on the event that the server housing the roaming
> profiles goes down I could redirect to a server that was part of the
> replication.
>
> Any articles or ideas on this?