Volume Liscensing check

Willie Page II 1 Reputation point

I work for a disaster recovery company. One of the services we offer is Imaging for our clients.. We require them to have a Volume license copy of windows in case we have to deploy multiple PCs/Laptops to recover them in a declaration. as were are unable to log into their windows environment, my Questions is, How do we check to see if they actually have a built their image with a volume licensed OS so that we are in compliance?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,180 questions
Service Manager
Service Manager
A family of System Center products for managing incidents and problems.
205 questions
Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,273 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Rich Matheisen 43,931 Reputation points

    It's been more than five years since I retired and I really don't recall if MSFT maintains per-machine information on their volume licensing. But you may find the information in the "Description" property of the object returned by this:

    Get-CimInstance -ClassName SoftwareLicensingProduct

    It's going to return a LOT of data (every licensed product on the machine!) so you may want to pipe the results into a where-object {$.description -like "*Windows(R)*" -and $.licensestatus -ne 0}.

    After that, I'm not sure of which property might hold the data you're after. Maybe ProductKeyChannel?

    You can also try this to see if the information it retrieves might be useful in looking through the properties: how-determine-if-license-oem-retail-volume-windows-10

  2. Rich Matheisen 43,931 Reputation points

    If you aren't joined to their domain then permission may(!) present a problem.

    Access to individual client machines may be related to their being off-line, or just inaccessible due to network routing (etc.), or to the "second-hop problem".

    Being more specific about the problem (i.e. providing the errors you receive) would be helpful.

    0 comments No comments