Uninstalling Office 2010, 2007, or 2003? - Problems? - Resolved :)

Office 2003 suites- To uninstall the 2003 Microsoft Office suite automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50416

 Office 2007 suites- To uninstall the 2007 Microsoft Office suite automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50154

Office 2010 suites- To uninstall the 2010 Microsoft Office suite automatically, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem
Microsoft Fix it 50450


For more information, see http://support.microsoft.com/kb/290301.

Upgrade to Microsoft SharePoint 2010 Products from MOSS 2007 and WSS 3.0

When we plan for an upgrade from MOSS 2007 or WSS 3.0 to SharePoint 2010 Products, we have different upgrade approaches as building blocks that can be used for optimal upgrade approach.

In-place upgrade: Use this approach to install the new version of SharePoint 2010 products on the same hardware that is used for the previous version. Upgrade the content and settings in the server farm as part of a single process.

Database attach upgrade: Use this approach to upgrade the content for the environment on a separate farm. It doesn't upgrade any of the services or farm settings. Content databases can be upgraded in any order and can upgrade several databases at the same time. Using this approach, it’s possible to attach a Shared Service Provider database during DB attach upgrade, this will upgrade the profile information in the database. Using this approach, it’s not possible to upgrade the search database.

Hybrid approaches: A hybrid approach lets us to take advantage of in-place upgrade's ability to upgrade content and settings, while we take advantage of the speed of a database attach upgrade. The advantages of this method is

1)   Farm wide settings can be preserved and upgraded

2)   Customization are available in the environment after upgrade, although manual steps may be required to upgrade or rework

We can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. For more information on Upgrade Process please refer to http://technet.microsoft.com/en-us/library/cc262483(office.14).aspx

Upgrade Best Practices SharePoint Server 2010

I was in a process of giving the details about migration to a organisation from 2007 to 2010 and found this useful article on Technet .

http://technet.microsoft.com/library/cc261992(office.14).aspx

To ensure a smooth upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, follow these best practices

• Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later.

Your environment must be updated to Service Pack 2 of Office SharePoint Server 2007 to run the upgrade process, either for an in-place or database attach upgrade. We recommend that you install the October 2009 Cumulative Update because it includes improvements to the pre-upgrade checker tool. Ensure that the environment is fully functioning before you perform an upgrade.

•  An upgrade does not solve any problems that might already exist in your environment. Therefore, ensure that the environment is fully functioning before you perform an upgrade. For example, if you have Web applications that are no longer being used, unextend them before you upgrade. If you want to delete a Web application in Internet Information Services (IIS), unextend the Web application before you delete it; otherwise, SharePoint Server 2010 will try to upgrade the Web application even though it does not exist, and the upgrade will fail. If you find and solve problems beforehand, you are more likely to meet the upgrade schedule that you have estimated.

• Before you try an in-place upgrade, migrate to 64-bit servers. Upgrade your operating system to a 64-bit version of Windows Server 2008 R2 or Windows Server 2008 with Service Pack 2 (SP2). If you are using SQL Server, upgrade or migrate to a 64-bit version of Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3.

• Do not try to combine these operations with your upgrade process. You cannot perform an in-place upgrade unless your system already runs on a supported operating system and platform.

For more information, see What's new in upgrade (SharePoint Server 2010).

• Run the pre-upgrade checker to look for potential issues.

The pre-upgrade checker reports missing customizations and issues with orphaned sites, and more, so that you can address these issues before you perform your upgrade.

 For more information, see Run the pre-upgrade checker (SharePoint Server 2010).

• Perform a trial upgrade on a test farm first.

Back up the live farm, restore to test servers, and then perform the upgrade. Examine the results to set expectations for what the live upgraded sites will look like, to determine how much post-upgrade customization will have to be done, and to estimate how long the upgrade will take. Try a full search indexing crawl. For more information, see Use a trial upgrade to find potential issues (SharePoint Server 2010).

• Plan for capacity.

Ensure that you have disk, processor, and memory capacity sufficient to handle upgrade requirements. For more information about system requirements, see Review system requirements for upgrade (SharePoint Server 2010). For more information about how to plan the disk space that is required for upgrade, see Estimate how long the upgrade process will take and the space that you need (SharePoint Server 2010). For more information about how to plan for capacity, see Performance and capacity management (SharePoint Server 2010).

• Back up your environment.

