Microsoft Office Tutorials and References
In Depth Information
Now you know how to add a user (or security group if you desire) to Central
Administration’s Farm Administrators group.
POWERSHELL AND STANDALONE INSTALLATIONS
PowerShell is a new command env ironment for manag ing SharePoint. In order to use PowerShell,
you must be logged in with an account that can use PowerShell. Once logged in with a PowerShell
admin account, you can run the Add-SPShellAdmin command and use it to create more
PowerShell admins.
Now often this causes a bit of a conundrum, because to give an account PowerShell admin rights,
you have to be logged in with an account that already has PowerShell admin rights.
However, for Standalone installations it’s easy. Because the databases are on the same server as
SharePoint, and because the account you used to install SharePoint owns those databases, it’s
easy to use that account to either do your PowerShell tasks, or at least use it, once SharePoint is
completely configured, to create other PowerShell admins.
If you are interested in practicing with PowerShell, a Standalone installation is the easiest to get started
in terms of permissions. For more about PowerShell, see Chapter 14, “STSADM and Powershell.”
S I T E C O L L E C T I O N A D M I N I S T R A T O R S
Now that you know how to add farm administrators to manage Central Administration, it’s
time to go one level down and see how to add administrators to site collections.
In both of the SharePoint installation types, among the elements created, whether manually
in a Complete installation or by the configuration wizard in a Standalone installation, were a
web application (remember SharePoint-80 in IIS?) and within it a site collection for you to get
started with. The first site created in a site collection is, by default, the top-level site. There can be
other sites that stem off that one, but there always has to be one top site. The top-level site
contains all the settings for the site collection.
To administer that site collection, create lists, add users, and change settings, there must be
site collection administrators. A site collection administrator will have power over not only the
top-level site of a site collection but all subsites contained therein. Permissions and settings trickle
down by default from the top-level site to all subsites (although subsites can be configured to
break inheritance), and that means site collection administrator control trickles too.
As with Central Administration, in the Standalone install, SharePoint, by default, used the
only account it knew—the account that installed it, to be the site collection administrator. Either
way, our site collection has one administrator. In case of emergency, there should be at least two.
To add a site collection administrator to a site collection after the collection has been created,
open the browser (preferably Internet Explorer of course), use the server address (mine is http://
spf1), and log into the site as a site collection administrator (my account is spf1\administrator).
1. Once logged in and on the home page of the top-level site, click the Site Actions tab (top
left), and select Site Settings from the bottom of the drop-down menu (Figure 2.62).(You
 
Search JabSto ::




Custom Search