• Bamboo.AJAXExtensions.wsp
• Bamboo.core.wsp

• Bamboo.core
• Bamboo.core.v1.wsp

• Bamboo.core.v2.wsp

From SharePoint Central Administration, from the Manage Farm Solutions page, Retract the solution and then Remove it.

No additional steps are required.

Stop the World Wide Web Publishing Service (W3SVC) of you are not using Claims Based Authentication (CBA) or SP2013. This will ensure that files that need to be removed during the install are not locked.

From the Start menu on the SharePoint server desktop, click Administrative Tools > Services. Scroll down and right-click on World Wide Web Publishing Service and select Stop.

If you are using CBA or SP2013, stop the App Pool(s) to ensure that files are not locked.

Notice in the screen shot above that it will be possible to proceed if the World Wide Publishing Service is started, although a yellow warning icon is displayed. If you are running with Claims Based Authentication (CBA) or if you are installing on SharePoint 2013, you need to keep this service on in order to automatically activate features during the install. Other than these scenarios, we strongly recommend that you stop this service before installing or upgrading. See Recommendations for a successful intstall for more information.

In the Repair, Remove or Install screen, select the Upgrade/Repair Existing and Install New option and click Next.

Wait while the components are upgraded. You will see progress displayed on the screen.

In SharePoint Central Administration, go to the Manage Farm Solutions page (its called Solution Management in SharePoint 2007).

In SP2010, click System Settings > Manage Farm Solutions.

In SP2007, click Operations > Solution Management.

Bamboo List Rollup Web Parts
Bamboo List Rollup XSLT Data View

NOTE: In releases prior to R7.x, the farm solutions listed below were included in the List Rollup:

Bamboo List Rollup Classic Edition
Bamboo List Rollup Grid View
Bamboo List Rollup Schema Designer

The individual web parts are still available in R7.x, just now bundled into the single site collection feature called Bamboo List Rollup Web Parts

Bamboo Gantt Chart Web Part
Bamboo PM Central Department Level Site – Lite
Bamboo PM Central Projects Site Creation Area
Bamboo PM Central Top Level Site – Lite Template
Bamboo PM Project Site – Lite Template
Bamboo PM Project Site – Stand-alone template
Bamboo Project Central Content Types
Bamboo Project Central Supporting Web Parts

PM Central installation files include a utility (called the Bamboo Feature Activation Tool) that will automate the activation of Site Collection features needed for PM Central. Using this utility will be MUCH easier than activating everything manually.

