Return to the MAP Toolkit Getting Started Guide


Known Issues

Data Collection Issues

  • If the MAP Toolkit is installed on a computer that is a member of a domain, log on to the computer using a domain user account. Use of a local computer account on a computer that is a member of a domain will result in authentication failures to remote computers, even if the correct domain credentials are provided to the Inventory and Assessment or Performance Metrics Wizards.
  • The Performance Metrics Wizard can collect performance data only if the Remote Registry service is running on the remote computer. By default, the Remote Registry service is disabled on Windows Vista/Windows Server 2008 or newer. Refer to the "Remote Registry Service" section of the Getting Started Guide for more information.
  • Computers running Home editions of Windows cannot be inventoried and assessed because remote WMI connections to computers running these versions of Windows are not allowed.
  • For assessments of environments of more than 5,000 computers, we recommend that you use a dedicated computer running only the MAP Toolkit. Hardware and software recommendations can be found in the "Installation Prerequisites" section of this document.
  • When running inventory collection MAP 9.0, some users will experience inventory failures. These failures can be found in the WMI Status column as Failure - Inventory not completed. This issue appears to be related to running without elevated permissions on the MAP computer. Start MAP using elevated permissions (right click and choose "Run as Administrator") and attempt to run the inventory again.

MAP Toolkit Reports

  • The MAP Toolkit collects the Number of Hyperthreads (per core), Number of Cores, and the L3 Cache Size for computers running Windows Vista/Windows Server 2008 or newer. The number of physical Hyper-threading enabled processors or the number of physical multicore processors is incorrectly reported in Windows XP/Windows Server 2003. For more information about how to address this issue, see For all other operating system versions, the corresponding cells in reports will be blank or display the value "Unknown".
  • All reports: MAP will report wrong processor information if a newer processor that uses extended family bits is running Windows XP SP3 or earlier or Windows Server 2003 SP2 or earlier. A hotfix is available at Note: This hotfix must be applied to each computer that meets this criterion to get the correct results.
  • Server Consolidation Recommendations: Reported guest values are rounded and may not equal the sum of the host total values.
  • Virtual Machine Inventory Report (VMReport): If the "Manually enter computer names and credentials" option is the only discovery method selected during inventory, the "Host and Guest Details" worksheet may not display both virtual machine hosts and virtual machine guests. This will occur if credentials for a host are specified but not the guest, or vice versa. To work around this issue, either manually specify credentials for both the host and all of its guest computers, or use another inventory method such as "Use Active Directory Domain Services."
    . For all other operating system versions, the corresponding cells in reports will be blank or display the value "Unknown".

Software Usage Tracker

  • While parsing log files and events to compute server usage, accesses from certain system accounts (NT Authority\anonymous logon, NT Authority\Local Service, NT Authority\Network Service, NT Authority\System) are filtered out by name based on their English spellings. However, the names of these system accounts are spelled differently on some non-English versions of the operating systems and the end-user can change the default account names for these system accounts manually (including on English versions of the operating system). In those cases these system accounts will not be filtered out and will be included in the counts of unique users accessing services in the Software Usage Tracker reports.
  • Currently the MAP Toolkit does not identify and account for enterprise usage of Exchange 2010 mailboxes using archiving and retention policies.


PowerShell failures when finding computers by IP address list

When running collections with PowerShell on machines discovered through the IP address list discovery method, connections can sometimes fail leaving the following message in the log:

Exception: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TrustedHosts run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

To make the assessments work, add the machine names (or IP addresses) to the local machine’s TrustedHosts.  You can read about how to do this in the PowerShell docs (see “How to Add a Computer to the Trusted Hosts List”).

PowerShell collector fails with error 502

If WinHTTP Proxy is configured, the PowerShell collector can fail with the following error:

The WinRM client received an HTTP status code of 502 from the remote WS-Management service.  For more information, see the about_Remote_troubleshooting Help topic.

To correct this issue, run the following command from an elevated command prompt:
netsh winhttp reset proxy

Desktop virtualization planning report shows no data

The desktop virtualization planning report can occasionally show "No data" even though MAP has sufficient information to generate the report.  This issue occurs when the host CPU selected is less powerful than the strongest CPU in the desktop workload model.  To correct this issue, adjust the CPU in available desktop workload models.

Virtual machine reports list Hyper-V hosted machines as "Unknown" virtualization technology

In order to properly discover the virtualization technology used for Hyper-V hosts, MAP queries the Hyper-V Virtual Machine Manager service (vmms.exe).  If this service is disabled, reports referencing the virtualization technology will read "Unknown" for machines managed by the service.

To correct the issue, you will need to start the Hyper-V Virtual Machine Manager service on affected hosts.

Lync phones with firmware predating Lync 2010 are not discovered

In order to properly discover phones when using the Lync Usage Tracking Scenario, the phones must have a minimum firmware version of Lync 2010 or higher.  Firmware predating Lync 2010 does not have the capability to be discovered by the MAP Toolkit.

Return to the MAP Toolkit Getting Started Guide