How to Migrate a Bamboo Web Part from SharePoint 2007 to SharePoint 2010 using the In-Place Upgrade Method

When you run an in-place upgrade from SharePoint 2007 to SharePoint 2010, the configuration data for the farm and all the content in the farm is upgraded on the existing hardware, in a fixed order. When you start the in-place upgrade process, Setup takes the Web server offline and the Web sites are unavailable until the upgrade is finished, and then Setup restarts the Web server.

Using the In-place Upgrade method, the following Bamboo products migrate to SP2010 with no errors or additional steps:

Alert Plus
Alerts Administrator
Chart Plus
Cross List
Column Level Security
Custom Identifier Column
Group Redirect
Group Email
In/Out Schedule Board
KPI Column
List Consolidator

List Rollup
List Search Simple
List Search Advanced
Lookup Selector Column
Mini-Calendar
My Alerts Organizer
Navigators
Password Expiration
Poll
Tree View
Site Creation Plus

Rich Text Column
Visual Indicator Column
Validator Column
Video Library
Task Master
User Manager for Sites
User Redirect
Virtual Map View
Wiki Publisher
World Clock and Weather

NOTE: If you are using a Bamboo product that is not on the above list and you are considering using the In-Place Upgrade method to migrate your farm, refer to the specific migration information for your product to learn more about possible limitations before proceeding with a migration.

Step	Action
1.	Follow Microsoft’s Upgrade In Place to SharePoint 2010 article to perform the in-place upgrade. NOTE: When running the SharePoint Products Configuration Wizard, be sure to select the option Change existing SharePoint sites to use the new user experience. Administrators control the user experience for end users and can decide which sub-option is then selected in this step.
2.	During the upgrade process or before, retrieve the installation package and license keys for the SharePoint 2010 version of the Bamboo products you are migrating. See Migrate My Existing Bamboo Product License Key From SharePoint 2007 to SharePoint 2010 for additional details.
3.	After successfully upgrading to SharePoint 2010 and after all sites have completed their conversion to the new user experience, run the SharePoint 2010 Bamboo product installation package that you retrieved in Step 2. On the Repair, Remove or Install screen, choose to Upgrade/Repair Existing and Install New. For more information, refer to Upgrading your Bamboo Web Part.
4.	Select and upgrade the Bamboo Web License Manager component provided in the same installation package. On the Repair, Remove or Install screen, choose to Upgrade/Repair Existing and Install New. NOTE: The Bamboo Web License Manager only needs to be installed once per farm. Skip this step for subsequent Bamboo product installations on the farm.
5.	Activate the SharePoint 2010 versions of Bamboo products. See Install and Activate a License for Bamboo Products in SharePoint 2010 for more information.
6.	Refer to specific migration steps for the Bamboo product(s) you are migrating. There may be some extra steps required to overcome a known migration issue.

How to Migrate a Bamboo Web Part from SharePoint 2007 to SharePoint 2010 using the Database Attach Upgrade Method

When you upgrade by using database attach upgrade, you detach the databases in the old farm and then attach them to the new farm. When you attach a database to the new farm, the SharePoint upgrade process runs and upgrades the whole database. The database attach upgrade process is similar to the in-place upgrade process. The difference is that the database attach upgrade process is performed manually, and is performed in a separate environment.

Using the Database Attach Upgrade method, the following products migrate to SP2010 with no errors or additional steps:

Chart Plus
Cross List
Column Level Security
Custom Identifier Column
Data-Viewer
Group Email
Group Redirect

List Search Simple
List Search Advanced
Mini-Calendar
Site Creation Plus
Task Master
Tree View
User Manager for Sites

Password Expiration
User Redirect
Validator Column
Visual Indicator Column
Wiki Publisher
World Clock and Weather

NOTE: If you are using a Bamboo product that is not on the above list and you are considering using the Database Attach Upgrade method to migrate your farm, refer to the specific migration information for your product to learn more about possible limitations before proceeding with a migration.

Step	Action
1.	The first step in the process is to set up a new environment to host the upgraded content. See Prepare the new SharePoint Server 2010 environment for a database attach upgrade for additional information from Microsoft.
2.	After you set up the new environment, use the procedures in Microsoft’s Attach Databases and Upgrade to SharePoint 2010 article to detach and then reconnect the databases to perform the actual upgrade. NOTE: When attaching the databases, you must choose to update to the new user experience. Your Bamboo products will not perform correctly if you choose to remain in the old user experience after upgrade.
3.	During the upgrade process or before, retrieve the installation package and license keys for the SharePoint 2010 release of the Bamboo product(s) you are migrating. See Migrate My Existing Bamboo Product License Key From SharePoint 2007 to SharePoint 2010 for additional details.
4.	After successfully upgrading to SharePoint 2010 and after all databases have been attached and converted, run the SharePoint 2010 Bamboo product installation package that you retrieved in Step 3. Since this will be a new install on new hardware, you will be asked to choose the Web Applications to deploy to. Be sure to select the same Web Applications where the Bamboo product was deployed on the old farm. For more information about installation, refer to How to run the Installation-Setup Program.
5.	Install the Bamboo Web License Manager provided in the same installation package. NOTE: The Bamboo Web License Manager only has to be installed once. Skip this step for subsequent Bamboo product installations.
6.	Activate the SharePoint 2010 versions of Bamboo products. See Activating Your Bamboo Product License for more information.
7.	Refer to specific migration steps for the Bamboo product(s) you are migrating. There may be some extra steps required to overcome a known migration issue.

Manually uninstall using PowerShell

IMPORTANT: As of April 2017, Bamboo no longer includes ManualUninstallation.ps1 file in product download packages. An updated uninstall script is included instead. Please see Overview of the Updated Installation Process for Bamboo components and Uninstalling using the updated process for details.

Typically, Bamboo products are uninstalled from a server simply by selecting the Uninstall button for the product components in the Setup program. If you choose, however, you may also uninstall our products via another simple method. In this article, I will show you how to manually uninstall a Bamboo product with PowerShell.

