Citrix DaaS; adding a Machine Catalog, we are presented with optimization settings now. Select an Experience Optimization option to apply to the machine catalog: • Apply default settings: Select this option to apply the default optimization settings, including automatic CPU spike protection and intelligent CPU optimization. • Apply custom settings: Select this option to create a configuration set for this machine catalog using the catalog name. After the configuration set is created, you can customize the optimization settings as needed. Alternatively, you can select an existing configuration set. We currently apply WEM configuration sets via OU and this is breaking that; if we set it to default settings, we now get a type=Machine Catalog in directory objects and our configuration set is not bound ; if we set it to custom, it forces us to select our configuration set. Is this the new model? we have to select it by Machine Catalog now? Our new machine catalog is in the OU path but an OU underneath it. Can someone else validate this? thanks

I had a customer, with the same issue. Turned out to be WEM agent being in Basic Mode on the VDAs. We removed the Machine Catalog type from the directory objects though.

You need to have additional wem settings in group policy. This bit us on the ass a few months ago, since they bundled the wem agent in with the VDA..

The install via VDA, can be excluded 👍

@Paul Brown is this policy in a newer admx file wasnt seeing this. we just started having issues with our UPM like it’s ignoring the exclusions and looks to be wem related

yes.