Microsoft Office Tutorials and References
In Depth Information
: This does a Basic SharePoint installation. Intended to install SharePoint
conveniently for evaluation, it has three options: provision, which simply installs SharePoint;
port, which allows you to specify the port used by the default SharePoint web application (if not
specified, 80 will be used); and overwrite, which will overwrite an existing IIS Web Site with
the new web application. Normally, if you specify a port that is already in use by SharePoint, it
will be shut down, and SharePoint will create its own website without disturbing the first one.
With overwrite enabled, it will replace the existing web application.
: This parameter copies the web application binaries, files, and other
shared application data for SharePoint to the web applications. This is good if you think those
files may have been removed or corrupted.
: A standard installation parameter, this will run the configuration wizard steps without
output. The data is written to a psconfig.exe [date] .log file.
: This parameter is what SharePoint uses to upgrade (or migrate) existing WSS 3.0
installations. This parameter has the option to do side-by-side or in-place upgrades. It has
an option, reghostonupgrade, which reverts customized pages to the WSS defaults. Other
options include inplace, preserveolduserexperience, and passphrase. Other
parameters, such as force, wait, and finalize, are used to control the upgrade process. For more
on upgrading SharePoint, see Chapter 15, “Migrating from Windows SharePoint Services 3.0
to SharePoint Foundation 2010.”
The syntax for using PSCONFIG is as follows:
psconfig.exe -cmd [parameter] parameteroption -
An example of this is as follows:
psconfig.exe -cmd setup -lcid <1033>.
If you are going to use PSCONFIG to automate the installation of servers in your server farm, make
certain that the installation of binaries (the initial installation step before configuration) has been
run on each server to install the necessary files PSCONFIG requires locally. You can string
parameters together to have one long command, but keep in mind that they execute in a certain order.
The order shown here is the order they run, with the upgrade going last.
So if you don’t like the graphic user interface or were wondering how to automate your SharePoint
installation, PSCONFIG might be what you’ve been looking for.
Initial Farm Configuration
At this point, you need to manually do some configuration tasks that were done
automatically in the Standalone installation. They are as follows (roughly in the order they’ll be
done in this chapter):
Configure managed accounts. New with this version of SharePoint, you have to register
the accounts used by web applications and services if you want to use something other
than the farm account for their application pool identities. Managed accounts allow
SharePoint to manage the passwords for those accounts, avoiding password expiration
or issues that might be caused by changing the account passwords outside SharePoint. It
helps to configure all the managed accounts you are going to use for the farm, before you
start configuring services and web applications.