25 March 2013

Home » » Powershell: WMIC Product headers

Powershell: WMIC Product headers

  Monday, March 25, 2013    No comments
If you are trying to query a list of installed applications using WMIC and want to only display certain headers, here is the list of header available:

wmic product get <header>

  • Node
  • AssignmentType
  • Caption
  • Description
  • HelpLink
  • HelpTelephone
  • IdentifyingNumber
  • InstallDate
  • InstallDate2
  • InstallLocation
  • InstallSource
  • InstallState
  • Language
  • LocalPackage
  • Name
  • PackageCache
  • PackageCode
  • PackageName
  • ProductID
  • RegCompany
  • RegOwner
  • SKUNumber
  • Transforms
  • URLInfoAbout
  • URLUpdateInfo
  • Vendor
  • Version
  • WordCount

Related Posts:

  • PowerShell: Microsoft Office and Windows MAK Activation Script Here is a script that will activate both Microsoft Office and Microsoft Windows. I wrote this script because we currently have both x86 and x64 systems, therefore the OSPP.vbs resides in different locations. I also chose t… Read More
  • Using Registry Keys to configure MSI Installations After posting the video on how to use registry keys to pre-configure the settings of an MSI during installation, I got a lot of interest, so I decided to create this blog to explain how it works and why it can be beneficial.… Read More
  • ImageX Error while Creating MDT Task Sequence While creating an MDT task sequence in SCCM, I encountered the error message: System.IO.FileNotFoundException: Could not find file '\imagex.exe'. I started Googling the error and the best info I found was to either … Read More
  • Microsoft Office Updater One of the things that has annoyed me in the past is having to keep the Microsoft Office Updates folder up-to-date with the latest .MSP files. The reason I bother with keeping the Updates folder up-to-date is because it spe… Read More
  • .Net Framework 4.5.x Error 0x80004005 Recently, I had to deploy .Net Framework 4.5.2 to all systems, as it was a requirement for a software update. I first deployed it through software updates in SCCM 2012. The status showed up as compliant. I thought nothing mo… Read More

0 comments:

Post a Comment