Share via

Microsoft Assessment and Planning Toolkit doesn't discover SQL Servers

Glenn Maxwell 12,876 Reputation points
2022-06-21T12:48:44.85+00:00

Hi All

i use Microsoft Assessment and Planning Toolkit 9.9.13.0 to discovery my SQL servers so that i can calculate my licensing and procure licensing. Few of my Azure servers which have SQL installed are not being discovered. Lets say i use server01 which has Microsoft Assessment and Planning Toolkit v9.9.13.0 installed and i use this server to perform discovery. The account i use is domain admin. I suspect it could be port blocking, experts please let me know which ports do i need to allow from server01 to all the SQL servers to perform the inventory.

Azure SQL Database
SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
3,064 questions
Windows for business | Windows Server | User experience | Other
SQL Server | Other
Accepted answer
  1. Limitless Technology 39,926 Reputation points
    2022-06-23T15:23:17.207+00:00

    Hi there,

    The MAP tool has to be run by a domain administrator.

    Also, there have to be (TCP/IP) ports open on the firewall of SQL Servers/instances behind a firewall, otherwise, the MAP tool will not find them.

    On the 'Discovery Methods' page, choose 'Use Active Directory Domain Services (AD DS) AND 'Use Windows networking protocol' as 'methods to use to discovery computers'.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

    MAP toolkit 9.5 not finding all SQL Server instances.

    https://social.technet.microsoft.com/Forums/en-US/9e0eb288-bcfa-485d-8f99-0ab4aebcf3f6/map-toolkit-95-not-finding-all-sql-server-instances?forum=map

    Hope this resolves your Query !!

    --------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bjoern Peters 8,921 Reputation points
    2022-06-21T14:02:30.97+00:00

    I would expect that you have to open at least one port for SQL Browser (UDP 1434) to contact the individual browser service and find relevant instances.
    TCP/1433 for SQL Server is also relevant in order to connect

    But that's it.

    If your servers are running in Azure you might have any NSG in your subnet(s) or on your virtual machines that are blocking those ports or someone has configured some instances to be "hidden" as some kind of security => https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/hide-an-instance-of-sql-server-database-engine?view=sql-server-ver16

    0 comments
  2. YufeiShao-msft 7,146 Reputation points
    2022-06-22T08:46:41.907+00:00

    Hi @Glenn Maxwell ，

    Please check which ports are assigned to the instances, and make sure those ports open and are not blocked by your firewall or other network protection service
    Using SQL Server configuration manager, enable Named Pipes or TCP/IP protocol
    https://social.technet.microsoft.com/Forums/en-US/9e0eb288-bcfa-485d-8f99-0ab4aebcf3f6/map-toolkit-95-not-finding-all-sql-server-instances

    -------------

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.