MAP Toolkit Content Index (en-US)
A: Microsoft Assessment and Planning Toolkit is available as a free download at...
Download the Microsoft Assessment and Planning Toolkit
A: The installation prerequisites can be found in the MAP Getting Started Guide under "Minimum Requirements" at http://social.technet.microsoft.com/wiki/contents/articles/17810.minimum-requirements-for-running-map.aspx
A: Yes. MAP can gather inventory information from machines on any domain as long as the appropriate administrator credentials are provided to the MAP wizard. The machine upon which MAP is running does not have to be a member of the target domain or forest.
A: MAP can gather performance data from multiple domains as long as the appropriate administrator credentials are provided to the MAP wizard and the MAP machine is a member of the same forest as the target machines.
A: Yes. See Manually installing SQL Server for use with MAP Toolkit for details.
A: The download package includes:
A: Sample reports are available here:
MAP Toolkit Sample Reports
A: A sample database is available in the
MAP Training Kit
A: To transfer MAP data to a different machine use the following steps:
Restore the database
Note: Databases cannot be moved to a lower version of SQL Server. For example, you can't move a database from SQL Server 2012 to a MAPS instance that is less than SQL Server 2012. When you try to move a database to a previous version of
SQL Server, an error will occur.
A: Back up the database
Restore the database
Note: When importing a database, the name cannot be the same as the name of a database already in MAP. If you want to overwrite an existing database with a backed up database, you will have to use SQL Server Management Studio. If you choose
to use SQL Server Management Studio to backup your database, if must be a full backup. MAP can only import a full backups, do not use the differential backup.
A: Currently, MAP does not provide the ability to inventory and report networking information such as persistent routes or network topology.
A: MAP can be used to inventory and assess the following operating system versions, regardless of whether they are 32-bit or 64-bit:
*Home versions of Windows XP and Windows Vista do not have WMI enabled and will generally not be inventoried by the MAP tool.
** Tested distros of Linux are Red Hat, Ubuntu, Suse, and CentOS. However distros that support SSH and use dpkg or rpm for installations should be able to be inventoried.
If you repeatedly run inventory into the same database, the results will be additive:
After you run several of these inventory cycles, the report(s) generated at the end will be an aggregate of all data. An easy way to take advantage of this capability is to:
Put MAP in a Virtual Machine (VM) and likewise move the VM around.
See Microsoft Assessment and Planning Toolkit Inventory Status Messages.
Only computers that are known to be SQL Servers will appear on the SQL Server report. If the inventory fails for a particular computer, the MAP tool won’t have enough information available to know that the computer is running SQL Server. To determine if
those servers were successfully inventoried, generate the “Inventory Results” report using the “Inventory Results” scenario in the "Environment" scenario group.
Open the “InventoryResults-<date/time>” report by going to View>Saved Reports. This report will show all computers that MAP has attempted to inventory. The second column, “WMI Status”, shows the result of the connection attempt to the computer. Use this
information to determine why the computer could not be successfully inventoried.
When the MAP tool discovers a computer serving as a Virtual Machine Host, such as Virtual Server 2005 or Hyper-V, it attempts to discover all the Virtual Machines hosted on that computer and subsequently attempts to inventory all of the guests.
Conversely, when the MAP tool determines that a computer is a Virtual Machine, the tool attempts to determine the network name (DNS host name) of the host machine. If it is successful, it will attempt to connect to that host machine and inventory it and
any other discoverable guest machines on that host.
MAP 3.2 and earlier depend on the Windows Installer Provider for WMI to report installed applications. On Windows Server 2003 and 2008, this dependency is problematic for two reasons:
In MAP 4.0 and newer versions, the application collection process has been rewritten to query the registry directly and bypass the Windows Installer WMI provider. In this scenario, applications that use MSI to install themselves should be reported by the
tool. However, applications that don’t use MSI to install will not be reported—for example, xcopy deployments and any other installer that doesn't use MSI will not be listed.
Application hotfixes will not typically be reported. Each major software vendor has their own way of dealing with hotfixes, so MAP doesn’t know how to interpret and report those.
A: The “Days Since Last Activity” field is computed based on the most recent activity and is the one field that should be used for filtering out inactive devices. This field might appear to be out of date. This is by
design Active Directory behavior which is a side effect of optimizing replication load. Even with this approximation, the dates in these fields are still accurate enough to allow filtering of inactive machines in the Active Devices
and Users scenario.
Q: Are the utilization figures that the MAP Toolkit provides in the PerfMetricResult spreadsheet
averages or maximums?
A: CPU and Memory utilization figures are computed as averages; Network and Disk I/O use maximums.
A: For the inventory, MAP uses approximately 1MB for each physical machine and .5MB for each virtual machine inventoried. For performance data, the database grows at approximately 53KB per observed machine per hour.
A: When running inventory, MAP transfers an estimated 512KB to 1MB of data per machine inventoried over the network. The main source of the variance is due to the number of items in the MSI database per machine (how many applications installed, how many
patches, and so on).
When running performance metrics collection, the amount of data collected is about 2MB per machine monitored initially and about 18-20KB every 5 minutes per machine monitored. Note that an inventory of each machine targeted for performance metrics collection
will be performed if that machine has not been previously inventoried in the database being used by MAP.
A: The virtual machine (VM) placement recommendation provided by MAP uses the amount of memory utilized by the guest machine for the memory calculation.
The mount of memory utilized is determined by taking the average of the amount of memory used over the observation period. The actual value is determined by subtracting the performance counter "Memory: Available Bytes" from the total amount of physical
memory on the guest computer. It's possible to reserve more memory than the calculated amount by specifying an additional reserve in the virtualization placement wizard.
A: Yes. If you have already run the “Performance Metrics Wizard” and have collected data, the next time you run the Wizard you will receive the following prompt:
A: No, MAP requires specific performance data to perform placement analysis. Import of this performance data is not currently supported.
A: MAP never persists security credentials to disk. The credentials you provide are encrypted using the
DPAPI and maintained only in memory. Credentials in memory are disposed of when the inventory completes. For each machine that MAP attempts to connect to, the credentials are passed to the connection
method being used, at which point the credentials are securely handled by the remote operating system that is being interrogated. Credentials are never logged or written to the database or any other file.
A: The following security features are provided by MAP:
A: MAP will only work if WMI traffic is allowed from the MAP computer to the inventoried machines. Many host-based and software-based firewall products will block DCOM traffic across the network adapters on the computer. To enable remote WMI access, you
need to make sure that the TCP/UDP ports for the "Remote Administration" and "File and Printer Sharing" exceptions are open on the computer running the software firewall. In addition, you will need to ensure that the following required configuration is implemented
prior to running the tool:
More detail on network configuration requirements is provided in the “Getting Started Guide” provided with the MAP tool.
A: MAP includes a getting started guide that provides step-by-step guidance. The Getting Started Guide is located on the MAP Wiki, which can be found at http://social.technet.microsoft.com/wiki/contents/articles/1640.microsoft-assessment-and-planning-toolkit.aspx
A: No, MAP does not currently have a scripting interface.
A: You may contact the MAP team in the following ways:
A: No. Client access data from IIS is not considered for Windows Server usage tracking.
A: By default, SQL Server is not configured to receive remote connections and Named pipe, TCP/IP protocols are disabled. In order to successfully inventory SQL Server computers in your environment you need to enable one of the protocols. Using SQL Server
Configuration Manager, enable either Named Pipes or TCP/IP protocol (with default port of 1433).
A: By default, no data about your environment is uploaded to Microsoft or anyone else by the MAP Toolkit. Previous versions of the tool do have a capability to download updated content and device driver compatibility information from Microsoft, however
this is an optional feature and can be disabled on the first page of the Setup wizard or from the Tools -> Options menu within those versions of the product itself. The only data that Microsoft receives when someone updates their device compatibility information
is the IP address of the computer (or intervening firewall) that requested the updates, along with standard HTTP header information, such as the user agent string, etc.
Additionally, you may choose to share certain information with Microsoft to aid in the improvement of MAP Toolkit features, via the Customer Experience Improvement Program. The Customer Experience Improvement Program (“CEIP”) collects basic information about
your hardware configuration and how you use our software and services in order to identify trends and usage patterns. CEIP also collects the type and number of errors you encounter, software and hardware performance, and the speed of services. We will not
collect your name, address, or other contact information.
A: Yes. See MAP to tell difference of a SQL in production vs evaluation for details.
A: See Microsoft Assessment and Planning Toolkit What data does Usage Tracking report for a detailed answer.
A: See How Does Microsoft Assessment And Planning Toolkit MAP discover Exchange Servers for a detailed answer.
A: The Organizational Health Tool that comes with Exchange Server 2010 RTM has a known bug where it is counting users with the default ActiveSync Policy enabled as requiring Enterprise CALs. Due to this, the count given by this tool does not match the count
given by MAP.
A: This is definitely possible, but not supported. In other words, if you’re really comfortable working with SQL and you want to inject data yourself into the database, it’s definitely possible to do. It is worth noting however, that there are a lot of interrelationships
between the data that would take some time to figure out, and there is a lot of processing and aggregation of the data that needs to happen in a particular order before the reports can be created from the data if you choose to extend the current system.
If you go down this path, the safest bet would be to not modify or extend existing tables, but to use “shadow tables” with the additional data you want to add, using the primary key of the main table you want to extend.
Modifying all the aggregation stored procedures, aggregation output tables, and reporting stored procedures to handle the added data is left as an exercise to the reader if you choose to go that route. Otherwise, write your own reporting stored procedures
or queries that incorporate the additional data may be more straightforward.
Finally, if you do modify databases in this way, you shouldn’t expect them to upgrade correctly when the next version of MAP toolkit is released.
A: Read this blog post for details on how to throttle MAP:
A: Possibly, however MAP has only been tested to discover HP-UX
To contact us:
A: Often times this is caused by the ports being blocked. Non-default instances of SQL Server use non-default ports. Check which ports are assigned to those instances and make sure those ports aren't being blocked by your firewall or other network protection
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
http://support.microsoft.com/kb/932370. For all other operating system versions, the corresponding cells in reports will be blank or display the value "Unknown."