Integrating with Dell Client Command Suite: VMware Workspace ONE Operational Tutorial

VMware Workspace ONE UEM 9.7 and later

Overview

Introduction

VMware provides this operational tutorial to help you with your VMware Workspace ONE®environment. In this tutorial, you integrate Dell Client Command Suite with VMware Workspace ONE® UEM. You add the Dell Command | Monitor and Dell Command | Update software, configure BIOS and OEM Updates profiles, and confirm the integrations.

Audience

This operational tutorial is intended for IT professionals and Workspace ONE administrators of existing production environments. Familiarity with networking and storage in a virtual environment is assumed, including Active Directory, identity management, and directory services. Knowledge of additional technologies such as VMware Identity Manager™ and VMware Workspace ONE® UEM, is also helpful.

Integrating with Dell Client Command Suite

Introduction

Workspace ONE UEM integrates with Dell Client Command Suite to enhance the modern device management of Dell Enterprise client systems. With the integration of Dell Command | Monitor, Workspace ONE UEM reports on custom system properties and reports and sets BIOS attributes. The integration with Dell Command | Update allows for OEM updates to be configured and applied on the device, such as applying driver, firmware, and BIOS updates to the device. This exercise helps you to configure these integrations in the Workspace ONE UEM console. In this exercise, you upload and deploy the Dell Command | Monitor and Dell Command | Update apps, configure the corresponding profiles, and view the additional attributes in the console. The steps are sequential and build upon one another, so make sure that you complete each step before going to the next step.

Integrate Workspace ONE UEM with Dell Client Command Suite

Integrating Workspace ONE UEM with Dell Client Command Suite enhances the information collected from enrolled devices, and allows you to configure device BIOS settings and to report on installed OEM updates. To watch a video demonstrating these features, click Dell Client Command Suite Integration with Workspace ONE UEM or click the video itself.

Prerequisites

Before you can perform the procedures in this exercise, you must satisfy the following requirements. For more information, see the VMware Identity Manager Documentation and VMware Workspace ONE UEM Documentation.

  • Windows Pro or Enterprise device, enrolled in Workspace ONE UEM. For more information, compare Windows 10 editions, or contact a Microsoft representative.
  • Meet the prerequisites for Dell Command | Monitor
  • Meet the prerequisites for Dell Command | Update
  • Meet the prerequisites for Dell Command | Configure (required only if planning to upload a CCTK configuration package)
  • Supported Dell Enterprise client system: Dell OptiPlex™ desktop devices, Dell Precision Workstation™ desktop and laptop devices, Dell Latitude™ laptop devices, and Dell XPS Notebook™ devices.

For more information about supported Dell systems, see the Dell product documentation.

Adding the Dell Command | Monitor Software

Before you deploy the BIOS profile in the Workspace ONE UEM console, first, upload and deploy the Dell Command | Monitor software to your managed Dell Enterprise client systems. 

1. Upload the Dell Command | Monitor Software

In the Workspace ONE UEM console:

  1. Select Apps & Books.
  2. Select Add Application.

1.1. Download Software

Download the latest Dell Command | Monitor software. In the Downloads section, select your corresponding architecture. 

Return to the Workspace ONE UEM console and click Upload.

1.2. Browse

Select Browse...

1.3. Select Dell Command | Monitor MSI

Unzip the downloaded package to extract the Command_Monitor_x##.msi then select the MSI file.

  1. Select the Command_Monitor-x64.msi file.
  2. Click Open.

1.4. Save Dell Command | Monitor MSI

Click Save.

1.5. Continue to Add Application

Keep the default values and click Continue.

2. Configure the Details Tab

  1. Ensure the Details tab is selected.
  2. Select 64-bit for the Supported Processor Architecture. Verify the relevant processor architecture for your device.

Note: When uploading MSI files, all possible fields are automatically pre-populated with all of the metadata. However, for ZIP and EXE packages, you must enter a Name and some of the Deployment options.

3. Configure the Files Tab

Select the Files tab.

3.1. Review Application File Settings

Familiarize yourself with the following settings, which enable you to configure additional application details and requirements:

  • App Dependencies — Enable the system to apply dependency files.
  • App Transforms  Apply MSI Transform (MST) files.
  • App Patches — Apply MSI Patch (MSP) files.

