| On the Configuration part of side… In order to upgrade to SharePoint Foundation 2010 or SharePoint Server 2010, you must first be running Windows SharePoint Services 3.0 at SP2 or Microsoft Office SharePoint Server 2007 at SP2, respectively. For customers running prior versions of SharePoint, including Windows SharePoint Services 2.0 and SharePoint Portal Server 2003, this means that you must first upgrade to Windows SharePoint Services 3.0 SP2 or Microsoft Office SharePoint Server 2007 SP2 prior to upgrading to 2010 versions. Windows SharePoint Server 3.0 with SP2 is available as a free download, and trial versions of Microsoft Office SharePoint Server 2007 are available and supported for use in this upgrade/migration process:
SP2 Slipstream Downloads and Trial Versions Windows SharePoint Services 3.0 (32-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A Windows SharePoint Services 3.0 (64-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA Microsoft Office SharePoint Server 2007 Trial Version (32-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831 Microsoft Office SharePoint Server 2007 Trial Version (64-bit) with SP2 http://www.microsoft.com/downloads/details.aspx?familyid=3015FDE4-85F6-4CBC-812D-55701FBFB563 Please note that the trial product versions are licensed for 180 days of use from the date of installation. Upgrade Method This upgrade process should be done using the Database Migration approach documented in the following links: Windows SharePoint Services and Microsoft Office SharePoint Server 2007 Determine upgrade approach (Office SharePoint Server) http://technet.microsoft.com/en-us/library/cc263447.aspx Determine upgrade approach [Windows SharePoint Services] http://technet.microsoft.com/en-us/library/cc287821.aspx SharePoint Foundation 2010 and SharePoint Server 2010 (pre-release documentation) Determine upgrade approach (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/cc263447(office.14).aspx Determine upgrade approach (SharePoint Foundation 2010) http://technet.microsoft.com/en-us/library/cc287821(office.14).aspx Note that this method is referred to as “Database attach upgrade” in pre-release documentation Please note that there are manual steps involved in this upgrade path in order to maintain some configuration information, as documented in the links above. Example Upgrade Sequence The upgrade documentation above should be referenced for full detail and information, but the following illustrates an example of an upgrade sequence for moving from Office SharePoint Server 2007 to SharePoint Server 2010. 1. Prepare Farms a. Set up a small, temporary farm running Office SharePoint Server 2007 b. Set up full SharePoint 2010 farm and verify that it is configured and running correctly 2. Upgrade content from 2003 to 2007 a. Detach the content databases from the 2003 farm and take the 2003 farm offline b. Attach the content databases to the 2007 farm and upgrade them c. Verify the content has upgraded and that the 2007 farm is working correctly 3. Upgrade content from 2003 to 2007 a. Detach the content databases from the 2007 farm b. Attach the content databases to the SharePoint Server 2010 farm and upgrade them in parallel c. Verify the content has upgraded to SharePoint 2010 and is working correctly 4. Start serving requests on the SharePoint Server 2010 farm Again, this is just an example for illustration: for full detail, including all steps and important considerations, please review the existing and pre-release documentation linked above. Additional Information and Notes Please note that SharePoint Server 2010 Beta cannot be upgraded to the final release version (RTM). Any use of these steps or guidelines with any pre-release version of SharePoint 2010 should be for testing/evaluation only. This upgrade path will necessarily mean a move from 32-bit OS architecture to 64-bit OS architecture. Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 were supported only on 32-bit operating systems, as opposed to SharePoint Foundation 2010 and SharePoint Server 2010, which are supported only on 64-bit operating systems. The database platform selected for Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 should be consistent with the planned platform for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010. For example, if SQL Server 2008 will serve as the database software for the Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 trial versions you should maintain that version for Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010 to avoid downgrade support limitations such as SQL Server 2008 to SQL Server 2005. For additional information on SQL Server 2008 downgrade rights see: SQL Server 2008 Licensing Frequently Asked Questions http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx |
Archive for December, 2009
It’s is really good to see the way the PowerShell interacts with the SharePoint 2010. I can say that this PowerShell scripting is really an extended form of the STSADM utility with additional programmatically features which can be achieved through batch files.
In this post I am going to show you how PowerShell works… and some tips and tricks for the PowerShell module on the SharePoint 2010
Let’s us create a new Web under the PowerShell console for the SharePoint 2010. To create a new Web under the existing Site Collection, PowerShell scripting will use the following command
“New-SPWeb”
The following are the input parameters for the respective command.
SYNTAX
New-SPWeb
[-Url] <String>
[-Language <UInt32>]
[-Template <SPWebTemplatePipeBind>]
[-Name <String>]
[-Description <String>]
[-AddToQuickLaunch]
[-UniquePermissions]
[-AddToTopNav]
[-UseParentTopNav]
[-AssignmentCollection <SPAssignmentCollection>]
[-Verbose]
[-Debug]
[-ErrorAction <ActionPreference>]
[-WarningAction <ActionPreference>]
[-ErrorVariable <String>]
[-WarningVariable <String>]
[-OutVariable <String>]
[-OutBuffer <Int32>]
[-WhatIf]
[-Confirm]
PowerShell provides us a set of commands which draws out the SharePoint Out-Off-Box functionalities and also it extends the SharePoint Object model.
Write-Host “Defining variables for creating a new Web under the different Site Collection”
# define variables for script
$SiteTitle = “Lab 1 – Getting Started”
$SiteUrl = “http://sharepoint2010v/Lab01/”
$SiteTemplate = “STS#0″
Write-Host “Creating a new SharePoint Web under the URL – “ $SiteUrl
PS C:\> New-SPWeb -Url $SiteUrl -Template $SiteTemplate -Name $SiteTitle
Write-Host “New SharePoint Web has been successfully created.”
Pack the above code snippet in a notepad and save it as CreateNewSite.ps1
Powershell -Command “& {.\CreatenewSite.ps1}” -NoExit
pause
Again pack the above two lines of code as a batch file and save it as “ExecuteNewSiteCreation.bat”
Now, run the above created “ExecuteNewSiteCreation.bat” file. PowerShell creates a new Web under the specified Site Collection…
Note: you should modify the “$SiteUrl” variable in order to execute the above scenarios.
Happy programming… will see more updates on the Powershell developement on SharePoint 2010…
This enables the end users to access the site hierarchy very quickly. Microsoft had implemented this instead of the breadcrumb.
Nicely carried out this design… Happy delving…
Several beta language packs for SharePoint Foundation 2010 Beta and SharePoint Server 2010 Beta are now available through the Download Center. Installing one or more language pack will allow you to evaluate the new Multi User Interface (MUI) features of SharePoint 2010.
The following language packs are available:
- German
- English
- Spanish
- French
- Japanese
- Russian
- Chinese (simplified)
SharePoint Foundation 2010
Language Packs
SharePoint Server 2010 Language Packs
Please follow the instructions on the download page to install language packs. For further reading, please refer to TechNet articles: Deploy language packs (SharePoint Foundation 2010) and Deploy language packs (SharePoint Server 2010).
