XenApp 7.6 Legacy ICA Support Wyse VX0 / V10L

Wouldn’t it be great if you could support your old Wyse VX0 / V10L after migrating to Citrix XenApp 7.6?  I was always under the impression that I would need to replace my Wyse VX0 clients with Windows Embedded thin clients in order to have my users connect to our newly created XenApp 7.6 site.  As it turns out, you can connect your legacy Wyse VX0 thin clients to XenApp 7.6 after all.

The key to accomplishing this incredible feat was the PNAgent Lite server settings on the Wyse VX0.  PNAgent Lite settings are located when clicking on Desktop – System Setup – Network in the Servers tab.

The PNAgent/ Lite Servers: setting should be populated with the StoreFront URL using the FQDN (see example below):


XenApp 7.6 / PNAgent Lite Servers

Upon reboot, the user will be prompted for credentials.  Once authenticated the user will have access whatever Apps he/she is authorized to use.

#legacy-ica-support, #pnagent-lite, #wyse-v10l, #wyse-vx0, #xenapp-7-6-2

Citrix CCA-V: Managing – Notes2

Manage Device Collections, Target Devices, and vDisks

Convert Private Mode vDisk to Standard Mode vDisk

Power down the VM to remove the lock associated with the VM.  In the Provisioning Services Console open the vDisk Properties and change Access Mode from Private Image to Standard Image.

Automation process for creating multiple VMs for Machine Catalog

Launch Streamed VM Setup Wizard

  • Requirements: Hypervisor connection and plate VM
  • Existing Provisioning Services Device Collection
  • A standard-mode vDisk for the selected VM template

A template VM in XenServer needs to be created prior because a container needs to exist for the settings that correspond with VM hardware.

In XenCenter:

  1. Create new VM.
  2. Name it Master Template
  3. Boot from Network
  4. Diskless VM
  5. Do not start automatically
  6. Convert to Template