Perform a full backup of your environment before upgrading. That way, you can recover your environment if you must roll back from an upgrade. For more information, see Back up environment before an in-place upgrade (SharePoint Server 2010).

• Optimize your environment before upgrade.

A few key limits have changed in SharePoint Server 2010, such as query throttling on large lists and lower limits on the number of site collections allowed per content database (from 5,000 warning and 15,000 limit to 2,000 warning and 5,000 limit). Be sure to optimize your Office SharePoint Server 2007 environment to meet these limits or restrictions before upgrade to mitigate errors during the upgrade process or broken lists or sites after upgrade. For more information about the site collection limit, see SharePoint Server 2010 capacity management: Software boundaries and limits. For more information about large lists and addressing the lower limit on site collections, see Clean up an environment before upgrade (SharePoint Server 2010).

• (Optional) If you are using the database attach upgrade method, set the original databases to read-only.

If you expect a long outage window while you perform a database attach upgrade, you can set the databases in the original environment to be read-only so that users can continue to access their data without changing it. For more information, see Attach databases and upgrade to SharePoint Server 2010.

• Do not add any servers to your server farm after you begin the upgrade process.

Running the SharePoint Products Configuration Wizard upgrades the configuration database. The configuration database contains the list of servers in the farm. Servers added to the farm after the configuration wizard has been run are not included in the database. Therefore, servers added after the wizard runs do not appear in the upgraded version topology. If you need to add servers to your farm, do so either before you start the upgrade or after you have completed the upgrade process.

• After upgrade, review the Upgrade Status page and upgrade logs to determine whether there are issues that must be addressed. Then review the upgraded sites.

The Upgrade Status page reports on the upgrade progress, and the upgrade logs list any errors or warnings that occurred during the upgrade process. You should verify all of the sites and test them before you consider the upgrade complete. For more information, see Verify upgrade and review upgraded sites (SharePoint Server 2010).

.Stp files are not working after upgrade

Unfortunately, SharePoint 2007 site templates (.stp) can't be used as in SharePoint 2010. Hmm... Then what to do with the custom SharePoint 2007 Site templates? Can't I use them in SharePoint 2010? well

Solution packages (.wsp files) are the supported method for creating sites that are based on a template in SharePoint Server 2010. You can convert an .stp file to a .wsp file to continue to use the template after upgrade.

http://technet.microsoft.com/en-us/library/cc262967(office.14).aspx#STP

Metalogix Content Migration and Upgrade for Microsoft SharePoint Server 2010

Microsoft’s SharePoint Products and Technologies have brought robust Enterprise Content Management and Collaboration capabilities to an increasing number of organizations in recent years. The popularity of the previous versions, such as Windows SharePoint Services 2.0 and 3.0, SharePoint Portal Server 2003 and Microsoft Office SharePoint Server (MOSS) 2007, led many organizations to deploy SharePoint to various business units, frequently on a large scale.

Many organizations are now looking toward the SharePoint 2010 wave of products, including SharePoint Foundation 2010 and Microsoft SharePoint Server 2010, because of key functionality improvements in the software. These include the integration of the Office ribbon into SharePoint sites, a more scalable services architecture, document management improvements, enterprise taxonomy and many more.

Unfortunately, the migration path provided by Microsoft does not always address organizations’ needs.

The out-of-box upgrade approaches available from Microsoft suffer from fairly significant limitations.

These approaches:

·         Do not support gradual upgrades

·         Do not support granular migration

·         Do not allow administrators to reorganize content during migration

·         Have limited support for 32-bit source systems

·         Do not support upgrades from SharePoint 2003 directly to SharePoint 2010

These limitations present organizations looking to upgrade to SharePoint 2010 with significant planning challenges that will limit both proof of concept and full implementations. Organizations must also ensure that the upgrade approach they select will not jeopardize the content on the existing platform.

Fortunately, Metalogix has released version 4 of SharePoint Site Migration Manager (SSMM 2010), a tool to migrate content from legacy SharePoint 2003/2007 technologies directly to SharePoint 2010.

SSMM 2010 allows organizations to take advantage of SharePoint’s new features without putting their valuable content at risk. SSMM 2010 provides significant advantages over existing migration tools and techniques, allowing for flexible migration between SharePoint versions and farms, granular migration, Power Shell support, reorganization of sites, templates, and databases during the process, as well as many other enhanced capabilities. Unlike some content migration options, SSMM 2010 uses only SharePoint’s fully supported APIs to migrate content, which ensures that it will not affect existing support agreements with Microsoft.

