Flexapp™ Techbrief: Using Vhds Vs. Vmdks Page 1

Flexapp™ Techbrief: Using Vhds Vs. Vmdks Page 1

TechBrief FlexApp™ Using VHDs vs. VMDKs Summary ProfileUnity’s FlexApp and ProfileDisk technologies offer the flexibility to choose between using VHDs or VMDKs. With these technologies applications, user profiles, and user data are stored inside a virtual hard disk (VHD) on the network or a VMware virtual machine disk (VMDK) on storage visible to the ESXi host. A VHD looks like a local file system but can be mounted from anywhere on the network that we want to host our applications. VMDKs also look like a local file system but are mounted from the storage visible to the ESXi host where the desktop is running. Using a virtual disk has a number of benefits including IOPS reductions, file system compression, and application portability. At Liquidware, a question we frequently get asked is, “Should I use a VHD or a VMDK?”. The answer is that it depends. Not all features in these technologies are supported on both platforms. Feature Comparison Chart Use this ProfileUnity feature comparison chart to help guide you in deciding which is the best storage option per feature for your environment. Feature VHD VMDK/FlexDisk ProfileDisk Supported Supported ProfileDisk RDSH Supported Not Supported (starting in v6.7.0) FlexApp: Computer-level Supported Supported (starting in v6.7.0) FlexApp: User-level Supported Supported FlexApp: User Group-level Supported Supported FlexApp: Attach Now Not Supported Supported FlexApp: Click-to-Layer (version 6.7.0 and higher) Supported Not Supported FlexApp: Click-to-Layer for Published Apps Supported Not Supported (version 6.7.0 and higher) FlexApp: Cached Mode Application Deployment Supported Not Supported FlexApp: Use of Other ProfileUnity UEM Filters Supported Not Supported FlexApp: Cloud Storage, AWS S3, Google GCS Supported Not Supported and Azure Blob Deployment Differences One of the most powerful features of ProfileUnity is the User Environment Management filters that can be leveraged during the assignment of FlexApp Layers. Please note that filters apply to VHD-based FlexApp packages/layers but not to VMDK-based FlexApp layers. VMDK-based FlexApp layers currently support user, group and basic machine assignments. The primary reason for the difference in VHD vs. FlexApp™ TechBrief: Using VHDs vs. VMDKs Page 1 TechBrief VDMK package types centers on architecture. The ProfileUnity Configuration INI-based workflow does not apply to the VMDK-based assignments controlled by vCenter. ©2019 Liquidware Labs Inc. All rights reserved. Stratusphere, ProfileUnity, FlexApp, FlexDisk and ProfileDisk are trademarks of Liquidware Labs. All other products are trademarks of their respective owners. 19-0416 FlexApp™ TechBrief: Using VHDs vs. VMDKs Page 2 .

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    2 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us