In Provisioning Services Console:

  1. Launch Streamed VM Setup Wizard
  2. Hypervisor connection to Citrix XenServer (or other Hypervisor)
  3. Select template
  4. Select vDisk
  5. Identify Collection
  6. Select number of VMs to create
  7. Choose to Create New Accounts in AD
  8. Choose proper AD OU and specify naming scheme (pvsdesktop##)

Process takes less than MCS.

In Citrix Studio Create Machine Catalog that interfaces with Provisioning Services:

  1. Create Machine Catalog
  2. Desktop OS Catalog
  3. Citrix Provisioning Services
  4. Choose Random Desktop
  5. Identify Provisioning Services server to connect to
  6. Identify Site and Collection
  7. Name Machine Catalog
  8. Associate with Delivery Group to deliver desktops to users

To add machines at a later time, run the Streamed VM Setup Wizard and add additional VMs.  Afterward, add them in Citrix Studio Machine Catalog.

Automation using XenDesktop Setup Wizard – create VMs in Provisioning Services and create Machine Catalogs in Citrix Studio

XenDesktop Setup Wizard can be launched in Provisioning Services Console under Site.


  1. XenDesktop Controller with permissions for current user
  2. Configured XenDesktop Host Resources
  3. Standard-mode vDisk for the selected VM template


  1. Launch XenDesktop Setup Wizard
  2. Connect to XenDesktop Controller
  3. Select XenDesktop Host Resources
  4. Select VM template and identify VDA version
  5. Choose the vDisk
  6. Create a new catalog or use an existing catalog
  7. Select the number of machines to create
  8. Choose the boot mode
  9. Select the AD OU


Update Tasks

vDisk Update Management Tool – to be discussed later

Updating a Base vDisk in Provisioning Services Console

  • Create new vDisk Version – Creating a new vDisk Version, creates a new differencing disk off of the base disk.

The differencing disk becomes a location on which to apply changes to.

The new version is created as a maintenance version.

  • In device collections, a target device can be selected and the Type can be changed from Production to Maintenance.  Once the VM is started up, it provides a menu from which to boot into maintenance mode.  The VM is then operating off of the differencing disk.  It provides for changes without impacting the base disk used by other users.
  • After updating the VM it should be powered down.
  • In Provisioning Services vDisk Pool, there are now two version.  The maintenance version has been updated.  Click Promote to Test or promote it to Production.  The base version still exists.  Users need to reboot the VM to be using the new version.  Once all VMs have been rebooted, the Merge function is used to get rid of unnecessary .vhd files by selecting Merged Base  and Production.

The two previous versions will have a red X and can be kept in case you need to revert back.



#cca-v, #citrix-xenapp-7-6-cca-managing, #managing, #provisioning-services, #vdisks

Citrix CCA-V: Managing – Provisioning Services Notes 1

Citrix Studio does not include Provisioning Services management.  A separate Provisioning Services Console is used to for managing PVS.

For an existing setup, in the Provisioning Services Console, a Farm will already exist and a Site exists within the Farm.  This is the location where all vDisks will be created.  For an existing setup, a server will already exist in the Servers node.

Also residing within  the Site is the Stores node.  A store should exist already and under Store Properties>Paths, a path to the location of the existing store is present.  In the case of Standard Mode vDisks, a different path can be specified for Differential Disks.  By default Deferential Disks will be stored in a sub-folder within the default store path.

Step 1:

Create new vDisk template.

By right-clicking over vDisk Pool in the Provisioning Services Console, a vDisk can be created.  This vDisk will include all information that exists in a template virtual machine that already exists in XenServer.  The new vDisk will reside in the Site and in the Store.  A file name needs to be  specified for the vDisk.  The size of disk can be modified as can be the Type and also Block size.  The defaults should work fine in most cases.

The vDisk creation process happens very quickly.  A new .vhd file will have been created in the default location of the Store directory.

Step 2:

Update PVS target device software that exists in the VM.

In XenCenter, create a clone of an existing Master Image and rename the clone and power on the VM.  Log in to the template VM from the XenCenter by selecting the VM and selecting the Console Tab.  PVS target device software needs to be installed on the VM.

As a best practice, before launching the Imaging Wizard at the end of the PVS target device software installation, it is recommended to run the Provisioning Service Device Optimization Tool on the VM first.  This tool helps improve VM performance by disabling some Microsoft services that can negatively impact performance on a VM.

Step 3:

Launch Imaging Wizard.

Identify the server that the VM image will be transferred to.  Select the existing vDisk created in Step 1.  Select the type of Microsoft Volume Licensing.  It is important that for Target Device Name, a name is entered that is different from the Active Directory name of the VM.

After clicking Finish, Provisioning Services Imaging Wizard will prompt to reboot and modify the BIOS boot order so Network boot is the first item in the boot order.  That can be accomplished by powering down the VM and modifying Boot Options in the VM Properties in XenCenter.  The VM will now boot in PXE after it is powered back on.  The Provisioning Services Imaging tool is presented upon logon to the VM.  At this point data is being transferred to the vDisk; the process can take a while.  The log will contain any errors with the data transfer.

In the Provisioning Services Console, under Device Collections, a new device will now show.

In the vDisk Pool, the vDisk will now show a lock; this is to protect the template from corruption.  Locks can be managed by right-clicking on the vDisk and selecting Manage Locks.

Right-clicking on the vDisk and selecting Show Usage will show mappings between target devices and vDisks.  Any VMs that are using the vDisk must be powered off prior to removing the lock off of a vDisk.

The .vhd file that was created is in Private vDisk Mode by default.  Private vDisk Mode is not usually used in a production environment.

Link VM Container to vDisk.

VMs can be created manually in XenCenter and linked to a vDisk such as the one already created.  When creating a new VM manually, instead of using a Virtual Disk, the option to create a Diskless VM that boots from the network should be selected.

To attached to the vDisk, the machine should be configured to boot from the network.  The MAC address is the unique identifier needed to link the VM to the vDisk.  The MAC address can be found under the VM’s Networking Tab in XenCenter.

In the Provisioning Services Console, create a new Target Device under Device Collections.

Set to boot from a vDisk.

Enter the MAC address information.

Under the Target Device Properties, in the vDisks tab, associate the target device with the vDisk.

#citrix-xenapp-7-6-cca-managing, #create-vdisk-template, #launch-imaging-wizard, #link-vm-to-vdisk, #provisioning-services, #pvs, #update-pvs-target-device

Citrix XenApp Application Error: “Cannot connect to the Citrix XenApp Server. SSL Error 61

Citrix XenApp Application Error: “Cannot connect to the Citrix XenApp Server.  SSL Error 61: You have not chosen to trust “certificate authority”, the issuer of the server’s security certificate.

You may receive SSL Error 61 when attempting to launch a Citrix XenApp application through Citrix Netscaler using  the legacy Program Neighborhood Agent (PN Agent).

As explained below, certificates are signed with SHA256 which older versions of the ICA client do not support.

Ensure that clients have the latest version of Citrix Receiver installed.


I ran into this issue today after having setup a new Netscaler VPX access gateway with new server cert linked. We are migrating from Citrix Secure Gateway.

When trying to establish the Citrix session via the Access Gateway, I got the same error. Of course the ICA client version we are using is 11.x

The reason for the error: Server certificates are now digitally signed using SHA256 algorithm, not SHA128. The older versions of the ICA client do not support this.

So the answer is to upgrade the client to the Online Plug-in 12.3 if you need PNAgent and / or Web Client. Upgrade directly to Citrix Receiver if you don’t need PNAgent.

#cannot-connect-to-the-citrix-xenapp-server, #citrix-receiver, #citrix-xenapp-application-error, #netscaler-access-gateway, #sha256, #ssl-error-61, #you-have-not-chosen-to-trust-the-issuer-of-the-servers-security-certificate

XenServer 6.5 – Add another hard drive

On a XenServer machine that is already running, you may want to add another hard drive.  After adding the hard drive you then notice it is not detected by the system.


To ensure that the new internal hard drive is available as storage repository, complete the following procedure:

  1. Install a hard drive on a XenServer.
  2. Run the following command from the command line interface to display the installed disks:
    fdisk -l
  3. Search for the new hard drive in the list. It will be the last on the list and it is indicated as /dev/sdc. c is the position it is in. Generally, it starts at a, and the list continues. You can verify the device path using the SCSI ID in /dev/disk/by-id directory by listing out the contents
  4. Run the following command from the command line interface:
    xe sr-create name-label=<Name of Storage> shared=false device-config:device=<Path of the Storage device> type=lvm content-type=user
    • Name of Storage is the name of the Storage Repository you require
    • Path of the Storage device is the path as noted in the preceding tasks, /dev/sdc)

    Now, the installed hard drive is visible in the XenServer Console.