Schedule the solution Retraction. You can schedule the solution to be retracted from one web application at a time:

 stsadm.exe 
 -o retractsolution 
 -name [Component].wsp 
 -immediate  
 -url [http://WebApplicationUri:Port]

or from all web applications at once:

 stsadm.exe 
 -o retractsolution 
 -name [Component].wsp 
 -immediate 
 -allcontenturls

Where:

• [Component] is the name of the installed component (i.e., Bamboo.TreeView.wsp), as shown in the cab installation sub-folder or in the list of solutions in the Manage Farm Solutions page of SharePoint Central Administration.
• [http://WebApplicationUri:portNumber] is the URL and Port for the web application where the solution is installed.

Execute the solution retraction.

NOTE: This command needs to be run on each Web front-end (WFE) server in the farm.

 stsadm.exe -o execadmsvcjobs

Remove the solution. Delete the solution from the SharePoint solution store only AFTER the retraction job is complete.

 stsadm.exe -o deletesolution -name [Component].wsp

Where:

• [Component] is the name of the installed component (i.e., Bamboo.TreeView.wsp), as shown in the cab installation sub-folder or in the list of solutions in the Manage Farm Solutions page of SharePoint Central Administration.

Repeat steps 2-4 for each solution included in the product.

NOTE: There are two solutions that are common across multiple Bamboo products. They are: Bamboo AJAX Config (SP2007 only) and Bamboo Core. Do NOT uninstall them unless you are sure there are no other Bamboo products remaining on your farm. If there are no other Bamboo products on your farm, uninstall these two solutions last.

Add the solution to the SharePoint solution store. Run this command on the appropriate server in your farm and be sure you are running the command with an account that is a member of the local server Administrators group.

The appropriate servers are typically those running the Foundation Web Application service or the Microsoft SharePoint Foundation Web Application service (or Windows SharePoint Services Web Application if you are using SharePoint 2007). Refer to Location of Install Files for more information.

 stsadm.exe -o addsolution -filename [path][Component].wspcab[Component].wsp

where:

• [path] – the path to the extracted installation folders
• [Component] – the name of the component you are installing, as shown in the installation folder. The name of the component in the cab sub-folder may be slightly different than the installation folder name.

Deploy the SharePoint solution. After adding the solution to the SharePoint solution store on your farm, it must be deployed to one or more Web Applications. This can be accomplished via Central Administration (see Deploying a Bamboo solution to a new Web Application for more information) or by running one of the following commands on the same server where you added the solution in Step 1 above.

To deploy to a specific Web Application, run this command:

stsadm.exe 
-o deploysolution 
-name [Component].wsp 
-immediate 
-url [http://WebApplicationUri:portNumber] 
-allowGacDeployment 
-allowCasPolicies

where:

• [Component] – the name of the component you installed, as shown in the cab installation sub-folder
• [http://WebApplicationUri:portNumber] – the URL and Port for the target Web Application. Repeat this command for each web app you need to deploy to.

OR

To deploy to all Web applications EXCEPT the Central Administration Web application, run this command:

stsadm.exe 
-o deploysolution 
-name [Component].wsp 
-immediate 
-allcontenturls 
-allowGacDeployment 
-allowCasPolicies

where:

• [Component] – the name of the component you installed, as shown in the cab installation sub-folder

Execute the deployment job(s). This is an optional step. The SharePoint Timer job will take care of the deployment eventually, but if you don’t want to wait for it, you can run this command.

NOTE: This command needs to be run on every server on the farm that runs the Foundation Web Application service (or the Windows SharePoint Services Web Application service if you are using SharePoint 2007):

stsadm.exe -o execadmsvcjobs

Manually Activate the Product Feature(s) in the appropriate Site Collection

After the Bamboo product solution is deployed to a Web Application, it must be activated in the site collection before it can be used. When you are ready to activate the site collection feature, please see Activating a Bamboo Site Collection Feature.

NOTE: You must be a Site Collection Administrator to activate site collection features.

Shut down the application pools for each Web application where you are installing the product. This will prevent other users from accessing sites and locking files that the installation script needs to update.

NOTE: If you are using SharePoint 2010 and not Claims Based Authentication (CBA), instead of shutting down the app pools, you can stop the World Wide Web Publishing Service to prevent users from accessing sites and locking files. You should NOT stop the WWW Publishing service in SP2013 or in a CBA environment.

On one Web front-end server (WFE), run the product .EXE file to extract its installation files. Browse to the misc folder.

NOTE: If you do not see the misc folder or a file called ManualInstallation in this folder, your Bamboo product does not support this type of install.

Right-click on the file DisableAllBambooTimerJobDefinitions.bat and choose Run as administrator. This script stops the timer job services for all Bamboo products installed on the farm, helping to put the farm in a quiescent state for the install.

NOTE: If this script is not present in the misc folder for your Bamboo product, skip this step.

On all WFE servers in the farm, perform the following actions:

1. Run the command iisreset.
2. Restart the SharePoint 2013 Timer (or SharePoint 2010) service.

Change to the misc folder in the extracted product installation files and enter the following command to start the manual installation script:

.ManualInstallation.ps1

When prompted, enter the Web application URL and choose whether you want to automatically activate the product features in the site collection(s).

NOTE: To allow the installation script to run without prompting for input, edit the miscManualInstallation.ps1 script file and replace Read-Host with the highlighted text shown below:

The script file installs Bamboo.Core.V2.wsp and Bamboo.Logging.V2.wsp, if they are not already in the solution store, and any required product components.

Return to the misc folder. Right-click on EnableAllBambooTimerJobDefinitions.bat and choose Run as administrator. This enables all Bamboo timer job services.

NOTE: If this script is not present in the misc folder for your Bamboo product, skip this step.

Manually Activate the Product Feature(s) in the appropriate Site Collection(s)

If you didn’t choose to activate site collection features automatically in step 7 above, don’t forget to activate those features in the site collections where you want to use them.

After a Bamboo product solution is deployed to a Web Application, it’s feature(s) must be activated in the site collection before it can be used. When you are ready to activate the site collection feature, please see Activating a Bamboo Site Collection Feature.

NOTE: You must be a Site Collection Administrator to activate site collection features.