Windows Intune now offers a number of improvements on reporting around hardware inventory. Previously, Windows Intune had the ability to collect and display comprehensive hardware information about your managed PCs, but only on a PC-by PC basis. Now with the addition of the hardware reporting area, you can produce a variety of hardware reports, save your reports parameters, and of course export the results for further analysis and review. Here, we will describe the steps you need to perform to get the most from the Windows Intune hardware reports.
Once you have deployed your Windows Intune client to a number of PCs and they have fully reported their inventory (this can take a few hours), you are ready to run hardware reports. Log into the administrator console, and click on the “Reports” link on the left hand navigation bar. This will take you to the Reports Workspace.
From this screen, you can select the type of reports you’d like to run. When you click on “Hardware Inventory Reports” you see the following screen:
Here, you can do a number of things:
For example, if you are investigating what would be required to move all your PCs to Windows 7, you might select hardware criteria that will produce a list of PCs that fail to meet the minimum hardware requirements for the Windows 7 operating system, and that have an older version of the operating system. This would help you understand what hardware upgrades may be necessary to complete the move to Windows 7.
Once you have chosen your parameters, you can save your custom report by selecting one of the options in the upper right corner. You can also open a previously saved report. Remember that when you save a report, it is only available to you. Other users of your Windows Intune account must create and save their own report criteria.
Finally, you can run the report and view the results:
The criteria you selected when generating the report are included, and you can sort the report results by clicking on each column header. You also select one or more rows in the report (by clicking, shift-clicking or control-clicking) and copy those rows (right-click your selection and select ‘copy’) so you can pasted them in another application. Last but not least, your report can be printed, or exported into CSV or HTML format, for further review, storing offline, or as an input for another system.
This demonstrates many of the improvements around hardware reporting that have been introduced into Windows Intune, and we hope these features will help you manage your PCs more effectively!
Are there any Powershell cmdlets that interact with Windows Intune? It would enable sysadmins to better manage their clients.
Thanks for the feedback, we'll keep it in mind for future releases. This is not currently supported.
Silly question probably, but is this only available in the U.S. ?
I'm in Europe and I can't see the hardware reports.
Not silly at all..these features are currently in beta and will be available in the production service by the end of the year. Sorry, that was not clear in this article. You should sign up for a beta account and try this out (and many other new features). There is an earlier blog post on this site that describes how to sign up for the beta.
I second the request for PowerShell support
Is there ANY way to control/manage either the Client or the server side, with ANY form of command line tools. Or is it just wait, hope and click???
Also, can you include serial number in the hardware reports. That is something that would help out tremendously when troubleshooting hardware issues with vendors.
I second the request for PowerShell Cmdlets too.
Could you expand on how you might use Powershell Commandlets? Maybe provide some scenarios? Thanks!
I 4th the request for PowerShell cmdlets!
I would really like to have a PowerShell Command lets that lets you see how many license are bought, how many PC ´s are installed/active. And maybe the PC names.
5th for PowerShell
Powershell cmdlets could allow you to generate a query and save the result to CSV. Would save running queries manually through the interface. I currently export between 12 -18 queries per day that all have to be performed individually through the interface. Would much rather run a script to connect to the interface query data and then export to csv files. Would save a lot of time and effort.