Archive

Archive for the ‘WSS 3.0’ Category

SharePoint 2007 Patching, SharePoint 2010 Site Usage Confirmation

August 30, 2012 1 comment

A couple of patching issues have come up recently that are worth sharing.

Security Update for WSS 3.0 Patch, July 2012

http://support.microsoft.com/kb/2596911

We saw this coming through a customers WSUS system, and almost approved it but I decided to take a look at the KB article, the thing that caught my eye was .

After you install this security update, PSCONFIG may run automatically.

From bitter experience we know that this is a bad thing….the WSUS installer will not have any SQL permissions, so this can leave you in a position with different binaries versions on your servers to the schema versions in your databases, so either install by hand or use the PATCH_ARGS=runupgrade=no switch on the command line and deal with PSConfig in a more controlled manner.

SharePoint Site use Confirmation and deletion.

As from the June 2012 CU for SharePoint 2010 the sites deleted by the usage confirmation job will now appear in the recycle bin, so if your using site usage confirmation get the June 2012 installed.

http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=149

Advertisements
Categories: MOSS, SharePoint 2010, WSS 3.0 Tags:

Documenting a SharePoint Farm

February 20, 2012 Leave a comment

Anyone involved with the building / running / supporting of a SharePoint system will know how important documenting the original build configuration is.

If you build farms using the excellent AutoSPIntaller, then most of your work is already done as you have to plan things like your service accounts and database names for the inputs.xml file.

But what if you are called into look at a system that you know nothing about ?. in this case the equally excellent SPSFarmReport will come to your help.

The download zip file has versions for both WSS 3.0 / MOSS (32 & 64 bit) and SharePoint Foundation / SP2010 / Project Server 2010.

Once downloaded onto one of your servers with the binaries installed, simply run the appropriate executable under Farm account credentials, once ran you can delete the executable if needed.

The report output file is a nicely formatted HTML document that covers just about every single aspect of your farm configuration, this can be used to create your documentation guide, and as a timed snapshot of your configuration for future comparison.

%d bloggers like this: