Unable to upgrade to SCCM 1511 when using Citrix XenDesktop Connector

Unable to upgrade to SCCM 1511 when using Citrix XenDesktop Connector

xendesktop-000In my lab environment I am using the Citrix XenDesktop 7.x Connector to manage my Citrix farm. Since the release of the new System Center Configuration Manager 1511 I wanted to upgrade my environment, but I was unable to do so.

Due to a bug in the connector, the XenDesktop related collections are created with a wrong value of the CollectionType property. The Citrix Connector creates collections with the CollectionType property equals 0 (zero) instead of 2 for Device Collections. (User Collections have a CollectionType equals 1).

The Upgrade to Configuration Manager 1511 is failing due to the fact that the collections exist with the CollectionType equals zero. Let’s see how you are able to fix this in a lab environment.

While trying to install 1511 of System Center Configuration Manager the prerequisite checker will fail with the following errors in the ConfigMgrPrereq.log.

The prerequisites checker fails

The prerequisites checker fails

ERROR: CheckMismatchedCollectionType failed, found mismatched collection type

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : HighAvailabilityLock”(ID=PS10005B)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : HighAvailabilityData”(ID=PS10005C)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop”(ID=PS10005D)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : ConfigMgr-Citrix-Lab : FarmGlobal”(ID=PS10005E)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : ConfigMgr-Citrix-Lab : FarmCatalogIds”(ID=PS10005F)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : ConfigMgr-Citrix-Lab : FarmDeliveryGroupIds”(ID=PS100060)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : ConfigMgr-Citrix-Lab : FarmFTA”(ID=PS100061)

ERROR: mismatched collection type for the dependent collections: “All Systems”(ID=SMS00001) and “Citrix XenDesktop : ConfigMgr-Citrix-Lab : FarmPublishingStatuses”(ID=PS100062)

CM01.configmgrlab.com;   Check for incompatible collection references;   Error;   One or more collections reference a collection of a different type. For example, a user collection cannot include or exclude a device collection and a device collection cannot use a limiting collection that contains users. Review the ConfigMgrPrereq.log file to identify problem collections and ensure that any referenced collections are of the same type.

xendesktop-00

Errors in the ConfigMgrPrereq.log

Since the WMI property of the CollectionType is read-only we cannot change this setting via for instance PowerShell or vbscript. The only (supported) way of correcting this is by removing the Connector and configuring everything again. Another not by Microsoft supported way is by changing the CollectionType property of the collections in the log file directly in the Configuration Manager Database. If you do not want to remove the connector or wait for the update of Citrix always call Microsoft PSS to help you out!

In my lab(!) environment I fixed the issue by editing the database directly. So when we look in SQL and query for the collections which are created wrongly.

SELECT * from dbo.collections_g where left(CollectionName,6) = ‘Citrix’ and CollectionType=0;

xendesktop-01

The records that have a collectiontype equals 0

Updating the records is done with the following SQL statement, again you should only do this in lab environments and don’t do this in production environments. It is not supported, Microsoft PSS is able to help you in production environments.

UPDATE dbo.collections_g SET CollectionType=2 where left(CollectionName,6) = ‘Citrix’ and CollectionType=0;

 

The prerequisites checker does not fail anymore

The prerequisites checker does not fail anymore

So after running the SQL statement in my lab environment the prerequisite checker does not fail on the collections and the installation of System Center Configuration Manager 1511 can be installed.


Do not make changes in production environments without the assistance of Microsoft.

Comments

 
Comments

Trackbacks for this post

Leave a Reply

Time limit is exhausted. Please reload CAPTCHA.

 
Read previous post:
Mobile Application Management Policies (also) available in Azure portal

Earlier this month Microsoft announced the new Microsoft Intune functionality that have been released earlier Read more

Close