Does anyone handle assignment in the SVM Manager policy by simply checking "Assign SVM if no rule is defined for the above client"? We are building out our MOVE MP environment, and will probably end up with two or three SVM's. It seems very tedious to tag systems or try to build IP rules (all of our VDI desktops are drawing from the same IP Pool). It also looks like you can't assign primary/secondary SVM's with these rules.
Or, does anyone have a good strategy for SVM Manager configuration?
We had to tick that option. Without it, we would randomly get clients failing to register. I suspected that it was because the MOVE service started before the VDT's IP assignment was effective (whether it was something on client-side or in our infrastructure I have no idea). I did log a support case, but McAfee's advice was simply to disable the related event ID to stop the noise.
We also draw from a pool of IPs. Ours are in two VLANs, so I ended up using subnets to evenly split them amongst our SVMs, leaving the 'assign if no match' option ticked.