Microsoft Office Tutorials and References
In Depth Information
Once you do that and that group policy applies to all servers on the domain, whenever SharePoint
(2010 or higher) is installed on one of those servers, it generates a connection point object in the
container in Active Directory. It also helps if you do not configure SharePoint using PowerShell but,
instead, the standard GUI interface or psconfig command. For more details on how to set it up,
look for the TechNet article “Track or Block SharePoint Foundation 2010 Installations.”
If you don’t need to use Active Directory to track your SharePoint installations, you can safely
ignore the error.
Running the Configuration Wizard
Now that you have an idea where you are in terms of changes, let’s start configuration.
1. Back on the Run The Configuration Wizard page in the installation wizard, click Close to
get started (I know it seems odd to click Close to start a wizard, but that’s how it’s done).
If you accidentally or intentionally remove the check from the Run The Configuration
Wizard page (so that the installation wizard closes and doesn’t continue with
configuration), you can just go to Start All Programs Microsoft SharePoint 2010 Products and
click SharePoint 2010 Products Configuration Wizard.
The first page of the configuration wizard, the Welcome To SharePoint Products page
(Figure 3.8), indicates that in order to configure SharePoint, you must know the SQL
server’s name, the name of the configuration database (if it has been premade for you), and
the account name and password of the farm account.
2. If you have the SQL server and farm account information handy (and if you don’t, go get
it), click Next.
3. A dialog box warns you that SharePoint services will be stopped or reset during the
configuration process. That should be fine, since those services aren’t being used by anything
yet, so click Yes.
The Welcome To
Products page
Search JabSto ::

Custom Search