In many environments it is desirable that the user have concurrent access to their Office 365 Container, or, in other words, have their O365 VHD attached to several computers at the same time.
The way O365 Containers uses difference disks is controlled via the "
VHDAccessMode" setting. This setting can have a value of
2, or 3.
|Mode ‘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 |
|Mode ‘1’ (Network)|
Mode '1' (Network) should not be used if the O365 Container is being used with Outlook Cached Exchange mode. Use mode '0' or '3'.
|Mode ‘2’ (Local)|
Mode '2' (Network) should not be used if the O365 Container is being used with Outlook Cached Exchange mode. Use mode '0' or '3'.
|Mode '3' (Per-session)|
- Local difference disks are stored in the local temp directory and are named
- Difference disks stored on the network are located next to the parent
VHD(X)file and are named
- When the difference disk is stored on the network, 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.
- 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). Therefore only the last session will be able to successfully merge its difference disk.
- Per-session VHD(X) files are named
sessionnumberis an integer from 0 - 9.
- The maximum number of per-session VHD(X) files is 10.