We have a similar issue, though we are upgrading from MA 184.108.40.206 to MA 220.127.116.11 and VSE 18.104.22.1685 to VSE 22.214.171.1249. The Agent update works fine, and most of the VSE updates go OK. Roughly 1/4 of the workstations resist the VSE update, but ePO 5.3.1 says they are successful. UpdateOptions.ini even lists: BuildVersion=8.8.01599 on the workstations. Wondering if there is a required reboot to complete the installation?
Even running "Run Client Task Now" and pushing the deployment manually gives all green lights, but no joy on 1599. Forcing cmdagent to update ePO and it's still reporting 1445 is installed. Just not patient enough?
Should we force the reboot?
Don't use that old upgrade chart, use this one: McAfee Corporate KB - Recommended upgrade paths for McAfee Agent, Host Intrusion Prevention, and VirusScan Enterprise K…
Was looking more specifically at your issue. We tag our equipment as either "server" or "workstation" and then create a Product Deployment based on the Group and/or Tags so we can roll out updates to either set of machines. The Product Deployment area will allow you to send out current or evaluation products. Hope this helps with your situation. Tags and Groups make it all pretty easy, and Product Deployment allows you to use both. I'm thinking you could tag your hardware "storage" or set all your storage equipment in a separate group which would allow you to perform global updates. Just thinking out loud here. I'm just another user, not an Intel employee.