This message was deleted.

Not quite sure I understand the question here? Do you want the wem agent on Citrix infrastructure servers?

Yes, to control some rogue security scanning processes from running the CPU to 100%

Yeah I’m not sure that would be OK @Anthony Shi ??

So why wouldn't you just lower process priority via powershell for example instead of using WEM? Or a lot of security scanning products (anti-virus?) have a setting built-in to only use idle cycles for a scan or a limit in CPU percentage, 100% cpu is not that worrying then.

We are using WEMagent to manage our own setup(actions, policies, monitoring,etc.) more than optimization. It is a good idea to check how manage whole Citrix infra..

WEM is the only tool we've had success in setting this up with (couldn't get ControlUp to do it in a way that works for our situation because these SVM processes are triggered by a powershell script). But our TAM told us there could be licensing issues because WEM is for the VDA which is extremely frustrating that they would actually limit that use case.

WEM could run on most windows os, more than VDA. From license perspective, it is part of Citrix DaaS.

@Anthony Shi This has been something of a grey area forever - I think the documentation needs to call out where and where it can't be used - for example • On the VDA • On Physical Desktops (if so, under what licencing constraints - Remote PC scenarios etc? What if the user is using a physical Windows machine to access a Citrix Virtual App or Desktop, does that mean WEM can be extended out there) • On Physical Infrastructure that supports the Citrix Platform (Eg, Delivery Controllers, StoreFront Servers, FAS Servers, WEM Brokers etc etc etc) We know technically it can do whatever, but it's the licencing side of things where things get fishy