The Unofficial Official VCP6-DCV Study Guide

vmworld2015

We are just a few short days away from one of my favorite weeks of the year, VMworld! Well just like a few years back, Josh Coen (blog / twitter) and I have teamed up with our good friends at Veeam Software (website / twitter) to release the latest version of “The Unofficial Official VCP6-DCV Study Guide”. With the short turn around time  Josh and I had to complete the study guide we have our fingers crossed that hard copies of the guide will be available next week (watch Twitter for updates) at the Veeam booth. For those who can’t wait, clink on the cover below to download an electronic copy.

Hope to see you at VMworld and happy Studying!

-Jason

Cover

VCP 6–Objective 7.2 Troubleshoot vSphere Storage & Network Issues

For this objective I used the following resources:

Objective 7.2 Troubleshoot vSphere Storage & Network

Knowledge

Verify Network Configuration

Refer to each objective under Section Two. Focus on the core concepts and configuration of both vNetwork Standard Switches and vNetwork Distributed Switches:

  • Port/dvPort Groups
  • Load Balancing and Failover Policies
  • VLAN Settings
  • Security Policies
  • Traffic Shaping Policies

For additional information read the VMware Information Guide “VMware Virtual Networking Concepts”. This document is based on VI3 but still does a good job with the core functions of a vStandard Switch.

Verify a Given Virtual Machine is Configured with the Correct Network Resources

Instead of duplicating work, refer to VMware KB 1003893, “Troubleshooting Virtual Machine Network Connection Issues”. More then enough information listed there.

Troubleshoot Physical Network Adapter Configuration Issues

This is pretty straight forward as there is not a lot of configuration done at the physical network layer. Be sure that your physical nics that are assigned to a virtual switch (vSwitch or dvSwitch) are configured the same (speed, vlans, etc) on the physical switch. If using IP Hash as your load balancing method make sure on the physical switch side link aggregation has been enabled. Refer to VMware KB 1001938 and VMware KB 1004048 for further details as well as examples. If using beacon probing for network failover detection it standard practice to use a minimum of three (or more) uplink adapters. See VMware KB 1005577 for further details.

Troubleshoot Virtual Switch and Port Group Configuration Issues

One key aspect to remember is when setting up Port Groups or dvPort Groups, spelling counts (as well as upper/lower case)! If a Port Group is spelled Test on one host and is spelled test on a second host vMotion will fail. Same holds true with Security Policies, if one vSwitch on a host is set to accept Promiscuous Mode and it is set to Reject on the other host, again vMotion will fail. Also, refer to the objectives under Section Two to be sure your switches are configured correctly.

Troubleshoot Common Network Issues

Using the above notes as well as the linked VMware KB articles one should be able to isolate issue to one of four areas:

  • Virtual Machine
  • ESX/ESXi Host Networking (uplinks)
  • vSwitch or dvSwitch Configuration
  • Physical Switch Configuration

Troubleshoot VMFS Metadata Consistency

Use the vSphere On-disk Metadata Analyser (VOMA) to identify and fix incidents of metadata corruption that affect file systems or underlying logical volumes. VOMA is executed from the CLI of an ESXi host and can be used to check and fix metadata inconsistency issues for a VMFS datastore or a virtual flash resource.  The following example was pulled from the vSphere Troubleshooting documentation:

  • Obtain the name and partition number of the device that backs the VMFS datastore that you need to check
    • #esxcli storage vmfs extent list
  • Run VOMA to check for VMFS errors. Provide the absolute path to the device partition that backs the VMDS datastore, and provide a partition number with the device name:
    • # voma –m vmfs –f check –d /vmfs/devices/disks/naa.600508e000000000b367477b3be3d703:3
  • The output lists possible errors

For the full run down of VOMA command options review the table on page 66 of the vSphere Troubleshooting documentation.

Verify Storage Configuration

Refer to the vSphere Storage and the SAN System Design and Deployment Guide (not specific to vSphere 6, but worth a read) by VMware. This will cover a lot of areas needed for working with a FC/iSCSI SAN environment with vSphere. Also a good understanding of the hardware you are using on the backend (storage arrays, FC switches, networking, etc) and there “vSphere Best Practices” documents will assist in the proper configuration.

