There are numerous ways to find where a SQL Server instance is running in a cluster. The most convenient tool was cluster.exe. Unfortunately, I have to say it was the most convenient tool, and no longer is because no single cluster.exe works with all versions of Windows. You could also use the PowerShell cluster cmdlets such as Get-ClusterGroup. But it’s not ubiquitous.
These days, if I have to quickly find out which node a SQL Server instance may be running, I generally run the following command on my workstation:
cmd>tasklist /S ServerNodeName | findstr sqlser
You should run this commend once for each node in the cluster. For me, this is by far the quickest way, primarily because it’s ubiquitous, requires no prior setup, and can be executed anywhere as long as there is connectivity and permission.
It works well with any single SQL Server instance cluster. If you have two or more SQL Server instances in a cluster, you can see where all these instances are running, but you can’t tell one from another. That is, if you use the above command to check all the nodes and find more than one sqlservr.exe, you may not be able to tell which sqlservr.exe is what you are looking for without further checking.