DHCP Conflict Detection- Realtime Scenario Issue: VMs are placed in Maintenance mode automatically.
A quick investigation revealed most of the desktop VMs had been placed in maintenance mode by the Desktop Delivery Controller. It will do this automatically if the VMs do not register after several reboots, see CTX126704 for the registry entries that control this behaviour.
After much investigation looking at the PXE and TFTP services on the Provisioning Servers, checking DHCP scopes weren’t full, confirming switch ACLs and VLANs were correct and more, It was found that the setting on the DHCP server for Conflict Detection had been recently enabled.
PXE-E32: TFTP open timeout Symptoms:
During a Ardence Client boot, the following error message is received:
“PXE-E32: TFTP open timeout"
Cause:
This error message indicates that the TFTP open request was not acknowledged and that you will need to verify that the TFTP service is running.
If an Ardence Client encounters a “PXE-E32: TFTP open timeout” error message during the boot process, verify the following:
1. Spanning Tree is disabled on the switch port connected to the Client.
XenDesktop provides full and partial power management of machines in desktop groups.
You can power manage virtual machines not physical ones. The ability to fully or partially control power management depends on how virtual machines in the desktop group are allocated to users or user devices. Permanently allocated machines can only be partially power managed.
In addition, note that desktops can be in one of these states:
In private or shared desktop groups: unallocated (and therefore unconnected) In private desktop groups: Permanently allocated and unconnected (but ready to be connected) Permanently allocated and in use In shared desktop groups: randomly allocated and in use At any given time, private desktop groups typically contain both permanently allocated and unallocated machines.
VM hosted apps allows you to isolate applications and host them from virtual machines or physical computers, including blade servers, running Windows single-user desktop operating systems. Users access these applications through a Web browser, the Citrix online plug-in, or Citrix Receiver, just as they would applications hosted from XenApp servers running Microsoft Terminal Services. VM hosted apps allows you to host applications that otherwise must be installed locally or require extensive compatibility testing on XenApp servers.
Note: The below process works only for esx version till 4.X. Not for 5 and 5.X
Changing your host’s network name and SSL certificate
When you first install ESXi your host will be given a hostname of “localhost” and domain of “localdomain”. You can change this at the console or with the VI client.
Using the Console 1) Press (Customize System) 2) Select Configure Management Network 3) Select DNS Configuration 4) Select the option “Use the following DNS server addresse and hostname” 5) In the hostname enter the hostname and domain for your host.
There are certain situations in which HDX MediaStream for Flash failsfor certain Website URLs. This happens as a result of certain Web pages that have been designed to work in a way that is not compatible with our HDX architecture. These failures cannot be detected, so HDX has been designed to create and use a Dynamic Blacklist to remember Websites that provoke these failures. In these situations, the HDX feature falls back to server-side Flash rendering for the current browser tab that provoked the failure.
Till XenApp 6.5 or XenDesktop 5.X In order for the users to access the desktops published in XenDesktop, they mst have client installed in their local machines. By default, Clients will be available at the Web Interface folder(at C:\Program Files (x86)\Citrix\Web Interface\5.4.0\Clients\Windows\Receiver). But in the webinterface.conf file we have ClientIcaWin32=Filename:Citrixonlineplugin.exe, which means when users who doesn’t have the receiver insalled, try to open the WI site, it searches for citrixonlineplugin.exe file and in the Receiver folder(given above), we dont have that exe and it will be redirected to Citrix.
Symptom
Citrix Microsoft Management Console (MMC) based administrative consoles such as Access Management Console, Delivery Services Console take an extended time to start. Once running, the consoles operate normally.
Cause
Citrix MMC based administrative consoles feature components that are written using the Microsoft .NET Framework. Citrix signs these .NET based components with an Authenticode signature as an added security mechanism.
In situations where a Citrix MMC based administrative console is run from a computer without internet access, Windows is unable to verify the Authenticode signature, and as a result this causes a delay during the startup of the console.
The personal vDisk feature in XenDesktop retains the single image management of pooled and streamed desktops while allowing people to install applications and change their desktop settings.
Unlike traditional Virtual Desktop Infrastructure (VDI) deployments involving pooled desktops, where users lose their customizations and personal applications when the administrator alters the base virtual machine (VM), deployments using personal vDisks retain those changes. This means administrators can easily and centrally manage their base VMs while providing users with a customized and personalized desktop experience.
XenDesktop Active Directory Configuration Wizard is not available in XenDesktop 5.x.
Background
If you decide to use Active Directory-based controller discovery in your environment, in the previous versions of XenDesktop, you could use Active Directory (AD) Configuration Wizard to create and configure the AD Organizational Unit (OU) for the farm but in XenDesktop 5.x, you have to use PowerShell script to perform that configuration.
AD-based Controller Discovery
Complete the following in order to configure your environment for AD-based controller discovery:
