No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionAccess Desktop Solution V100R006C20 Windows Desktop Management Guide 09 (FusionSphere V100R006C10 or Earlier)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
VM Types

VM Types

Administrators create VM templates on FusionCompute based on the actual application requirements.

Virtual desktop provisioning has two types:

  • Quick provisioning: Create a VM template in the virtualization platform and use the template to provision VMs in FusionAccess. It takes about 10 minutes to create user VMs and provision VMs to users. This minimizes IT management time.
  • Import provisioning: Import VMs from FusionSphere, OpenStack, and other platforms to FusionAccess for unified management.

In Windows desktop scenarios, user VMs can run on Windows 7, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012 R2, and Windows Server 2016 OSs. Table 2-1 lists the supported OS versions.

Table 2-1 Supported Windows OS versions

OS Type

Version

Remarks

Windows 7

  • Enterprise 32-bit or 64-bit
  • Professional 32-bit or 64-bit
  • Ultimate 32-bit or 64-bit

Simplified Chinese, traditional Chinese, English, Russian, Arabic, French, Spanish, Portuguese, and Polish OSs are supported. To use OSs in other languages, contact technical support.

Windows 8.1

  • Enterprise 32-bit or 64-bit
  • Professional 32-bit or 64-bit

Chinese and English OSs are supported. To use OSs in other languages, contact technical support.

Windows 10

  • Enterprise 32-bit or 64-bit
  • Professional 32-bit or 64-bit
  • Education 32-bit or 64-bit

Chinese, English, and Russian OSs are supported. To use OSs in other languages, contact technical support.

NOTE:

For Windows 10 VMs, only LTSB and CBB are supported. You are advised to update the VM patch using Windows Server Update Services (WSUS). For details about patch version mapping, see Huawei FusionCloud Compatibility Check Assistant.

Windows Server 2008 R2

  • Enterprise
  • Datacenter
  • Standard

Chinese and English OSs are supported. To use OSs in other languages, contact technical support.

Windows Server 2012 R2

  • Standard
  • Datacenter

Chinese and English OSs are supported. To use OSs in other languages, contact technical support.

Windows Server 2016

  • Standard
  • Datacenter

Chinese and English OSs are supported. To use OSs in other languages, contact technical support.

Windows desktop management involves four types of computers, full copy VMs, QuickPrep VMs, linked clone VMs, full memory VMs, and hosting computers. Table 2-2 shows their features and application scenarios.

Table 2-2 VM types

VM Type

Feature

Typical Scenario

Common Operation

Full copy

Independent VM that is created using a source VM (does not join a domain) template.

  • Users can save data changes (such as software installation) on VMs.
  • The source VM and each full copy VM use independent CPU, memory, and disk resources.
  • Users need to maintain software (for example, upgrade software or update the antivirus database) on each full copy VM.
  • After a VM is shut down, the personalized data of the user can be saved.

There are personalized applications and data.

The typical scenarios are as follows:

  • Common office
  • High-security desktops
  • Call centers
  • High-performance graphics processing

QuickPrep

Independent VM that is created using a source VM (has been added to a domain) template.

  • Users can save data changes (such as software installation) on VMs.
  • The source VM and each QuickPrep VM use independent CPU, memory, and disk resources.
  • Users need to maintain software (for example, upgrade software or update the antivirus database) on each QuickPrep VM.
  • After a VM is shut down, the personalized data of the user can be saved.
  • QuickPrep VMs do not support restoration after shutdown and one-click restoration.

Creating QuickPrep VMs does not require decapsulation, and the VMs have been added to domains in advance, requiring no restart. For this reason, provisioning a QuickPrep VM requires less time than provisioning a full copy VM.

NOTE:

The local SIDs of all VMs provisioned using the QuickPrep template are the same. Some industry software uses local SIDs to identify VMs. The software regards all VMs provisioned using the QuickPrep template as one VM, causing installation and use problems. When using the QuickPrep template, provision a few test VMs and ensure that the industry software required by the customer can work properly.

There are personalized applications and data.

The typical scenarios are as follows:

  • Common office
  • High-security desktops
  • Call centers
  • High-performance graphics processing

Linked clone

VM that is created by using a source VM (has been added to a domain) template. Multiple linked clone VMs share the same system disk.

  • Multiple linked clones of a parent VM can share the same memory and disk space. A linked clone base volume supports a maximum of 128 linked clones.
  • With the same server resources, more VMs can be created in linked clone mode than in full copy mode, reducing enterprise IT costs.
  • VMs can be updated in batches by using templates (for example, upgrade software or update the antivirus database).
  • Linked clone VMs support automatic system restoration after shutdown.
    NOTE:

    Advanced SAN storage does not support this feature.

  • A single linked clone VM can be created quickly.

There is personalized data but no personalized application.

The typical scenarios are as follows:

  • Task-based employees
  • Counters

Full memory

Full memory VMs are similar to linked clone VMs. The difference is that the system disk of a full memory VM is deployed in the memory.

  • Full memory VMs provide better storage experience than PCs.
  • Full memory virtual desktops resolve storage I/O storm problems in some special scenarios (clearing viruses or updating patches) to ensure faster VM startup and shutdown.
  • Full memory virtual desktops reduce VM data space usage by using online deduplication and real-time memory compression technologies. As main storage media, memory completely replaces the disk requirements of system volumes and greatly reduces the number of disks.
  • Full memory VMs provide high read and write performance and support quick start and restart.

There is no personalized application or data.

The typical scenarios are as follows:

  • Public computers (such as computers in Internet cafes)
  • Training rooms
  • School computer rooms
  • Electronic reading rooms

Hosting computer

Third-party computers (including VMs provisioned or created in the OpenStack platform or other third-party platforms) added to FussionAccess for management.

-

Translation
Download
Updated: 2019-04-25

Document ID: EDOC1000182394

Views: 20796

Downloads: 57

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next