Updating svaconfig.xml for multiple SVA's

[CharlieWork]

I need to update the svaconfig.xml file on 200+ MOVE SVA's. I am increasing workerthreads to address performance issues in our VDI environment (per the Best Practices section of the product guide).

I would like to avoid manually updating all the SVA's, and SSH is disabled by default.

Is there a centralized/automated way to make this change?

Please and Thank you.

[patrakshar]

@CharlieWork We never suggest performing any change manually on the config file. What exactly you want to change within that file which cannot be done through EPO? May I know the background issue and what exactly the change you want to make in that file?

[CharlieWork]

@patrakshar I configured one resource cluster according to page 66 of the Program Guide - Section Titled "Best practices for Agentless". This provided an improvement to end user experience. We were experiencing sporadic freezing in VDI during boot storms.

When there is a significant workload running on the client systems, you might notice issues like the VM getting hung during its bootup, latency during file scanning, etc. To prevent such issues, it is recommended to upgrade the SVM configuration with this configuration:
Memory                                      4 GB RAM or higher
CPU                                             4 vCPU
Maximum worker threads        512 (You can log on to the SVM and change this number)
1 Log on to the SVM as a root user.
2 Open /opt/McAfee/move/etc/svaconfig.xml.
3 Under <EPSEC>, set the value for workerthreads to 512. Default value is 256.
4 Save the changes.
5 Restart the MOVE service.

[patrakshar]

Thank you for clarifying this.

So if I understand correctly your concern is that you cannot change the EPSECvalue for workerthreads to 512 from 256 remotely.
This is a EPSEC configuration which is not changeable from  EPO side. This has to be done locally on the SVA and it requires a reboot of the SVA post performing the change. 

[CharlieWork]

This is an unfortunate solution for any large scale VDI customer. It would be beneficial to your customers to provide the capability, considering that it is labeled as 'best practice'.