NOTE: I implemented this is a lab envirnoment. I would recommend this approach before attempting any of the steps below on a production system (to allow for any adjustmensts or tailoring of steps for your setup).

1. Run “SharePoint Products and Technologies Configuration Wizard”

2. Click “Next” followed by “Yes” (stop services)

3. Select “Disconnect from this server farm” and click “Next” followed by “Yes”

4. Click “Finish”

5. Detach all MOSS databases (configuration and content) from SQL Express

6. BACKUP DATABASES

7. Stop SQL Server Express Service

8. Attach all MOSS databases (configuration and content) to new SQL Server 2005

9. Run  “SharePoint Products and Technologies Configuration Wizard” again

10. Click “Next” followed by “Yes” (stop services)

11. Select “Yes, I want to connect to an existing server farm”

12. In Database Server text box enter name of server where SQL Server 2005 is installed

13. Click “Retrieve Database Names” – This should return the configuration database now on SQL Server 2005

14. Under Specify Database Access Account enter DOMAIN\User_Name (domain account with access to DB) and password

15. Click “Next”

16. Specify port number for Central Admin - should default to old port number, if not enter old port number

17. Click “Next”

18. Confirm configuration settings and click “Next”

19. Click “Finish”

20. Once complete Central Administration will automatically open up

Within Central Administration you will need to restart any services which are not started and create a new search database.

Hopefully this will have done the trick and you are now up and running again but using a different database :)

Also, the following "Migrate Content Databases" TechNet article is worth reading if you are interested in the topic:  http://technet2.microsoft.com/windowsserver/WSS/en/library/03c94172-a203-4d47-bf9f-239bb6647aa61033.mspx?mfr=true 

Note:It is essential that you read Planning and deploying SP1 for Microsoft Office SharePoint Server before attempting this task.

I ran into a small issue when attempting the install WSS 3.0 SP1 on a WFE server, failing after step 2.

I investigated the issue (check log file) and set out to re-install WSS 3.0 SP1. Running the installation for SP1 again greets you with "The update is already installed on this system":

Now I knew that wasn't true sure I witness SP1 kicking me out after step 2 :) After some further investigation I found out to re-install a failed SP1 installation you need to use STSADM.exe in the command line:

§  stsadm -o upgrade -forceupgrade –inplace

This fixed all my problems and a smooth MOSS SP1 deployment followed. I hope this helps you if you are left banging your after a failed SP1 install.

Check out the press release here for more details.

"Update the password for the account that is used by the Central Administration application pool. To do this, follow these steps: a. On all servers in the server farm, open a command prompt, type the following line, and then press ENTER: cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin b. On the server that hosts the Central Administration Web site, type the following line at the command prompt, and then press ENTER: stsadm –o updatefarmcredentials –userlogin DomainName\UserName -password NewPassword c. On all other servers in the server farm, type the following line at the command prompt, and then press ENTER: stsadm –o updatefarmcredentials –userlogin DomainName\UserName -password NewPassword -local d. Restart Microsoft Internet Information Services (IIS) 6.0. To do this, type the following line at the command prompt, and then press ENTER: iisreset /noforce"

To prove you can change the username as well I kicked off my VPC....  Here are a few screen shots to show you it working :)

SharePoint Central Admin App Pool – Before updating username and password:

STSADM.exe command run: Note: IIS did moan a little when I tried to iisrest /noforce - once I did a full iisreset everything restarted with out error.

SharePoint Central Admin App Pool – After updating username and password:

Remember never ever under any circumstances attempt to change app pool accounts directly within IIS!!! This is what STSADM is for :)

Over all changing usernames and passwords of SharePoint service accounts is a fairly important feature of STSADM; especially as company security department policies dictate not just changing passwords periodically but usernames as well.

- What is the necessary hardware investment?
- What kind of topology is needed to meet organizational requirements for availability and performance?
- How will additional users from a recent merger affect deployment?

When planning a new SharePoint deployment, you will need a way to quickly characterize the general topology and minimum hardware requirements to support expected usage loads with adequate performance. You will need a way to explore plausible scenarios and get pointed in the right direction. The SharePoint Capacity Planning Tool gives you a quick way to draft topology and equipment sizing for your particular scenario and usage profile.
This solution reduces "SharePoint sizing" estimation efforts from a matter of days to a matter of hours.

