PENDING Building Collections for WMF versions

[Kevinlw]

My ultimate goal is to get all of our systems, servers and workstations, to WMF 5.1. Building the packages is easy enough. What I am struggling with is reporting and building collections to identify what we have.

The Path:

From what i have read, it will be better to update everything to at least 4.0. Then go to 5.1. That seems to be the easiest route. I have built one package for the purpose to get to 4.0.

My problem.

There just isn't an easy report to get the WMF level. I found something that said to set a default client setting to inventory the powershell.exe file from %windir%\system32\WindowsPowerShell\v1.0 directory. Then build a collection to queryfiles powershell.exe for the correct version number wildcard for the various versions.

My question.

Is this the best way? Does someone have a better way? I need to get all machines and I can deploy and be fairly sure we are good upon successful deployments. However, I really need to get some kind of a report to show management that we are good.

 

[Prajwal Desai]

I found something that said to set a default client setting to inventory the powershell.exe file from %windir%\system32\WindowsPowerShell\v1.0 directory. Then build a collection to queryfiles powershell.exe for the correct version number wildcard for the various versions.

You could enable and use Software Inventory feature in your client settings. By default SINV disables scanning of C:\Windows so you need to re-enable the Powershell path %windir%\System32\WindowsPowerShell\v1.0
After that, you can create Queries or Collections that leverage the "Software Files" attribute class to see what you have.

 

[Prajwal Desai]

And i think if you are just looking to report the PS versions the above method works well.