viernes, 26 de octubre de 2012

Reusing a server in a SharePoint farm


The last days we have been working hard to get some farms built in a record time, and the main issue and time consuming was the fact that we´re reusing servers. Now I can say it´s the worst idea ever.

When you remove a server form a SharePoint farm (you might check the procedure here) many configurations remain on the server, from the hive folder until the web.config of the Internet Information Services (IIS). If you really need to reuse a server but you don´t have the choice to reinstall the operating system take into account at least some steps to clean up the environment;

  • Delete the hive folder: program Files\Common files\Microsoft Shared\Web Server Extensions\14
  • Remove the Application and IIS feature of the server. And here comes the point; you should first uninstall any SharePoint product, stating always with any language pack.So you should:
    • Remove SharePoint language pack
    • Remove SharePoint server
    • Remove application and IIS feature
    • Restart the server
    • Install the application and IIS feature
    • Install SharePoint prerequisites
    • Install SharePoint server
    • Install language pack (foundation and server) ... for sure I´m missing some restarts of the server ...
 After my experience I´m willing to reinstall the operating system and apply any necessary  update prior to try to reuse a server that was before a SharePoint server.

miércoles, 24 de octubre de 2012

How to add the role of Central Administration in your farm


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:

 
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:


Now the Central Administration web page will open on both URLs.