As part of
the high availability procedure, the central administration service should be
in more than a server. That way you ensure the availability of the service.
What happens when you add the service to a different server? Let´s
discover it!
Imagine a farm of 5 servers: 3 WFE, 2 App servers (Query/Crawl) and a SQL server.
Let´s call them that way:
WFE01.dragons.com >> Central administration
WFE02.dragons.com
WFE03.dragons.com
QRY01.dragons.com
CRA01.dragons.com
SQL01.dragons.com
Let´s look
at the AAM (alternate access mapping), select the Central Administration web
application and you will see:
Now we want
to add the role of the CA to the following server: CRA01.dragons.com
Go to
Central administration > services on server and select the server CRA01.dragons.com. Look for the
service "Central administration" and press "start". It will
take a while, it depends on how large your farm is. Take it easy.
When it will
appear "started" a new site called "SharePoint Central Administration v4" appears in the IIS of the server.
Now let´s check the alternate access mapping and you will find this
configuration:
|
Default
|
||
|
Default
|
Maybe this
doesn´t mean anything for you, so let´s check if the get our goal:
Open an IE
and write down the new URL of the CA: http://cra01.dragons.com
, and after a while it will appear the CA , could you please let me know
which URL appears in the navigator? Maybe this one? http://wfe01.dragons.com??
The key is
the AAM. It seems that when you add the service SharePoint creates a new entry
in the AAM, but as a redirection to the original Site. If we need to ensure
high availability of the service we need the service to respond on another
server.
Solution:
Change the alternate access mapping, and assign the new URL to another Zone. For
example:
|
Default
|
||
|
intranet
|
Now the
Central Administration web page will open on both URLs.
