A blog by Jose Barreto, a member of the File Server team at Microsoft.
All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights.
Information on unreleased products are subject to change without notice.
Dates related to unreleased products are estimates and are subject to change without notice.
The content of this site are personal opinions and might not represent the Microsoft Corporation view.
The information contained in this blog represents my view on the issues discussed as of the date of publication.
You should not consider older, out-of-date posts to reflect my current thoughts and opinions.
© Copyright 2004-2012 by Jose Barreto. All rights reserved.
Follow @josebarreto on Twitter for updates on new blog posts.
I’m working on a step-by-step procedure to install Microsoft Office SharePoint Server 2007 Beta 2 (MOSS 2007), to allow my customer to create their environment by themselves. The main difficulty they have right now is the exact sequence to follow to get a basic infrastructure for team collaboration with self-service site creation, search and my sites. The Administrative Tasks list in Central Admin is supposed to help with this, but they could not do it themselves because of a number of dependencies in the several steps.
You can do this in a single server, but for my testing I am using one server (Server1) for AD/DNS/SQL and another server (Server2) for MOSS. I'm also using host headers for the three main web sites: "team" for the team sites, "my" for the my sites and "ssp" for the shared services provider. They all point to Server2 in my configuration, but this allow for future growth.
Here’s my first draft:
Your SQL Server will end up with 8 databases, listed in the order they are created:
That should be enough to enable a fully functional http://team with a site directory, search center, “Create new site” link and my sites at http://my. With proper DNS and/or load balancer configuration, these steps would also allow for adding more web front end servers, because of the use of host headers.
Please note that the procedure was created by experimentation and it could be incomplete (although I did test it with the Beta 2 version currently available for download). Suggested settings might not apply to your specific configuration. Try it at your own risk.
* I noticed that if I set the quota template, self-service site creation might fail with an error message. Not sure if I’m doing something wrong, if additional permissions are needed or if it’s a bug in beta 2.
** I noticed that, although the sites are properly added to the site directory, the URL is not properly populated. It would be fairly simple to create a workflow to update this information based on the Title. The way it is, the approver needs to update the URL before approving. The URL for approving sites in the directory would be http://team/SitesList.
Good guide from Jose Barreto on the steps to configure a basic MOSS 2007 farm.
Might be useful if...