MOSS 2007 auditing by Mark Deraeve

I was asked today to enable auditing on a document library because there are always documents dissappearing from this library. Never having done this before I googled a little around and found an excellent article on how to configure this on a site collection written by Mark Deraeve.

If you need to set it up, then go read Mark’s article at


MOSS 2007 with SP1 (Slipstream) Released

Finally, Microsoft has released the installation source for MOSS 2007 with SP1 slipstreamed. No more installing MOSS2007, then WSS 3.0 SP1 followed by MOSS 2007 SP1. these installation sources make history of that.

Beware these sources are for new installations only, so do not use them for upgrading an existing MOSS 2007 installation.

Find the sources here:

Office SharePoint Server 2007 with SP1 (32 bit)
Office SharePoint Server 2007 with SP1 (64 bit)

Note: You’ll notice two executables: OfficeServer.exe 295.0 MB and OfficeServerwithSP1.exe 409.2 MB.  The OfficeServer.exe is the full RTM version.  The OfficeServerwithSp1.exe is the new special slipstreamed version which is RTM plus the SP1 (slipstreamed).

Now these are the executables for the Trial Version of MOSS 2007. I haven’t checked yet on MSDN to see if there are also RTM versions available yet. If not, then I guess they will be made available soon.

Configure Moss using psconfig.exe and stsadm

If you have read my post on configuring moss to use a database in an untrusted domain adn have tried it out, you will have noticed that the configuration of MOSS is not yet complete. Actually when running the Config wizard you can see 9 steps being performed. If you used psconfig to create or connect your server to a database, then there are only 3 steps performed.

So here are all the commands for setting up your MOSS using psconfig. The information is based on a blog article I found from Alpesh Nakar

Of course these commands will not work if you are not in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN or have not added this path in your environment variables yet.

psconfig.exe -cmd configdb -create -server <SQL Server name> -database <database name> -user <AD user account> -password <AD user password>
 ( if you are adding an additional server to a farm, replace -create by -connect and stop after the command psconfig -cmd installfeatures)

psconfig -cmd helpcollections -installall

psconfig -cmd secureresources

psconfig -cmd services -install

psconfig -cmd installfeatures 

psconfig -cmd adminvs -provision -port 8000 -windowsauthprovider onlyusentlm

psconfig -cmd applicationcontent -install

Now Alpesh also gives you the stsadm commands to go and finish up the rest of the Moss configuration:

stsadm -o osearch -action start -role indexquery -farmcontactemail [email protected] -farmserviceaccount domain\username -farmservicepassword password -defaultindexlocation “C:\Program Files\Microsoft Office Servers\12.0\Data\Applications”

This starts your Office Search Services.

stsadm -o extendvs -url http://%computername%:8100 -ownerlogin domain\username -owneremail [email protected] -exclusivelyusentlm -apidname “OurSSPon8100″ -apcreatenew -apidtype configurableid -apidlogin domain\username -apidpwd password

stsadm -o extendvs -url http://%computername%:8200 -ownerlogin domain\username -owneremail [email protected] -exclusivelyusentlm -apidname “MySiteson8200″ -apcreatenew -apidtype configurableid -apidlogin domain\username -apidpwd password

stsadm -o createssp -title “Shared Service Provider” -url http://%computername%::8100 -mysiteurl http://%computername%:8200 -indexserver %COMPUTERNAME% -indexlocation “%Programfiles%\Microsoft Office Servers\12.0\Data\Applications” -ssplogin domain\username -ssppassword password

stsadm -o extendvs -url http://%computername%:80 -ownerlogin domain\username -owneremail [email protected] -exclusivelyusentlm -apidname “SiteCollectionon80″ -sitetemplate SPSPortal -apidtype configurableid -apidlogin domain\username -apidpwd password

This will setup your webapps for shared services, my sites, create shared service provider and create your site collection as well.

That’s it.

Setup Moss to use a database hosted on a SQL box in an untrusted domain.

I had to configure a MOSS environment to run in a DMZ with its own Active Directory forest and using a SQL box that is located outside that forest on a separate network.

To configure SharePoint, one of my colleagues pointed me to a KB article that is worth mentioning. The default SharePoint Configuration wizard did not work in this case.

Here is the article:


Database Maintenance for Microsoft SharePoint Products and Technologies

Bill Baer has recently published a whitepaper regarding Database Maintenance tasks specific for SharePoint databases. I have gone though the document and had some mixed feelings about the section regarding shrinking your databases, because I have always read that you should never do that at all….

But Ok, if Bill says you should do it, then who am I?

So go read this whitepaper, because I ‘m sure that your SQL guys have already asked you about this before.