Monthly Archives: June 2011

How to delete a newly created predefined dhcp option – windows server 2003

OS: Windows Server 2003

Service: DHCP Server

Problem: sometimes you might need to create a predefined dhcp option on your Windows 2003 dhcp server.

and sometimes you might select a wrong data type for your option.

The problem is that when you try to delete the newly created option the delete button is inactive!!!!


Solution: from the command line run the following:

netsh dhcp server \\servername delete optiondef optionnumber


  • servername = name of your server
  • optionnumber = number of the newly created option

Discovering VUEM – VirtuAll User Environment Manager

Written by Pierre Marmignon, a Citrix Professional, VUEM – VirtuAll User Environment Manager is a tool that facilitates management and maintenance of both virtual and physical desktops.

VUEM has been created to complement Citrix User Profile Manager. With VUEM it is now easier to manage network printers and drives, environment variables, registry values, file associations and more without using login script and all from a central console.


VUEM can be used carry out the following tasks:

  • Applications Shortcuts
  • Network Printers
  • Network Drives
  • Virtual Drives
  • Environment variables
  • Registry Values
  • Ports (COM/LPT) Mapping
  • Ini Files Entry
  • External Tasks Execution
  • File / Folder Operations
  • File Associations Management
  • User DSN Creation
  • Fast Logoff (only for virtual desktops)
  • CPU Management
  • Memory Management
  • Processes Management


VUEM’s architecture is pretty simple, it includes:

  • A centralized management console

The Management Console


  • Two types of client, one graphical and one console agent. The console agent executes command line actions and exits after all tasks are executed. The graphical agent executes tasks within a splash screen and then can be accessible through a systray icon; users can refresh settings and manage printers.


UI client systray menu

  • SQL Server Database. Support for versions 2000 to 2008 R2, including Express. The VUEM database model has been validated on environments containing more than 10.000 users.


There are two kinds of license editions:

  • Community License, free, doesn’t include maintenance and support.
  • Subscriber License, has an annual cost, includes a maintenance and support package.

For more info visit the product page at:


Citrix License Server 11.9 installation hangs

OS: Windows 2003 32-bit

License Server version: 11.9


Issue: when installing Citrix License Server 11.9 on a Windows 2003 box the installer stays forever on “Please wait while setup wizard installs…” and the installation doesn’t finish successfully.


Solution: make sure you have .NET 3.5 sp1 and, more importantly, install the following Microsoft Security Patch: KB956572.


HOW TO: stream 3.2.1 on XenApp 6

This short “how to” explains how to create a streamed profile of the 3.2.1 suite and stream it to server.

Profiling applications in Citrix’s jargon means creating a sort of box containing an application with all its files and registry entries. The application is then streamed, see delivered, to a server or a client and then executed into a kind of sandbox, almost isolated from the rest of the OS. This means that, for example, on one Windows server I can run multiple version of Microsoft Office at the same time, keeping them separated and avoiding any kind of conflict between them.

Well, after this little explanation… let’s go ahead and do the intriguing part!


I’d say that you have to be familiar with application streaming but, actually, the process is straightforward and very easy to follow. There are only two details that need to be considered and they regard the first-run wizard and the default file format, we’ll look at this later in the article.

Of course the first thing to do is to make sure that we have the appropriate environment to make a working profile. The following is a checklist of the essential components we need:

  • A Windows Server (2008 R2 in my case)  configured exactly in the same way as your farm servers, this means same service packs, same patches, same language pack and same software installed (except for the offline plugin, that has not to be installed on the profiling server). The server may or may not be a member of the Citrix farm.
  • The server must not be used to deliver applications, it will only be used as a Streaming Profiler, it should remain as clean as possible. Remember that if a software application is present on the streaming profiler and not on the farm server it will probably create you problems when streaming the application to your server.
  • Citrix Streaming Profiler must be installed on the server, it can be found on the XenApp 6 DVD or directly downloaded from
  • A copy of is required it can be downloaded here:
  • The OpenOffice installation files must be installed. Run the OpenOffice installer, extract the installer files into a directory of your choice and stop the installation process. The files we need to carry out the installation are those now located in the directory you choose, the original installer can be deleted.

