Use Microsoft Assessment and Planning Toolkit to do inventory of the Windows servers

In this post I will show how to do inventory of servers with the tool Microsoft Assessment and Planning Toolkit (MAP). To be able to do this the servers needs to be accessible by WMI because MAP will use this technology to connect and collect information from servers.

Technet resources:

Download Microsoft Assessment and Planning Toolkit:


The installation is very strait forward and can be ran directly on a server. Just run the installation executable and follow the wizard.


When the installation is done, create a database to store the data that is going to be collected.



To start doing inventory on the servers, click Server on the left side of the application.


Then click “Collect inventory data”. This will bring up a wizard. To do inventory of Windows computers checkbox “Windows computers” and click next.


Choose how you want to discover the servers to get the inventory from.




To do inventory with “Windows Networking Protocols” one need to have started “Computer Browser” service. This service is disabled by default.



Add IP range if this is selected.


At the ”All Computers Credentials” hit enter if the dialog below don’t show up. Add the accounts needed. For example different accounts that have access to enter different servers.


Put the credentials in the order they should be used.



Click “Finish” to start the inventory.


When the inventory is done the status is published in the dashboard. To get a report click on the dashboard, in my example I clicked “Windows Server 2012 R2” and then “Generate Windows Server 2012 R2 Report” to get an Excel report.



In the Excel report there are a lot of information regarding the servers. The information is divided in different Sheets in Excel. Below is a summary of what is covered in the report.

  • Windows Server 2012 R2 Assessment Summary
  • System Requirements Used in the Assessment
  • Assessment Results for Servers
  • Server Role Assessment Summary for Windows Server 2012 R2
  • Discovered Applications
  • Device Summary
  • Device Details
  • Inventory Results for All Windows Servers

Inventory Results in the Excel Sheet “Inventory Results for All Windows Servers”

Below is a screenshot of inventory results regarding the servers that is inventoried.


More information that are included in the report.

  • Computer Name
  • WMI Status
  • Machine Type
  • Current Windows Server 2012 R2 Readiness
  • Installed Roles
  • Computer Model
  • Current Operating System
  • Service Pack Level
  • Active Network Adapter
  • IP Address
  • MAC Address
  • DNS Server
  • Subnet Mask
  • WINS Server
  • Registered User Name
  • Domain/Workgroup
  • Number of Processors
  • Number of Cores
  • Number of Logical Processors
  • CPU
  • System Memory (MB)
  • Video Card
  • Video Card Memory (MB)
  • Sound Card
  • Disk Drive
  • Disk Drive Size (GB)
  • Optical Drive
  • BIOS
  • BIOS Serial Number
  • BIOS Manufacturer
  • BIOS Release Date

Inventory Results in the Excel Sheet “Discovered Applications”

Below is a screenshot of the inventoried applications.


Deploy a Windows Container Host to a New Hyper-V Virtual Machine based on the Windows Server 2016 ISO

The following documentation “Deploy a Windows Container Host to a New Hyper-V Virtual Machine” explains in a very nice way how to deploy a Windows Container Host. In the example a Windows Server 2016 TP4 image will be downloaded to the computer that the script is ran on.

If you already have downloaded a copy of the Windows Server 2016 you can use the example below to deploy your Windows Container Host to a new Hyper-V VM without downloading a new copy of the OS.

Start by downloading the “New-ContainerHost.ps1” script.

wget -uri -OutFile c:\New-ContainerHost.ps1

To build the Windows Container Host on a new Hyper-V VM from a Windows Server 2016 ISO run the following and make a note of the parameter “-IsoPath” that points to the ISO.

c:\New-ContainerHost.ps1 -IsoPath C:\iso\Server2016TP4\10586.0.151029-1700.TH2_RELEASE_SERVER_OEMRET_X64FRE_EN-US.ISO -VmName ConTP401 -WindowsImage NanoServer -HyperV -Verbose

Creating Nano Container VM with New-ContainerHost.ps1 script and not language en-us

If you, like me, are running an OS that do not use the language en-us then you can run into problems when building an Nano Container server with the script New-ContainerHost.ps1.

This is the error you can get.
12/08/2015 09:50:39 ========================================
12/08/2015 09:50:39 New-NanoServerImage Cmdlet Started
12/08/2015 09:50:39 ========================================
12/08/2015 09:50:39 The ‘sv-se’ directory does not exist in the ‘Packages’ directory (‘D:\NanoServer\Packages’).
at Test-Paths, D:\NanoServer\NanoServerImageGenerator.psm1: line 1406
at New-NanoServerImage<Process>, D:\NanoServer\NanoServerImageGenerator.psm1: line 634
at Cache-HostFiles, C:\New-ContainerHost.ps1: line 323
at New-ContainerHost, C:\New-ContainerHost.ps1: line 660
at <ScriptBlock>, C:\New-ContainerHost.ps1: line 1455
at <ScriptBlock>, <No file>: line 1
12/08/2015 09:50:39 Terminating due to an error. See log file at: C:\Users\u\AppData\Local\Temp\NanoServerImageGenerator.log

Creating Nano Container VM with New-ContainerHost.ps1 script and not language en-us1

To fix this, edit the script at line 323 by adding the parameter “-language en-us” at the end of the line.

New-NanoServerImage -MediaPath “$($driveLetter):\” -TargetPath $global:localVhdPath -Compute -Containers -ReverseForwarders -GuestDrivers -AdministratorPassword $Password -Language en-us