Microsoft Office Tutorials and References
In Depth Information
FIGURE 3.52
The new site
collection’s
home page
And we’ve done it. This SharePoint Complete installation is configured as completely as the
Standalone installation, only using domain accounts and databases on a full-blown SQL server
rather than SQL Express.
At this point, it’s a good idea to go through and quickly confirm what was changed by your
configuration settings. You’ve created databases for Search, BDC, and usage and health, as well
as the web application, so now let’s confirm they are there. You should also check IIS for the
application pools and Web Site changes.
So, let’s go see what SharePoint has wrought.
Confirming Configuration Changes
During the prerequisites and installation, we checked to see what changes occurred on the
server, and now it’s time to see what the final configuration changes did. Again, I’ll go through
this a little faster than in the Standalone installation, because it’s already been done in the
previous chapter.
You know the SharePoint root, at %Program Files%\Common Files\Microsoft Shared\Web
Server Extensions\14, was created; we saw that earlier.
The SharePoint services running on the server are the same, but Search uses the search
account you configured, and the SharePoint timer job uses the farm account (Figure 3.53), and
the User Code Host service uses the account you specified earlier for the Sandboxed Code
service. The other SharePoint services are using local accounts because they interact with the local
server. The service applications we configured don’t run within the context of SharePoint and
don’t have their on services on the server per se.
Search JabSto ::




Custom Search