Tag Archive: Troubleshooting

I had a user report when he uses the Citrix Receiver to access our XenDesktop environment all sessions would reconnect and open windows. He liked XenDesktop but was annoyed by getting all his sessions opened. I explained that it was by design and that the receiver was “helping” him by giving him those sessions as he would need them anyway. He would have none of that. He wanted the control to start as he saw the need.

There is a way to disable this feature. I don’t know if the ability was always present but a newer version of the receiver might be needed. You will know if you follow these steps and the options aren’t there.

What to do:

  1. The receiver should already be installed.
  2. Look on the toolbar to the bottom right for the “^” and click it (this is for Windows 7 and up).
  3. Look for the Citrix Icon which looks like a “C” and right-click it.
  4. Select Advanced Preferences.
  5. Click the Settings Option link.
  6. Click the Reconnect Options tab.
  7. De-select Enable for Workspace Control Support.
  8. Click OK

This will restart the Receiver and should disable the starting of all disabled sessions when a user connects via the receiver. I did have an instance where it required a reboot but that should not be needed.



Citrix VDA version check

I had a question as to the VDA version installed on a Linux virtual machine. I didn’t find anything obvious through the basic ctx commands.

Why not the check the VDA module?

rpm -q XenDesktopVDA

Which in turn showed:


Now let’s see why director is giving me the wrong version information…..



Minor issue and one of those “DOH!” moments.

Installing a new XenDesktop Delivery Controller. I get as far as creating the connection and my connection address is rewarded with:

The Name Resolver service could not resolve the supplied name.

I checked DNS and sure enough it was there!

The “DOH!” moment?

This is a semi-isolated setup which has it’s own DNS.  The company DNS had the record.

This setup did not.

Oh well!

A brand new XenServer pool in an external office had an interesting problem. Two hosts were added to the pool and yet they could not access two mounts on a NetApp filer.

A repair of the SR would give an error message:

There was an error while attempting to mount the NFS share.

Three other XenServer hosts had no issues.

Checked all the obvious and yet they would not repair. I considered a reload but how would that solve it?

Tried using the mount command to mount one of the shares to a directory and received an error that the server rejected the request.

I mentioned this to the administrator who owned the filer and it turns out he likes to use host lists to control access.

He added the hosts to the list and I was able to repair the SRs.


I was creating a new Xenserver test pool.  A simple thrasher setup that would have two hosts.  I created the pool and when I tried to add the second server; I received an error message:

This server has a different Active Directory configuration to the master

Odd message what has AD have to do with anything? Then….I remembered this was a temporary setup and was added to AD at one point.

I removed it by clicking the “Leave Domain” button found under the Users tab.

It didn’t need a reboot and was added to the new pool.

There was an odd issue with one of my xenserver pools.  I looked at xencenter and found the following as offline pool SRs:

DVD drives
Local storage
Removable storage

Rather strange and I was too busy to review the log files for errors. I wasn’t sure when those appeared and of course nobody knew anything.

How to get rid of them?

Trying the GUI had no options to remove them.  Time for the command line.

Right-Clicking an entry and selecting properties, I copied the UUID.

I opened a shell and entered:

xe sr-forget uuid=<pasting the UUID>

Repeated two more times and the entries disappeared.

Back to regular work……

We were installing fiber Nics and somebody tried to assign the management interface IP on one of the new ports. The result of course was an IP conflict and system went offline.

In the Linux world, you simply access the console, change a couple entries in files and reboot.

Such is not the case with Xenserver.  I tried to simply reassign the management interface, but it did not work. I decided to use the XE commands to remove the IP from the offending port (in this case it was xenbr1).

Locate the UUID by entering : xe pif-list

Drop the IP information by entering : xe pif-reconfigure-ip mode=none uuid=<big string>

One nice feature of Xenserver in this matter is you can tab out parameters and the UUID info after enter a few characters.

The system did need a reboot.

I had a case where I was building an image for windows 2008. The host uses 10 GB NICs and for some reason, they were not recognized.

I would add them to the configuration, reboot and nothing happened. I installed Xentools and nothing happened. Thinking it might be the age old driver issue but I did not find any on the vendor site. Setup issue?

To get around this “feature;” you have to delete all NICs and then add the one you want.

A quick reboot and the network was available.


One thing I have noticed on the Net; information about Citrix can be lacking at times.

I had an instance where a resource pool was established and the thinking behind it was wrong. I wanted to destroy it. I started Xencenter and accessed the doomed pool. I removed all the extra Xenserver hosts by simply right-clicking the entry and selecting “Remove Server from pool”

When it came time to kill the master, there wasn’t an option. I tried the xe options of eject and forgetting but they gave errors.

As mentioned, the Net was lacking on information. So I basically started hunting around thinking “it can’t be a reload!” I didn’t want to go through patching again.

I looked at the Xencenter window tab for Pool and sure enough there was an interesting entry!

Make into standalone server

I selected the master host, clicked “Pool” and selected the option. It ran really fast and the pool entry disappeared with the server showing up at the bottom of list of resources. I expected it to reboot but it didn’t. I gave it a reboot for good measure and then added the ex-master as a host to the correct pool.


My adventures with Xenserver found a couple interesting problems today. The first I will leave for another post. This one involved trying to install an update: XS65E1003.

I was trying to install it via the updates wizard and when it came time to run the Prechecks; it would fail with the message:

Checking server side status ... failed with an unknown error.

Ever so helpful.

I ran the update a couple more times just to see if there was a bad download but the error continued.

The messages log didn’t show anything obvious then again I could have missed it.

I checked the Net to see if there was anything similar especially for the unknown error. I found similar errors but not exact.

I was reading through a problem with xenserver 6.2 and saw an interesting suggestion. From the shell enter:

xe vm-cd-eject --multiple --force

I figured why not? It couldn’t hurt as this pool was not in service yet.  It gave a few errors. Nothing is the CD/DVD drive and couldn’t talk to a host. I did notice there wasn’t a message for each system.

I re-ran the install and sure enough; it passed the prechecks.

Strange but expected considering Xenservers error messaging at times.

Normally, I would give a link to where I found the command to credit the person but for the life of me; I can’t find the page anymore. If I find it later, I will add a link.