Microsoft Office Tutorials and References
In Depth Information
For example, say you have a branch office—a different location with its own group of people,
unique needs, and documents. At first, you might be tempted to give that location its own
subsite off your main top-level site. However, there will be times when this arrangement is less than
optimal. For example, you’d have to give those subsite users permissions in the site collection and
handle the increased administration required to restrict their account groups to their subsite.
With a new site collection, you have a whole new top-level site, with new users and groups. You
could then give the branch office’s IT department administrative rights to that site collection. The
branch office administrator could then manage that office’s own sites, permissions, and subsites—
without having access to your main SharePoint site. They could have their own templates,
navigation, permissions, logo, and whatever they like, and you wouldn’t have to worry about them.
New site collections can be created using PowerShell or STSADM or using Central
Administration. For this example, we’ll be using Central Administration’s interface so you can
get an idea of what settings are required (because the GUI will have descriptions that the
command line and shell tools won’t). To create a site collection, follow these steps:
1. Open Central Administration. You can do so using the SharePoint 2010 Central
Administration link in the Start menu, or you can enter the URL for the server and the
port for Central Administration. In my example, that would be http://spf2:9876 .
2. The Create Site Collections link is under the Application Management category in
Central Administration. Click this link to go to the Create Site Collection page, as
shown in Figure 10.1.
Here you’ll configure your new site collection and the required top-level site that will
start this collection.
The Create Site