Book Image

Microsoft SharePoint 2010 Administration Cookbook

By : Peter Serzo
Book Image

Microsoft SharePoint 2010 Administration Cookbook

By: Peter Serzo

Overview of this book

Collaboration and content management are the major business needs of every organization in this increasingly global and connected environment. Microsoft SharePoint is a solution to these needs that offers a software platform that facilitates collaboration and provides content management features for the effective implementation of business processes. With a vast amount of functionality available with SharePoint, it is easy to get confused in carrying out administrative tasks. Microsoft SharePoint 2010 Administration Cookbook starts off by demonstrating the various upgrading and post-upgrading tasks to be performed in SharePoint 2010. Next come recipes for managing SharePoint service-level applications and for monitoring the SharePoint environment. The book introduces one of the best new tools that should be in your arsenal, PowerShell, and the commands you will need to script your tasks with Powershell. Collaboration and content management are the most important features of SharePoint and this book contains many recipes that focus on improving them. Enterprise monitoring and reporting are also covered in detail so that you can ensure that your SharePoint implementation is up and running all the time. You will find recipes to manage and customize SharePoint Search. When you are half way through the book, you will explore more advanced and interesting topics such as customizing and securing the SharePoint environment. You will learn to extend SharePoint to include features similar to social networking sites such as Facebook and Twitter. Lastly, the book covers backup and recovery solutions for SharePoint so that you can ensure that your system is protected from data loss and virus attacks.
Table of Contents (17 chapters)
Microsoft SharePoint 2010 Administration Cookbook
About the Author
About the Reviewers

Creating an Alternate Access Mapping (AAM)

SharePoint's repository is the content database that resides in the SQL server. These databases house all the data for an organization. Organizations may require that users outside the company have access to a subset of this data. For example, vendors may wish to see if their invoices have been paid.

Another example at a large enterprise is hourly workers may see a different subset of data than salary workers. The data all resides in the same content database.

Appropriately architecting the taxonomy and authentication lead into providing two different URLs. The end user will put in the appropriate URL and be directed to the trimmed content associated with that URL.

This is the point of AAMs. This recipe shows how to set up an AAM and the components involved.

Getting ready

Ensure that you are a member of the Farm Administrators SharePoint group on the computer accessing the Central Administration site.

There should also be an existing web application.

How to do it...

  1. 1. Open the Central Administration screen and click System Settings.

  2. 2. Under the Farm Management section, select the Configure alternate access mappings option.

  3. 3. A list of the current AAMs, associated with the web application, will be presented. This will be shown in the upper right-hand portion of the screen.

  4. 4. Click Add Internal URLs.

  5. 5. Fill in the data in the screen that appears. In the following screenshot, we have entered a URL as an example:

  6. 6. Click Save. The updated listing of AAMs will be visible.

  7. 7. Set up DNS to correctly reference the URL that was just entered.

How it works...

When the URL is entered by a user, IIS takes the page request and passes it to SharePoint. It is SharePoint's job to fulfill this request. SharePoint checks the AAM to make a decision on which web application to map the request.

There's more...

A point of confusion about AAMs is that they can be used for redirecting sites, with a completely new URL, to a custom port. For example, consider the following URL: http://spmysite:2222.

This URL cannot be redirected to a URL such as http://mysite.

If a SharePoint site is created on a port other than port 80(HTTP) or port 443(HTTPS), the port number must be supplied. AAMs deal only with the base URL for a web application.

More info

Host headers allow IIS to use a single port for multiple sites on the same machine. The result of this is that organizations do not need to use custom ports. That is why in this book, we have asked to use port 80.

See also

  • Extending a web application