Hi Everyone, Is anyone else running into issues with the WEM agent getting bound to multiple configuration sets in Citrix DaaS? It looks like a recent update forces a new default setting during catalog setup. In our environment, we map one Machine Catalog to multiple Delivery Groups. When building a new catalog now, the "Experience Optimization" section defaults to "Apply default settings". This auto-binds the VDAs to WEM's "Unbound Agents" config set. The issue is that we already assign specific config sets by linking our Active Directory OUs inside WEM. Because of this new feature, our recent agents are getting choked up by binding to two configuration sets at once. We only see this on catalogs built over the last few weeks—older catalogs have that optimization field completely blank and work perfectly. Has anyone seen this and found a workaround to prevent this auto-assignment? Changing it to "Apply Custom Settings" will not solve it for us. Because a single catalog supplies VDAs to different delivery groups, we can't just pick one blanket WEM config set for the whole catalog. Slack Conversation