May 2007 Archives

Good stuff, looks like they are building their library all the time.

http://www.learnsharepoint.com/

Now I just need to find a similar Office Sharepoint 2007 resource.

A classic, had to bookmark it.

http://www.youtube.com/watch?v=nQq2MjX3Y_0

Who wants to read a giant and so far (painfully normal for Sharepoint info) innacurate and deplete of information, manual.

So, here is my short list of steps to upgrade WSS from 2.0 to 3.0.

1. Set your WSS 2.0 database to read only (note: only if you are migrating to a different system as a phased approach)
2. Backup everything (duh)
3. Install Sharepoint 3.0
4. Run PreScan (note, you need to do this before step 5, despite what the popup wizard tells you)
5. Run WSS Configuration Wizard

Don't forget your friend iisreset /noforce :)

Took a while to find this one AND it isn't totally useful for MOSS/WSS 2007/3.0 installations but it could help.

http://h71019.www7.hp.com/activeanswers/Secure/79168-0-0-0-121.html

For reference:

SQL Server 2000 (MSDE): 2GB

SQL Server 2005 (Express): 4GB

http://www.sunbelt-software.com/ihs/alex/marx/detections_2007q2.htm

Ever wondered how your Antivirus Product Stacks Up? Good listing here, too bad it isn't sortable.

So... I did.

YouTube - Broadcast Yourself.

YouTube - Dave Weckl, Vinnie Colaiuta, Steve Gadd

This clip is a must see! 3 of my favourites, together!

DNS Stuff - http://www.dnsstuff.com

DNS Reports - http://www.dnsreport.com/

These brief documents were worth a review as WSS 3.0 permissions are quite a bit different than in previous versions.

Microsoft Permissions briefs

Permission Management Utility (haven't tried it yet though)

Ps. thanks Avi.

I've been seeing this happen quite a bit...

WHAT?
SQL Server disks are filling up with backups from Database Maintenance Plans despite having settings that they should be removing transaction log or database backups after X days.

SO WHAT?
The problem is that a Database Maintenance Plan cannot properly purge these backups if the job contains any databases that have mismatched backup job 'recovery modes'. For example, most databases by default start off with the 'Full' Recovery Mode, yet some system databases only allow the 'Simple' Recovery Mode.

As defined in http://support.microsoft.com/kb/303292/en-us , this just won't work (i.e. your backup files will grow and grow and grow and never get lopped off 'after Y days' as you might have defined in your maintenance plan.

NOW WHAT?
Well, you can approach this several ways but possibly the best way is to follow these simple rules:

- Create a separate database backup plan for your User Databases (production) and a separate database plan for your System Databases

- Should you decide to change the recovery mode for a Production Database, be sure to have a separate Database Maintenance Plan (or perhaps have a 'Full Database Recovery Maintenance Plan' and a 'Simple Database Recovery Maintenance Plan'

- Consider having a separate plan altogether for the 'other' actions you might want, such as optimizations and integrity checks so that any failure of these do not disrupt the success of your backups

Check 'em out...

http://www.microsoft.com/technet/community/en-us/exchange/webcasts.mspx

Great stuff but most useful if you run it BEFORE you have problems so you have something to compare to.

http://www.microsoft.com/downloads/details.aspx?familyid=61a41d78-e4aa-47b9-901b-cf85da075a73&displaylang=en

and

http://www.microsoft.com/downloads/details.aspx?familyid=09115420-8c9d-46b9-a9a5-9bffcd237da2&displaylang=en