If the site is top-level, then follow the following steps in order to create a new content database:

1. Log into Central Administration and go to: Application Management, Content Databases
2. Click “Add a content database”
3. Select the default database server (NIPR: c556\moss2007)
4. Set the database name to: WSS_Content_<site name>
5. Leave other settings as default
6. Wait for the Content DB to be created, and then:
7. Click on the database name
8. Check the “Remove content database” checkbox
9. Click OK

We will now log into the SQL server and go through the following steps to allocate the files to the correct disks.

1. Connect to the database server using SQL Server Management Studio
2. Find the newly created database (named the same as the content database in MOSS)
3. Right-click the DB, choose properties, click on Files, and note the location of the mdf and ldf files
4. Right-click the DB again, select “Detach”
5. On the next screen, check the box for “drop connections” and “update statistics” and click OK
6. Go to the disk you noted above, and move the files to the proper location (insure you MOVE, and don’t just COPY)
   1. NOTE: generally, the data and log files are kept on separate, paired disks (eg. E/F, G/H, etc).  Just pick a pair of disks that has enough room for the new site.
7. Back in SQL Server Management Studio, right-click “Databases” and select “Attach”
8. In the new window, click “Add”
9. Navigate to the database and select it
10. In the second window, the log file will be unfound.  Click the ellipsis next to the “Current file path” field and navigate to the new location.
11. Click OK to re-attach the database.  You may need to refresh the view in order to see the DB in the list.

We will now return to MOSS to re-attach the database

1. Return to the “Manage Content Databases” page from above
2. Click “Add a content database”
3. The database must be named identically as before in order to attach to it, otherwise a new database will be created
4. Click OK
5. The new Content DB will appear in the list
6. Go back to SQL Server Management Studio and confirm that a new database wasn’t created.  If you named them correctly, there should only be the one database.

In order to control where the new site is placed in MOSS, we must deactivate every other Content DB, so only our new DB is “started”

1. One by one, click on each Content DB and set “Database status” to “Offline”
2. Once finished, every Content DB should appear as “Stopped” in the list.  Only the new Content DB should read “Started”

Create the new site in MOSS

1. Click on the “Application Management” tab to return to the parent page
2. Under “SharePoint Site Management” click on “Create Site Collection”
3. Fill in the site title, description, and URL
4. Insure that you choose “/sites/” from the URL drop-down!
5. Fill in the site collection admin with the MOSS service account: EUR\svc.moss.adm.hqu
6. Click OK
7. Wait for the site to be created
8. Confirm that the new site is operational
9. Return to the Application Management page and navigate to “content databases”
10. Re-activate all the content databases, so that “Database Status” is “Started” for all of them

We’ll now set the site up with the default look & feel

1. On the new site’s root page, click “Site Actions” and then “Site Settings”
2. Under “Users and Permissions” click “Site collection administrators”
3. Add any additional administrators
4. Under “Look and Feel” click “Site Theme”
5. Select “Lichen” and Apply

The site is now operational.

1. Log into Central Administration and select the SSP of the Site Collection where you want to run the trusted location.  You may need to click on the “Operations” or “Application Management” tab at the top in order to see the list of SSPs, as below:

2. Click on the SSP where you want to create the trusted site.  You will be brought to the “Shared Services Administration” page.

3. Click on “Trusted file locations”

4. Click on “Add Trusted File Location”

5. The new page has a lot of info.  Fill in the following information:

• Address: Enter the full Windows SharePoint Services location, network file share or Web folder address of this trusted location.
• Location Type: select the type of location you want to make trusted (Usually “Windows SharePoint Services”)
• Trust Children: select this option if you want sub-libraries and sub-directories to be trusted as well
• Description: is optional, but might help you in 6 months when you can’t remember why you set this up
• The rest of the fields should be self-explanatory.  I left everything as the default.  Once you’ve filled everything in, click on “OK”

 6. You should now see the new Trusted File Location listed