Collab365

Stop Hunting SharePoint CA URL: PowerShell + Registry Hacks

Q: How to get SharePoint Central Administration URL across the farm?

Run: Get-SPWebApplication -IncludeCentralAdministration | Where {$_.DisplayName -match "SharePoint Central Administration*"} | Select DisplayName,Url

Q: How to verify if the current server hosts Central Administration?

Use: Get-SPWebApplication -IncludeCentralAdministration | Where {$_.IsAdministrationWebApplication} | Select DisplayName,Url

Q: How to find Central Administration URL via Registry without PowerShell snap-in?

For 2013: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\" -Name CentralAdministrationURL. For 2010: Use 14.0 path.

C

Collab365 TeamAuthorPublished Dec 23, 2016

361

At a Glance

Target Audience: SharePoint Administrators
Problem Solved: Wasting time manually hunting Central Administration site URL across multi-server SharePoint farms via IIS or logins.
Use Case: Quickly mapping SharePoint farm infrastructure or verifying CA host during troubleshooting on specific servers.

Most SharePoint admins waste time hunting for the Central Administration site. They log into multiple servers. They dig through IIS manager hoping to spot it. It is a massive waste of time. You do not need to click around to map your infrastructure. You just need to ask the server directly. Here is the exact process to locate your CA URL without the guesswork. <h3 id="the-n-tier-farm-search">The N-Tier Farm Search</h3>If you are running a multi-server architecture, you need to know exactly where your admin center lives. The fastest method is querying your web applications. Run this PowerShell cmdlet to pull the URL across the farm: <pre><code class="hljs language-powershell">Get-SPWebApplication -IncludeCentralAdministration | Where {$_.DisplayName -match "SharePoint Central Administration*"} | Select DisplayName,Url </code></pre>That works perfectly when you just need the address. But what if you are troubleshooting a specific node? You need to verify if the machine you are currently logged into is actually the host. The previous command will not confirm that for you. To verify the local machine, filter by the administration property instead: <pre><code class="hljs language-powershell">Get-SPWebApplication -IncludeCentralAdministration | Where {$_.IsAdministrationWebApplication} | Select DisplayName,Url </code></pre><h3 id="the-registry-route">The Registry Route</h3>Sometimes you are on a server and the SharePoint PowerShell snap-in is not loaded. Do not panic. You do not need the snap-in to find the truth. The URL is hardcoded into the Windows Registry. You just need to read the right version path. For SharePoint 2013, query the 15.0 hive: <pre><code class="hljs language-powershell">Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\" -Name CentralAdministrationURL </code></pre>For SharePoint 2010, simply drop down to the 14.0 path: <pre><code class="hljs language-powershell">Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS\" -Name CentralAdministrationURL </code></pre>Stop guessing where your admin center lives. Do the boring work. Run the commands. Get your answers and move on.