Before creating the profile, we need to take care of two aspects:

  1. Default file format: by default OpenOffice saves files in its format, if you want to change the default behavior and make the application save files in the Microsoft format you have to make some adaptations and they are well described here.
  2. First-run wizard: if you don’t want your users to be annoyed by the first-run registration wizard you need to go to this page: openoffice wiki and download the oxt file for the version of OpenOffice you downloaded.Save it in a directory on the profiler server. On the same directory of the oxt file create a batch file (anything.bat) containing the following text:

cd \
“c:\program files (x86)\ 3\program\unopkg” add –shared c:\DisableFirstStartWzd_ooo321.oxt

Profile creation

  • On the server go to Start > All Programs > Citrix > Streaming Profiler > Streaming Profiler


  • Click New Profile
  • Click next
  • Give a name and click next
  • Leave User Updates check box clear and click next
  • If you need to link additional profiles choose them now, otherwise click next
  • Make sure that on the list of Target Operating Systems you see the system on which you will stream the package, if you are profiling on Server 2008 R2 x64 you’ll be able to stream the package on 2008 R2 x64 servers and maybe on windows 7 x64 clients


  • Click next
  • Choose Advanced Install
  • Select “Run Install Program or command line script”


  • Click browse and find the setup file for OpenOffice in the folder you extracted
  • Click next and launch installer
  • Enter company and user name and click next
  • Choose custom and click next
  • On-line Update, Windows Explorer Extensions and Quickstarter are not useful in a XenApp installation, uncheck them:


  • Click next and clear the box to create a Start Link on Desktop
  • Click Install and finish the installation
  • Click Finish to return to the profiler
  • Click Next
  • Select Perform Additional Installations and click Next
  • Select “Run Install Program or command line script”
  • Enter the name and path of the batch file you created in the first text box and click next
  • Click Launch Installer
  • You should see the oxt installation:


  • Click next and select Finish Installations
  • You should now see a list of the main applications that you allowed at installation
  • Try to run any of them to see if they work properly
  • Click next, next, next and Finish
  • When the process is completed and if you haven’t any modifications to make, you can save the profile on a file share

Application publishing

You can now publish the applications you just profiled.

  • Open the Citrix Delivery Services Console and start to publish an application as you would do for a normal installed application
  • Give it a name and the description you like
  • When you have to choose the type of application to publish choose “Accessed from a server” and “Streamed to server”:


  • Go ahead and click browse to find your profile on the share you previously saved it, then from the list of applications choose the one you want to publish (e.g. Writer, Calc, etc…)
  • Go ahead and choose the servers on which to stream the application and the users that will have access to it
  • Make sure that each XenApp server you are using to run the application has the offline plugin correctly installed (it runs as a service and you can find it in the services management console)

You can now access and run the application!

Configure XenApp 6 to return FQDN instead of IP in the ICA file

XenApp’s default behavior is to provide clients with an ICA file (launch.ica) containing the IP address of the XenApp server chosen to provide the application or content required.

The default behavior can be modified in order to provide clients the server’s FQDN instead of its IP. Obviously, the clients must be able to resolve the address.

The following steps shows how to do that:

  1. Enable DNS address resolution on the XenApp 6 Server
  2. Edit the WebInterface.conf configuration file
  3. Wait for the default interval or run gpupdate
  4. Recreate the local host cache if necessary


1 – Enable DNS address resolution on the XenApp 6 Server

DNS Address Resolution must be enabled on the XenApp farm in order to return the fqdn through the xml service:

  • Open the Citrix Delivery Services Console
  • Edit an existing computer policy or create a new one

  • On the Server Settings section enable “DNS Address Resolution”

2 – Edit the WebInterface.conf configuration file

Edit the WebInterface.conf file located under: \Inetpub\wwwroot\Citrix\MetaFrame\conf\WebInterface.conf:

  • Find: AddressResolutionType
  • Replace “ipv4-port” with “DNS-port”

3 – Wait for the default interval or run gpupdate

Wait for the default interval  for the policies to take effect or run gpupdate /force on your XenApp servers

4 – Recreate the local host cache if necessary

If the ICA file still returns the IP address, recreate, on the XenApp servers, the local host cache with the following commands (the server must be able to contact the Data Store):

  • net stop imaservice (stops the IMA service, necessary to recreate the LHC, alternatively use the services console)
  • dsmaint recreatelhc
  • net start imaservice (restarts the IMA service, alternatively use the services console)


For more information visit: