Upgrade MOSS 2007 to SharePoint 2010... My Notes!
Things to consider before the upgrade
OS architecture?
SharePoint services 3.0?
Using 32 bit of SQL on Windows Server 2003?
Upgrade path?
Methods:
- In-place upgrade
- Database attached
- Hybrid (combination of both)
In-Place Upgrade
- If server OS and SQL version is up to date, e.g. 64 bit etc.
- Take MOSS offline during the process.
- Easiest solution but need to allow for down time.
Database Attached (more like a migration)
- More like a migration.
- Moving the content of the existing server and moving it to a new server and a new server farm.
- Moving it to a new hardware and everything should be compliant, start from scratch
- The negative side is that there is a bit of more.
- No server down time. Bring all the data over but not the configuration.
- After the migration, there is a bit of a clean up to do.
Hybrid
- Make existing "Read Only" while working on the contents on the new server
- In-place to upgrade the farm and settings and then detached and upgrade multiple database in parallel on the same farm or a separate farm.
- Preserve farm wide settings
- Upgrade multiple database at the same time.
- More planning.
Perform pre-upgrade check
- At least MOSS 2007 Sp2
-stsadm -o preupgradecheck (program files\common files\microsoft shared\web server extension\12\bin)
- note that stsadm has been deprecated by powershell command
- The report will show support upgrade types.
In-Place Upgrade:
- Make sure we have a backup and perform a recovery to ensure the back works in the event that the upgrade failed.
- Install the prerequites.
- Kick off the installation
- Installation will detect an installation of SharePoint and will offer the "Upgrade earlier versions"
- Launch product configuration wizard.
- Visual upgrade dialog, you change or preserve the look. E.g. Ribbon. (One way ticket, can only be reversed using powershell)
- Preserved the visual for the time being and let admin decided when the upgrade the visual
- Finish installation and Central Administration will start for monitoring the upgrade.
You can initial the visual upgrade by:
Powershell (for site administrator) to imitate a site collection upgrade.
or
Handle page by page or site collection visual upgrade.
- Go to Site Actions | Visual Upgrade, it will bring you to the Site Settings | Title, Description, and Icon
- You can select "Preview" to have a look at the visual.
- Go to Site Actions | Site Settings | Site Collection Administration | Visual Upgrade. You can hide Visual Upgrade or Update All Sites.
After In-place upgrade:
- Fixing the photo store
- Some user profile property changes
- perform a full search crawl to rebuild the search index.
Database Attached Upgrade
Backing up the database on the SQL side and moving it to the new SharePoint 2010 server to reconnect to the new site collection. This method not often perfect as there maybe warning messages about pieces that are missing or services aren't exact, you can go back and ensure services are install. Create a brand new install of SharePoint 2010 with temporarily SharePoint farm with team site collection.
- Decide if you want to allow the content database to continue service or set it as "read only"
- Detach the content database
- Copy to the 2010 server
- Attach to the new farm
Steps (roughly):
On the existing MOSS 2007 server:
- Open MOSS SharePoint Site Central Administration | Application Management on the left, under SharePoint Web Application Management, go to Content Database. It will show the database name. Select different web application from the drop down list to see other database. (WSS_Content_XXXX)
- Open SQL Management Studio, select the WSS_Content database, go to properties | options and scroll down to select "true" for database read-only.
- Select the WSS_Content database, right lick and go to task and backup... specify the destination and give it a useful name.. MOSS2007_content or something. Specify a useful destination path.
- Locate the backup file and move it to the SharePoint 2010 server
On the SharePoint 2010 server:
- Start SQL Management Studio
- Right click Databases on the expanded tree and restore database.
- Provide a new database name such as "moss2007" and "from device" (select the backup file) and select the database, click OK and restore.
- Now you want to go to your temporary site which you have created on the SP2010, disconnect the existing database and reconnect to the new database.
- Go to Central Administration, Application Management on the left, Databases (Manage content database). Select WSS_Content (for the standard top level site), scroll down, tick the "remove content database" (we are not removing the database, just removing the connection to the site..). You will get a warning and OK.
- Open SharePoint 2010 Management Shell (powershell)
- test-spcontentdatabase - name moss2007 -webapplication http://sp2010 [enter]
- As long as we don't see any upgrade block set to true then we should be fine.
- mount-spcontentdatabase -name moss2007 - databaseserver sp2010 -webapplication http://sp2010 [enter]
- In Central Administration, you will see that the Web Application the moss2007 pointing to http://sp2010 and if you go to the main site, the migrated content database will be online.
- Something might not came through such as the picture etc. Move the pictures over to _layout folder. Discover where the path is from IIS, E.g. Go to SharePoint - 80 and go to _layouts. Right click and go Explore.
- Go to Site Action and Visual Upgrade and upgrade to the new visual.
Sunday, July 29, 2012
Friday, July 27, 2012
Installing Sharepoint 2010.. My Notes
My notes on installing SharePoint Server 2010.
User Accounts Requirement:
"Least privileged" is idea of assigning only what is needed for the account to function.
1. sp_admin - Sharepoint Setup User Account.(member of the local admin)
2. sp_sql - SQL Server Service Account. (no administrator privilege on the OS)
3. sp_farm - Server / Farm Database Access Account.
SQL Installation
SQL Server 2008 R2
- SQL Server Feature Install
- Database Engine Services and Management Tools
- Keep default instance
- SQL Agent (sp_sql account)
- SQL Database Engine (sp_sql account) - Complete.
- Windows Authentication Mode
- Specify SQL Server Administrator - Add current user
- Complete the install.
In Microsoft SQL Server Management Studio
- Connect
- Goto Security | Login
- Right click and new login
- Create domain\sp_admin and in Server Role, enable dbcreator, securityadmin.
In Local Users and Group
- Add domain\sp_admin into local administrators group.
Login to sp_admin into the SHAREPOINT server
- Run the setup.hta and complete the "Install software prerequisites".
- Install Sharepoint server
- Insert product key
- Accept the terms
- Select server farm
- Select complete install. (standard alone installation is the same as the previous standalone version).
- When finish, close and Sharepoint Products Configuration Wizard will begin
- Next and yes to restart the services/reset
- Create a new server farm
- Name of database server
- Database name would be default Sharepoint_Config
- Database Access Account, Username sp_farm and insert the password
- Might receive error about not able to connect database master sql server and no permission.
- Make sure SQL server firewall is allowing traffic in, otherwise create inbound rules. 1433
- Specify the passphrase (very import to take note that in order to join to this server farm, you need to know the passphrase) Complex rule applies
- Specify the port number: e.g. 12345
- Select NTLM for easy working sharepoint site, however, kerberos is recommended.
- Summary is provided and click yes to kick off the configuration.
- Exit the installation if successful.
Configure your sharepoint site.
- Select the wizard or do it yourself. Select the wizard at this stage.
- Best practice is to create a new managed service account.
- Create a service account call something like sp_service in the domain
- Provide the domain\sp_service account info into the field.
- Check through the services which are enable by default.
- Services will affect the performance of the server. De-select those that are not needed.
- Once completed, you will be given the the option to create you new first site.
- Insert a title and description.
- In the Web Site Address. You don't have to put in the URL. leave it as default
- Select the template. Select team site. (for starting..)
- OK and complete the farm configuration wizard.
- Click on the link and open in new tab to show your team site
- Click finish to bring up the central administration site.
- Add to local Trusted Sites.
Sharepoint farm and advanced deployment.
Components:
Web server
Application server
Database server
Single Tier
All 3 components in one server
Multi-server 2 Tier Deployment
Web and Application on one server
Database on one server
Multi-server 3 Tier Deployment
Web, Application and Database on individual server
High availability
Failover Clustering on SQL server.
Network Load Balancing on the Sharepoint site. (Web Frontend)
Note:
- When there is a problem with the installation, check the installation log files in %temp%
- Installation can be scripted. setup /config config.xml
- Language packs can be downloaded from Microsoft to support multilanguage site.
User Accounts Requirement:
"Least privileged" is idea of assigning only what is needed for the account to function.
1. sp_admin - Sharepoint Setup User Account.(member of the local admin)
2. sp_sql - SQL Server Service Account. (no administrator privilege on the OS)
3. sp_farm - Server / Farm Database Access Account.
SQL Installation
SQL Server 2008 R2
- SQL Server Feature Install
- Database Engine Services and Management Tools
- Keep default instance
- SQL Agent (sp_sql account)
- SQL Database Engine (sp_sql account) - Complete.
- Windows Authentication Mode
- Specify SQL Server Administrator - Add current user
- Complete the install.
In Microsoft SQL Server Management Studio
- Connect
- Goto Security | Login
- Right click and new login
- Create domain\sp_admin and in Server Role, enable dbcreator, securityadmin.
In Local Users and Group
- Add domain\sp_admin into local administrators group.
Login to sp_admin into the SHAREPOINT server
- Run the setup.hta and complete the "Install software prerequisites".
- Install Sharepoint server
- Insert product key
- Accept the terms
- Select server farm
- Select complete install. (standard alone installation is the same as the previous standalone version).
- When finish, close and Sharepoint Products Configuration Wizard will begin
- Next and yes to restart the services/reset
- Create a new server farm
- Name of database server
- Database name would be default Sharepoint_Config
- Database Access Account, Username sp_farm and insert the password
- Might receive error about not able to connect database master sql server and no permission.
- Make sure SQL server firewall is allowing traffic in, otherwise create inbound rules. 1433
- Specify the passphrase (very import to take note that in order to join to this server farm, you need to know the passphrase) Complex rule applies
- Specify the port number: e.g. 12345
- Select NTLM for easy working sharepoint site, however, kerberos is recommended.
- Summary is provided and click yes to kick off the configuration.
- Exit the installation if successful.
Configure your sharepoint site.
- Select the wizard or do it yourself. Select the wizard at this stage.
- Best practice is to create a new managed service account.
- Create a service account call something like sp_service in the domain
- Provide the domain\sp_service account info into the field.
- Check through the services which are enable by default.
- Services will affect the performance of the server. De-select those that are not needed.
- Once completed, you will be given the the option to create you new first site.
- Insert a title and description.
- In the Web Site Address. You don't have to put in the URL. leave it as default
- Select the template. Select team site. (for starting..)
- OK and complete the farm configuration wizard.
- Click on the link and open in new tab to show your team site
- Click finish to bring up the central administration site.
- Add to local Trusted Sites.
Sharepoint farm and advanced deployment.
Components:
Web server
Application server
Database server
Single Tier
All 3 components in one server
Multi-server 2 Tier Deployment
Web and Application on one server
Database on one server
Multi-server 3 Tier Deployment
Web, Application and Database on individual server
High availability
Failover Clustering on SQL server.
Network Load Balancing on the Sharepoint site. (Web Frontend)
Note:
- When there is a problem with the installation, check the installation log files in %temp%
- Installation can be scripted. setup /config config.xml
- Language packs can be downloaded from Microsoft to support multilanguage site.
Friday, July 20, 2012
Deployment of PKI Certificates Required for Configuration Manager Native Mode
This post is about my experience with configuring Microsoft PKI to provision certificates requirement for Configuration Manager to run in native mode. Please note that I am working with Windows 2008 Certificate Authority and SCCM 2007.
A lot of the stuff here are duplicated and copied from these TechNet Articles.
Step-by-Step Example Deployment of the PKI Certificates Required for Configuration Manager Native Mode: Windows Server 2008 Certificate Authority.
http://technet.microsoft.com/en-us/library/cc872789
Deploying the PKI Certificates Required for Native Mode.
http://technet.microsoft.com/en-us/library/bb680312
Windows Server 2008 Active Directory Certificate Services.
http://technet.microsoft.com/en-us/windowsserver/dd448615.aspx
Active Directory Certificate Services Step by Step Guide. http://technet.microsoft.com/library/cc772393(v=ws.10).aspx
PKI certificates must be installed prior to configuring Configuration Manager 2007 to operate in native mode. The follow describes 3 types of PKI certificates that are required and describes how they are used in Configuration Manager 2007 native mode.
Three types of PKI certificates
Site server signing certificate - This certificate is install on the Configuration Manager site server. It is used to sign client policies.
Web server certificate - This certificate is installed on servers that will be Configuration Manager 2007 site systems, with roles such as the management point and distribution point. It is used to encrypt data and authenticate the server to clients.
Client certificates - This certificate is installed on computers that will be Configuration Manager 2007 clients, and it is installed on the management point. It is used to authenticate the client to site systems; on the management point it is used to monitor the server's operational status.
The site server will require the signing certificate. The management point, software update point, distribution point and the state migration point (web server) will require the web server certificate. Lastly, the Configuration Manager Client will require the client certificate and the management point will also require the client certificate to report its status to the site server.
I followed these steps to provision all the certificates.
http://technet.microsoft.com/en-us/library/cc872789#BKMK_siteserver12008
Once the PKI certificates are provisioned, follow the Administrator Checklist: Migrating a Site to Native Mode. http://technet.microsoft.com/en-us/library/bb632727
Issues I have encountered:
Software Update Point reported errors trying to communicate with WSUS. This is due to the WSUS installed on a separate website on port 8530 and 8531 HTTPS rather than the default website. Enabling the certificate on the WSUS intranet fixes the problem.
A lot of the stuff here are duplicated and copied from these TechNet Articles.
Step-by-Step Example Deployment of the PKI Certificates Required for Configuration Manager Native Mode: Windows Server 2008 Certificate Authority.
http://technet.microsoft.com/en-us/library/cc872789
Deploying the PKI Certificates Required for Native Mode.
http://technet.microsoft.com/en-us/library/bb680312
Windows Server 2008 Active Directory Certificate Services.
http://technet.microsoft.com/en-us/windowsserver/dd448615.aspx
Active Directory Certificate Services Step by Step Guide. http://technet.microsoft.com/library/cc772393(v=ws.10).aspx
PKI certificates must be installed prior to configuring Configuration Manager 2007 to operate in native mode. The follow describes 3 types of PKI certificates that are required and describes how they are used in Configuration Manager 2007 native mode.
Three types of PKI certificates
Site server signing certificate - This certificate is install on the Configuration Manager site server. It is used to sign client policies.
Web server certificate - This certificate is installed on servers that will be Configuration Manager 2007 site systems, with roles such as the management point and distribution point. It is used to encrypt data and authenticate the server to clients.
Client certificates - This certificate is installed on computers that will be Configuration Manager 2007 clients, and it is installed on the management point. It is used to authenticate the client to site systems; on the management point it is used to monitor the server's operational status.
The site server will require the signing certificate. The management point, software update point, distribution point and the state migration point (web server) will require the web server certificate. Lastly, the Configuration Manager Client will require the client certificate and the management point will also require the client certificate to report its status to the site server.
I followed these steps to provision all the certificates.
http://technet.microsoft.com/en-us/library/cc872789#BKMK_siteserver12008
Once the PKI certificates are provisioned, follow the Administrator Checklist: Migrating a Site to Native Mode. http://technet.microsoft.com/en-us/library/bb632727
Issues I have encountered:
Software Update Point reported errors trying to communicate with WSUS. This is due to the WSUS installed on a separate website on port 8530 and 8531 HTTPS rather than the default website. Enabling the certificate on the WSUS intranet fixes the problem.
Subscribe to:
Posts (Atom)