Note: You can upload the transforms (.mst) included in the extracted folder to specify the installation language. Workspace ONE UEM automatically updates the install command line and supports uploading multiple transforms, which will be assigned to different groups later. If the installation language is not specified, the installer selects the default operating system language, or English if the default operating system language is not supported. For more information about installation language, see the Dell Command | Monitor Installation Guide.

4. Configure Deployment Options

Select the Deployment Options tab.

4.1. Define When to Install

Configure details about requirements to install the application. This example uses suggested values which you can customize for your environment.

  1. Enter 100 for the Disk Space Required which specifies the amount of disk space the device must have available to install the application.
  2. Select MB for the Units of the Disk Space Required.
  3. Enter 25 for the Device Power Required which specifies the battery power, in percentage, that the device must have to install the application.
  4. Enter 500 for the RAM Required which specifies the amount of RAM the device must have to install the application.
  5. Enter MB for the Units of the RAM Required.

4.2. Define How to Install

  1. Scroll down to find the How To Install section.
  2. Ensure msiexec /i "Command_Monitor_x64.msi" /qn is entered for the Install Command.
  3. Select Yes for Admin Privileges.
  4. Ensure 3 is entered for the Retry Count, which specifies the number of times the system attempts to install the application after an unsuccessful attempt.
  5. Ensure 5 is entered for the Retry Interval, which specifies the time (in minutes) the system waits when it tries to install the application after an unsuccessful attempt.
  6. Enter 15 for the Install Timeout, which specifies the time (in minutes) the system allows the installation process to run without success.
  7. Ensure 1614 is entered for the Installer Reboot Exit Code, which specifies the code the installer outputs to identify a reboot action.
  8. Ensure  0 is entered for the Installer Success Exit Code, which specifies the code the installer outputs to identify a successful installation.

5. Add the Application Icon

Select the Images tab.

5.1. Open Icon Settings

  1. Select the Icon tab.
  2. Click the area labeled Click or drag files here.

5.2. Select the Icon File

  1. Navigate to the folder containing your Dell logo file.
  2. Select your Dell logo image.
  3. Click Open.

6. Set Terms of Use

  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here.
  3. Click Save & Assign.

7. Assign & Publish

7.1. Add Application Assignment

Click Add Assignment.

7.2. Assign Office 365 Pro Plus

  1. Select All Devices for the Assignment Groups, or your custom created Assignment Group for your Dell devices.
  2. Select Auto for App Delivery Method.
  3. Click Add.

7.3. Save and Publish

Click Save & Publish.

7.4. Publish

Click Publish.

8. Confirm the Application Appears in the List View

In the Internal Applications List View, confirm that the Dell Command | Monitor application is displayed.  

You have successfully added the Dell Command | Monitor app to Workspace ONE UEM for deployment.  

Configuring the BIOS Profile

Profiles allow you to modify how the enrolled devices behave. This section helps you to configure the BIOS using a profile that we will verify applied to the device.

1. Add a Profile

First, add a new Windows Desktop Profile.

1.2. Add a Windows Profile

Select the Windows icon.

Note: Make sure that you are selecting Windows and not Windows Rugged.

1.3. Add a Windows Desktop Profile

Select Windows Desktop.

1.4. Select Context - Device Profile

Select Device Profile.

2. Configure Profile Settings

Next, configure the profile general settings and the BIOS settings.

2.1. Define General Settings

  1. Select General if it is not already selected.
  2. Enter a profile name in the Name text box, for example, Windows 10 - BIOS.
  3. Copy the profile name into the Description text box.
  4. Click in the Assigned Groups field. This will pop-up the list of created Assignment Groups. Select the All Devices Assignment Group.
    Note: You may need to scroll down to view the Assigned Groups field.

Note: You do not need to click Save & Publish at this point. This interface allows you to move around to different payload configuration screens before saving.

2.2. Open the BIOS Payload

 Note: When initially setting a payload, a Configure button will show to reduce the risk of accidentally setting a payload configuration.

  1. Scroll through the payload section on the left until you see the BIOS payload.
  2. Select the BIOS payload.
  3. Click the Configure button to begin configuring the payload settings.

2.3. Configure BIOS Settings

