Microsoft Office Tutorials and References
In Depth Information
C O N F I G U R E A L T E R N A T E A C C E S S M A P P I N G S
This setting is also located (and explained in more detail) under Application Management, in the
Web Application subcategory. The link takes you to the Alternate Access Mappings page, where
you can specify the public and private URLs for web applications, as well as a link to specify an
outside resource URL to be used by the farm. For more step-by-step details, see Chapter 10.
M A N A G E F A R M F E A T U R E S
Features can be scoped to be applied at the level of the farm, web application, site collection,
or even site. This capability is specified in the feature’s contents and cannot be forced during
install. The Manage Farm Features setting displays the features that are scoped to be available
at the farm level.
A feature simply changes or adds to the functions that SharePoint can do. It usually consists of
one feature.xml file and occasional supporting files that are installed in SharePoint’s Features
folder (where all default features are located). Features are then activated per their scope (that’s why
you can manage features at the farm, web application, site collection, or site level).
The only place you can install or uninstall features is at the command line using STSADM or
PowerShell. However, if you have added features to your SharePoint server that are scoped for
the farm level, they’ll be listed here. For more about adding features to a server, see Chapter 14,
“STSADM and PowerShell.”
If a feature is applied, you can activate it either at the command line or on the Features page
at the level for which it was scoped.
On the Manage Farm Features page (Figure 11.39), you can see whether there are any
features available at that level. In my example, you can see that a feature (Office.com Entry Points
from SharePoint) is available for the farm and is activated. Remember, features can be added to
SharePoint as features on their own or as part of a larger solution.
The Manage Farm