VDA FunctionalLevel too low for Catalog

http://discussions.citrix.com/topic/333618-registration-issues-using-mcd-and-two-different-resource-pools/

Registration issues using MCD and two different resource pools

Started by Terry Duplantis, 26 July 2013 - 02:03 PM

Login to Reply

2 replies to this topic

Best AnswerWilliam Charnell,26 July 2013 - 03:41 PM

As these are XP machines, you need to set the functional level appropriately on the catalog. This would have been done for you if you had checked the box saying 'The Master Image is built using Windows XP or Windows Vista'.

As you have the catalog created now, I think that you can change to the lower functional level by using the 'Downgrade Catalog' action from the catalogs node of Studio if these are MCS-provisioned, or directly via the SDK by saying (if they're not MCS).

Set-BrokerCatalog catalogname -MinimumFunctionalLevel L5

or maybe delete and re-create the catalog from the master image again with the right settings.

William

Go to the full post

Terry Duplantis Members

• #1

• 
• 38 posts

Posted 26 July 2013 - 02:03 PM

I have two resource pools, two machine catalogs (3 XP VMs each), all created from the same master VM. There is one Delivery Group using all 6 machines from the two machine catalogs, setup to deliver one application.

The 3 machines at one resource pool are registering fine, however, at the other, they will never register. I noticed the following text in one of the events:

VDA FunciontalLevel too low for Catalog

William Charnell Citrix Employees

• #2

• 
• 
• 309 posts

Posted 26 July 2013 - 03:41 PM

As these are XP machines, you need to set the functional level appropriately on the catalog. This would have been done for you if you had checked the box saying 'The Master Image is built using Windows XP or Windows Vista'.

As you have the catalog created now, I think that you can change to the lower functional level by using the 'Downgrade Catalog' action from the catalogs node of Studio if these are MCS-provisioned, or directly via the SDK by saying (if they're not MCS).

Set-BrokerCatalog catalogname -MinimumFunctionalLevel L5

or maybe delete and re-create the catalog from the master image again with the right settings.

William