Release Notes

● When you upload a local file to GCP folder, a new file is created under GCP with the same name after every upload. This is
because you create multiple files with the same name in GCP. When any of the duplicate files is made offline, all files in the
same name are also available in the offline mode.
● When you save any cloud file to a local drive using the Save Offline option, the UI displays all the files with the same name
in the in offline mode. But, only the selected file is saved in the offline mode which is a known issue in the UI.
● You cannot manually enter credentials while accessing network drives. Credentials must be configured in the Wyse
Management Suite server when you are creating drives.
● Cloud files launch with VDI, local file launch with cloud and file synchronization is achieved only after you log off and log in
again.
● Device specific cache directory and drafts directory are created in the cloud root for Azure and GCP.
NOTE: New device specific cache directory and drafts directory is created in the cloud root for GCP when you
unregister the device from Wyse Management Suite or when you reset the device to factory settings.
● For GCP, any local file that is uploaded by a user is available in the cloud root. The Azure file is uploaded to the Uploads
folder in the cloud drive.
● You can manually upload cloud files of any size. However, the automatic synchronization of VDI files that you edited offline is
limited to 4 MB for Azure. For more information, see Upload or replace the contents of a DriveItem at https://
docs.microsoft.com/.
● Occasionally, a file opened by the user in OneDrive may be temporarily locked with the error message Error Code 423 and
become inaccessible. This is as per the design from Azure. For more information, see Microsoft Graph error responses and
resource types at https://docs.microsoft.com/.
● Progress bar is not displayed when you copy the files. You must click the Sync button to view the copied file.
File affiliation
File affiliation feature enables you to restrict the user's ability to access applications depending on the mode. In the cloud mode,
the client displays applications that are supported by Cloud services. In the local mode, the client displays the local and VDI
applications that are installed and configured using Wyse Management Suite. In the offline mode, the client displays the tools
and applications that operate on the cached files. You can configure different modes on the same device for different users
using the User Policy groups.
The following are the different modes that are supported for file affiliation:
● Cloud+VDI+Local
● Cloud+Local
● Cloud
● VDI+Local
● VDI
Files in the File Explorer launch based on the priority that is set. File open function falls back to the second priority application
when the first priority fails.
Known issues and expected behavior
The following are the known issues and expected behavior of the file affiliation feature:
● Fallback mechanism works only when the server is not reachable. For example if the priority is set to VDI, and the VDI server
is not reachable then file open falls back to second priority applications. But if the server is reachable and application fails to
launch then the fallback mechanism does not work.
● When a network is not reachable, files always open using local applications.
Google Cloud Provider and Azure
Using File Explorer, users can access their files and applications in the Google cloud environment and Microsoft Azure
environment. You can use Active Directory log-in and Single Sign-On support for Azure using Azure AD sync with On-prem
Domain. You can configure these settings using Wyse Management Suite.
NOTE:
Dell Hybrid Client does not support SSO for GCP (GSuite), and you must enter the credentials when you log in for
the first time. The subsequent login works with SAML-based SSO authentication until you delete the browser cache.
Dell Hybrid Client 1.0 19