Configure the Security, Boot, Virtualization, and Connectivity sections of the BIOS payload that match your organizational requirements. Following are some sample values:

  1. Enter the password you want used to unlock the BIOS.
  2. Select Enabled to enable the device Trusted Platform Module.
  3. Select Enabled to enable hardware virtualization support.
  4. Select Enabled to enable input/output virtualization on the device.
  5. Select Enabled to enable trusted execution which requires TPM, CPU Virtualization, and Virtualization IO to be enabled on the device.

Note: Configure the settings to match your organizational requirements. For more information about these options, see Configure a BIOS Profile (Windows Desktop) in the VMware Workspace ONE UEM Documentation.

2.4. Configure Power Management Settings

  1. Using the scroll bar on the right, scroll down to the Storage section.
  2. Select Enable to use peak shift to control when a device uses battery charge or AC current. Peak shift allows you to use battery power instead of AC current during specified times.
  3. Click the calendar icon to set the schedule for Peak Shift.

Note: Configure the settings to match your organizational requirements. For more information about these options, see Configure a BIOS Profile (Windows Desktop) in the VMware Workspace ONE UEM Documentation.

2.5. Configure System Properties and BIOS Attributes Settings

  1. Using the scroll bar on the right, scroll down to the Custom section.
  2. Click Add System Property twice (2x).
  3. Enter DCIM_Battery or select it as it auto-completes.
  4. Enter ChargingStatus or select it as it auto-completes.
  5. Enter DCIM_PhysicalMemory or select it as it auto-completes.
  6. Enter Capacity or select it as it auto-completes.
  7. Click Add BIOS Attribute three times (3x).
  8. Enter Power Warning or select it as it auto-completes.
  9. Enter Enable or select it as it auto-completes.
  10. Enter Wake-On-LAN or select it as it auto-completes.
  11. Enter LAN or WLAN or select it as it auto-completes.
  12. Enter SMART Errors or select it as it auto-completes.
  13. Click Save & Publish.

Note: If you leave the Value field blank for a BIOS Attribute, it will read and report this value back to Workspace ONE UEM. When selecting a value, Workspace ONE UEM sets that value on the device.

For more information about generating Dell Command | Configure configuration packages (CCTK) to configure additional BIOS settings, see the Dell Command | Configure User's Guide.

Note: Configuration packages override any custom system properties or attributes, whereas any custom system properties or attributes override any BIOS settings set in the profile. Overall, as the profile progresses so does the order of precedence applied.

2.6. Publish the BIOS Profile

Click Publish.

3. Verify the Profile Exists

Confirm that the newly created profile exists.

3.2. Locate the Profile in the List View

The Windows 10 - BIOS Profile now appears in the Device Profiles list view.

Validating BIOS Properties and Attributes

When you push the BIOS profile to the device, it interfaces with Dell Command | Monitor to update system properties and set and report on BIOS attributes. In this section, review the results of your integration in the console.

1. Select a Managed Device

First, select your Dell managed device.

1.2. Select Managed Device

Click the friendly name of one of your Dell managed devices.

2. Validate the App and Profile Applied

Confirm that the applications and profiles installed successfully.

2.1. Verify Apps and Profiles Installed

You can quickly verify that the profiles and apps deployed to your device. The next steps review each of these configurations.

Note: Two new attributes—BIOS Version and Battery Health Status—appear on the device details view when Dell Command | Monitor is deployed.

2.2. Validate Dell Command | Monitor Installed

  1. Select the Apps tab.
  2. Validate that the Dell Command | Monitor software has successfully installed on the device before continuing on to the next steps.

2.3. Validate the Windows 10 - BIOS Profile Installed

  1. Select the Profiles tab.
  2. Validate that the Windows 10 - BIOS profile was successfully installed before continuing.

3. Check BIOS System Properties and BIOS Attributes

Workspace ONE UEM configures the BIOS on the device leveraging Dell Command | Monitor and also retrieves the specified BIOS attributes and other useful system information.

  1. Select the More tab, then select BIOS.

You have successfully integrated Workspace ONE UEM with Dell Command | Monitor, and validated the settings are applied and BIOS attributes are reported to the Workspace ONE UEM console.

Adding the Dell Command | Update Software

Before you deploy the OEM Updates profile in the Workspace ONE UEM console, first, upload and deploy the Dell Command | Update software to your managed Dell Enterprise client systems. 

1. Upload the Dell Command | Update Software

In the Workspace ONE UEM console:

  1. Select Apps & Books.
  2. Select Add Application.