Step	Action
1.	Access the installation files for the product you want to uninstall. They are usually on the WFE Server where you installed. Go to the Misc folder and locate the file ManualUninstallation.ps1 This is a PowerShell script. NOTE: Not all Bamboo products include a PowerShell script for uninstalling.
2.	Next, open the SharePoint 2013 Management Shell program and Run as administrator:
3.	In the SharePoint 2013 Management Shell, go to the Misc folder of the Bamboo product installation files. Then run the script by entering: `.ManualUninstallation.ps1`
4.	A warning is displayed telling you to do the following before proceeding: Deactivate the site collection feature for the product you are uninstalling. This script does not deactivate the features. They must be deactivated on all site collections where they have been activated. Recycle the App Pool or reset IIS on all WFE servers before continuing.
5.	Press Enter when ready, and the script will start. Wait for it to report Solution Removed Successfully, and then press Enter to exist.
6.	Check that the solution is successfully removed. In Site Collection features, the solution should no longer appear. In Solutions Management in Central Administration, the solution should no longer be listed.
7.	Notice that the Bamboo.Core.v2.wsp solutions remains on the list in Solution Management. This solution is part of other Bamboo products and is left intentionally. If you have no other Bamboo products on your farm, please see What is left behind after uninstalling to learn how to remove the Bamboo.core.v2.wsp also.

How to find the release number of a Bamboo web part

NOTE: Since you need to access the web part tool pane, you must be user with Design permissions on the site in order to determine the web part version.
Not all of Bamboo’s products are Web Parts; some products are custom columns for SharePoint and some are desktop programs, so this information does not apply to those particular components.

Step	Action
1.	Navigate to the SharePoint page where the web part is used. It can be any page, on any site. Because web parts are installed on your farm, the version is the same in all web apps, site collections, and sites.
2.	Access the Web Part’s configuration tool pane. In edit mode (select Edit Page from the Site Actions menu), select Edit web part from the web part menu in the upper right corner.
3.	Locate the About Web Part section of the tool pane and expand it. The most important version is the File Version number for the first component listed. This is the current product version installed. See About Bamboo product Version Numbers for more information about how our products are versioned.

How to deactivate your Bamboo Product License if your server doesn’t have access to the Internet

If your SharePoint WFE server does not have Internet access, you will not be able to deactivate a Bamboo product license from Central Administration. Instead, you can access the My Bamboo area of the Bamboo Solutions web site to deactivate any Bamboo product license key.

Follow the steps below:

Step	Action
1.	Determine the license key you want to move or deactivate. Go to Central Administration and under the Bamboo Solutions section, click Manage My License Keys. NOTE: If you are using SharePoint 2007, in Central Administration, go to the Operations tab to see the Bamboo Solutions section and the Manage My License Keys link. Locate the product that you need to deactivate and click the product name link. The license Status Page will be displayed. Each server that is licensed for that product is listed on the page. NOTE: If you don’t see the License Key on this page see Is there a way to find a lost or unknown Bamboo product license key.
2.	Log in to My Bamboo from a computer with an Internet connection. NOTE: If you don’t have a login account, you can create one quickly. All you need is a valid email address.
3.	At the bottom of any My Bamboo page in the My Orders tab, locate the Manage License link and click it. The Manage License page will be displayed.
4.	On the Deactivate Your License side of the Manage License page, enter your license key and then click the magnifying glass (). The Assembly Name licensed with this key will be displayed. Ensure it is the product you expect and then click Deactivate. Once deactivated, the license key can be re-used on your new or changed server. A license key can be used on only one server at a time. Please see Activating Your Bamboo Product License for more information.

How to check the status of your trial license

Overview of Licensing and and Product Activation

To check the status of your trial, follow these steps:

NOTE: If you are trialing a Bamboo Desktop application, please see Checking the status of a Bamboo Desktop application trial.

Step	Action
1.	Open SharePoint Central Administration. Notice the Bamboo Solutions heading on the page with the Manage My License Keys link beneath it.
2.	Click Manage My License Keys. On the page that appears, expand the Individual Products section and locate the product you are trialing.
3.	Click the product name or select Status from the associated menu to view the license status.
4.	If you are running a trial, your license status will be Trial. The status page will show when your trial started and when it will end. Bamboo Product Trials last 30 days from when the product is installed on your SharePoint farm.

How many License Keys do I need for my SharePoint farm?

Overview of Licensing and and Product Activation

For most products, you will need one Bamboo product License Key per Web Front End (WFE) server. A WFE server is any farm server running the Microsoft SharePoint Foundation Web Application (or Windows SharePoint Services Web Application in WSSv3/MOSS).

CA-servers on farm.jpg To determine which servers on the farm run these services, go to Central Administration > System Settings > and then Manage servers in this farm. If you are using WSSv3/MOSS, this page is accessed in Central Administration through Operations > Servers in Farm. In this example, there are two WFE servers on the farm.

Some SharePoint farms have WFE servers that do not serve content to users, even though they are running the Microsoft SharePoint Foundation Web Application. You will not need a license key for WFEs that do not deliver content to end users.

Desktop applications, such as List Bulk Import and List Bulk Export require only one license per instance.

Some products, such as List Rollup and Alert Plus may include optional components that run on application servers in addition to WFE servers. To use these product features, you may need an additional server license for each separate (non-WFE) application server on which you would like to run the associated service for that product. Using application server features on already licensed WFE servers does not require any additional licensing.

How to Add a web.config Modification Using PowerShell

Background

Please see How to modify a web.config file using PowerShell for some additional background information about why you should modify your web.config file(s) programmatically.

Many Bamboo products implement Telerik controls and install a specific version of Telerik.Web.UI assembly to the SharePoint farm. If the farm already has a different version of Telerik.Web.UI assembly, this may cause a conflict and you may see errors on SharePoint pages where you use these controls.

Resolution

To resolve this problem, we need to add an assembly binding to the web.config to specify which version to use. However, adding text by manually editing a web.config file is not recommended because it is not synced across the servers in the farm and is not saved in the SharePoint configuration database.

The best way to modify a web.config file programmatically is via PowerShell.

NOTE: Be extra careful when making changes to the web.config. Backup your file before changing it. Do not add or remove something unless you are absolutely sure what it is.

To demonstrate, we will use an example with Telerik controls. Consider this scenario:
Before a Bamboo product is installed, a server has Telerik.Web.UI version 2012.3.1016.35 previously installed. During the Bamboo product installation process, Telerik.Web.UI version 2011.2.915.35 was installed. Although it is OK to have multiple Telerik versions on a single server, it may cause a conflict in SharePoint.