Identify Storage I/O Constraints

With the mention “storage constraints” I am assuming they are hinting at I/O throughput or I/O latency issues. I find the quickest and easiest way of measuring/checking this is via esxtop/resxtop. VMware KB 1008205 and Duncan Eppings esxtop blog post covers this is in more detail.

Metrics to be aware of:

Disk Metric Threshold Description
DAVG 25 This is the average response time in milliseconds per command being sent to the device
GAVG 25 This the response time as it is perceived by the guest operating system. This number is calculated with the formula: DAVG + KAVG = GAVG
KAVG 2 This is the amount of time the command spends in the VMKernel

 

The following diagram (provided by VMware) provide a visual representation of the chart above:

Horizon_6_Storage_ESXi

Monitor/Troubleshoot Storage Distributed Resource Scheduler (SDRS)

Refer to Section 6, Troubleshooting Resource Management in vSphere Troubleshooting 6.0 documentation (pages 47 thru 55).

Troubleshoot Common Storage Issues

Refer to Section 7, Troubleshooting Storage in vSphere Troubleshooting 6.0 documentation (pages 55 thru 72). The section covers several storage related issues that you may run into.

VCP-6 Objective 6.1–Configure and Administer a vSphere Backups/Restore/Replication Solution

For this objective I used the following resources:

Objective 6.1 – Configure and Administer a vSphere Backup/Restore/Replication Solution

Knowledge

Identify Snapshot Requirements

Create/Delete/Consolidate Virtual Machine Snapshots

For these two topics I am going to group other them together with a list of VMware KB articles that easily cover the topics and provide a deeper level of the how’s and why’s of VMware snapshots. But for an overview a VMware snapshot is:

  • Represents the state of a virtual machine at the time it was taken
  • Include the files and memory state of a virtual machine’s guest operating system
  • Includes the settings and configuration of a virtual machine and its virtual hardware
  • Is stored as a set of files in the same directory as other files that comprise a virtual machine
  • Should be taken when testing something with unknown or potentially harmful effects
  • Can take up as much disk space as the virtual machine itself. If multiple snapshots are possible, the amount of disk space used increases with the number of snapshots in place

For a complete run down of VMware snapshots, have a look at the following VMware KB articles:

Identify VMware Data Protection Requirements

Software Requirements

  • Minimum requirement is vCenter Server 5.1, while vCenter Server 5.5 or later is recommended
  • VDP 6.0 supports the Linux-based vCenter Server Virtual Appliance and the Windows based vCenter Server
  • VDP .1 is not compatible with vCenter 5.5 or later
  • Web browsers must be enabled with  Adobe Flash Player 11.3 or later to access the vSphere Web Client and VDP functionality
  • Deploy VDP appliances on shared VMFS5 or later datastores to avoid block size limitations
  • Make sure that all virtual machines are running hardware version 7 or later to support Change Block Tracking (CBT) functionality
  • Install VMware Tools on each virtual machine that VDP will backup

Unsupported  Virtual Machine Disk Types

  • Independent
  • RDM Independent – Virtual Compatibility Mode
  • RDM Physical Compatibility Mode

System Requirements

VDP is deployed based disk capacity. The options are:

  • .5TB
  • 1TB
  • 2TB
  • 4TB
  • 6TB
  • 8TB
    Based on the disk/repository sizing the CPU/Memory resources minimum requirements are:

.5TB

1TB

2TB

4TB

6TB

8TB

CPU 4 x 2GHz 4 x 2GHz 4 x 2GHz 4 x 2GHz 4 x 2GHz 4 x 2Ghz
Memory 4GB 4GB 4GB 8GB 10GB 12GB
Disk Space 873GB 1.6TB 3TB 6TB 9TB 12TB

Explain VMware Data Protection Sizing Guidelines

  • Up to 400 virtual machines supported per VDP appliance
  • Up to 20 VDP appliances supported per vCenter
  • Available storage size of 8TB’s
  • Number of protected virtual machines and the dataset size
  • Types of data being backed up (OS files, documents, databases, etc)
  • Backup data retention period (daily, weekly, monthly, or yearly)
  • Data change rates

Identify VMware Data Protection Version Offerings

This is an interesting objective as of vSphere 6.0 there is only a single version offering product. Just note that earlier versions of VDP (5.x days) there were two versions of the product, VDP and VDP Advanced. With the release of vSPhere 6 it appears VMware has consolidated the “Advanced” edition of the product into one.  Let’s review some of the features in the product:

  • Agentless virtual machine backup
  • Integration with EMC Data Domain for additional scale, efficiency, and reliability
  • Agent support for application consistent backup and restores of Microsoft Exchange, SQL and Sharepoint (used to be in the “Advanced” version)
  • Granular File Level Restores (FLR)
  • Deployment of external proxies, enabling as many as 24 parallel backup operations
      For a deeper dive into the functions of features of VDP 6.0 have a look at the

VMware vSphere Data Protection 6.0 Technical Overview

    whitepaper.

Describe vSphere Replication Architecture

vSphere Replication is an included feature with VMware vSphere that provides hypervisor-based virtual machine replication. vSphere Replcation is an alternative over using storage-based replication technologies and allows for replicating to unlike storage (FC to NFS for example). vSphere Replication supports replicating between sites in the following configuration.

From a source site to a target site:

Site to Site

Within a single site from one cluster to another:

Single Site

From multiple source sites to a shared remote target site:

Multi Site Shared

vSphere replication supports both the Linux-based vCenter Appliance as well as the standard vCenter Server Windows installation. Combinations of both are supported, IE Windows based vCenter at your primary site and the Linux-based appliance at the DR target location.

Bundled with the vSphere Replication appliance are all the needed components  required:

  • Plug-in for the vSphere Web Client
  • Embedded database that stores replication configuration and management information
  • vSphere Replication management server
    • Configures the vSphere Replication server
    • Enables, manages, and monitors replications
    • Authenticates user and checks their permissions to perform vSphere Replication operations
  • vSphere Replication server that provides the core of the vSphere Replication infrastructure

Install and Configure VMware Data Protection

Prior to installing VDP there are few house cleaning items that need to be taken care of first:

  • Both forward and reverse DNS entries need to be configured
  • Configure NTP settings on both your vCenter Server and ESXi hosts
  • Minimum requirement is vCenter Server 5.1, vCenter Server 5.5 or later is recommended

Now, on with the show.

  • Log into the vSphere Web Client with administrative privileges
  • From the Home screen in the vSphere Web Client, select Hosts and Clusters in the right hand navigation
  • In the left hand pane select expand your Datacenter object and select the vSphere Cluster you wish to deploy VMware Data Protection to
  • Right click on the vSphere Cluster and select Deploy OVF Template
  • Provide the Source location for the installation. Options are either URL or Local File
  • Review the virtual appliance settings/details and click Next
  • Accept the EULA and click Next
  • Provide a Name and Location for the virtual appliance. Click Next
  • Select the Virtual Disk Format and Datastore location. Click Next
  • Provide the needed Networking information:
    • Management Network Portgroup
    • IP Protocol
    • Manual IP addressing
    • Select the check box to Power On the virtual appliance after deployment and click Finish

With the deployment of the appliance complete, if you pop open a console connection you will see a listing for the next steps to complete the configuration of the device:VDP_Console

  • From a web browser open :8543/vdp-configure/”>:8543/vdp-configure/”>:8543/vdp-configure/”>https://<VDP_IP_Address>:8543/vdp-configure/
  • Type root in the User field and changeme in the Password field, and then click Login
  • On the VDP Welcome screen click Next
  • Verify/Complete the Network Settings options, click Next
  • Select the appropriate Time Zone, click Next
  • Provide a Password for the VDP Credentials, click Next
  • For the vCenter Registration provide a Username and Password and related vCenter Server information. Use the Test Connection to validate the settings. Click Next when completed
  • For Create Storage select either Create New Storage or Attach Existing VDP Storage. If using new storage, select from the available storage capacities. Click Next
  • Provide the storage location/locations on the Device Allocation window. Click Next
  • For CPU and Memory assign the needed amount of RAM to the appliance. Click Next
  • Choose to enable the Product Improvement feed back. Click Next
  • On the Ready to Complete dialog choose to run the Run Performance Analysis on Storage Configuration. Note, this is optional. Click Next
  • Finally, from the Complete screen click Restart Appliance

Create a Backup Job with VMware Data Protection

  • Log into the vSphere Web Client with administrative privileges
  • From the Home screen in the vSphere Web Client, select VDP in the right hand navigation
  • Click the Backup tab
  • From the Backup Job Actions menu, select New to begin the Create a new backup job wizard
  • On the Job Type page, select the job type. For this example we are going to to select Guest Images. Click Next
  • For the Data Type select either Full Image or Individual Disks
  • On the Backup Sources dialog select the vCenter object or objects you wish to schedule in the backup job. These can be Datacenter, Clusters, groups of virtual machines, or individual virtual machines
  • On the Schedule page, select the schedule for the backup job and click Next
  • From the Retention Policy page, select a retention period and click Next
  • Provide a Name for the backup job
  • Review the settings on the Ready to Complete screen. Click Finish when ready

Install/Configure/Upgrade vSphere Replication

  • Log into the vSphere Web Client with administrative privileges
  • From the Home screen in the vSphere Web Client, select Hosts and Clusters in the right hand navigation
  • In the left hand pane select expand your Datacenter object and select the vSphere Cluster you wish to deploy vSphere Replication to
  • Right click on the vSphere Cluster and select Deploy OVF Template
  • Provide the Source location for the installation. Options are either URL or Local File
  • Review the virtual appliance settings/details and click Next
  • Accept the EULA and click Next
  • Provide a Name and Location for the virtual appliance. Click Next
  • Select the Configuration size of the appliance (Either 2 or 4 vCPU). Click Next
  • Select the Virtual Disk Format and Datastore location. Click Next
  • Provide the needed Networking information:
    • Management Network Portgroup
    • IP Protocol
    • DHCP or Static-Manual IP addressing
  • Provide a Root password for the appliance. Click Next
  • Review the binding to the vCenter Extension vService and click Next
  • Select the check box to Power On the virtual appliance after deployment and click Finish
  • One the deployment has succeeded Log Out and then back into the vSphere Web Client
  • The vSphere Replication icon will be presented on the Home screen

Complete the above steps on your secondary/DR site and vSphere Replication is ready for use!

 

Configure VMware Certificate Authority (VMCA) Integration with vSphere Replication

