XenApp and XenDesktop in a Single AMC

A Guide to Console Consolidation

As an administrator of both XenDesktop and XenApp environments, I’m absolutely sick of multiple consoles. I’ve finally managed to easily integrate XenDesktop and XenApp administration into a single console (AMC). Unfortunately, we’re unable to integrate the “Presentation Server Console” that is still used for manging policies.

While alternative methods may exist, I know the following steps will work.

  1. On your XenDesktop 3.0 Media, run autorun.exe
  2. Select Install Optional Components.
  3. Install Management Consoles.
  4. Install XDE300AMC004 (Download here).
  5. Open the Access Management Console, you should see Desktop Delivery Controller in the left pane. If you do, you may continue.
  6. On your XenApp Media (I’m using 4.5 media) navigate to Administration\Access Management Console\Setup\
  7. Run ASC_PresentationServer.msi
  8. After following the prompts, you should now have Presentation Server as an option in the left tree below Desktop Delivery Controller.

If you also want other snap-ins you can find them on your media under Administration\Access Management Console\Setup\. There are snap-ins for Web Interface, etc. as well.

Hardware Planning Tips for XenDesktop 3.0, Part 1

Planning for your new XenDesktop environment can be a tough process. Being a relatively fresh technology, there aren’t too many places to find straight answers regarding scalability. I intend on changing that. Here are a few helpful tips and straight answers to help you decide whether you have the hardware already, or need to purchase new. This will be a multi-part series, only some aspects will be addressed in this initial post.

Assumptions

  • XenDesktop 3.0, Platinum Edition.
  • XenServer 5.5.
  • Provisioning Server 5.1.
  • XenApp 5.0, Platinum Edition.
  • Windows Vista Business (x86)
  • 300 Users, all will use XenDesktop for OS and XenApp for Application Delivery.
  • Endpoints are XP Embedded Thin Clients.
  • Single Location, Single Data Center.
  • Users occasionally want to access the environment from home.
  • Users are “Task Workers”

While this scenario is pretty simple, I’ll be more than happy to help you with your questions in the comments, via Twitter, or e-mail.

In the next post, I’ll discuss Virtual Machine Specifications and choosing the right server specifications for your XenServer hosts.


Enabling Logging for Citrix XenDesktop 3.0

When troubleshooting problems, it’s essential you have as much information is possible. Logging is the best passive way to achieve this. Even in 2009, we’re editing files in Notepad…

Virtual Desktop Agent Logging

1.     Create a new directory called c:\ctxlogging\. The Network and Local service accounts should have write access. If you are using standard vDisks, I recommend putting the log file on local storage so that it persists after log out.

2.     Navigate to c:\Program Files\Citrix\Virtual Desktop Agent\

3.     Open WorkstationAgent.exe.config with your Text Editor of Choice.

4.     Find the <appSettings> tag.

5.     Within the <appSettings> tag, insert the following two lines:

<add key="LogToCDF" value ="1"/>
<add key="LogFileName" value ="C:\ctxlogging\vda.log"/>

6.     Restart the Virtual Desktop to start logging.

Desktop Delivery Controller Logging

1.     Create a new directory called c:\ctxlogging\. The Network and Local service accounts should have write access.

2.     Navigate to c:\Program Files\Citrix\VMManagement\

3.     Open CdsPoolMgr.exe.config with your Text Editor of choice.

4.     Find the <appSettings> tag.

5.     Within the <appSettings> tag, insert the following two lines:

<add key="LogToCDF" value ="1"/>
<add key="LogFileName" value ="C:\ctxlogging\ddc_cdspoolmgr.log"/>

6.     Navigate to c:\Program Files\Citrix\Desktop Delivery Controller\

7.     Open cdscontroller.exe.config with your Text Editor of choice.

8.     Find the <appSettings> tag.

9.     Within the <appSettings> tag, insert the following two lines:

<add key="LogToCDF" value ="1"/>
<add key="LogFileName" value ="C:\ctxlogging\ddc_cdscntrl.log"/>

10.  You will need to reboot your DDC for this to take effect. If you have more than 1 DDC, perform these steps on all of them.

Some of the paths may vary depending on OS (x64) and whether you changed the default install paths during installation.

EDIT 8/23/09: Added CTX Article, http://support.citrix.com/article/CTX117452 and CTX Article for Enabling PortICA Logging http://support.citrix.com/article/CTX118837

The user Network Service will need Full Control over the log directory. While this is not officially documented by Citrix, it has been reported by others. (Thanks to Alistair Gillespie)

Making Changes to a vDisk in XenDesktop & Provisioning Server

I’m often asked how to update a vDisk for use with XenDesktop, so I figured I should publish my answer.

1. Navigate to your store via Windows Explorer, Copy the .VHD file currently in use, then Paste it.

2. Rename it – We use A,B,C,D and rotate each time we update.

3. Open the PvS Console, Navigate to your vDisk Pool.

4. Right Click on vDisk Pool, Select Add Existing vDisk.

5. Make sure your Store and Server are correct, then click Search.

6. Select the new vDisk and click Add then Close.

7. Open your vDisk Pool in the PvS Console.

8. Right Click on the new vDisk, click Properties.

9. Click Edit file properties…

10. Change the Access Mode to Private Image and adjust your revision numbering.

For the next steps, I use a VM that is exactly like the VMs the image will be used on. This method is documented in the XD Getting Started Guide and is referred to as BaseDesktop1.

11. Expand Device Collections.

12. Assign your BaseDesktop1 (or whatever you’ve named it) the new vDisk that is in Private Mode.

13. Boot the VM in your Hosting Infrastructure of choice.

14. Make Changes.

15. Shut Down VM.

16. Change the vDisk to Standard Mode.

17. Assign vDisk to whichever VMs you wish.

These steps should suffice to answer most questions regarding updating vDisks for XenDesktop. I’ll be happy to assist you if you have more questions or require clarification. Just leave a comment.