1.1. Download Software

First, download the latest 2.x version of the Dell Command | Update software. 

Return to the Workspace ONE UEM console and select Upload.

Important: Dell Command | Update 3.0 is not supported with Workspace ONE UEM.

1.2. Browse

Select Browse...

1.3. Select Dell Command | Update EXE

  1. Select the Dell-Command-Update_<XXXXX>_WIN_<###>_A00.EXE file.
  2. Click Open.

1.4. Save Dell Command | Update EXE

Click Save.

1.5. Continue to Add Application

Keep the default values and click Continue.

2. Configure the Details Tab

  1. Ensure the Details tab is selected.
  2. Enter Dell Command | Update for Name.
  3. Select 64-bit for the Supported Processor Architecture. Verify the relevant processor architecture for your device.

Note: When uploading MSI files all possible fields are automatically pre-populated with all of the metadata. However, for ZIP and EXE packages, you must enter a Name and some of the Deployment options.

3. Configure the Files Tab

Select the Files tab.

3.1. Configure the App Uninstall Process

  1. Scroll down to find the App Uninstall Process section.
  2. Select Input for the Custom Script Type.
  3. Enter msiexec /x {EC542D5D-B608-4145-A8F7-749C02BE6D94} /qn as the Uninstall Command.

4. Configure Deployment Options

Select the Deployment Options tab.

4.1. Define When to Install

Configure details about requirements to install the application. This example uses suggested values which you can customize for your environment.

  1. Enter 150 for the Disk Space Required which specifies the amount of disk space the device must have available to install the application.
  2. Select MB for the Units of the Disk Space Required.
  3. Enter 25 for the Device Power Required which specifies the battery power, in percentage, that the device must have to install the application.
  4. Enter 500 for the RAM Required which specifies the amount of RAM the device must have to install the application.
  5. Enter MB for the Units of the RAM Required.

4.2. Define How to Install

  1. Scroll down to find the How To Install section.
  2. Ensure Dell-Command-Update_XXXXX_WIN_###_A00.EXE /s is entered for the Install Command.
  3. Select Yes for Admin Privileges.
  4. Ensure 3 is entered for the Retry Count, which specifies the number of times the system attempts to install the application after an unsuccessful attempt.
  5. Ensure 5 is entered for the Retry Interval, which specifies the time (in minutes) the system waits when it tries to install the application after an unsuccessful attempt.
  6. Enter 15 for the Install Timeout, which specifies the time (in minutes) the system allows the installation process to run without success.

4.3. Define When To Call Install Complete

  1. Scroll down to the When To Call Install Complete section.
  2. Select Defining Criteria for Identify Application By.
  3. Click + Add.

4.4. Define the Application Criteria

  1. Select Registry Exists for the Criteria Type.
  2. Enter HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{EC542D5D-B608-4145-A8F7-749C02BE6D94} for the Path.
  3. Enter DisplayName for the Value Name.
  4. Select String for the Value Type.
  5. Enter Dell Command | Update for the Value Data.
  6. Click Add.

Note: There are multiple Criteria Types to choose from, allowing you to be flexible in determining if your deployment was successful.  You can also add multiple Criteria configurations and link them together logically to cover complex deployments.

5. Add the Application Icon

Select the Images tab.

5.1. Open Icon Settings

  1. Select the Icon tab.
  2. Click the area labeled Click or drag files here.

5.2. Select the Icon File

  1. Navigate to the folder containing your Dell logo file.
  2. Select your Dell logo image.
  3. Click Open.

6. Set Terms of Use

  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here.
  3. Click Save & Assign.

7. Assign and Publish

7.1. Add Application Assignment

Click Add Assignment.

7.2. Assign Dell Command | Update

  1. Select All Devices for the Assignment Groups, or your custom created Assignment Group for your Dell devices.
  2. Select Auto for App Delivery Method.
  3. Click Add.

7.3. Save and Publish

Click Save & Publish.

7.4. Publish

Click Publish.

8. Confirm the Application Appears in the List View

In the Internal Applications List View, confirm that the Dell Command | Monitor application is displayed.  

You have successfully added the Dell Command | Monitor app to Workspace ONE UEM for deployment.  

Configuring the OEM Updates Profile

Profiles allow you to modify how the enrolled devices behave. This section helps you to configure an OEM Updates profile that we will verify applied to the device. When you push the OEM Updates profile to the device, this configures Dell Command | Update with the respective settings and prevents the end-user from modifying the settings on their devices. Users can still run scans and apply updates, however, all of the settings are disabled for modifications.

1. Add a Profile

First, add a Windows profile.

1.2. Add a Windows Profile

Select the Windows icon.

Note: Make sure that you are selecting Windows and not Windows Rugged.

1.3. Add a Windows Desktop Profile

Select Windows Desktop.

1.4. Select Context - Device Profile

Select Device Profile.

2. Configure Profile Settings

Configure the profile general settings and OEM updates settings.

2.1. Define General Settings

  1. Select General if it is not already selected.
  2. Enter a profile name in the Name text box, for example, Windows 10 - OEM Updates.
  3. Copy the profile name into the Description text box.
  4. Click in the Assigned Groups field. This will pop-up the list of created Assignment Groups. Select the All Devices Assignment Group.
    Note: You may need to scroll down to view the Assigned Groups field.

Note: You do not need to click Save & Publish at this point. This interface allows you to move around to different payload configuration screens before saving.

2.2. Open the OEM Updates Payload

  1.  Scroll through the payload section on the left until you see the OEM Updates payload.
  2. Select the OEM Updates payload.
  3. Click the Configure button to begin configuring the payload settings.

Note: When initially setting a payload, a Configure button will show to reduce the risk of accidentally setting a payload configuration.

2.3. Configure OEM Updates Settings

Configure the Schedule and Level sections of the OEM Updates payload that match your organizational requirements. Following are some sample values:

  1. Select Weekly to set the interval used to Check for Updates. Supported values are Never, Weekly, and Monthly.
  2. Select Friday for the Day of the Week to check for updates.
  3. Set the Time to 10:00 PM. This sets the time of day to check for updates.
  4. Select Scan Download Notify for the Update Behavior. Supported values are Scan Notify, Scan Download Notify, or Scan Notify Apply Reboot.
    • Scan — Scans for updates.
    • Notify — Notifies the user that updates are available.
    • Download — Downloads any available updates.
    • Apply — Installs any available update.
    • Reboot — Reboots the device according to the Reboot Delay configuration.
  5. Select Manual Reboot for the Reboot Delay. Supported values are Manual Reboot, 5, 15, or 60 Minutes.
  6. Select the Level of updates to scan for while checking for updates, any disabled value will be ignored while scanning and applying updates.

Note: Configure the settings to match your organizational requirements. For more information about these options, see Configure the OEM Updates Profile (Windows Desktop) in the VMware Workspace ONE UEM Documentation.

Warning: You must close Dell Command | Update for the scheduler to check for updates during the scheduled interval.

Note: Dell Command | Update checks for updates at random intervals within 30 minutes of the time set in the Time field.

2.4. Configure Update Type Settings

Configure the Update Type section of the OEM Updates payload that match your organizational requirements.

  1. Using the scroll bar on the right, scroll down to the Update Type section.

Choose to enable or disable the different Update Types in this section of the profile; the default values are shown in the screenshot.

Note: Configure the settings to match your organizational requirements. For more information about these options, see Configure the OEM Updates Profile (Windows Desktop) in the VMware Workspace ONE UEM Documentation.

2.5. Configure Device Categories Settings

Configure the Device Categories section of the OEM Updates payload that match your organizational requirements.

  1. Using the scroll bar on the right, scroll down to the Device Categories section.
  2. Click Save & Publish.

Note: Configure the settings to match your organizational requirements. For more information about these options, see Configure the OEM Updates Profile (Windows Desktop) in the VMware Workspace ONE UEM Documentation.

2.6. Publish the OEM Updates Profile

Click Publish.

3. Verify the Profile Exists

Confirm that the newly created profile exists.

3.2. Locate the Profile in the List View

The Windows 10 - OEM Updates Profile now appears in the Device Profiles list view.

Validating OEM Updates

When you push the OEM Updates profile to the device, it configures Dell Command | Update with the respective settings and prevents the end-user from modifying the settings on their devices. Users can still run scans and apply updates, however, all of the settings are disabled for modifications. In this section, review the results of your integration on the device and in the console.

1. Select a Managed Device

First, select your Dell managed device.

1.2. Select Managed Device