Description of the Tool

Imagine a tool that you could use to input a few key facts about users, user needs, business requirements, and organizational resources in order to:
- Build a topology model based on this input
- Run simulations that show the impact of this topology
- Generate a summary report that will help you evaluate alternatives
The SharePoint Capacity Planning Tool consists of System Center Capacity Planner 2007 (SCCP) models for:
- Microsoft Office SharePoint Server 2007 (MOSS)
- Windows SharePoint Services 3.0 (WSS)

The tool can be used for planning and feasibility studies of a deployment project to give you a rough estimate of hardware requirements. The tool can generate estimated performance metrics based on a simulation and provide useful Visio schematics of the proposed deployment to be included in documents and proposals.

You can obtain the SharePoint Capacity Planning Tool on Microsoft Download. For a short introduction to the tool and its usage, please go to this TechNet overview page: http://go.microsoft.com/fwlink/?LinkID=93030
Note: This Solution Accelerator needs SCCP 2007 to be installed first.

Downloads
SharePoint Capacity Planning Tool on Microsoft Download Center
System Center Capacity Planner

• Supported global solutions and recommendations for Office SharePoint Server 2007 deployments
• Extending Office SharePoint Server global solutions with Office Outlook 2007 and Office Groove software
• Design global information architecture and governance
• Plan for global enterprise search
• Plan for bandwidth requirements
• Optimizing Office SharePoint Server for WAN environments
• Optimizing custom Web parts for the WAN

Happy reading :)

Here are some resources and links that you should find helpful:

• Improvements in accessibility
• Accessibility Kit for SharePoint (AKS) - AA compliance toolkit
• Telerik Rich Content Editor

"The Accessibility Kit for SharePoint (AKS) provides templates, master pages, controls, and web parts along with technical documentation that enable designers and developers to advance the accessibility of Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services (WSS) 3.0 based web sites and applications for people with disabilities, especially those who are vision impaired.

Microsoft has hired HiSoftware to develop the AKS. The decision was made primarily based on HiSoftware’s in-depth expertise and broad industry experience in providing tools and services for improving software accessibility to the point of compliance with key industry and goverment standards and beyond. The contractual Statement of Work calls for HiSoftware to deliver a kit that can significantly reduce the time, knowledge, and effort required to implement a SharePoint-based web site that conforms to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 1.0 Priority 1 and 2 checkpoints, which are collectively known as WCAG 1.0 AA. The AKS can also be used to address the exceptions that have been identified in the U.S. government’s Section 508 of the Rehabilitation Act’s Voluntary Product Accessibility Template or VPAT documents for MOSS 2007. While most of our customers find the improvements in accessibility (more info at Office Online) over previous versions of SharePoint to be adequate for their needs, a growing number has asked us to provide even more. The AKS is our near term response. Longer term, we plan to make significantly further improvements in accessibility in the next version of SharePoint, but we don't have any details to disclose at this time." .... codeplex.com

InfoPath 2007 however, does not meet WCAG 1.0 level of accessibility. This is primarily because WCAG 1.0 restricts the use of scripting (checkpoint 6.3) which is something that InfoPath relies on extensively. In my opinion Microsoft is definitely acting on the need for accessible Web sites (hence AKS). Now I just hope there will be some sort of accessibility kit released for InfoPath or that the next Office wave addresses this need. Until then there is always custom .NET :)

BTW: I have seen a couple of cool sites were MOSS and accessiblity (WCAG 1.0 AA compliant) have been deployed really really well ... check out:

• http://www.plymouthhospitals.nhs.uk/Pages/Home.aspx 
• http://www.wise-woman.net/Pages/default.aspx

I am sure there are plently more but these two jump to mind :)

Other important links:

• W3C WCAG 2.0
• W3C ATAG 2.0

I bought a new 160GB 2.5'' external hard drive.... sure why not! Anyhow, when I tried to format the drive I received the following error message "All NTFS boot sectors are unwriteable. Cannot Continue." Screen shots below:

Screen shot of my reaction:

Not really :) but that's how I felt when I searched the web and couldn't find anything to help resolve the issue. In the end I simply deleted the partition and formatted the drive without any problems or errors. For some reason the initial partition must have been corrupted somehow and caused the format to fail. Hopefully, this doesn't happen to you but if it does you know what to do!