Richmond Code Camp: WSS Upgrading from v2 to v3 coming soon

If you have been looking for the promised slides from my presentation on "Upgrading from WSS 2.0 to 3.0" at the Richmond Code Camp 4, don't give up.  They will be here soon.  I have excuses. 

  • I corrupted my registry
  • I am helping get a new user group going
  • There's too much good football on TV - Go Mountaineers!   (#7 in the BCS)
  • The dog ate my homework

 UPDATE: The slides have been posted to the RCC4 site here

Upgrading from WSS 2.0 to 3.0: Another Approach

Microsoft provides three approaches for upgrading from WSS 2.0 to WSS 3.0. More here.
If you are installing WSS 3.0 on a different server than the existing WSS 2.0, the only approach available is the “Database Migration”. This approach is considered "advanced" and requires additional steps. If you have a WSS 2.0 that has not been customized, this seems likes overkill for such a simple upgrade.
 
The following approach lets WSS do some of the behind the scenes work for you. This approach has WSS 3.0 creating the files needed for a new Web application and configuring IIS.
 
SUMMARY: 
  • Using Central Administration, create a new Web application in WSS 3.0  
    • Create with all of the “production” values desired EXCEPT create a temporary content database. 
  • Using STSADM, attach the V2 content (which WSS 3.0 will upgrade to V3) . 
  • Using Central Administration, remove the temporary database. 
DETAILS:
 
  • Install WSS 3.0 on the new server (if you have not already done so)
  • Copy the WSS 2.0 content database to the database you wish to use for 3.0
    • (copy MyContent2 to MyContent3). 
  • Using WSS 3.0 Application Management:
    • Create a new Web Application          
      • Create new IIS Web site with a temporary database
      • Database Name : wss_Portal_Temp (this database will be deleted, you must use a name of a database that does not already exist when creating a new Web application) 
  • Attaching content from WSS v2
    • Verify the SetupService account is a dbowner for the  MyContent3  database
    • Run stsadm
      • stsadm –o addcontentdb –url http://wss/ -databaseserver MyWSSServerName –databasename MyContent3
      • This might run a while if you have a large database
    • Review log file: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS\Upgrade.log
    • Review the Application event log on the WSS 3.0 server
  • Using WSS 3.0 Central Administration remove the temporary database
    • Application Management tab
    • SharePoint Web Application Management section
    • Content Databases Link
    • In the “Manage Content Databases”
      • Select desired web application in the Web Application dropdown
      • Click the link for the Temporary Database
      • In the “Manage Content Database Settings”
        • scroll to the last section and check “Remove Content Database”
        • Click “OK”

RVSPUG - Another User Group for Roanoke

Roanoke Rocks! 

Three years ago when I had recently assumed leadership of the Roanoke Valley .NET User Group and attendance was waning and I was becoming discouraged, Geoff Snowman, Microsoft DE at the time came to visit.  He delivered a presentation.  I emailed him a thanks and appreciation for visitng with such a smal group.  In his reply, he said Roanoke had a great user group.  The members were fantastic.  He closed with"Roanoke Rocks".  I never forgot those words.  They have carried me through meetings with 5 attendees to launches where we were renting chairs the night before the event due to an unexpected high attendance of 78.

Roanoke Rocks again with the formation of the Roanoke Valley SharePoint User Group (RVSPUG).  I am an advisor on the board and the enthusiasm of the board is motivating.  Their first meeting is next Tuesday (October 30th).  For more information visit the RV.NUG site. 

 

«October»
SunMonTueWedThuFriSat
30123456
78910111213
14151617181920
21222324252627
28293031123
45678910