#xenserver-add-another-hard-drive, #xenserver-hard-drive-install

XenServer Install Error – Hardware Virtualization Assist Support is Not Available on this System

“Hardware Virtualization Assist Support is Not Available on this System…”

Error occurs when the XenServer installation does not detect Virtualization Support enabled for the processor.  There first thing to do to resolve this is to enable Virtualization Support in the BIOS of the machine.  For this, the processor must be capable of supporting virtualization.

Another common scenario:

“Hardware Virtualization Assist Support is Not Available on this System…”

Error can also occur after Virtualization Support is enabled on the physical machine but XenServer is being installed on a VM that was created in VirtualBox or some other desktop virtualization technology as a means of testing and/or lab environment.

AMD-V/Intel-VT are not often passed to the Virtual Machine as was pointed out here: https://www.experts-exchange.com/questions/27899552/Citrix-XenServer-on-VMWare-Installation-Error-Hardware-Virtualization-Assist-Issue-with-AMD-V-CPU.html

However, it appears that VMware Workstation 12 Player is able to pass on AMD-V and Intel-VT on to the virtual machine that will host XenServer.  VMware Workstation 12 Player can be found here:


#amd-v, #intel-virtualization-support, #intel-vt, #virtualbox-xenserver, #vmware-workstation-player-xenserver

Polycom Error “Image is not compatible with phone”…”Application Not Present”

“Image is not compatible with phone” and “Application not Present”

error messages can occur after selecting the Format File System option on a Polycom IP phone and if, upon booting, the IP phone downloads an update to the bootROM.

That is, the bootROM is updated but the phone firmware remains the same version, then,”Image is not compatible with phone” and “application not present” will display.

There are two solutions for correcting these error messages:

“Image is not compatible with phone” and “Application not Present”

Option 1: Downgrade to the previous bootROM.

Option 2: Update phone firmware.

See detailed instructions on Downgrading or Updating Polycom UC Software in the following link:



#application-not-present, #image-is-not-compatible, #polycom-bootrom, #polycom-downgrader, #polycom-ip-335, #polycome-update-downgrade-uc-software