MCS fails when selecting a VM that was moved from a different XenServer pool.

If you are dealing with Citrix XenDesktop 7.5 and XenServer 6.2 (SP1 with all patches in this specific case), you may get the following error when trying to create a new machine catalog with a VM that was initially created in a different XenServer Pool.

DesktopStudio_ErrorID : ExceptionThrown
Exception : Object has been deleted. VM:Ref:3577
Reason : Failure
Message : Object has been deleted. VM:Ref:3577
Sdk Error Message : An exception occured.  The associated message was Object has been deleted. VM:Ref:3577
Sdk Error ID : Citrix.XDPowerShell.Status.ExceptionThrown,
ErrorCategory : NotSpecified
DesktopStudio_PowerShellHistory : Create Machine Catalog ‘Architect Catalog’
11/4/2014 1:21:51 PM


The quick and dirty solution is to power the machine down, create a “Full Copy” of the VM, and then delete the original.  As long as you are not also planning on using the “broken” VM, there is no need to sysprep, and you can change the name of the copy back once you delete the original.  As always I would not delete the original until you are 100% sure that the MCS catalog was successfully created!


happy cloning!

Deploying XenServer 6.2 with PXE — Part 1

Being that this is my first post, instead of posting a welcome post or anything like that, I can do that later and just back date it.  This article is long overdue and I want to get everything out of my head.

In part 1, I will be covering the initial setup of our PXE environment as well as the steps that I had to run through to “slipstream” the PXE image (install.img on the XenServer ISO), with the necessary NIC drivers.

Read more…