Key Benefits

·         Migrates SharePoint Sites, Lists and Libraries between Servers with full fidelity.

·         Upgrade from SharePoint 2003 and SharePoint 2007 to SharePoint 2010.

·         Re-Organize and re-template your SharePoint Content.

·         Manage your upgrade with zero downtime.

·         Migrate to the cloud or hosted SharePoint environments and reduce infrastructure costs.

Supported Source Systems

·         SharePoint Portal Server (SPS) 2003

·         Windows SharePoint Services (WSS) v2

·         Microsoft Office SharePoint Server (Moss) 2007

·         Windows SharePoint Services (WSS) v3

·         SharePoint Server 2010

·         SharePoint Foundation 2010

·         SQL Server 2000, 2005, and 2008 Unattached SharePoint databases (Read Only)

·         Microsoft Online Services (MOS) [a.k.a BPOS, Exchange Online, or SharePoint Online ] Standard and Dedicated Versions

Key Features

Easy to Use

Run your migration with a tree-based, copy-and-paste-style user interface that is similar to the familiar Windows File Explorer.

Reorganize or re-template sites during migration

Re-define site structure while migrating. Split Sites and Site collections into multiple targets and re-template Sites. Administrators and content owners can define what content is migrated.

Migrate all list types

Migrate Document Libraries, Issues, Tasks, Contacts, Announcements, Discussions and Custom Lists while preserving views, metadata, and user-edit information.

Retain your valuable data

Preserve all views, version chains, metadata, and user-edit information.

Migrate Permissions

Map and migrate site permissions from WSSv2/SPS 2003 and WSSv3/MOSS 2007 to SharePoint 2010 easily.

Migrate Web Parts

Migrate all out-of-the-box and custom web parts from WSSv2/SPS 2003 and WSSv3/MOSS 2007 sites to SharePoint 2010.

Connect to multiple sites

Connect to multiple SharePoint sites, across any number of servers, for easy consolidation or distribution of your SharePoint data.

Work remotely

Do all the heavy lifting for your SharePoint migration from the convenience of your own machine. SharePoint Site Migration Manager connects to any SharePoint site that you can access with your browser -- even those outside your organization’s intranet.

PowerShell Enabled

Access and extend all SharePoint Site Migration Manager Functionality via PowerShell commandlets, to script and automate all migration functionality.

Migrate from live sites and unattached content databases

SharePoint Site Migration Manager provides native capabilities to migrate directly from unattached content databases to live sites, eliminating the need to build temporary farms. Simply point to an unattached database extracts the data directly and migrate it into a live SharePoint 2010 environment.

Distribute the Workload

Use SSMM to delegate and distribute migration efforts across the organization to individual departments or content owners. This reduces IT workload, enhances buy-in on the new target system, and improves decision-making in terms of content re-organization. You can manage a distributed workload because SharePoint Site Migration Manager reads and writes only to the supported SharePoint APIs, so content is security trimmed properly. Content owners simply need read access to their source sites using the SSMM client, along with write access to their new target locations.

Latest Version

SharePoint 2010

SharePoint Foundation 2010

Microsoft SharePoint Server 2010

SharePoint Site Migration Manager 2010

Upgrade to Microsoft SharePoint 2010 Products from MOSS 2007 and WSS 3.0

When we plan for an upgrade from MOSS 2007 or WSS 3.0 to SharePoint 2010 Products, we have different upgrade approaches as building blocks that can be used for optimal upgrade approach.

In-place upgrade: Use this approach to install the new version of SharePoint 2010 products on the same hardware that is used for the previous version. Upgrade the content and settings in the server farm as part of a single process.

Databases attach upgrade: Use this approach to upgrade the content for the environment on a separate farm. It doesn't upgrade any of the services or farm settings. Content databases can be upgraded in any order and can upgrade several databases at the same time. Using this approach, its possible to attach a Shared Service Provider database during DB attach upgrade, this will upgrade the profile information in the database. Using this approach, it’s not possible to upgrade the search database.

Hybrid approaches: A hybrid approach lets us to take advantage of in-place upgrade's ability to upgrade content and settings, while we take advantage of the speed of a database attach upgrade. The advantages of this method is

·         Farm wide settings can be preserved and upgraded

·         Customizations are available in the environment after upgrade, although manual steps may be required to upgrade or rework

We can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. For more information on Upgrade Process please refer to http://technet.microsoft.com/en-us/library/cc262483(office.14).aspx