• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 90
  • Last Modified:

Looking for a PowerShell query to help satisfy a Microsoft software SAM audit

Hello Experts!

I'm a newer admin at a relatively small (75 computers, 4 physical servers) manufacturing firm, and I'm being 'asked' by Microsoft to work with them on a SAM audit of my MS software.

We didn't have an administrator before me (the controller and owner were handling all things IT), so I'm a bit nervous about finding all the supporting documentation, but I'll cross that bridge when I come to it.

What I'm looking for right now is to see how other admins on a 'tight' IT budget (I don't have much in the way of inventory tools) have done the internal querying to find the installed software on each computer and server.

The admin in me thinks that a request like this screams 'PowerShell!'  Unfortunately, while I can write rudimentary scripts at this point, my PowerShell skill isn't such that I can dump in a list of workstations and output a list of only the Microsoft Products, their versions, and license information.

Has anyone devised a PowerShell script to do such a thing?  If so, would you be willing to share it?

I'm assuming that all SAM audits are the same, but in case they aren't, MS is looking for the version and edition for each of the following products:

Workstation Operating System, Office, Project, Visio, Visual Studio/MSDN, SQL Server Developer, Server Operating System (and CALS), SQL Server (and CALS), SBS (we don't have one), Exchange Server (we don't have one), Sharepoint Server (we use Sharepoint Foundation, which I don't believe is part of the audit), Dynamics CRM (we don't use it), and Remote Desktop (and CALS).

If anyone has such a script 'tucked away', I'd really appreciate your help!

Thanks,

Scott
0
Scott Milner
Asked:
Scott Milner
  • 2
  • 2
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
You could utilize WMI queries in powershell (Get-wmiobject) to determine product licenses, but you would probably be better of using the Volume Activation Management Tool (VAMT). It's capable of going through all the systems in your environment to determine activation status, what Microsoft Software is installed, and it will let you install licenses remotely if needed. http://www.terminalworks.com/blog/post/2015/12/13/volume-activation-management-tool-3-1-implementing-and-activating has information on installing version 3.1 of VAMT.
0
 
Scott MilnerApplication AdministratorAuthor Commented:
Thanks Adam... I'll take a look at it and get back to you!
0
 
Adam BrownSr Solutions ArchitectCommented:
No response, but VAMT is designed for this purpose.
0
 
Scott MilnerApplication AdministratorAuthor Commented:
Sorry Adam... I got tied up with things and forgot to get back to you.

I was able to install VAMT and get it configured to poll my network.  It pulled some good information, but ultimately didn't get me everything I needed.  I suspect part of the problem was the fact that so many of our Office installations are done with box-copy products rather than volume licenses, however it may have been user error on my part.  I'm going to continue to work with the tool as I move forward--it may be that I can make it more useful with experience.

Ultimately I ended up using a combination of VAMT, WMI polling, and touching each machine to build my spreadsheet.  It took more time that I wished, but I now have detailed documentation that I can build on.

Thanks for your response, and sorry again for my late feedback.

Scott
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now