Provided you are running this on a platform that supports the Win32_Product class, you could do
Get-WmiObject -Class "Win32_Product"
and check the Name and Version properties.
Or you could check the registry branch HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, find the "vCenter Update Manager PowerCLI" entry and look in the DisplayVersion key.
On backward compatibility and PowerCLI version dependencies, a VMW source should be able to make a statement.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Sorry Luc, I don't think I've stated my issue correctly. I'm able to find out the local vCenter Update Manager PowerCLI version. What I'm trying to figure out is the version of Update Manager the target vCenter version uses, w/o the VUM cmdlets. What you have stated would work for next step if I knew the target Update Manager server name, assuming it's installed on another system that is not vCenter.
I am playing a little more w/ the VUM cmdlets and they do return errors on their compatiblity status, so I think I might go down that route to determine whether the local system that script is being run from is correct.
Ok, now I get it.
I think your assumption is correct. The Release Notes state that Update Manager 5.0 (the snapin) only works with Update Manager 5.0 (the service).Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz