Problem:
ProfileDisk VHD files stay open for a long time after user is already logged off. If the ProfileUnity logoff script did not run they can stay open for a very long time.
Symptoms:
Long open file timeouts for VHD files.
Resolution(s):
1) Disable Oplocks. (Default is enabled)
"Choose whether the appliance will grant Opportunistic Locks to SMB clients. This will improve performance for most clients. Default is on. The SMB server grants an oplock to a client process so that the client can cache data while the lock is in place. When the server revokes the oplock, the client flushes its cached data to the server."
https://docs.oracle.com/cd/E27998_01/html/E48433/configuration__services__smb.html
2) Enable "Non-blocking mandatory locking" (his property must be enabled to allow byte range locking to function correctly.)
"Controls whether SMB locking semantics are enforced over POSIX semantics. This property is only valid for filesystems. By default, filesystems implement file behavior according to POSIX standards. These standards are fundamentally incompatible with the behavior required by the SMB protocol. For shares where the primary protocol is SMB, this option should always be enabled. Changing this property requires all clients to be disconnected and reconnect."
https://docs.oracle.com/cd/E27998_01/html/E48433/configuration__services__smb.html
Note: It is recommended to setup "MMC Integration" Microsoft Management Console could be used to close open VHD files is necessary. More information is found on this page:
https://docs.oracle.com/cd/E27998_01/html/E48433/configuration__services__smb.html
Product: ProfileUnity
Product Version: 6.5+