We need to add an assembly binding to the web.config to tell the assemblies looking for version 2011.2.915.35 to use version 2012.3.1016.35. The assembly binding addition to the web.config file will look like this:

<dependentAssembly>
    <assemblyIdentity name "Telerik.Web.UI" publickKeyToken "121fae78165ba3d4" culture "neutral" />
    <bindingRedirect oldVersion "2011.2.915.35" newVersion "2012.3.1016.35" />
</dependentAssembly>

NOTE: Always redirect all versions found to the newest version of Telerik.Web.UI on the system, for backwards compatibility of functionality.

Step	Action
1.	First, open the SharePoint 2010 Management Shell. From the Start menu, select All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell.
2.	Next, create the SPWebConfigModification object for the assembly binding Where: Path: A string that contains an XPath expression that specifies the node. If the Type property specifies EnsureChildNode, the Path property contains the XPath expression for the parent node under which the node is created. In this example, the runtime element of the web.config file is placed in another xml-namespace, so we have to identify the namespace. Otherwise, that element will not be found. Name: A string that contains the name of the attribute or section node. When the type of web.config modification is EnsureChildNode, the Name property refers to an XPath expression that uniquely identifies the node under the parent node, as identified by the Path property. Sequence: A 32-bit unsigned integer between 0 and 65536. This property throws an InvalidOperationException if the number is outside this range. A sequence is used only if there is more than one modification of the same type to the same node or attribute. In this case, modifications with lower sequence numbers are applied first. Owner: A string that specifies the owner of the modification. You can use the Owner property to track ownership of modifications. Type: An SPWebConfigModification.SPWebConfigModificationType value that specifies the type of modification. There are 3 types: EnsureChildNode: Specifies that the web.config modification must ensure the existence of a child node of the node to which the XPath expression points. Value = 0. EnsureAttribute: Specifies that the web.config modification must ensure that there is a value for a particular attribute. Value = 1. EnsureSection: Ensures a singleton node. This node is only written once, even if multiple entities register multiple instances of EnsureSection to ensure the existence of a section. Value = 2. Value: If the Type property specifies EnsureChildNode, the Value property contains an XML string that represents the node to be populated as a child of the specified parent node. If the type is EnsureSection, Value contains the name of the section. If the type is EnsureAttribute, Value contains the value set in the attribute.
3.	Then, apply the modification to the Web application (replace ‘WebApplicationURL’ with the actual URL of the Web application). NOTE: Bamboo products are only tested with the Telerik version that they install. Therefore, if a newer Telerik version is used, there might be some unexpected problem.

Step

Action

First, open the SharePoint 2010 Management Shell. From the Start menu, select All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell.

Next, create the SPWebConfigModification object for the assembly binding

Where:

Path: A string that contains an XPath expression that specifies the node. If the Type property specifies EnsureChildNode, the Path property contains the XPath expression for the parent node under which the node is created. In this example, the runtime element of the web.config file is placed in another xml-namespace, so we have to identify the namespace. Otherwise, that element will not be found.
Name: A string that contains the name of the attribute or section node. When the type of web.config modification is EnsureChildNode, the Name property refers to an XPath expression that uniquely identifies the node under the parent node, as identified by the Path property.
Sequence: A 32-bit unsigned integer between 0 and 65536. This property throws an InvalidOperationException if the number is outside this range. A sequence is used only if there is more than one modification of the same type to the same node or attribute. In this case, modifications with lower sequence numbers are applied first.
Owner: A string that specifies the owner of the modification. You can use the Owner property to track ownership of modifications.
Type: An SPWebConfigModification.SPWebConfigModificationType value that specifies the type of modification. There are 3 types:
- EnsureChildNode: Specifies that the web.config modification must ensure the existence of a child node of the node to which the XPath expression points. Value = 0.
- EnsureAttribute: Specifies that the web.config modification must ensure that there is a value for a particular attribute. Value = 1.
- EnsureSection: Ensures a singleton node. This node is only written once, even if multiple entities register multiple instances of EnsureSection to ensure the existence of a section. Value = 2.
Value: If the Type property specifies EnsureChildNode, the Value property contains an XML string that represents the node to be populated as a child of the specified parent node. If the type is EnsureSection, Value contains the name of the section. If the type is EnsureAttribute, Value contains the value set in the attribute.

Then, apply the modification to the Web application (replace ‘WebApplicationURL’ with the actual URL of the Web application).
apply mods.jpg

NOTE: Bamboo products are only tested with the Telerik version that they install. Therefore, if a newer Telerik version is used, there might be some unexpected problem.

How to activate a Bamboo Site Feature

NOTE: In order to activate a site feature, you need to have at least the Manage Hierarchy level of permission for the site.

Step	SharePoint 2007	SharePoint 2010/2013
1.	From a page on the site where you want to activate the feature, click Site Actions > Site Settings > Modify All Site Settings. In the Site Administration columnn of the Site Settings page, click Site features.	From a page on the site where you want to activate the feature, click Site Actions > Site Settings. In the Site Actions section of the Site Settings page, click Manage site features.
2.	Find the appropriate feature. If it hasn’t yet been activated, click the Activate button. The features available depend on the Bamboo products installed on your farm and deployed to your web application.

Step

SharePoint 2007

SharePoint 2010/2013

From a page on the site where you want to activate the feature, click Site Actions > Site Settings > Modify All Site Settings. In the Site Administration columnn of the Site Settings page, click Site features.
sp2007 site features.jpg

From a page on the site where you want to activate the feature, click Site Actions > Site Settings. In the Site Actions section of the Site Settings page, click Manage site features.
site settings - site actions2010.png

Find the appropriate feature. If it hasn’t yet been activated, click the Activate button.
sp2010 site features.jpg

The features available depend on the Bamboo products installed on your farm and deployed to your web application.

How long do trial versions of Bamboo software last and when do they start?

Overview of Licensing and and Product Activation

Currently, trials for Bamboo products run for 30 days, and begin when the product is installed. So if you download the software today, but don’t actually install for two weeks, that’s OK.

If you need an extension to a trial, contact your Bamboo Sales Representative (Sales@bamboosolutions.com).