By default the vSphere Replication appliance will use self-signed certificates for authentication purposes. If you wish to upload your own certificates for stronger security you will need to access and log into the virtual appliance management interface (VAMI) of your replication appliance and complete the following:

  • Connect to the VAMI of the vSphere Replication appliance in a web browser (default URL is :5480″>:5480″>:5480″>https://<appliance-address>:5480)
  • Type the root user name and password for the appliance
  • Click the VR tab and click Security to review the currentl SSL certificate
  • Click Configuration
  • To enforce verification of certificate validity, select the Accept only SSL certificates signed by a trusted Certificate Authority check box.
  • Generate or install a new SSL certificate
  • Click Save and Restart Service to apply the changes

Configure Replication for Single/Multiple VM’s

  • Log into the vSphere Web Client with administrative privileges
  • From the Home screen in the vSphere Web Client, select VMs and Templates in the right hand navigation
  • In the left hand pane select a Datacenter object, click the Related Objects tab in the right hand navigation
  • Click the Virtual Machines tab under Related Objects
  • Either select a Single virtual machine or Multiple virtual machines using the Ctrl and Shift keys
  • Right-Click the virtual machine/virtual machines and click All vSphere Replication Actions > Configure Replication from the menu
  • Acknowledge the number of virtual machines to replicate
  • Verify the virtual machine validation and click Next
  • Select the Target replication site
  • Select the target location Datastore
  • Use the RPO slider or enter a value to configure the maximum amount of data that can be lost in the case of a site failure
  • Select a Guest OS Quiescing configuration, if applicable to the source virtual machine operating system
  • Review the settings and click Finish to establish replication

Identify vSphere Replication Compression Methods

Data compression is supported for vSphere Replication if the envirionment meets certain requirements. For full support of end to end compression both the Source and Target ESXi hosts need to be running ESXi 6.x. If you have a “mixed” environment of 6.x hosts and earlier the ability to compress data will be limited. Refer to the chart below:

Source ESXi Host Target ESXi Host Data Compression Support
Earlier than 6.0 Any supported version vSphere Replication does not support data compression for the source ESXi host, so the option Enable network compression for VR data is disabled in the Configure Replication wizard.
6.0 Earlier than 6.0 The ESXi host on the source site sends compressed data packets to the vSphere Replication server on the target site. The vSphere Replication server searches the target site for ESXi 6.0 hosts that can decompress the data. If no 6.0 hosts are available for the target datastore, the vSphere Replication server uses the resources of the vSphere Replication appliance to decompress the data, and sends the uncompressed data to the ESXi host.
6.0 6.0 This is an environment that supports full end-to-end compression. The ESXi host on the source site compresses the data, and the vSphere Replication server on the target site passes the data off to the ESXi host where the host decompresses the data and writes it to disk.

 

Recover a VM using vSphere Replication

Recovering a virtual machine by using vSphere Replication is a manual task. Prior to attempting the steps to recover a virtual machine, insure that the virtual machine at the source site is powered off. If the virtual machine is powered on and running an error message will be displayed reminding you to power it down.

    • Log into the vSphere Web Client with administrative privileges
    • From the Home screen in the vSphere Web Client, select vSphere Replication in the right hand navigation
    • Select the appropriate site/vCenter Server. Click on Monitor in the navigation bar
    • Choose the Incoming Replication tab, right-click the virtual machine to recover and select Recover
    • Select whether to recover the virtual machine with all the latest data, or to recover the virtual machine with the most recent data from the target site
    • Select the recover folder and click Next
    • If the virtual machine contains hard disks for which you have not enabled replication, select a target destination for the disk or detach the disk, and click Next
    • (Optional) Select Power on after recovery
    • Click Finish

Recovery_Options

Perform a Failback Operation Using vSphere Replication

After performing a successful recovery on the target vCenter Server site, you can perform failback. You log in to the target site and manually configure a new replication in the reverse direction, from the target site to the source site. The disks on the source site are used as replication seeds, so that vSphere  Replication only synchronizes the changes made to the disk files on the target site.

VCP5-DT Objective 3.1–Configure Automated Pools Using Linked Clones

Objective 3.1 – Configure Automated Pools Using Linked Clones

For this objective I used the following resources:

  • VMware View Administration documentation
  • VMware KB Article Differences Between QuickPrep and Sysprep

Knowledge

Identify Floating vs. Dedicated Assignments

  • Dedicated Pool – In a dedicated assignment pool, each user is assigned  to a desktop. Users receive the same desktop each time they login.
  • Floating Pool – In a floating assignment pool, users receive different desktops each time they log in.

User_Assignment

Identify Persistent Disk Settings

Identify the Disposable Disk Settings

The blueprint has each of these broken out separately, but as each option is configured on the same screen (see below) I thought I would tackle them together.

  • Persistent Disk – Allows you to store Windows user-profile data on a separate disk. Using a persistent disk allows you to preserve users data and settings even during View Composer tasks (refresh, recompose, and rebalance). Another added feature is the ability to detach and reattach the persistent disk to another virtual desktop. Note, this can’t be used as a migration tool from Windows XP to Windows 7. Persistent disks can only be reconnected to the same source/destination OS.
  • Disposable Disk – Use a disposable disk when redirecting the guest OS’s paging file and temp files. The disk size needs to be larger than the page file size of the guest OS.

Composer_Disks

Identify Pools Settings

Setting

Options

State
  • Enabled. After being created, the desktop pool is enabled and ready for immediate use
  • Disabled. After being created, the desktop pool is disabled and unavailable for use, and provisioning is stopped for the pool. This is an appropriate setting if you want to conduct post deployment activities such as testing or other forms of baseline maintenance.
Connection Server Restriction
  • None. The desktop pool can be accessed by any View Connection Server  instance.
  • With Tags. Select one or more View Connection Server tags to make the desktop pool accessible only to View Connection Server instance that have those tags. You can use the check boxes to select multiple tags.
Remote Desktop Power Policy Determines how a virtual machine behaves when the user logs off of the associated desktop
Automatically Logoff After Disconnect
  • Immediately. Users are logged off as soon as they disconnect
  • Never. Users are never logged off
  • After. The time after which users are logged off when they disconnect. Type the duration in minutes
Allow Users to Reset Their Desktops Allow users to reset their own desktops without administrative assistance
Allow Multiple Sessions Per User Allow a user to connect to multiple desktops in the pool at the same time.
Delete Desktop After Logoff Select whether to delete floating-assignment, full virtual machine desktops.

  • No. Virtual machines remain in the desktop pool after users log off.
  • Yes. Virtual machines are powered off and deleted as soon as users log off
Delete or Refresh Desktop on Logoff Select whether to delete, refresh, or leave alone floating-assignment, linked-clone desktops.

  • Never. Virtual machine remain in the pool and are not refreshed after users log off.
  • Delete Immediately. Virtual machines are powered off and deleted as soon as users log off. When users log off, View Manager immediately puts virtual machines in a Deleting state.
  • Refresh Immediately. Virtual machines are refreshed as soon as users log off. When users log off, View Manager immediately puts virtual machines in maintenance mode to prevent other users from logging in as the refresh operation begins.
Refresh OS Disk After Logoff Select whether and when to refresh the OS disks for dedicated-assignment, linked-clone desktops.

  • Never. The OS disk is never refreshed
  • Always. The OS disk is refreshed every time the users logs off
  • Every. The OS disk is refreshed at regular intervals of a specified number of days. Type the number of days
  • At. The OS disk is refreshed when its current size reaches a specified percentage of its maximum allowable size. The maximum size of a linked clone’s OS disk is the size of the replica’s OS disk. Type the percentage at which refresh operations occur.
Default Display Protocol Select the display protocol that you want View Connection Server to  use to communicate with View Clients

  • PCoIP – The default option wherever it is supported. PCoIP is supported as the display protocol for virtual-machine desktops and physical machines that have Teradici hardware. PCoIP provides an optimized PC experience for the delivery of images, audio, and video content for a wide range of users on the LAN or across the WAN.
  • Microsoft RDP – Microsoft Remote Desktop Connection (RDC) uses RDP to transmit data. RDP is a multichannel protocol that allows a user to connect to a computer remotely.
Allow Users to Choose Protocol Allow users to override the default display protocol for their desktops by using View Client
Windows 7 3D Rendering You can select whether to enable 3D graphics rendering if your pool comprises Windows 7 desktops that run on vSphere 5.0 or later, PCoIP is the selected protocol, and the Allow users to choose protocol setting is set to No.When you select this feature, you can configure the amount of VRAM that  is assigned to desktops in the pool. You can select at most two monitors for your View desktops. The maximum resolution of any one monitor is set to 1920×1200 pixels. You cannot configure this value
Max Number of Monitors If you use PCoIP as the display protocol, you can select the maximum number of monitors on which users can display the desktop.
When the Windows 7 3D Rendering setting is not selected, the Max number of monitors setting affects the amount of VRAM that is assigned to desktops in the pool. When you increase the number of monitors, more memory is consumed on the associated ESX hosts.
When the Windows 7 3D Rendering setting is selected, you cannot change the maximum resolution of any one monitor. The resolution is set to 1920×1200 pixels.
Max Resolution of Any One Monitor If you use PCoIP as the display protocol and you do not select
the Windows 7 3D Rendering setting, you should specify the
maximum resolution of any one monitor.
When the Windows 7 3D Rendering setting is not selected,
the Max resolution of any one monitor setting affects the
amount of VRAM that is assigned to desktops in the pool.
When you increase the resolution, more memory is
consumed on the associated ESX hosts.
When the Windows 7 3D Rendering setting is selected, you
cannot change the maximum resolution of any one monitor.
The resolution is set to 1920×1200 pixels.
Adobe Flash Quality Determines the quality of Adobe Flash content that is displayed on Web pages.

  • Do Not Control. Quality is determined by We Page settings
  • Low. This setting results in the most bandwidth savings. If not quality level is specified, the system defaults to Low.
  • Medium. This setting results in moderate bandwidth savings
    • High. This setting results in the least bandwidth savings
Adobe Flash Throttling Determines the frame rate of Adobe Flash movies. If you
enable this setting, you can reduce or increase the number of
frames displayed per second by selecting an aggressiveness
level.

  • Disabled. No throttling is performed. The timer interval is not modified
  • Conservative. Timer interval is 100 milliseconds. This setting results in the lowest number of dropped frames
  • Moderate. Timer interval is  500 milliseconds
  • Aggressive. Timer interval is 2500 milliseconds. This setting results in the highest number of dropped frames

Pool_Settings

Identify Provisioning Settings

Setting Description
Enable Provisioning Instructs View Manager to create (provision) desktops for the pool
Stop Provisioning on Error Desktop provisioning (creation) will stop if an error is encountered during desktop creation
Virtual Machine Naming
  • Desktops can be provisioned by manually specifying a list of desktop names or by providing a naming pattern and the number of desktops to be created in the pool.For manually specifying desktop names follow these guide lines:
  • Type each desktop name on a separate line
  • A desktop name can have up to 15 alphanumeric characters
  • You can add a user name to each desktop entry. Use a comma to separate the under name from the desktop name
  • To leverage automated deployments View uses a “token” to apply a unique number to identify each desktop. You can place the token anywhere in the desktop name.
  • For example, if you type amber-{n:fixed=3}, View Manager replaces {n:fixed=3} with a three-digit number and creates these desktop names: amber-001,amber-002, amber-003, and so on
Max Number of Desktops The maximum number of desktops that will be provisioned for the pool
Number of Spare (Powered On) Desktops Number of desktops that will be available and “idle” to accept in coming connections
Provision Desktops on Demand Desktops will be provisioned “as needed” as users connect
Provision All Desktops Up-Front All desktops for the pool are  provisioned (see Max Number of Desktops)

Provisioning_Settings

Identify vCenter Server Resource Settings

View Composer leverages vCenter for it provisioning operations. By default vCenter is configured to allow “Max concurrent provisioning operations” at 8 and  “Max concurrent power operations” at 5. The options can be modified in View Administrator by going to View Configuration –> Servers –> Highlight your vCenter and click “Edit”. Under “vCenter Server Settings” click the “Advanced’ icon and modified the settings as needed:

vCenter_Resources

Identify Guest Customization Settings (e.g., QuickPrep, Sysprep)

Note –  Information taken directly from VMware KB Article Difference Between QuickPrep and Sysprep

QuickPrep is a VMware system tool executed by View Composer during a linked-clone desktop deployment. QuickPrep personalizes each desktop created from the Master Image. Microsoft Sysprep is a tool to deploy the configured operating system installation from a base image. The desktop can then be customized based on an answer script. Sysprep can modify a larger number of configurable parameters than QuickPrep.

During the initial startup of each new desktop, QuickPrep:

  • Creates a new computer account in Active Directory for each desktop
  • Gives the linked-clone desktop a new name
  • Joins the desktop to the appropriate domain
  • Optionally, mounts a new volume that contains the user profile information

This table lists the main differences between QuickPrep and Sysprep

Function QuickPrep Sysprep
Removing local accounts No Yes
Changing Security Identifiers (SID) No Yes
Removing parent from domain No Yes
Changing computer name Yes Yes
Joining the new instance to the domain Yes Yes
Generating new SID No Yes
Language, regional settings, date, and time customization No Yes
Number of reboots 0 1
Requires configuration file and Sysprep No Yes

 

Happy Studying!

-Jason