Click the friendly name of one of your Dell managed devices.

2. Validate App and Profile Applied

Confirm that the applications and profiles installed successfully.

2.1. Verify Apps and Profiles Installed

You can quickly verify that the profiles and apps deployed to your device. The next steps reviews each of these configurations.

2.2. Validate Dell Command | Update Installed

  1. Select the Apps tab.
  2. Validate that the Dell Command | Update software has successfully installed on the device before continuing on to the next steps.

2.3. Validate the Windows 10 - OEM Updates Profile Installed

  1. Select the Profiles tab.
  2. Validate that the Windows 10 - OEM Updates profile was successfully installed before continuing.

3. Check OEM Updates and Configurations

In this section, confirm the OEM Updates settings and Dell Command | Update settings.

3.1. Check Applied OEM Updates

Workspace ONE UEM queries the device for all of the applied OEM Updates installed using Dell Command | Update.

  1. Select the More tab, then select OEM Updates.
  2. Click Intel Management Engine Components Installer, or any other update to view more details about that update.

 

3.2. OEM Updates Details

Workspace ONE UEM reports on the OEM Updates and details such as Release ID, Version, Criticality, Update Type, Category, and the Date Applied.

Click X to close the pop-up window.

3.3. Dell Command | Update History

On your Dell enterprise managed device in the Dell Command | Update software, the Update History should also match the details in the Workspace ONE UEM console.

3.4. Dell Command | Update Settings

  1. Click the settings icon.
  2. Click Schedule.

Note that the settings are unavailable (dimmed) and set to match the profile configuration options.

Important: If you set a scheduled time which does not have 00 for minutes (for example, ##:00) then Dell Command | Update displays a blank value for Select the time field. Regardless of the blank value, the correct time is set on the device—you can validate by exporting the setting and comparing the scheduled minutes field.

3.5. OEM Updates Consolidated View

Workspace ONE UEM provides a consolidated view of the deployed OEM Updates to your managed devices. You can filter the updates by Type and click any of the updates to see which devices have that update installed.

  1. Select Devices.
  2. Select Lifecycle.
  3. Select Updates.
  4. Select OEM Updates.

You have successfully integrated Workspace ONE UEM with Dell Command | Update, and validated the settings are applied and OEM Updates are reported to the Workspace ONE UEM console.

Summary and Additional Resources

Conclusion

This operational tutorial provided steps to integrate Dell Client Command Suite with VMware Workspace ONE UEM. Procedures included adding the Dell Command | Monitor and Dell Command | Update software, configuring BIOS and OEM Updates profiles, and confirming the integrations were successful.

Terminology Used in This Tutorial

The following terms are used in this tutorial:

application store A user interface (UI) framework that provides access to a self-service catalog, public examples of which include the Apple App Store, the Google Play Store, and the Microsoft Store.
auto-enrollment Auto-enrollment simplifies the enrollment process by automatically enrolling registered devices following the Out-of-Box-Experience.
catalog A user interface (UI) that displays a personalized set of virtual desktops and applications to users and administrators. These resources are available to be launched upon selection.
cloud Asset of securely accessed, network-based services and applications. A cloud can also host data storage. Clouds can be private or public, as well as hybrid, which is both private and public.
device enrollment The process of installing the mobile device management agent on an authorized device. This allows access to VMware products with application stores, such as VMware Identity Manager.
identity provider (IdP) A mechanism used in a single-sign-on (SSO) framework to automatically give a user access to a resource based on their authentication to a different resource.
mobile device management
(MDM) agent
Software installed on an authorized device to monitor, manage, and secure end-user access to enterprise resources.
one-touch login A mechanism that provides single sign-on (SSO) from an authorized device to enterprise resources.
service provider (SP) A host that offers resources, tools, and applications to users and devices.
virtual desktop The user interface of a virtual machine that is made available to an end user.
virtual machine A software-based computer, running an operating system or application environment, that is located in the data center and backed by the resources of a physical computer.

For more information, see the VMware Glossary.

Additional Resources

About the Author

This tutorial was written by:

  • Josue Negron, Senior Solutions Architect, End-User-Computing Technical Marketing, VMware

Feedback

The purpose of this tutorial is to assist you. Your feedback is valuable. To comment on this tutorial, contact VMware End-User-Computing Technical Marketing at euc_tech_content_feedback@vmware.com.