Highlights of User Manager for Sites

Managing a large number of users and multiple groups within an organization can be difficult in SharePoint, and usually requires heavy IT involvement. Wouldn’t it be nice if you could allow managers to create and remove their own users, reset passwords, and change group settings using a simple, centralized interface? User Manager for Siteslets you do just that. You can define which specific users within your organization can modify user information, and which business unit they can affect. You can even exclude specific accounts from being accessed by the product. User Manager for Sites provides you with the flexibility to decide who can manage users, and which users they can manage.

User Manager for Sites provides administrators or specific users with access to a simple, SharePoint-based application that lets them maintain and organize user access security information for Sites in a Site Collection. Managers can create, modify, or remove both users and groups from a single interface. Multiple default views allow managers to handle large numbers of users easily. Create users with multiple group access instead of having to do it one group at a time.

Error Log Files

Applies To

Bamboo Products
Windows SharePoint Services v3 and Microsoft Office SharePoint Server 2007
SharePoint Foundation 2010 and SharePoint Server 2010
SharePoint Foundation 2013 and SharePoint Server 2013—Standard Edition
SharePoint Server 2016

While troubleshooting issues, the Bamboo support team may request a copy of the log files for your Bamboo product(s). Many licensing, functionality and access issue information is captured in the log files found in the BambooSolutions file folder.

This directory is located at C:WindowsTempBambooSolutions

The log files are named in this format: bsc_bamboo_{processID}.log

where {processID} is the ID of the w3wp.exe process which was handling the request at the time of the error

NOTE: These files will be created on any farm server running the Microsoft SharePoint Foundation Web Application (on SharePoint 2010 or SharePoint 2013) or the Windows SharePoint Services Web Application (on SharePoint 2007).

To determine which servers on the farm run these services:

SharePoint 2007:

Go to the page Central Administration > Operations > Servers in Farm

SharePoint 2010:

Go to the page Go to the page Central Administration > System Settings > Manage Servers in this Farm

SharePoint 2013:

Go to the page Central Administration > System Settings > Manage Servers in this Farm

There may be many log files. When reporting a problem to support, attach the most recent file(s) to your support ticket. If you know the time at which the error occurred, choose the file with the corresponding date/time.

Refer to Topology and Services in SharePoint Central Administration for a list of servers running this service. Learn more…

Deploying a Bamboo solution to a new Web Application

Note: Perform these steps using an account that is a member of the SharePoint Farm Administrators group.

Step	for SharePoint 2007	for SharePoint 2010/2013
1.	In SharePoint Central Administration, click the Operations link. In the Global Configuration section, click the Solution Management link. A list of installed solutions is displayed.	In SharePoint Central Administration, click System Settings link. In the Farm Management section shown on the page, click the Manage farm solutions link. A list of installed solutions is displayed.
2.	Click on the name of the solution you want to deploy.	Click on the name of the solution you want to deploy.
3.	Click the Deploy Solution link.	Click the Deploy Solution link.
4.	Select the Web application to deploy to and a deployment schedule, and then click OK.	Select the Web application to deploy to and a deployment schedule, and then click OK.

CSS Overview

Classes for customizing CSS in your environment are provided by Bamboo so that you can customize web parts to match your branding. We also provide skins that change the look and feel but these are used discretely. See the topic Skins Overview for more information.

Calendar Plus

CSS for Calendar Plus

Chart Plus

Cross List

CSS for Cross List – this topic covers the classes you would need to modify for Cross List.

Navigators

Password Change

CSS for Password Change Web Part

PM Central

PMC Skin Templates

Team Calendar

CSS for Team Calendar

Virtual Map View

CSS for Virtual Map View

Configure the Settings Menu in User Manager for Sites

Return to Overview of Web Part Configuration

User Manager for Sites also has a Settings menu on its tool bar. This button is only available to Site Collection administrators. It is hidden for all other users. Once these settings are configured, they are global for all User Manager for Sites web parts within a Site Collection.

This menu contains the following options:

Column	Description	Image
Profile	Enter the LDAP path to acquire the Active Directory user schema (i.e. LDAP://ENGR.BAMBOO.LOCAL), and click OK. You only need the fully qualified domain name here – not the LDAP path that includes organizational units that you entered into the tool pane. Then select from the list of Active Directory properties to be displayed in user profiles.
User Setup Properties	Enter in the Active Directory Property Name and then a user friendly Property Display Name, and click the Add Property button to create user setup properties. These properties are stored per Site Collection in SharePoint and displayed for input during user account creation. Use the Order column to set the order in which these properties are displayed on the first screen in user account setup, then click OK. Click the trash can icon to the right of the property to delete it. You can use this setting if you want to create SharePoint users at the same time that you create an Active Directory user.	NOTE: The LDAP path entered into the Active Directory Services Settings in the Web Part tool pane is used when creating a new user in order to attain the appropriate organizational units from Active Directory in which to create the user’s account.
E-mail	Here you need to configure the SMTP server name and the e-mail address from which all e-mails from User Manager for Sites will be sent. The system uses this mail server to send notification and e-mails to users. Note that some mail servers require the From address to be a valid e-mail address in order for mail to be sent correctly.
Excluded Users	Exclude certain user profiles from being displayed in any view. Separate users by semicolon. Click the Check Names icon to verify the user exists or select the address book icon to search for users.

Complementary Products for User Manager for Sites

You will find many of our products complement each other quite nicely saving you the time and trouble to write custom code. With Bamboo at the heart of your SharePoint investment, you gain access to a huge catalog of enhancements, components, and accessories that add the critical functionality your business requires.

The same components can be easily used in future applications and they all come from a single, trusted vendor, ensuring an easy purchase process and support you can count on. That’s the Bamboo Way!

Choosing which farm servers to license

Bamboo products are deployed to all servers in the farm running the Microsoft SharePoint Foundation Web Application service (or Windows SharePoint Services Web Application in WSSv3/MOSS), which may include servers that do not serve Web content. For most products, only servers that serve Web content need a license key (Alert Plus is an exception), but all servers that run the Microsoft SharePoint Foundation Web Application service will appear on the Web License Manager Status and Activation pages by default.

If you would like to see only certain servers displayed in the Web License Manager, follow these steps:

Step	Action
1.	Click the Choose License Server(s) link on the Bamboo Web License Manager main page.
2.	Although this step is optional, it makes it easier for SharePoint Administrators to see which servers in the farm need a license key, if not all do. On the page displaying the list of servers, check the box for each server functioning as a Web Front End (WFE). Some products, such as Alert Plus or List Rollup, may include optional features that require licensing of a SharePoint application server as well. If so, these servers can also be selected.

Step

Action

Click the Choose License Server(s) link on the Bamboo Web License Manager main page.

Although this step is optional, it makes it easier for SharePoint Administrators to see which servers in the farm need a license key, if not all do.

On the page displaying the list of servers, check the box for each server functioning as a Web Front End (WFE).

Some products, such as Alert Plus or List Rollup, may include optional features that require licensing of a SharePoint application server as well. If so, these servers can also be selected.

WLM-choosing license servers2.jpg

Can trials be extended?

Overview of Licensing and and Product Activation

Once you have installed a Bamboo product on your farm and the trial period has passed, you cannot install a second trial. Instead, you need to extend the original trial period. Contact your Bamboo Sales Account Manager (Sales@bamboosolutions.com) for a trial extension.

Before you uninstall

IMPORTANT: Before you uninstall a Bamboo product, make sure that it is no longer in use on any site in your farm. If a web part resides on a page and you uninstall the web part, an error will be displayed for users that visit that page. The uninstall process does not update individual pages in your SharePoint portal.

Also, if you uninstall Workflow Conductor (WFC) and some workflows built with WFC are still active, those workflows will fail.

You have several choices for how to uninstall your Bamboo product:

Option	Comment
Use the Updated Uninstall Process for Bamboo components	Based on feedback from our customers, Bamboo introduced updated install/uninstall processes for component products (web parts). Instead of the Setup.exe Installation Application, we now supply two PowerShell scripts – one for Install/Upgrade and the other for Uninstall – to be used to install, upgrade, or uninstall the product. For more information, see Overview of the Updated Installation Process for Bamboo components.
Bamboo Installation Package	IMPORTANT: As of April 2017, Bamboo no longer includes the Installation/Setup program in product download packages. You can use the Bamboo product installation package that you used to install the product to uninstall. This is the preferred method, because it performs some automated system checks to help ensure the uninstall will be successful. It also steps you through each component, so its easier to make sure everything is uninstalled. See Using the Setup program to Uninstall for more information.
SharePoint Central Administration	Many Bamboo products are deployed as SharePoint solutions, so you can retract and remove them from Central Administration. See Uininstalling from SharePoint Central Administration for more information.
PowerShell	Some Bamboo products are packaged with a PowerShell script that you can use to uninstall. See Manually uninstall using PowerShell for more information.
stsadm	If you prefer, you can use stsadm commands to retract and delete Bamboo SharePoint solutions. See Manually uninstall using stsadm for more information.
Add/Remove Programs	Some Bamboo products include components that are installed using an EXE or MSI installer. See Uninstalling a Bamboo .msi or .exe for more information.

Depending on the uninstall method you choose, there may be a solution left behind after the install. This is intentional, as several Bamboo products use some of the same components. See What is left behind after uninstalling? for more information and steps for how to uninstall completely.

Before you Migrate from SharePoint 2007 to SharePoint 2010 Read This

Overview

Microsoft recommends that you use one of two basic approaches when you upgrade from SharePoint 2007 to SharePoint 2010:

In-place upgrade. An in-place upgrade is used to upgrade all Microsoft SharePoint sites on the same hardware. See How to Migrate a Bamboo Web Part from SharePoint 2007 to SharePoint 2010 using the In-Place Upgrade Method for details.
Database attach upgrade. A database attach upgrade enables you to move your content to a new farm or new hardware. See How to Migrate a Bamboo Web Part from SharePoint 2007 to SharePoint 2010 using the Database Attach Upgrade Method for details.

You can also combine these two types of upgrade in hybrid approaches that reduce downtime during an upgrade. For more information about these approaches, see Determine upgrade approach (SharePoint Server 2010) from Microsoft TechNet.

General Migration Restrictions for Bamboo Products

Regardless of the upgrade method you choose, you MUST change existing SharePoint sites to use the new user SharePoint 2010 experience. If you don’t, some features of your Bamboo products will not work as expected.
You need to make sure that you are running the latest available Bamboo product release in your SP2007 environment before migrating. Review information specific to the product(s) you are migrating to learn the minimum product release to migrate. See Bamboo product releases that are supported for migration from SharePoint 2007 to SharePoint 2010 for details.
Bamboo Solutions does not support the migration of Bamboo products deployed on WSSv2/SharePoint 2003 environments to SharePoint 2010 farms.
Bamboo Solutions does not support the downgrade of SharePoint editions when migrating from SharePoint 2007 to SharePoint 2010. For example, Bamboo products are not supported when migrating from MOSS 2007 to SharePoint Foundation 2010.

Migration Restrictions for Specific Bamboo Products

Before following the instructions for the method you choose, review information specific to the product(s) you are migrating. The In-Place Upgrade method is sometimes easier, but it takes longer. Some Bamboo products do not support the In-Place upgrade method and we recommend a hybrid In-Place Upgrade method as an alternative.

Bamboo products that use Telerik

Product	Uses Telerik?
Alerts Administrator	Yes
Alert Plus	Yes
Bulk Export	No
Bulk Import	No
Calendar Plus	Yes
Chart Plus	Yes
Column Level Security	Yes
Community Central	Yes
Cross List	No
Cross Site Display	No
Custom Identifier	No
Data Viewer	Yes
Discussion Board Plus	Yes
File Share Library	No
Filters Collection	Yes
Grants Management	Yes
Group Email	Yes
Group Redirect	Yes
In/Out Schedule Board	Yes
Knowledge Base Solution Accelerator	Yes
KPI Column	Yes
List Consolidator	Yes
List Print	No
List Rollup	Yes
List Rotator	No
List Search	Yes
Lookup Selector	No
Mini Calendar	No
My Alerts Organizer	No
Navigators	Yes
Password Change	Yes
Password Expiration	No
Password Reset	No
Password Management Toolkit	Yes
PM Central	Yes
Poll	Yes
Project Portfolio Dashboard	Yes
Rating	Yes
Rich Text	Yes
Site Creation Plus	No
SQL View	No
Task Master	Yes
Team Calendar	Yes
Time Tracking and Management	Yes
Tree View	Yes¹ No²
User Account Setup	Yes
User Directory	Yes
User Manager for Sites	Yes
User Profile Plus	No
User Profile Sync	No
User Redirect	No
User Registration Accelerator	No
Validator column	No
Video Library	No
Virtual Map View	No
Visual Indicator column	No
Wiki Publisher	No
Workflow Conductor	Yes
World Clock and Weather	No

¹SharePoint 2007 and SharePoint 2013
²SharePoint 2010

Bamboo product releases that are supported for migration from SharePoint 2010 to SharePoint 2013

The table below shows the minimum required Bamboo product version required when migrating Bamboo products from SharePoint 2010 to SharePoint 2013. If you have an earlier version installed than the one listed, please upgrade that product before migrating to SharePoint 2013.

For additional information:

Product	minimum SP2010 version	minimum SP2013 version
Alert Plus	30.2.115	30.2.121.2013
Alerts Administrator	10.4.52	10.4.62.2013
Calendar Plus	40.1.143	40.1.155.2013
Chart Plus	30.5.109	30.5.143.2013
Column Level Security	10.3.34	10.3.48.2013
Community Central	10.1.91	10.5.76.2013
Cross List	10.5.20	N/A
Cross Site Display	10.2.26	10.2.40.2013
Custom Identifier Column	10.0.45	10.0.57.2013
Data-Viewer	30.5.67	30.5.57.2013
Discussion Board Plus	10.5.22	20.0.57.2013
DWG Parser SharePoint 2007 Only	N/A	N/A
Filters Collection	10.3.25	10.3.35.2013
File Share Library	20.0.60	20.0.81.2013
Grants Management	10.5.20	N/A
Group Email	10.7.43	10.7.46.2013
Group Redirect	20.3.27	20.3.33.2013
Hello	20.1.9	N/A
In/Out Schedule Board	10.4.56	10.4.57.2013
Knowledge Base	20.2.47	20.2.75.2013
KPI Column	10.3.65	10.3.78.2013
List Bulk Export	1.4.12	20.0.18.1
List Bulk Import	2.5.105	30.0.29.2013
List Consolidator	10.0.79	10.0.107.2013
List Print	10.4.31	10.4.35.2013
List Rollup	60.0.64	60.0.70.2013
List Rotator	20.5.82	20.5.99.2013
List Search Advanced	10.8.93	10.8.121.2013
List Search Simple	20.1.140	20.1.167.2013
Lookup Selector Column	20.3.61	20.3.88.2013
Mini-Calendar	20.8.67	20.8.86.2013
My Alerts Organizer	10.4.43	10.4.51.2013
Navigators	10.3.47	10.3.57.2013
Password Change	40.1.65	40.1.68.2013
Password Expiration	10.6.43	10.6.49.2013
Password Reset	20.4.51	20.4.70.2013
Poll	10.4.53	10.4.63.2013
Project Management Central	40.1.135	40.1.109.2013
Project Portfolio Dashboard	10.8.58	10.8.80.2013
Quick Add	10.0.29.0	10.0.29.2013
Rating Column	10.2.43	10.1.54.2013
Rich Text Column	10.3.27	10.3.28.2013
Site Creation Plus	10.4.66	10.4.71.2013
SQL View	10.6.26	N/A
Task Master	30.5.117	30.5.116.2013
Team Calendar	10.7.18	10.7.36.2013
Time Tracking and Management	1.6.46	10.6.88.2013
Tree View	10.7.83	10.8.23.2013
User Account Setup	40.0.107	40.0.148.2013
User Directory	10.7.53	10.7.81.2013
User Manager for Sites	10.3.46	10.3.62.2013
User Profile Plus	10.4.39	10.4078.2013
User Profile Sync	1.6.10	20.0.20.2013
User Redirect	10.5.16	10.5.27.2013
User Registration Accelerator	10.3.24	10.3.35.2013
Validator Column	10.3.20	10.3.35.2013
Video Library	20.0.87	20.0.106.2013
Virtual Map View	10.9.46	10.9.42.2013
Visual Indicator Column	10.3.59	10.3.79.2013
Wiki Publisher	10.0.65	10.0.85.2013
Workflow Conductor	30.0.0	30.0.1.2013
World Clock and Weather	20.4.47	20.4.52.2013

Bamboo product releases that are supported for migration from SharePoint 2007 to SharePoint 2010

The table below shows the minimum required Bamboo product release required when migrating Bamboo products from SharePoint 2007 to SharePoint 2010. If you have an earlier release installed than the one listed, please upgrade that product before migrating to SharePoint 2010.

For additional information:

Product	minimum SP2007 release	minimum SP2010 release
Alert Plus	3.0.62	30.0.59
Alerts Administrator	1.4.12	10.4.30
Calendar Plus	4.0.96	40.0.36
Chart Plus	2.5.43	20.5.25
Column Level Security	1.3.4	10.3.7
Cross List	1.5.5	10.5.6
Custom Identifier Column	1.0.35	10.0.35
Data-Viewer	3.3.59	30.3.67
DWG Parser	N/A	N/A
Filters Collection	1.3.5	10.3.13
File Share Library
Grants Management	TBD	TBD
Group Email	1.7.4	10.7.11
Group Redirect	2.3.11	20.3.14
Hello	TBD	TBD
In/Out Schedule Board
Knowledge Base	2.0.71 NOTE: Releases earlier than 1.2 are no longer supported for upgrade or migration.	20.0.56
KPI Column	1.2.40	10.3.33
List Bulk Export	N/A	N/A
List Bulk Import	N/A	N/A
List Consolidator	1.0.87	10.0.62
List Print	1.4.5	10.4.18
List Rollup	Classic: 5.0.55 Schema: 5.0.77	Classic: 40.5.13 Schema: 50.0.85
List Rotator	2.5.24	20.5.44
List Search Advanced	1.8.51	10.8.48
List Search Simple	1.8.64	10.8.60
Lookup Selector Column	1.3.24	20.3.15
Mini-Calendar	2.7.8	20.7.11
My Alerts Organizer	1.4.13	10.4.40
Navigators	1.3.11	10.3.12
Password Change	3.5.8	30.5.14
Password Expiration	1.5.11	10.5.19
Password Reset	2.4.11	20.4.31
Project Management Central	2.1.21	20.1.12
Rich Text Column	1.3.9	10.3.14
Site Creation Plus	1.4.31	10.4.18
SQL View	1.6.17	10.6.23
Task Master	2.0.150	20.0.34
Team Calendar	1.5.4	10.5.11
Tree View	1.7.29	10.7.27
User Account Setup	3.4.8	30.4.31
User Directory	1.7.1	10.7.2
User Manager for Sites	1.3.1	10.3.19
User Profile Plus	1.4.7	10.4.35
User Profile Sync	N/A	N/A
User Redirect	1.5.3	10.5.14
Validator Column	1.3.1	10.3.12
Virtual Map View	1.9.25	10.9.9
Visual Indicator Column	1.3.7	10.3.19
Wiki Publisher	1.0.26	10.0.25
Workflow Conductor	1.5.1	1.5.1
World Clock and Weather	2.3.15	20.3.15

Activating Your Bamboo Product License

Overview of Licensing and and Product Activation

Licenses for Bamboo products that are installed on SharePoint servers are activated in SharePoint Central Administration using the Bamboo Web License Manager. Follow these instructions to activate a Bamboo product license.

NOTE: Licenses for desktop/server applications such as List Bulk Import, User Profile Sync, and List Bulk Export are activated using a standalone version of the licensing application, called Bamboo License Manager. See Activating a Bamboo Desktop Product Using the License Manager for more information.

Before performing the steps listed below, be sure you have installed the Bamboo Web License Manager on your SharePoint farm. See Installing the Bamboo Web License Manager for more information.

Step	Action
1.	From SharePoint Central Administration, click Manage My License Keys under Bamboo Solutions. NOTE: If you don’t see this option listed, see Why isn’t Manage My License Keys displayed in SharePoint Central Administration?
2.	You may see two groupings on the page, Suites and Packs or Individual Products. When activating a Web Part or Application, expand the Individual Products section. Locate the product you need to activate. Hover over a product name to see a drop-down menu associated with the product. Select Activate/Deactivate from the menu.
3.	On the displayed page, the available servers in your SharePoint farm will be listed. You will need an individual License Key for each Web Front End server. Certain products, such as Alert Plus and List Rollup include features that can be run on application servers as well. In these cases, separate licenses may also be required for one or more application servers. NOTE: If some of the servers listed do not receive web traffic, or if there are application servers that do not need a license, you can remove them from the list. Please see Choosing which farm servers to license for more information. To activate a license for a server, type or copy and paste the License Key into the field provided and click Activate. NOTE: If your SharePoint server does not have Internet access, you may get an error when you click Activate. If you experience this, see Activating My Bamboo Product License Offline for more information.
4.	Your Bamboo product is now Active and is ready for use, as shown by the Status column. If you ever need to check which license key you used to activate each server, the license key used is shown on this status page.

Activating Your Bamboo Product License Offline

Overview of Licensing and and Product Activation

Licenses for Bamboo products that are installed on SharePoint servers are activated in SharePoint Central Administration using the Bamboo Web License Manager. Licenses are normally activated online, but sometimes SharePoint servers do not have access to the Internet. If this is the case with your servers, follow these instructions to activate a Bamboo product license offline.

NOTE: Before performing the steps listed below, be sure you have installed the Bamboo Web License Manager on your SharePoint farm. See Installing the Bamboo Web License Manager for more information.

Step	Action
1.	From SharePoint Central Administration, click Manage My License Keys under Bamboo Solutions. NOTE: If you don’t see this option listed, see The Bamboo Web License Manager does not show up in Central Administration. How do I fix that
2.	You may see two groupings on the Manage My License Keys page, Suites and Packs and Individual Products depending on what Bamboo products you’ve installed on the farm. When activating a Web Part or Application, expand the Individual Products section. Locate the product you need to activate. Hover over a product name to see a drop-down menu associated with the product. Select Activate/Deactivate from the menu.
3.	All servers in your SharePoint farm that are running the Microsoft SharePoint Foundation Web Application service will be listed. The license status for each will be Not Active or Trial. You will need an individual License Key for each server. If some of the servers listed do not receive web traffic, you can remove them from the list. Please see Choosing which farm servers to license for more information. To activate a license for a server, type or copy and paste the License Key into the field provided, check the Activate Offline box, and then click Activate.
4.	On the page displayed, a Machine Key will be displayed with the License Key and a space to enter the Activation Key. NOTE: Eight spaces are shown if you are running WSSv3/MOSS. If you are running SharePoint 2010 or 2013, there is just one space. Copy the License Key and the Machine Key to an email and send it to Bamboo’s Support Team at Support@bamboosolutions.com. They will reply via Email with the Activation Key. If you have several servers in your farm, you can send the License Key-Machine Key combinations for all of them in one Email message to the Support Team. Alternatively, you can generate the Activation Key yourself via the My Bamboo area of the Bamboo Solutions website. See Generating Activation Keys using My Bamboo for more information. Once you have the Activation Key, enter it in the space provided and click Activate. NOTE: The Machine Key, as you may have guessed, is tied to the HW profile of the server. As such, the Activation Key is also tied to the HW profile. If the HW profile of a server changes, the License will fail and need to be deactivated and then re-activated, similar to what is required when you move your farm to new servers. See Migrate your Bamboo Product License Key From one SharePoint version to another for more information on what to do when this happens.
5.	After the license is activated, it’s status will be displayed on the page.

How to activate a Bamboo Site Collection Feature

Product feature activations can be done automatically at the site collection level when the product is installed using the Bamboo Installation/Setup program. However, there are a few reasons why you may need to manually activate (or deactivate) Bamboo product features:

You are using the updated installation process for Bamboo components.
You opted out of automatic feature activation during installation using the older Setup program.
You added a new site collection and want to add Bamboo features to it.
You want to remove Bamboo product features from an existing site collection.

To manually activate (or deactivate) Bamboo product features, follow the instructions below.

IMPORTANT: Perform these steps using an account that is a Site Collection Administrator.

Step	Action
1.	From a page on the top level site of a site collection, click Site Actions and then Site Settings. In the Site Collection Administration section of the page displayed, click Site collection features. If you don’t see this section, you may not be a Site Collection Administrator. If you don’t see the link, you may not be on the top level site of the collection. A list of available features will be listed.
2.	Find the appropriate feature. The status column indicates if the feature is currently active. If it hasn’t yet been activated, click the Activate button. If it’s activated and you need to Deactivate, click Deactivate. For information about which feature to activate for a particular product, please see this article.

Step

Action

From a page on the top level site of a site collection, click Site Actions and then Site Settings. In the Site Collection Administration section of the page displayed, click Site collection features.

If you don’t see this section, you may not be a Site Collection Administrator. If you don’t see the link, you may not be on the top level site of the collection.

A list of available features will be listed.
SCA-Active SCFeatures.png

Find the appropriate feature. The status column indicates if the feature is currently active. If it hasn’t yet been activated, click the Activate button. If it’s activated and you need to Deactivate, click Deactivate.

For information about which feature to activate for a particular product, please see this article.

About the Installation Files

Options for Installing

image showing install files for Tree View web part When you extract the product EXE to a location on your SharePoint server, several folders are created that contain installation files and Setup program configuration files. The root level of the extracted file system includes the file Setup.bat, which launches the Setup program. The list below shows the installation files for the Tree View Web Part, as an example.

For manual installation, you will access the following folders that contain installation files:

Component.wsp: There may be several folders with names ending in .wsp, depending on your product. Each WSP folder contains the installation files for a specific SharePoint Solution. One or more SharePoint Solutions may be installed for each product component.
docs: Contains the Installation and Licensing Quick Start Guide.
misc: The MISC folder includes miscellaneous files, including PowerShell scripts for manually installing or uninstalling the product.
msi: If a MSI folder exists for your product, it could contain multiple files ending in .msi. Each is an installation executable. Some MSI installers in the msi installation folder have both a 32-bit and a 64-bit version. The 64-bit version will include .x64 in the file name. Run the version of the MSI that is appropriate for your operating system. Do not install both.
res: Contains files required by the Setup program but not necessarily needed during a manual install.

A license error occurs after successful license activation

SYMPTOM

You followed the directions in Activating Your Bamboo Product License successfully activated your license. However, when you go to a page where the web part is used you see a license error:

license error on web part page.png

CAUSE

If this happens immediately after successful activation, the error is typically that one or more WFE servers on the farm do not have an activated license. If you are sure all servers have been successfully activated, another cause could be that a trial extension file (.lic) remains on one of the WFE servers in the farm and is causing a conflict.

If the license error happens after you have been using your activated product for some time, the cause for the issue could be that the hardware profile of one of your WFE servers has changed. Bamboo product licenses are tied to the hardware profile. If that profile changes (i.e., you add a new hard drive), the license needs to be re-activated. See How to move your Bamboo Product License to a new server for resolution information.

RESOLUTION

Confirm that there are no Bamboo trial extension files (Bamboo.lic) on the any of the WFE servers. Follow these steps:

Step	Action
1.	From the SharePoint server, use Windows Explorer to drill down the inetpub folder structure to locate and access the appropriate virtual directory for the web application where the license error appears.
1.	Locate the ‘bin’ folder where the Bamboo product’s DLL should be found.
1.	Search for files that start with “Bamboo” and have a .lic extension. If one exists for the product with the license issue, delete it. NOTE: Be sure to check all WFE servers for the .lic file.

Step

Action

From the SharePoint server, use Windows Explorer to drill down the inetpub folder structure to locate and access the appropriate virtual directory for the web application where the license error appears.

Locate the ‘bin’ folder where the Bamboo product’s DLL should be found.

Search for files that start with “Bamboo” and have a .lic extension. If one exists for the product with the license issue, delete it.

NOTE: Be sure to check all WFE servers for the .lic file.

About Bamboo product Release Numbers

Overview

Bamboo products have several releases throughout the year. To understand more about the type of releases available, see the Bamboo Solutions Upgrade Policy.

Its important to know what release you have installed on your farm because:

You can better follow the Release Notes for the product, which tell you about new features and known limitations for each version/release.
If you are planning to migrate to a new version of SharePoint, you need to make sure you have a certain minimum version/release installed.
If you need to report an issue to our Support Team, they will need to know what version/release you are using.

Where to find Release Notes

As you look at each product’s documentation page, you will see there is a link to the Release Notes for that product at the top of the page.

Bamboo produces different version numbers of our products for the different SharePoint platforms.

SharePoint 2007 (WSSv3/MOSS) Release Numbers

If you are running SharePoint 2007, the version/release number consists of 4 parts, such as:

R1.2.3.0

The first digit indicates the Major Release. In the case above, this is “1”.
The second digit indicates the Minor Release (2 in the example above).
The third number indicates the build number.
The fourth number will always be 0 unless you are using SharePoint 2013 (see explanation below).

SharePoint 2010 Release Numbers

If you are running SharePoint 2010 (SharePoint Foundation 2010 or SharePoint Server 2010), the Major Release digit of the installed product’s file version includes a zero (0) in the digit such as:

10.2.3.0

To match your current installed product with the release notes, remove the first zero (0). The end result is version 1.2.3.0.

SharePoint 2013 Release Numbers

If you are running SharePoint 2013 (SharePoint Foundation 2013 or SharePoint Server 2013), the Major Release digit of the installed product’s file version includes a zero (0) and the fourth digit is “2013” such as:

10.2.3.2013

To match your current installed product with the release notes, remove the first zero (0) and the 2013. The end result is version 1.2.3.0.

Background

Resolution

Applies To

Calendar Plus

Chart Plus

Cross List

Data-Viewer

List Rotator

List Search

Mini Calendar

Navigators

Password Change

PM Central

Team Calendar

Virtual Map View

Overview

General Migration Restrictions for Bamboo Products

Migration Restrictions for Specific Bamboo Products

SYMPTOM

CAUSE

RESOLUTION

Overview

Where to find Release Notes

SharePoint 2007 (WSSv3/MOSS) Release Numbers

SharePoint 2010 Release Numbers

SharePoint 2013 Release Numbers