If one client begins the merge operation and is interrupted or powered off, another client can safely continue and complete the merge).
The merge operation can be safely interrupted and continued. Difference disks stored on the network are located next to the parent VHD(x) file and are named %computername%_ODFC.VHD(x). Local difference disks are stored in the local temp directory and are named %usersid%_ODFC.VHD(x). If the VHD(x) is marked for deletion, it's deleted. If a new VHD is created, resulting in session-based VHD(x) files greater than the number specified to keep in the setting, NumSessionVHDsToKeep, the VHD(x) is marked for deletion on sign out. If found, it's directly attached and used. Client searches for a session-based VHD(x) that isn't currently in use. To use Concurrent\Multiple Connections, the VHDAccessMode Type need to be 3: The RO client also attempts to merge the RW VHD(x) as it may be the last session to disconnect.Ĭoncurrent and Multiple connections require specific configuration for the ODFC container in order to make use of VHD(x) differencing disks. Merge operations can only be done if there are no open handles to either the difference disk or the parent VHD(x). Merge operations on an ReFS file system, where the difference disk and the parent are on the same ReFS volume, are nearly instantaneous regardless the size of the difference disk. This is why both RW and RO clients attempt a merge operation. The RW difference disk is stored on the network next to the parent VHD(x) file and is named RW.VHD(x). RO difference disks are stored in the local temp directory and are named %usersid%_RO.VHD(x). If the RW.VHD(x) file does exist, the client takes the RO role and does the same steps as ProfileType = 2. 
If it doesn't, the client takes the RW role and performs the same steps as ProfileType = 1. Client checks to see if a RW.VHD(x) file exists.To use Concurrent\Multiple Connections, the ProfileType must be set to 3.Ĭomputer attempts Read/Write lock, revert to Read Only: Profile container VHD(x) differencing disksĬoncurrent and Multiple connections require specific configuration for the Profile container in order to make use of VHD(x) differencing disks. Unlike concurrent connections, no other configuration is required beyond the differencing disks.
This scenario is only supported using VHD(x) differencing disks. Multiple connections are used when a user needs to have more than one (1) session, each on a different computer, using the same Profile or ODFC container. Registry Key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server Value Name Concurrent connections are NOT supported by Session Hosts running in an Azure Virtual Desktop Host Pool.
0 kommentar(er)
