In many environments it is desirable that the user have concurrent access to their profile, or, in other words, have their Profile VHD attached to several computers at the same time. For example, a user may be logged in on one computer for their desktop and simultaneously logged in to another machine that is providing a remote application.
The way Profile Containers uses difference disks is controlled via the "ProfileType" setting. This setting can have a value of 0, 1, 2, or 3.
|Type ‘0’ (Normal) - This is the default behavior if the setting is not present|
|On Logon||Client tries to directly attach the |
|On Logoff||Client detaches the |
|Type ‘1’ (Read/Write)|
|Type ‘2’ (Read Only)|
|Type ‘3’ (Attempt RW role, but fall back to RO role if another client has the RW role)|
Client checks to see if a
ROdifference disks are stored in the local temp directory and are named
RWdifference disk is stored on the network next to the parent
VHD(X)file and is named
- The merge operation can be safely interrupted and continued. If one client begins the merge operation and is interrupted (e.g. powered off), another client can safely continue and complete the merge. This is why both the
ROclients begin by attempting a merge of the
- Merge operations on an
ReFSfile system (where the difference disk and the parent are on the same
ReFSvolume) are nearly instantaneous no matter how big the difference disk is.
- Merge operations can only be done if there are no open handles to either the difference disk or the parent
VHD(X). This is why the
ROclient also attempts to merge the
RW.VHD(X). It may be the last session to disconnect.