To do this cool thing… http://www.microsoft.com/technet/windowsserver/sharepoint/techinfo/gboverview.mspx
You’ll need to download this:
And if you have WSUS 3.0 installed, you’ll need to ensure you know about this:
Don’t forget to call PSS at 1-800-936-4900, press 2 for IT pros for the free hotfix that you’ll need to do before step three:
So first download .NET 3.0 – http://go.microsoft.com/fwlink/?LinkId=77799
(Okay so first backup your file server, but that’s a given)
Download Sharepoint 3.0 – http://go.microsoft.com/fwlink/?LinkId=77800
· Step 1: Install Microsoft .NET Framework 3.0.
Ensure .net 3.0 hasn’t stomped on the asp.net of the default web site (all default SBS web sites need to stay on 1.1), launch companyweb to ensure everything is still working
Backup the server
· Step 2: Install Windows SharePoint Services 3.0.
Weirdly I have to check to unblock the file to install it …I think this is due to Windows 2003 sp2?
Remember to check the “Data Location tab (right after step 4 b) if you don’t want that on the C: drive
<<<< install Sharepoint hotfix>>
You’ll want to “untick” that box if you have WSUS 3.0 installed and at this point install the Sharepoint hotfix
· Step 3: Configure Windows SharePoint Services Products and Technologies.
At this point you’ll launch the wizard, step two may take a little while, don’t worry
· Step 4: Create a new intranet site using Windows SharePoint Services 3.0.
It’s very important to do this step by step here and check off each item
Ensure you read and do each step
· Step 5: Delete the Windows SharePoint Services 3.0 default Web site.
This step gets you back to where Companyweb works again
· Step 6: Start the default Web site and the Windows SharePoint Services 2.0 http://companyweb Web site
One thing I think that it’s forgotten in the steps is the “add user” step to add authenticated users or selected users to the new Sharepoint.
Oh yeah, and P.S. In my opinion… if you have WSUS 3.0 on here AND this? Make sure you have 4 gigs of ram…. I still have lots of room but Sharepoint embedded is not one to be stingy on RAM.
My last, unfinished task?
How to make that domain easier to get to. That’s sort of a sucky web address in my opinion. I don’t need/don’t want external access over 443 …but that’s a sucky address nonetheless.
(duplicate post due to server hardware issue…stay tuned for blog post at Yoda’s blog for details)