What version of Telerik Components are deployed by Bamboo Products?

The Q1 (2017) Cumulative Update for Bamboo products, released in April 2017, updates the Telerik version used in all Bamboo component products that use Telerik:

Telerik Library

Version deployed for SP2013/SP2016

Version deployed for SP2010

Telerik.Web.UI

2016.3.1027.45

(previously, version 2012.3.1016.35 was deployed)

2016.3.1027.35

(previously, version 2011.2.915.35 was deployed)

Telerik.Web.UI.Skins

2016.3.1027.45

(previously, version 2012.3.1016.35 was deployed)

2016.3.1027.35

(previously, version 2011.2.915.35 was deployed)

IMPORTANT: The new Telerik assemblies are deployed from Bamboo.Framework.wsp. Some Bamboo component products may error if there are older and/or newer versions of Telerik assemblies in the SharePoint environment.

To fix errors caused by multiple Telerik versions deployed on your SharePoint farm, add an assembly redirect in your web.config file for each web application. See an example below and refer to How to Add a web.config Modification Using PowerShell for details.

<configuration>
...  
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">   
...
<dependentAssembly>
<assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" culture="neutral" /> 
<bindingRedirect oldVersion="2012.3.1016.35" newVersion="2016.3.1027.45" /> 
</dependentAssembly>   
</assemblyBinding>     
</runtime>
...
</configuration>

What is left behind after uninstalling?

After uninstalling a Bamboo product, you may see one or more of the following solutions remain on your farm…

	SharePoint 2007	SharePoint 2010	SharePoint 2013
What’s left	Bamboo.AJAXExtensions.wsp Bamboo.core.wsp	Bamboo.core Bamboo.core.v1.wsp	Bamboo.core.v2.wsp
Why?	Bamboo.core.wsp is left behind because it put specific versions of the Telerik.web.ui and Telerik.web.ui.Skins assemblies into the GAC. You may have other Bamboo products remaining on your farm that use these Telerik assemblies. If this solution is removed, those other products would cease to work properly	See the note under SharePoint 2007	See the note under SharePoint 2007
How to get rid of it	Please contact Bamboo Support should you wish to perform an AJAX uninstall.	See How to uninstall Bamboo.core.v1.wsp from your SharePoint farm	From SharePoint Central Administration, from the Manage Farm Solutions page, Retract the solution and then Remove it. No additional steps are required.

SharePoint 2007

SharePoint 2010

SharePoint 2013

What’s left

Bamboo.AJAXExtensions.wsp
Bamboo.core.wsp

Bamboo.core
Bamboo.core.v1.wsp

Bamboo.core.v2.wsp

Why?

Bamboo.core.wsp is left behind because it put specific versions of the Telerik.web.ui and Telerik.web.ui.Skins assemblies into the GAC. You may have other Bamboo products remaining on your farm that use these Telerik assemblies. If this solution is removed, those other products would cease to work properly

See the note under SharePoint 2007

How to get rid of it

Please contact Bamboo Support should you wish to perform an AJAX uninstall.

See How to uninstall Bamboo.core.v1.wsp from your SharePoint farm

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

No additional steps are required.

WBS Level Format Settings

Return to Configuration Overview

You can configure the text for the Work Breakdown Structure (WBS) numbering in the Task Master tool pane. To format a WBS level:

Step	Action	Result
1.	In the tool pane under WBS Level Format Settings, choose the WBS level in the WBS Level drop-down list.
2.	Select Click here to format the selected WBS Level.	After you select a WBS level and click on the green hyperlink, a blue formatting box is added to the WBS Level Format Settings section. Click the blue box to set the text formatting for that level. ImportantThe level you pick in the drop down box will be matched in the blue selector box that appears above it. In our screen shot above, we picked X.X.X.X.X and that is the formatting option that appears in the blue box above it.
3.	A dialog box allows you to choose format the font, font color (i.e. Foreground > Pick), font size and font style.
4.	After you finish formatting the text for each level, click Apply and then click OK.	This is an example of how each level is formatted differently: The result of the formatting will appear as follows: NOTE: If when you are working with Task Master and the text color in the grid changes after you click Recalculate, refresh the browser by clicking F5 to reapply color coding.

Using the Setup program to Uninstall

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

Before uninstalling a Bamboo web part product, be sure to delete the web part from all pages where it was used. If you forget to do this, your users will see errors on those pages after you uninstall.

Step	Action
1.	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.
2.	Locate the installation files used to install the product. Double-click the Setup.bat program included in the main folder. Select the product in the Components section in the Setup program. Verify the installation location and required permissions and then click Install.
3.	Click Next to begin the uninstall. Verify that the system checks pass successfully and click Next.
4.	In the Repair, Remove or Install screen, select the Remove All option and click Next. Wait while the components are uninstalled.
5.	When uninstallation is complete, click Next to review the summary screen and confirm that the product removal was successful. Click Close.
6.	If there are additional components in the Components list in the Setup program, follow steps 2-5 above for each component.
7.	If you stopped the World Wide Web Publishing Service, restart it. 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 Start.

Use the provided .lic file to extend your product’s trial period

Your Bamboo Account Manager may send you a *.lic file to use to extend your Bamboo product trial. The *.lic file needs to be placed in the folder on each WFE server where the product activation DLL resides. For SharePoint 2010 or SharePoint 2013, this is typically the Global Assembly Cache (GAC).

If you receive one, follow these instructions to install it.

Step	Action
1.	It is not possible to copy the .lic file directly to the GAC. Instead, you will copy it to the gac_msil* folder. On the SharePoint WFE server, from the Run command, enter `%systemroot%assemblygac_msil` Verify that you see the activation DLL for your Bamboo product listed. See Listing of Bamboo Solutions Web Parts and their associated Activation DLLs for details.
2.	Copy and paste or drag and drop the .lic file into the gac_msil folder.
3.	Repeat steps 1-2 for each WFE server in the farm.
4.	If a trial expired error was surfacing, browse to the site and refresh the page. The error should disappear once the .lic file is copied successfully to each WFE server. If you weren’t getting a trial expired error, you can verify the license was successfully extended by checking the status of your trial. See How to check the status of your trial license for more information. IMPORTANT: When you license this product after purchase, you will need to remove the *.lic file used to extend the trial as it may impact the license activation process.
5.	If the expired license message doesn’t go away, it could mean that the assembly file for the product you are trialing is in the Global Assembly Cache (GAC) rather than the /bin. This more typical for SP2010/2013 than for SP2007. In this case, the *.lic file needs to be added to the GAC.

Upgrading your Bamboo Web Part

Migrating in this documentation refers to moving from one version of SharePoint to another. Upgrading, on the other hand, refers to updating your Bamboo product to a newer release.

IMPORTANT: If you are migrating from one version of SharePoint to another version (i.e., SharePoint 2007 to SharePoint 2010), please see the topics under Migrating to a new SharePoint version…. You may need to upgrade the Bamboo products on your SharePoint farm before migrating.

To upgrade from a previous release of this product, perform the following upgrade procedure:

Step	Action
1.	Review Best practices for a successful install to learn which servers to install on and what services to stop or restart. These steps apply if you are upgrading or installing for the first time.
2.	Locate the product installation files. If you are upgrading, you may have downloaded a new version from the My Bamboo area of the Bamboo Solutions web site. If you just unpacked a new version, the Setup.bat will run automatically. Otherwise, double-click the Setup.bat program included in the root directory of the Installation Files. See About the Installation Files.
3.	Select the first product component in the Components section in the Setup program. When a component is selected, information specific to it is displayed on the right side of the interface. Verify the Location of Install Files and Required Installation Permissions. When ready, click Install. The installation program starts. It is a step-by-step wizard. The example screen shot shown is for the Tree View Web Part, but most Bamboo product installs look similar.
4.	Click Next to begin the upgrade. Verify that the system checks pass successfully and click Next. If the system checks do not pass, you will not be able to proceed. 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.
5.	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.
6.	When the upgrade is complete, click Next to review the Summary screen and confirm that the product upgrade was successful. You may need to scroll up to review the entire summary. When satisfied, click Close.
7.	If there are additional components listed in the Setup program, repeat steps 3-6 for each.
8.	When all the component upgrades have been completed successfully, be sure to restart the World Wide Web Publishing Service if it was stopped.

Upgrading using the updated process

Overview of the Updated Installation Process

In April 2017, with the Q1 Cumulative Update (CU) Bamboo introduced updated install/uninstall processes for component products (web parts). For more information about why this was introduced, please see Overview of the Updated Installation Process for Bamboo components

To upgrade a Bamboo product using the updated install process, please follow these steps (Warning.. Upgrades should be performed in Non-Peak hours as your farm will temporarily go offline)::

No.	Function
1.	Download the install package from downloaded from My Bamboo.
2.	Extract the contents of the package.
3.	Run the Install.ps1 from a WFE server in PowerShell as an admin. The install.ps1 script is used to install a new product or uppgrade an existing product.
4.	The script will look for WSPs in the install folder and list those found. Next, it will check to see if those solutions are already installed on the farm. If so, the installed solutions will be saved to a backup folder before proceeding. The folder will be named *bak_2017033015340* where the number represents the datetime the backup was created. This will provide the capability to rollback if the upgrade doesn’t conclude as expected. Rather than deploying the solution immediately, the script schedules deployment time for 1 minute in the future so multiple upgrades won’t collide. If a solution was previously deployed, the script uses Update-SPSolution to update it since that cmdlet is fast and reliable.
5.	When the deployment completes, deployment status information will be displayed for each solution. Check Central Administration to confirm deployment completion.
6.	If the upgrade doesn’t conclude as expected, you can easily rollback the install by simply copying the install.ps1 file to the *bak* folder created during the upgrade and running it from there as an Administrator.

Uninstalling using the updated process

Overview of the Updated Installation Process

To uninstall using the updated process, please follow these steps:

No.	Function
1.	Download the install package from My Bamboo.
2.	Extract the contents of the package.
3.	Run the Uninstall.ps1 from a WFE server in PowerShell as an admin.
4.	The script will look for WSPs in the install folder and list those found. It will uninstall them in alpha order. Rather than removing the solution immediately after its retracted, the script schedules deployment time for 1 minute in the future so multiple installs won’t collide. IMPORTANT: The script does not uninstall Bamboo.framework.wsp because it is a shared component and needed by other Bamboo components that are still installed. If you do not have other Bamboo products insalled on the farm, you can comment out the part of the script that skips the Bamboo.Framework.wsp.
5.	When the retraction completes, check Central Administration to confirm retraction completion.

Uninstalling from SharePoint Central Administration

NOTE: You need to be a machine administrator in order to Retract and remove a solution via Central Administration.

Step	Action
1.	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.
2.	Solutions are listed alphabetically. Find the solution you need to uninstall and click its Name. The solution status will be displayed. NOTE: The image below is from SharePoint 2010, but solution status from SP2007 and SP2013 look very similar. If the solution is deployed, you will see a Retract Solution link at the top of the page. If the solution is not deployed, you will see a Remove Solution link.
3.	Retract the solution from all web applications. Choose to retract now, or schedule it to occur at a particular time. Choose to retract from All content Web applications. Click OK when ready. NOTE: IF you are not a machine administrator, you may see an Access denied error. Make sure you have the appropriate permission level before attempting to retract a solution.
4.	Remove the solution. Once a solution has been retracted, the Remove Solution link is shown. Click Remove Solution to remove the solution.

Troubleshoot Problems with Deploying Farm Solutions

Troubleshoot Problems with Deploying Farm SolutionsTop

This topic applies to:

WSS 3.0 and MOSS 2007
SharePoint Foundation 2010/2013 and SharePoint Server 2010/2013/2016

Several issues and their corresponding solutions are described below. Click the link to jump to the appropriate issue.

Issue 1: Copying or Removing Assemblies
Issue 2: Deployment Fails or Times Out
Issue 3: Copying a File Failed
Issue 4: Resources Scoped for one Web App must be deployed to more Web Apps
Issue 5: Cannot Find a Certain File

Issue 1: Copying or Removing Assemblies

With SharePoint 2010 and 2013, we sometimes see failures when trying to copy assemblies to the Global Assembly Cache (GAC) or remove assemblies or other files from the bin or 14 or 15 hive during solution retraction and/or deployment.

Resolution:

Restart the SharePoint 2010/2013 Administration service on all of the Web Front End servers (all servers on the farm where the Foundation Web Application service is running).
Restart the SharePoint 2010/2013/2016 Timer service as well.

NOTE: The SharePoint Administration service carries out the actual removing and adding of files during deployment. Restarting the service works most of the time because the service should release the handle on a file. However, if the Administration service does not release the handle on the file, then deployment can fail. Restarting the timer service on SharePoint 2010/2013 will restart all SharePoint 2010/2013 timer jobs and you will need to delay installation for a while, until all of those jobs have had a chance to complete.

Remove the solution.
Reinstall the solution.

For more information, see:
http://msdn.microsoft.com/en-us/library/aa544500.aspx
Top

Issue 2: Deployment Fails or Times Out

Deployment fails, and the reason is not clear from the error shown in installation feedback (or just shows time out errors), or the Bamboo GUI installer appears to stop in the middle of the deployment, and eventually times out.

The Timer Job Definitions in Central Administration may show one or more persistent “one time” timer jobs listed.

Manual installations using stsadm also fails to complete the installation.

Resolution:

Delete the one-time timer jobs listed in the timer job definition list. Restart the SharePoint 2010/2013 Timer service on each server in the farm running the Foundation Web Application service.
Try the installation again.
Any solutions that show up in on the Solution Management page in Central Administration with a status of “undeployed” or “error” need to be either deployed manually in Solution Management, or removed, if you are going to run the Bamboo GUI installer. For more information, see Installation stops at the Repair Remove or Install screen
Run the stsadm installation using the -local rather than the -immediate parameter for stsadm -deploysolution. This will not invoke the timer service. As stated in this Technet article:

-local “Deploys the solution synchronously on the local computer only. The timer service is not used.”

You will have to run the deploysolution with the -local parameter on each server running the Windows SharePoint Services Web Application service or Foundation Web Application service.
For more information about deploysolution, see:
Deploysolution: Stsadm operation (Office SharePoint Server)

For more information about which server is running the Windows SharePoint Services Web Application Service, look in Central Administration:
– on SP 2007 in Operations > Servers in Farm
– on SP 2010 in System Settings > Manage Servers in this Farm

Clear the SharePoint Configuration cache. The Web Front End servers may be out of sync. For more information and instructions see Clear the SharePoint Configuration Cache for Timer Jobs.

If you experience issues with WSS and MOSS timer jobs failing to complete are receiving errors trying to run psconfig, clearing the configuration cache on the farm is a possible method for resolving the issue. The config cache is where we cache configuration information (stored in the config database) on each server in the farm. Caching the data on each server prevents us from having to make SQL calls to pull this information from the configuration database. Sometimes this data can become corrupted and needs to be cleared out and rebuilt. If you only see a single server having issues, only clear the config cache on that server, you do not need to clear the cache on the entire farm.

To clear the cache a single server, follow the steps below on just the problem server.

Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
On the Index server, navigate to:

Server 2003 location: Drive:Documents and SettingsAll UsersApplication DataMicrosoftSharePointConfigGUID and delete all the XML files from the directory.
Server 2008 location: Drive:ProgramDataMicrosoftSharePointConfigGUID and delete all the XML files from the directory.
Delete all the XML file in the directory.

NOTE: ONLY THE XML FILES, NOT THE .INI FILE.

Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
After you see XML files appearing on the Index server, repeat steps 2, 3 & 4 on each query server, waiting for XML files to appear before moving to subsequent servers.
After all of the query servers have all been cleared and new .xml files have been generated, proceed to the WFE and Application servers in the farm, following steps 2, 3, 4 and 5 for each remaining server.
Top

Issue 3: Copying a File Failed

This is the error message that you get: “Copying of this file failed. This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again.”

Resolution:

For instructions and more information, see this MSDN article.
Top

Issue 4: Resources Scoped for one Web App must be deployed to more Web Apps

This is the error message that you see: “This solution contains resources scoped for a Web application and must be deployed to one or more Web applications.”

Resolution:

Usually this can be resolved by running the Bamboo GUI installer, removing the product, and then reinstalling it.

We have also found that if the solution is showing up in the Solution Management page as installed but not deployed, you can try to run a manual deployment using stsadm.

See Best Practices for Installing Bamboo Products

Also see MSDN Issues Deploying SharePoint Solution Packages
Top

Issue 5: Cannot Find a Certain File

After an apparently successful deployment, you see errors about not being able to find file(s) when attempting to view products on a page.

Resolution:

Be sure to exclude directories such as %systemroot%Program FilesCommon FilesMicrosoft SharedWeb Server Extensions from file level antivirus scanning, or you may find that files that were deployed in that directory will be removed when the antivirus scan runs.

For more information, see this TechNet article.
Top

The Bamboo Web License Manager does not show up in Central Administration. How do I fix that?

The Manage My License Keys link is only displayed in SharePoint Central Administration if the Bamboo Web License Manager Web application feature has been installed and activated.

During the installation of the Bamboo Web License Manager, on the Deployment Targets step, the option to automatically activate features is enabled by default. If this checkbox was deselected, the Bamboo Web License Manager feature will not be activated automatically after it is installed and you will need to activate it manually by following the steps below.

Step	Action
1.	Access SharePoint Central Administration as a member of the SharePoint Farm Administrators group.
2.	On the Central Administration home page, select Manage web applications in the Application Management section.
3.	In the Web Applications Management page, click the SharePoint Central Administration v4 web application.
4.	Notice that the Web Applications ribbon appears. Click the option Manage Features in the ribbon. The available features are listed.
5.	Locate Bamboo Web License Manager feature and click Activate.

Task Master Preferences

Return to Configuration Overview

Click on a category name below for details about the options available in the Preferences section of the Web Part Settings. To edit Task Master Web Part Settings, edit the Web Part properties and click the Task Master Web Part Settings button in the Web Part tool pane.

Step	Action	Result
1.	Show Go to List	When selected, the Go to List button is displayed in the Task Master web part. Go to List opens the task list in a SharePoint list view.
2.	Show Legends	Allows you to show or hide the legend at the bottom of the Task Master web part. The legend defines the color codes used for items displayed in the Gantt view.
3.	Show Critical Path	When selected, includes an option in the Task Master web part to highlight tasks that are in the critical path. See: How to Show the Critical Path.
4.	Show Grid or Show Gantt	Select whether the Task Master web part displays the task grid, the Gantt chart, or both. NOTE: You must select at least one.
5.	Allow Insert Task	When selected, allows users to insert new tasks above or below existing ones directly in the task grid. When Insert Task is enabled, an Insert Task icon is displayed next to each task in the task list so that users can click the Insert Task icon. NOTE: Notice this option is disabled. To enable this option, you must deselect the option Save changes to my task list every time a change is made in the Gantt chart in the Dependency Settings section. See Task Master Schedule and Calculation Settings for further clarification.
6.	Show Delete Items	When selected, the Delete Item button is displayed in the Task Master web part. To delete one or more tasks, select the radio button next to the task(s) and click Delete Item in the toolbar menu. Click OK in the prompt to delete the selected task(s) and its subtasks.
7.	Automatically expand level	By default this field is set to 0, which means that all of the summary task groups in your task list will be collapsed when you first access Task Master. If you set this field to 1, the summary task groups will be expanded and will show the first level of tasks under the summary task. To view tasks under a first-level task, click the + to expand that level. You can set the level to work with as many levels as you introduce in your task list.
8.	Duration and Work	Choose how your calculated duration and work are displayed: by days, hours or minutes. After adding a new task, click the Recalculate button to calculate the duration and work for the new task.
9.	Total slack is displayed in	A Total Slack of zero indicates the task is a critical task, meaning that the amount of time a task finish date can be delayed without affecting the project finish date.
10.	WBS Level Format Settings	Configure these settings to format the display properties for a Work Breakdown Structure (WBS) level. For each summary task group, X represents the WBS level for that task and corresponds to the Task Master outline structure. In the example above, Initiation Phase with a WBS of 1 is at level 1 (X), while Contractor Labor Hours with a WBS of 1.2.2.1 is at level 4 (X.X.X.X). Formatting WBS levels does not require that you show the WBS column or maintain the WBS structure. More detailed description can be found here.

Task Master Progress Bar Settings

Return to Task Master View Settings

Use these settings to configure the progress bar for tasks in the Gantt chart.

Select progress bar color: Enter in the Hex color number or select a color from the drop-down list.
Select Percent Complete Column: Select your column to be displayed. The only columns available in this drop-down list are the Number data-type columns from the list you selected earlier, such as % Complete or Assignment Units.

Task Master Schedule and Calculation Settings

Return to Configuration Overview

Click on a category name below for details about the options available in the Schedule and Calculation Settings section of the Task Master web part settings.

To edit Task Master web part Settings, edit the web part properties and click the Task Master web part settings button in the web part tool pane.

Task Master Task Assignments

Return to Configuration Overview

You can calculate task assignments based on three options:

Start Date and Due Date (the default option)
Start Date and Work
Start Date and Duration

These options give you more flexibility when assigning tasks and building schedules. They are located in the tool pane under Dependency Settings.

Use the following table to decide which option to choose.

Task Type	If Duration is modified	If Work is modified	If Assignment Units is modified
Fixed Work Task	Assignment Units is recalculated	Duration is recalculated	Duration is recalculated
Fixed Duration Task	Work is recalculated	Assignment Units is recalculated	Work is recalculated

Calculate resources method: In Task Master (Release 3.5 and above), you can choose how task resources are calculated when resources are added or removed from an existing task. These options give you more flexibility when assigning tasks and building schedules. They are located in the tool pane under Dependency Settings.

Task Master View Settings

Return to Configuration Overview

Click on a category name below for details about the options available in the View Settings section of the Task Master web part Settings.

To edit Task Master web part Settings, edit the web part properties and click the Task Master web part Settings button in the Web Part tool pane.

Task Master Working Hours Settings

Return to Configuration Overview

By default, Task Master uses a 24-hour day, 7-day week, 365-day calendar to schedule tasks. Nights, weekends and holidays are not excluded in task schedule calculations, but they can be. If you want to define specific workdays, exclude holidays, or enforce working hours for tasks, you can configure these settings in the Task Master tool pane. The workdays and working hours you select are designated as the only time that tasks can be worked on. Task schedule calculations will only include the days and times you specify in the tool pane settings.

NOTE: In Task Master 3.5 and above for SharePoint 2010/2013, you have the option to exclude lunch breaks.

The following settings can be configured in the Task Master tool pane. Click a setting to learn more.

Configure Task Master Workdays – The days of the week tasks can be worked on.
Configure Task Master Working Hours – The hours of the day tasks can be worked on.
Configure Task Master Holiday List – A Calendar list that contains holidays that tasks are not worked on.

Additional information about working hours can also be found on these topics:

Return to Task Master Schedule and Calculation Settings

Task Master Data Source Settings

Return to Configuration Overview

Click on a category name below for details about the options available in the Data Source Settings section of the Web Part Settings.

Each Task Master instance connects to a single data source. A data source contains the data to be represented in the schedule:

To connect to a data source, first select its type (SharePoint List or Bamboo List Rollup) in the Select Data Source Settings page.
Then click SharePoint or List Rollup in the left menu to configure connection details.

Configure a SharePoint List or Library

Configure Bamboo List Rollup Settings

Task Master Dependency Settings

Return to Configuration Overview

In the tool pane under Task Master Configuration > Dependency Settings, you can select the following Dependency Settings:

Save changes to my Task list every time a change is made in the Gantt chart: Select this option to save selected changes immediately. If you do not select this option, Save and Refresh are available on the menu. Refresh will undo your changes from the last time that you saved. Save will save the new changes.
Do not show warning message when users click the Save button: You will see this option disabled if you have checked the box in Step 1. If you deselect that check box, then you can see this box enabled and select it so that users receive a warning message each time they click the Save button.

Show the Recalculate button: Select this option to display the Recalculate button on the Task Master toolbar. Clicking Recalculate allows Task Master to recalculate and adjust your schedule after you make changes or add new tasks.

NOTE: You can disable the Recalculate button in order to turn off Task Master calculations and applied business rules.

To disable the Recalculation button, deselect Show the Recalculate button. This will remove the Recalculate button from the toolbar menu and Task Master will not re-compute anything until the button is enabled again.
Calculate task based on: With this option, you can assign tasks based on three options:
- Start Date and Due Date (the default option)
- Start Date and Work
- Start Date and Duration

Calculate resources method: With this option, you can choose how task resources are calculated when resources are added or removed from an existing task. Calculate resources methods are as follows:
- Increase or decrease duration in Task Master – this lets a task ends sooner or later but requires the same work.
- Increase or decrease the total work in Task Master – if the task requires less or more work hours, this keeps the duration of a task constant.
- Increase or decrease working hours in Task Master – you can add or subtract hours that resources work per day and this setting keeps the duration and work the same.

Task Master Display Columns Settings

Return to Task Master View Settings

Column Settings: Configure these settings to display specific columns in the task grid.

Value: Select a column from the drop-down list to be displayed in the task grid, such as Title, WBS or Parent Task.
Width (px): Type in the width of each column in pixels.
Add Row: Click this button to add another column.
Remove Row: Click this button to remove a column.
Show the task number (No.) column: Select this option to show the No. column. This column only shows the order of the tasks in the grid. It is not the same as WBS numbering.

Task Master Gantt Settings

Return to Task Master View Settings

Gantt Bar Text Settings: Configure the settings for the text that is displayed next to the task bar in the Gantt chart.

Show Gantt Bar text: Select this option to display text next to the task bar in the Gantt chart.
Display text from this column: Select the column that contains the text you want to display.
Font color: Enter in the Hex color number or select a color from the drop-down list.

Gantt View Display Settings: Use these settings to configure the appearance of the Gantt chart.

* Filter and show all tasks starting from this date: Enter the date that you want to use to filter the tasks in the Gantt view. For example, if you enter 6/1/2011, then all tasks with a start date prior to 6/1/2011 will not be displayed in the Gantt view.

NOTE: This filtered date is applied to all selected list views.

Scale for Gantt View: Select the default time scale for the Gantt chart (Day, Week, Month, Quarter or Year).
Gantt View Start Date: Enter the Start Date for the date interval in the Gantt view, select the Today option to use today’s date, or click to select a date.
Show week number in Gantt view: Select this option to display the week numbers in the Gantt view. This option displays the week number in Week, Month and Quarter views only.
Display graphical bar as an absolute task duration in Quarter and Year view: Select this option so that the bar in the Gantt view represents the absolute task’s duration when using the Quarter or Year views. If you do not select this option, the bar represents the relative task’s duration.

Task Master Glossary of Terms

Top

The terms listed below are words that are commonly used in task and resource management, scheduling and other related practices. There are also explanations for what some of the functions in Task Master are.

% A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

%

% Complete: The percentage of the duration that actually is completed for the task (or sub-tasks, if a summary task). For more information on how % Complete is calculated, read this Microsoft KB.

% Work Complete: The percentage of work that is completed for the task (or sub-tasks, if a summary task). % Work Complete is calculated the same way as % Complete, but using the Actual Work and Work fields instead of Actual Duration and Duration.

A

Actual Cost: Based on the percentage of the cost.

Actual Cost (Enter): This field allows you to manually enter the Actual Cost if you want to replace Actual Cost, which is automatically calculated by the application.

Actual Duration: The actual span of a task from start to finish, based on % Complete.

Actual Finish: The date when an assigned resource is actually finishing working on a task.

Actual Start: The date when an assigned resource actually begins to work on a task.

Actual Work: The actual percentage of the work that the resource has completed.

Actual Work in Days: The actual percentage of the work in days that the resource has completed.

Actual Work in Hours: The actual percentage of the work in hours that the resource has completed.
**
Assigned To: The resource that has been delegated to a task, risk, issue, etc.

Assignment Units: Determines the assigned resource’s allocation to a task, such as 50% or 100%.

Top

B

BSC: Balanced scorecard–a performance management tool used to keep track of the execution of the activities by staff members.

C

Child Task: The subtask of a Parent Task or Summary Task.

Constraint: Applied to a task to restrict how the task’s start and finish dates are calculated. Use constraints when you need to control the start or finish date of a task. See Constraint Type.

Constraint Type: Constraints are applied to a task to restrict how the task’s start and finish dates are calculated. See Constraints. Constraint Types include:

As Soon As Possible (ASAP): Schedules the task to begin as early as possible. Do not enter a start or finish date with this constraint. This is the default choice.
Start No Earlier Than (SNET): Schedules the task to start on or after a specified date. Use this constraint to ensure that the task does not start before a specified date.
Start No Later Than (SNLT): Schedules the tasks to start on or before a specified date. Use this constraint to ensure that the task does not start after a specified date.
Must Start On (MSO): Schedules the task to start on a specified date.
Critical Path: The longest path to finish a project. It includes the series of tasks that dictate the finish date for the project. If one task in the critical path is delayed, the project finish date will change.

Critical Task: A task that has zero Total Slack: the task is in the Critical Path. Critical tasks cannot be delayed without affecting the project finish date.

Top

D

Days Overdue: The number of days an incomplete task is overdue. If Today > Due Date and % Complete < 100%, the task is overdue. The number of days it is overdue is the number of workdays between today and the Due Date.

Duration: The total span of a task from start to finish. Duration is calculated by (Due Date – Start Date)(Working Hours/Day)

E

Early Finish: The earliest date a task can finish based on the Early Finish dates of predecessor and successor tasks and other task constraints. This is the earliest date a task can finish if all predecessor and successor tasks also finish on their Early Finish dates.

Early Start: The earliest date a task can start based on predecessor and successor tasks and other constraints.

F

Finish: The date when an assigned resource is scheduled to finish working on a task.

L

Late Finish: The latest date a task can finish without delaying the project finish date.

Late Start: The latest date a task can start without delaying the project finish date.

Top

M

Milestone: A scheduled event that signifies the completion of a major deliverable. Milestones are used to monitor the project’s progress. Typically, they are tasks with a duration of 0 time units (such as hours, days or weeks).

O

Overallocation: Assigning more tasks to a resource than the resource can accomplish in the available working time.

P

Parent Task: Tasks that are made up of subtasks and that summarize those subtasks. Also called Summary Tasks.

Predecessor Task: A dependency task on which the task depends before it can be started or finished.

R

Resource Allocation: How a resource is assigned to a task or project.

Top

S

Schedule Status: A status indicator based on the number of days a task is overdue. The indicator and number of days can be configured by modifying the Schedule Status column settings in the task list.

Start: The date when an assigned resource is scheduled to begin working on a task.

Summary Tasks: Tasks that are made up of subtasks and that summarize those subtasks. Also called Parent Tasks.

Top

T

Task Dependency: The relationship between tasks.

Total Slack: The amount of time a task finish date can be delayed without affecting the project finish date. A Total Slack of zero indicates the task is a critical task.

U

Units: The quantity that a resource is assigned to a task. See Assignment Units and Maximum Units.

W

WBS (Work Breakdown Structure): A hierarchical structure used to organize tasks for reporting schedules and tracking costs. Tasks are typically grouped beneath their summary or parent tasks, with each level down representing an increasingly detailed description of the task deliverable. For example, the Parent Task Develop Application has a WBS of 1.0. It has two child tasks, Write Requirements Document, which has a WBS of 1.1, and Review Preliminary Build, which has a WBS of 1.2.

Work: The hours that the resource works on a task.

Workdays: The days of the week when work can be done on a project task. Workdays can be defined in the Task Master Web Part settings.

Working hours: The hours of the day when work can be done on a project task. Working hours can be defined in the Task Master Web Part settings.

Top

Task Master Milestone Settings

Return to Task Master View Settings

Configure the appearance of milestones in the Gantt chart.

Select the Milestone column: Select the Milestone column in the task list. If you use a different list, then select the column that contains the Milestone indicator.
Milestone label: Select a column to be displayed next to the milestone in the Gantt view.

Click inside the box next to the Milestone label column drop-down list to set formatting for the Milestone label text. A dialog box is displayed so that you can choose font color (Foreground > Pick), font size and font style.

Set milestone color based on: Select a Choice column in the task list to base the milestone color on the value for that column. For example, to base your milestone column color on the current task status, select the Status column and choose a color for each status choice.

NOTE: To use the same color for all milestone tasks (like previous versions of Task Master), select any Choice column and use the same color for all choices.

Task Master Multiple Predecessor Tasks

Return to Configuration Overview

If your task requires that more than one other task in your project be completed before it can start, you can assign multiple Predecessor Tasks. By default, Task Master is configured to allow only one Predecessor Task per item. To allow multiple Predecessor Tasks, perform the following steps:

Step	Action	Result
1.	Go to Site Actions > View All Site Content. In the Lists section, select the task list configured for Task Master. The default task list is Bamboo Project Task List.
2.	In the List Tools > Lists ribbon, click the List Settings button.
3.	In the Columns section, click the Predecessor Task column to edit its settings.
4.	In the Additional Column Settings section, select the Allow multiple values option.
5.	Click OK to save the column setting changes.

Now when you add or edit a task, you have the option to select one or more Predecessor Task items. The Start Date of the new/updated task will be after the Due Date of the latest Predecessor Task.

You can also add or edit Predecessor Tasks directly in the grid. Click in the Predecessor Tasks column and check the tasks you want to add to the list.

In the example below, notice that Task 1 and Task 2 are assigned as Predecessor Tasks for Task 3. The Start Date of Task 3 is after the Due Date of Task 2, which finishes latest.

Return to Configuration Overview

System Requirements

	SharePoint 2010	SharePoint 2013	SharePoint 2016
Operating System	Microsoft Windows Server 2008	64-bit edition of Windows Server 2008 R2 Server Pack 1 OR 64-bit edition of Windows Server 2012 Standard or Datacenter	64-bit edition of Windows Server 2012 R2 Standard or Datacenter For database server: 64-bit edition of Microsoft SQL Server 2014 Service Pack 1 (SP1)
SharePoint Version	Microsoft Windows SharePoint Foundation 2010 OR Microsoft Office SharePoint Server 2010	Microsoft SharePoint Foundation 2013 OR Microsoft SharePoint Server 2013	Microsoft SharePoint Server 2016
Browser	Microsoft Internet Explorer 8 or higher	Microsoft Internet Explorer 8 or higher	Microsoft IE 10 or higher

SharePoint 2010

SharePoint 2013

SharePoint 2016

Operating System

Microsoft Windows Server 2008

64-bit edition of Windows Server 2008 R2 Server Pack 1

64-bit edition of Windows Server 2012 Standard or Datacenter

64-bit edition of Windows Server 2012 R2 Standard or Datacenter

For database server: 64-bit edition of Microsoft SQL Server 2014 Service Pack 1 (SP1)

SharePoint Version

Microsoft Windows SharePoint Foundation 2010

Microsoft Office SharePoint Server 2010

Microsoft SharePoint Foundation 2013

Microsoft SharePoint Server 2013

Microsoft SharePoint Server 2016

Browser

Microsoft Internet Explorer 8 or higher

Microsoft IE 10 or higher

Cross Browser Support:

All products are tested to work with IE 8 and higher.

Not all Bamboo products support all browsers that SharePoint 2016 supports. The products listed below offer cross-browser support for the following: Microsoft Edge, latest version of Google Chrome, latest and immediate previous release of Mozilla Firefox, and latest release of Apple Safari.

Note: Bamboo products are not supported in an IIS Web garden configuration.

Some of our products which are not Web Parts are installed on an individual’s desktop or laptop. Examples are List Bulk Import and User Profile Sync. The requirements for these products are dependent on the operating system on which they are used.

Operating System

Windows Vista (32-bit or 64-bit)
Windows 7 (32-bit or 64-bit)
Windows 8 (32-bit or 64-bit)
– Windows Identity Foundation 3.5
Windows Server 2003 or 2008 (32-bit or 64-bit)
Windows Server 2012 (64-bit)
– Microsoft .NET Framework 3.5
Windows 10 (32-bit or 64-bit)
– Windows Identity Foundation 3.5

Server

SharePoint 2013:

SharePoint Foundation 2013 or SharePoint 2013

SharePoint 2010:

SharePoint Foundation 2010 or SharePoint 2010

SharePoint Release 3:

Microsoft Windows SharePoint Services v3 or Microsoft Office SharePoint Server 2007

SharePoint Online

Microsoft 365, Multi-Tenant Hosting and Built-in Authentication

Task Master Color Coding Settings

Return to Task Master View Settings

Configure the color of the Gantt bar for any Choice column in the task list, such as Constraint Type, Priority or Status. Color coding is automatically added to the Task Master legend (if displayed).

Select a column to color code: The only columns available in this drop-down box are the Choice data-type columns from the list you selected earlier. After selecting a column, the values are displayed below for color selection.
Auto Select: Click this button to randomly select colors for the values.
Column Name: This is the choice value as defined by the selected column.
Hex: Enter in the Hex color number or select a color from the Color drop-down list.
Color: Select a color for each value from the drop-down list.

Task Master Custom Task Identifier

Return to Configuration Overview

If you need a way to identify tasks other than a simple Task ID or WBS number, you can configure an automatically-generated task ID using Bamboo’s Custom Identifier Column. Custom Identifier Column allows you to add a custom column to your task list that generates a unique ID every time a new task is added.

NOTE: Custom Identifier Column is not included with SharePoint Task Master, but can be purchased separately and is compatible with it.

Add Custom Identifier Column to your task list before you create project tasks.

Important Notes::

If you add Custom Identifier Column to a task list that already has tasks, any existing tasks will not be updated with a unique ID. Only new tasks that are created after the column is added will be assigned a unique ID value.

If you configure Custom Identifier Column with the option to Automatically Generate Unique ID, Task Master users will not able to change the ID for their tasks. Instead, consider using the option Force User-Entered ID to be Unique. This allows users to specify their own ID for tasks, and only checks that they enter one that has not been used before.

After you add Custom Identifier Column to your task list, you can display it in Task Master by adding a column to the grid view; see how to do it here.

The example below shows a task that was assigned a unique ID value using Custom Identifier Column.

Switch Between Enforcing Working Hours and Not Enforcing Working Hours

Return to Configuration Overview

If you choose to switch back to NOT enforcing working hours, you can clear the Enforce these working hours option in the tool pane:

Step	Action
1.	On the page where you have placed Task Master, open the configuration tool pane by clicking the arrow to the right of the Task Master title bar and selecting Modify Shared Web Part.
2.	In the Working Hours Settings, uncheck Enforce these working hours.
3.	Click Apply and then OK to save your changes.
4.	Click Recalculate on the Web Part tool bar.
5.	When you click Recalculate, Task Master updates the Due Date of your tasks to use a 24-hour day. The new Due Date is the Start Date + Duration in hours (or Start Date + Work in hours, if tasks are calculated using Start Date and Work). NOTE: If you display Duration in days, the number of days will change when you return to a 24-hour day, but Duration in hours remains the same. For example, if you have a task with a Duration of 16 hours and you previously had working hours of 9 AM to 5 PM, Duration in days was 2 days (two 8-hour working days). When you stop enforcing working hours, the Duration is still 16 hours, but only 0.67 days (16 hours out of a 24-hour day). In this example, working hours of 9 AM to 5 PM were previously enforced. Task Duration was 18 hours: May 4th 9 AM to 5 PM (8 hours), May 5th 9 AM to 5 PM (8 hours), and May 6th 9 AM to 11 AM (2 hours). Start Date and Time: May 4, 2010 at 9 AM Due Date and Time: May 6, 2010 at 11 AM When working hours are no longer enforced, the Start Date remains the same, but a new Due Date is calculated using the Duration of 18 hours and a 24-hour workday : Start Date and Time: May 4, 2010 at 9 AM (15 hours) Due Date and Time: May 5, 2010 at 3 AM (3 hours)

You can also choose to format the Start and Due Date columns as Date Only instead of Date & Time. In the example above, this would change the Start Date to May 4th and the Due Date to May 5th (without a time).

Return to: Task Master Working Hours Settings

Configure Task Assignments Based on Start & Due Dates

Return to Task Assignments

Why use this option? Use Start Date and Due Date to assign a task when you know when the task will start and when it will finish. You have two other options; see also:

Start Date and Due Date is the default option for assigning tasks. The new Assignment Units allows you to assign multiple resources to a task. You can enter a percentage of time that one or more resources are assigned to the task. In this case, two resources are assigned at 50%.

Use Case

Richard Kimble, a project manager, has a task for team members JeffDesign and QA One.
JeffDesign and QA One can start the task on October 4, 2012, and finish it on October 6, 2012.
JeffDesign and QA One are both able to work on the task 50% of the time.
Richard needs to create the task using a Start Date of 10/4/2012 at 8:00 AM and a Due Date of 10/6/2012 at 5:00 PM with Assignments Units of 50% for both JeffDesign and QA One.

In the tool pane under the Working Hours Setting, Richard selects the Enforce these working hours option, chooses his work hours as 8:00 AM to 5:00 PM and selects Exclude lunch time. He also excludes weekends from task scheduling.

Under Dependency Settings, Richard selects the Default using Start Date and Due Date option and the Increase or decrease duration so task ends sooner or later but requires the same total work option.

Richard creates the task as shown below and then clicks Recalculate from the Task Master toolbar.

Task Master updates the task to use the specified Start and Due Dates of 10/4/2012 and 10/6/2012.

Return to Task Master Task Assignments

Task Master Start Date and Duration

Return to Task Assignments

Use Start Date and Duration to assign tasks if you know the length of time that it will take to complete the task and when the task can start. You have two other options:

Start Date and Due Date (the default option)
Start Date and Work

These options give you more flexibility when assigning tasks and building schedules. They are located in the tool pane under Dependency Settings. When you assign tasks based on Start Date and Duration, Work, Assignment Units and Due Date are calculated based on the Duration units.

Use Case

Richard has a task he knows will take about 10 days and will begin on October 4, 2012. He wants to enter the Start Date as 10/4/2012 at 8:00 AM and the Duration as 10 days. He does not want to have to look at his calendar and count out the days in order to determine what the task’s end date will be.

In the tool pane under Working Hours Setting, Richard selects the Enforce these working hours option
He chooses his work hours as 8:00 AM to 5:00 PM and selects Exclude lunch time
He also Excludes weekends from task scheduling

Under Dependency Settings, Richard selects the Using Start Date and Duration option and the Increase or decrease the total work because the task requires less or more work hours. Keep duration constant. option.

Richard creates the task as shown below and then clicks Recalculate on the Task Master toolbar.

Task Master uses the specified Start Date and Duration and updates the task to have a Due Date of 10/17/2012 at 5:00 PM.

Return to Task Master Task Assignments

Start Date and Work

Return to Task Assignments

Assign tasks using Start Date and Work if you know how much work is required to complete the task and when your resource can start working on the task. You can only use this option if the task is assigned to a resource in the Assigned To column.

You have two other options:

Start Date and Due Date (the default option)
Start Date and Duration

These options give you more flexibility when assigning tasks and building schedules. They are located in the tool pane under Dependency Settings.

Use Case

Richard has a task for Ashley. She can start the task on October 4, 2012, but can only work on the task half of the time because she has been assigned to another project as well. Ashley estimates that the task will take her 34 hours to complete.

Richard needs to create the task using a Start Date of 10/4/2012 at 8:00 AM
He sets the amount of Work 34 hours
The Assignment Units will be 50%.

In the tool pane under Working Hours Setting, Richard selects the Enforce these working hours option, chooses work hours as 8:00 AM to 5:00 PM and selects Exclude lunch time. He also excludes weekends from task scheduling.

Under Dependency Settings, Richard selects the Using Start Date and Work option and the Increase or decrease duration so task ends sooner or later but requires the same total work option.

Richard creates the task as shown below and then clicks Recalculate from the Task Master toolbar.

Task Master uses the specified Start Date and Work and updates the task to have a Due Date of 10/16/2012 at 12:00 PM.

Return to: Task Master Task Assignments

What Site Collection Features are associated with my Bamboo product?

For information about how to activate a SharePoint Site Collection Feature, see Activating a Bamboo Site Collection Feature. If you know how to activate, but just aren’t sure which site collection feature goes with which product, see the table below.

If you are wondering about Site Features, rather than Site Collection Features, see How to activate a Bamboo site feature.

Product	Site Collection Feature Name	Mandatory?
Alert Plus	Bamboo Alert Plus Web Part	Yes
Calendar Plus	Bamboo Calendar Plus Web Part	Yes
Chart Plus	Bamboo Chart Plus Web Part	Yes
Column Level Security	Bamboo Column Level Security Column	No
Community Central	Bamboo Community Central Add Blog Comment Web Part Bamboo Community Central Content Types Bamboo Community Central Reporting Web Parts Bamboo Community Central Search Result Bamboo Community Central Supporting Web Parts	Yes
Cross List	Bamboo Cross List Web Part	Yes
Cross Site Display	Bamboo Cross-Site Display Web Part	Yes
Custom Identifier Column	Bamboo Custom Identifier Column	No
Data-Viewer	Bamboo Data-Viewer Web Part	Yes
File Share Library	Bamboo File Share Library	Yes
Filters Collection	Bamboo SharePoint Filters	Yes
Grants Management	Bamboo Grant Master Site Template Bamboo Grant Project Site Template	Yes
Group Email	Bamboo Group Email Web Part	Yes
Group Redirect	Bamboo Group Redirect	Yes
Hello	Bamboo Hello Web Part	Yes
In/Out Schedule Board	Bamboo In and Out Schedule Board Bamboo Solutions – SharePoint In/Out Schedule (is this old?)	Yes
Knowledge Base	Bamboo KB Accelerator Reporting WebPart Bamboo KB Admin Site Template Bamboo KB Admin Site Template R2 Bamboo KB Client Site Template – Meeting Workspace Bamboo KB Client Site Template – Team Site Bamboo KB Client Site Template R2 Bamboo Knowledge Base Accelerator Bamboo SharePoint Secure Trim Web Part	see bolded
KPI Column	Bamboo KPI Column Bamboo KPI Column Display WebPart	see bolded
List Consolidator	Bamboo List Consolidator Web Part	Yes
List Print	Bamboo List Print	Yes
List Rollup	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	see bolded
List Rotator	Bamboo List Rotator Web Part	Yes
List Search	Bamboo List Search Advanced Web Part Bamboo List Search Simple Web Part	Yes
Lookup Selector Column	Bamboo Lookup Selector	No
Mini-Calendar	Bamboo Mini-Calendar Web Part	Yes
My Alerts Organizer	Bamboo My Alerts Organizer	Yes
Navigators	Bamboo Navigator Site Action Menu Bamboo Navigator Web Parts	Yes
Project Management Central	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.	see bolded
Poll	Bamboo Poll Admin Web Part Bamboo Poll Voting Web Part	Yes
Project Portfolio Dashboard	Bamboo Project Dashboard Data Mapping Bamboo Project Portfolio Dashboard	see bolded
Rating Column	Bamboo Rating Web Part	Yes
Rich Text Column	Bamboo Rich Text	No
Site Creation Plus	Bamboo Site Creation Plus	Yes
Task Master	Bamboo Task Master	Yes
Team Calendar	Bamboo Team Calendar	Yes
Time Tracking and Management	Bamboo Time Tracking and Management Reporting Web Part Bamboo Time Tracking and Management Site Template Bamboo Time Tracking and Management Web Parts	Yes
Tree View	Bamboo Tree View Web Part	Yes
User Account Setup	Bamboo User Account Setup Web Part	Yes
User Directory	Bamboo User Directory Web Part	Yes
User Profile Plus	Bamboo User Profile Plus	yes
User Redirect	Bamboo User Redirect	Yes
Validator Column	Bamboo Validator Column	Yes
Virtual Map View	Bamboo Virtual Map View Web Part	Yes
Visual Indicator Column	Bamboo Visual Indicator	Yes
Wiki Publisher	Bamboo SharePoint Wiki Publisher	Yes
Workflow Conductor	Bamboo Workflow Conductor Feature Manager Bamboo Workflow Conductor Studio Bamboo Workflow Conductor Web Parts Bamboo Workflow Conductor Widgets Bamboo.StartWorkFlow.wsp	see bolded
World Clock and Weather	Bamboo World Clock And Weather Web Part	Yes

Required Installation Permissions

The installation account must be a member of the local server Administrators group and have the db_owner role for the SharePoint configuration database.

To automatically activate site collection features during installation (optional), use an account that is also a SharePoint site collection administrator.

If the installation account is not a Site Collection Administrator for all site collections in a web application, then you should choose to not automatically activate the solution during the installation. Site Collection Administrators can activate the solution when they are ready to use it in their site collection.

How to modify a web.config file using PowerShell

Background

Some custom SharePoint products make changes to the web.config file of a web application via SPWebConfigModification calls in order to support particular features. There is a web.config file for each web application on your farm and they reside on each WFE server. If your farm has 3 WFE servers and 2 web applications, you have 6 web.config files.

For SharePoint 2010, Bamboo product installs may add entries to the web.confg to support Telerik functionality. Telerik is a 3rd party that provides some user interface controls for some Bamboo products. See Bamboo products that use Telerik for a list.
For SharePoint 2007, Bamboo product installs may add entries to the web.confg to support Telerik and AJAX functionality. We use AJAX to allow web applications to send data to, and retrieve data from, a server asynchronously (in the background) without interfering with the display and behavior of the existing page. See Bamboo products that use AJAX for more information.

At times, some of these changes need to be modified (via additions to the web.config), or partially removed for particular web applications on your SharePoint farm.

It is neither recommended nor a best practice to manually update a web.config file. Manual changes are not tracked by SharePoint in the configuration database; as such, they will likely cause future problems for users on the farm. For example, when creating a new web application, the new web.config is generated automatically by SharePoint and the auto-generated file will not include any changes that were made manually.

Resolution

Use PowerShell to programmatically remove or add web.config modifications so that changes are updated in the configuration database as well as on the server(s). An added benefit of making changes via PowerShell is that SharePoint will propagate the changes, so if you have 6 web.config files on your farm, you need to run the PowerShell script only once.

For more information, please see:

Release Notes for Task Master

NOTE: Release Notes will open in a new browser tab

WSSv3/MOSS	SharePoint 2010	SharePoint 2013	SharePoint 2016
Release Notes	Release Notes	Release Notes	Release Notes
Microsoft ended mainstream support for SharePoint 2007 in October 2012. See Microsoft’s Lifecycle Support Policy. At that time, Bamboo stopped enhancements to our SharePoint 2007 product line, but continues to provide support and bug fixes to customers with active support contracts until October 2017. Previously purchased licenses will continue to function after October 2017, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2007 products in October 2016 to ensure customers will be eligible to receive support for at least one year after purchase.	Microsoft plans to end mainstream support for SharePoint 2010 in October 2015. See Microsoft’s Lifecycle Support Policy. At that time, we will stop any enhancements for our SharePoint 2010 product line but will continue to provide support and bug fixes for our SharePoint 2010 products to customers with active support contracts until October 2020. Previously purchased licenses will continue to function after October 2020, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2010 products in October 2019 to ensure customers will be eligible to receive support for at least one year after purchase.	Visit our website where you can get the latest info about each of our products for SharePoint 2013. A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles: How to Migrate Your Bamboo Products to SharePoint 2013 How to Move Bamboo Product Licenses to SharePoint 2013	Bamboo Solutions has also begun releasing products for SharePoint 2016. For additional details, check the product release notes in the link above, or contact us. For details on migration, see the Knowledge Base Article “Migrate Bamboo Products from SharePoint 2013 to SharePoint 2016”

WSSv3/MOSS

SharePoint 2010

SharePoint 2013

SharePoint 2016

Release Notes

Microsoft ended mainstream support for SharePoint 2007 in October 2012. See Microsoft’s Lifecycle Support Policy.
At that time, Bamboo stopped enhancements to our SharePoint 2007 product line, but continues to provide support and bug fixes to customers with active support contracts until October 2017. Previously purchased licenses will continue to function after October 2017, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2007 products in October 2016 to ensure customers will be eligible to receive support for at least one year after purchase.

Microsoft plans to end mainstream support for SharePoint 2010 in October 2015. See Microsoft’s Lifecycle Support Policy. At that time, we will stop any enhancements for our SharePoint 2010 product line but will continue to provide support and bug fixes for our SharePoint 2010 products to customers with active support contracts until October 2020. Previously purchased licenses will continue to function after October 2020, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2010 products in October 2019 to ensure customers will be eligible to receive support for at least one year after purchase.

Visit our website where you can get the latest info about each of our products for SharePoint 2013.

A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles:

Bamboo Solutions has also begun releasing products for SharePoint 2016. For additional details, check the product release notes in the link above, or contact us.

For details on migration, see the Knowledge Base Article “Migrate Bamboo Products from SharePoint 2013 to SharePoint 2016”

Understanding Bamboo Releases:

Bamboo offers Trial, Basic and Premium support.
- Free Trial support expires after 30 days.
- For more information about Basic and Premium support, please see the Support Plans page.
- There may be a fee to upgrade from a major version to another.

See Also:

Best Practices for a successful install

Follow these guidelines to ensure a successful installation:

No.	Function
1.	Back up your system.
2.	Make sure that your system meets the requirements listed in the System_Requirements section.
3.	Installing PM Central, Community Central, Grants Management, or other applications may upgrade some Bamboo components previously installed in your SharePoint farm. For example, PM Central includes the Data Viewer Web Part (among other things) and installing PM Central may upgrade the Data Viewer Web Part that you may have previously installed. Before installing PM Central or another Bamboo application, make sure you understand the effect upgrading installed components will have on your existing solutions.
4.	Before installing, review information about where to run the Setup program in Location of Install Files and the Required Installation Permissions. This information is shown on the Installation/Setup program interface, but is also available from the links above.
5.	If you are upgrading an existing, installed product rather than installing it for the first time, read the information about Upgrading for the product you are interested in. The upgrade process is slightly different than installing for the first time.
6.	On all servers in the SharePoint farm where the solution will be deployed: Go to Start > Administrative Tools > Services and stop or restart the following services: Stop the World Wide Web Publishing Service on all servers. Do this step first because it prevents users from accessing sites during installation and files that may need to be updated from being locked. Note: If your SharePoint environment is configured for Claims Based Authentication or is running SharePoint 2013 or SharePoint 2016, you should NOT stop the World Wide Web Publishing Service if you wish to automatically activate product features during installation. Read SharePoint 2010 solution deployment when Claims Based Authentication is configured for more information. Restart the Microsoft SharePoint Foundation Timer service (called SharePoint Timer Service for SharePoint 2013 and 2016, SharePoint 2010 Timer service if you are using SharePoint 2010, or Windows SharePoint Services Timer service if you are using SharePoint 2007) on all servers. Do this step even if the service is currently running. It will ensure no files that may need updating are locked. Restart the Microsoft SharePoint Foundation Administration service (called SharePoint Administration in SharePoint 2013 and 2016, SharePoint 2010 Administration service if you are using SharePoint 2010, or Windows SharePoint Services Administration service if you are using SharePoint 2007) on all servers. Do this step even if the service is currently running. It will ensure no files that may need updating are locked.
7.	Review the Options for Installing.

Return to Installing for the first time

Overview of the Installation/Setup Program

Options for Installing

IMPORTANT: As of April 2017, Bamboo no longer includes the Installation/Setup Program in product download packages. Please see Overview of the Updated Installation Process for Bamboo components for details.

There are several areas of note in the Installation/Setup program interface, shown below.

No.	Function
1.	The Setup program contains links to various product components listed under the Components header on the left. Click on any of these links to view additional information about the component on the right. The product components fall into the following categories: Prerequisites: Some products include prerequisite components that must be installed before the Bamboo product core components. Not all products will have prerequisites. Examples of prerequisites include the Microsoft Exchange Web Services (EWS) Managed API, Shared Assemblies Library, Microsoft AJAX Extensions, and Bamboo AJAX Config. If you have more than one Bamboo product installed on your farm, some of the pre-requisites may already be installed. Core Components: The product will include one or more core components that are required for the Bamboo product to work. Optional Items: Optional items provide additional features or functionality but are not required to use the Bamboo product. Not all products will have optional items. Licensing: All products will include the Bamboo Web License Manager or Bamboo License Manager. Licensing is required to activate a product license. It is not required during 30-day product trials. If you have previously installed the Bamboo Web License Manager with another Bamboo product, it may not be necessary for you to install it again. Help: When clicking the Help component, you will see links for the Online Documentation and other product-related resources. Click the Home icon () at the top of the components list to return to the Setup main page.
2.	The Installation Location section will tell you where to run the Installation/Setup program for the selected component. Read this information carefully before proceeding.
3.	The Required Installation Permissions section will explain required permissions for the selected component. Read this information carefully before proceeding. If the person running the installation/setup doesn’t have the appropriate level of permission, the install will fail.
4.	When ready, click the Install button to begin the installation process. It will do a few system checks, ask you to agree to our End User License Agreement, ask which Web Applications you want to install to (you don’t have to pick any), and ask if you want to automatically activate the solution on the selected web apps. When the install is complete, it will display an Installation Summary that you should review carefully. See an example below.

Click here for information about running the installation or go back to Installing for the first time… topics.

Overview of the Updated Installation Process for Bamboo components

Options for Installing

In April 2017, with the Q1 Cumulative Update (CU) 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. The install package downloaded from My Bamboo is now a *.zip file rather than a self-extracting executable.

The installation process was updated based on feedback from our customers. We are excited about the benefits the new processes offer:

Benefits
The processes are now very transparent; you know exactly what happens during the install/upgrade/uninstall. If you want/need to modify the scripts for your farm, you can do that.
If you are upgrading to a new version of a Bamboo product or if a new install updates a shared component used by another Bamboo product installed previously, the installed solution is saved before the upgrade. If the new install fails, you can easily rollback to the previously installed solution.
Rather than deploying each solution individually, deployments are queued which minimizes farm disruption by reducing the IIS Resets on the farm.
By design, the scripts are written to be compatible with PowerShell versions found on an SP2010 WFE server. Written to use the features of the older version of PowerShell, the scripts are simple and should work the same in all environments. If you would prefer to employ some PowerShell features available in new versions (e.g., output results to the grid/table), you can modify the scripts to use the PowerShell features available in your environment.

Please note the following for the new scripts:

The script installs all the WSPs found in the installation folder, in alpha order
The install/upgrade script deploys to all content web apps. If you would prefer to deploy to a single web app, you can modify the script or deploy via Central Administration.
Uses Upgrade instead of Install for existing components.

For additional information about how to use the updated processes:

Overview of Task Master

SharePoint Task Master shows tasks and milestones hierarchically, with dependencies and related task information, in a task details grid and Gantt chart view. Display only the task information you choose, in the order and level of detail you need. Task data is stored in the Bamboo Project Task List or in a task list of your choice, anywhere in the SharePoint site collection.

To use SharePoint Task Master:

Step 1: Add the Web Part to a page and configure it.

Add the Bamboo Task Master Web Part to a page and open the tool pane to select a task list, set working hours and holidays, and define Gantt chart and grid view options.

Step 2: Add tasks.

To start adding tasks, click the New Item button and enter task information. Indicate whether the task is a Parent Task (i.e., Summary Task), has Predecessor Tasks that must be completed before this task can start, or has constraints like Start No Later Than or Must Start On a specific date.

Step 3: Manage tasks using the task grid and Gantt views.

In the Task Master Web Part, edit tasks, switch views (i.e., Day, Week, Month, Quarter or Year) or filter the tasks displayed by selecting a different task list view. Print the task details grid or Gantt chart, zoom the timescale in or out to view more or less task detail, show the critical path, and more.

Overview of Task Master Configuration

Click any of the topics linked below for details about configuring Task Master and to gain more knowledge about the various settings. There is a lot to consider when setting up Task Master; some of these topics may have sub-topics associated to them as well.

To start editing the settings for Task Master, add the web part to a page and edit the Web Part properties. Click the Task Master Settings button in the Web Part tool pane to display the Web Part Settings page.

NOTE: You must disable pop-up blockers for the site to display the web part Settings page.

Configuring Task Master

Task Master Preferences – Configure general settings and select a language.
Data Source Settings – Configure one of two data source types:
- Configure a SharePoint List or Library
- Configure Bamboo List Rollup Settings
Task Master Schedule and Calculation Settings – Configure schedule and holiday list settings.
Task Master View Settings – Configure view settings including columns, color coding, progress bar, milestone, and Gantt settings.
Configure Working Hours – Define specific workdays, exclude holidays, or enforce working hours for tasks.
WBS Level Format Settings – Format the display properties for a Work Breakdown Structure (WBS) level.
About the Bamboo Project Task List – List that is automatically created when you add Task Master to a page.
Task Master Task Assignments – Calculate tasks based on time, work or duration.
Task Master Dependency Settings – Establish dependencies within Task Master settings.
Task Master Multiple Predecessors – Allow multiple predecessor tasks.
Task Master Custom Task Identifier – Configure an automatically generated task ID.
Localizing Task Master – Overview of the process to localize Bamboo products.

Overview of Licensing and Product Activation

When to Activate

After you purchase, you receive License Keys to use to activate the product license on each WFE server on your farm. License Keys never expire. See How many License Keys do I need for my SharePoint farm for more information. You can use a license key on only one server at a time. Servers in non-production (i.e., Staging, Test, Dev) farms require licenses too, just like servers in your production farm.

Activating a Standard Product License

For most Bamboo products, license keys are required for each WFE server in the SharePoint Farm. For certain products, such as Alert Plus or List Rollup, additional license keys may be required for application servers as well to use certain features. See Activating Your Bamboo Product License

Suites, Packs, Libraries, and Toolkits

For Bamboo Suites, Packs, Libraries and Toolkits, a single license activates all the products in the suite or pack for a specific WFE server. See Overview of Suite or Pack Licensing.

Keyless Licensing

On very large farms with several Bamboo products installed, it is often difficult to manage so many license keys. Bamboo offers keyless licensing for these scenarios. Please contact your Sales Manager for more information about keyless licensing.

Use the Bamboo Web License Manager to activate Bamboo products install on the SharePoint farm. For additional details, please see

Installing the Bamboo Web License Manager
Activating Your Bamboo Product License
Activating My Bamboo Product License Offline if your server doesn’t have access to the Internet.

Desktop Applications

Some Bamboo products are not installed on the SharePoint farm, but on a PC or server somewhere on your network. To activate the license for these products, please see Activating a Bamboo Desktop Product Using the License Manager.

Moving or Migrating your farm

If you are moving your SharePoint farm to new servers, please see Migrating my Bamboo Product License to a New Server. Licenses are activated to a particular hardware profile of the server. If the profile changes (i.e., you add a hard drive), the license will require migration.

If you have migrated your environment to a new SharePoint version (i.e., from SharePoint 201 to SharePoint 2013), see Migrate your Bamboo Product License Key From one SharePoint version to another. License keys for products running in different SharePoint versions are different. On-Prem Bamboo products on active support are eligible for no-cost upgrades to a newer SharePoint version (2016/2019/2022) as long as the two farms are not running concurrently for more than 60 days. Migrations to Microsoft 365 will require the purchase of new licenses. However, we do offer a discount for customers on current support for an on-premise product that has a Microsoft 365 equivalent

Trials

For product trials, no license is required. If you are wondering about the status of your trial or when it will expire, please see

Overview of Bamboo Product Trials

Overview of Licensing and and Product Activation

Try our products before you buy!

Trials are fully functional for 30 days from the date of installation.
Once a 30 day trial of a product has been installed on a server or farm, no further trial copies of the same product will function on the server or farm. When a product license key is purchased and activated (even after the trial has expired), the product will continue to work as it did during the trial.
Users who need additional time to evaluate a product will need to request a trial extension from their Bamboo Sales Account Manager (sales@bamboosolution.com).
There is no functional difference between the trial and purchased version of our products, with the exception of List Bulk Import and List Bulk Export. When a trial user purchases a license, it is not necessary to install a new version to replace the trial. You simply activate the license of the “trial” copy. Any configuration done on the product during the trial period will remain after the license is activated.
The List Bulk Import and the List Bulk Export product trials are limited in the number of items that can be imported/exported. Regardless of the number of items in an import file or in a SharePoint List/Library, only 15 items will be imported/exported with the trial version of these products. Once the license is activated, this restriction is lifted.

Overview of the new Bamboo product Logging

In April 2017, Bamboo released Bamboo.Logging v3.1.0.0 with the Q1 (2017) Cumulative Update of Bamboo component products.

In response to customer feedback the new logging version uses SharePoint ULS logs by default, instead of the the Bamboo logs. The main benefits of this change are:

Bamboo Log files will not fill the C: drive on WFE servers. Previously, Bamboo products reported errors to proprietary log files located in C:WindowsTempBambooSolutions on each web front end server in the farm as described in Error Log Files.
SharePoint administrators are very familiar with ULS logs and the ULS Log Viewer. When Bamboo products log to ULS, SharePoint administrators have one less set of logs to review.
ULS log files can be more easily managed for size and archived, a feature that was not previously available for Bamboo logs.

Bamboo component products installed or upgraded after April 2017 will have the new Bamboo Logging deployed as part of the Bamboo.Framework.wsp solution, which is common to Bamboo products and globally deployed to the SharePoint farm.

IMPORTANT:
1) If you have multiple Bamboo products installed on your farm, some Bamboo log files may remain in C:/Windows/Temp/BambooSolutions until you upgrade all of the Bamboo products.
2) Bamboo applications (e.g., PM Central, Workflow Conductor, In/Out Schedule Board) will not have the new Bamboo Logging until their respective CU’s are available in Q2 2017.

Please note the following for the new scripts:

The script installs all the WSPs found in the installation folder, in alpha order
The install/upgrade script deploys to all content web apps. If you would prefer to deploy to a single web app, you can modify the script or deploy via Central Administration.
Uses Upgrade instead of Install for existing components.

For additional information about how to use the updated processes:

Installing using the updated install process
Upgrading using the updated process
Uninstalling using the updated process

My product was licensed yesterday and today there is an error; what happened?

License keys are tied to the hardware GUID of the WFE server and if the GUID changes, the license will revert to the trial status. You will need to deactivate the license key and then re-activate the license using the same key.

GUIDs may change when a WFE server is dropped from a farm and then re-added.

IMPORTANT: For products licensed with the Bamboo License Manager (rather than the Web License Manager), the license key is tied to the hardware profile of the PC where the product is installed. If the hardware profile changes (i.e., a hard drive is added), the license will revert to the trial status. You will need to deactivate it and then re-activate it using the original license key. Products that use the Bamboo License Manager include: List Bulk Import, List Bulk Export, and User Profile Sync.

The problem is that the license status will no longer show the license key once the GUID changes, it will show as an expired trial license. See Is there a way to find a lost or unknown Bamboo product license key and then How to move your Bamboo Product License to a new server to resolve this issue.

Overview of moving a Bamboo Product License

To move a license, you need to deactivate the license key for the old server so you can activate it on the new server. A license key can be used on only one server at a time.

If the WFE servers in your SharePoint farm have access to the Internet, see How to move your Bamboo Product License to a new server.
If your WFE servers do not have Internet access, you will need to deactivate the license key via My Bamboo. See How to deactivate your Bamboo Product License is your server doesn’t have access to the Internet.

Migrating Task Master from SharePoint 2010 to SharePoint 2013

Be sure you have at least the Minimum SharePoint 2010 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2013 farm requires at least the Minimum SharePoint 2013 product release shown.

IMPORTANT: When migrating from SharePoint 2010 to SharePoint 2013, the Database Attach Upgrade Method is the only method supported.

Minimum SharePoint 2010 Product Release	30.5.117	Minimum SharePoint 2013 Product Release	30.5.118.2013

Database Attach Upgrade Method
Issues	The Task Master migrates without any errors or additional steps required.
Resolution	N/A

Migrating Task Master from SharePoint 2007 to SharePoint 2010

Be sure you have at least the Minimum SharePoint 2007 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2010 farm requires at least the Minimum SharePoint 2010 product release shown.

IMPORTANT: When migrating from SharePoint 2007 to SharePoint 2010, you MUST select the option to change existing SharePoint sites to use the new user experience. Your Bamboo products will not perform as expected with the old look and feel.

Minimum SharePoint 2007 Product Release	2.0.150	Minimum SharePoint 2010 Product Release	20.0.34

In-Place Upgrade
Issues	The Task Master Web Part migrates without any errors or additional steps required.
Resolution	N/A
Database Attach Upgrade Method
Issues	The Task Master Web Part migrates without any errors or additional steps required.
Resolution	N/A

Migrate your Bamboo Product License Key From one SharePoint version to another

Overview of Licensing and and Product Activation

Bamboo Solutions completed its migration of more than 60 Bamboo products to SharePoint 2013 I the fall of 2013. A few years earlier, we completed the migration of many of those same products from SharePoint 2007 to SharePoint 2010.

Bamboo License Keys for previous versions of SharePoint are not valid for newer versions. If eligible, you can retrieve license keys for newer SharePoint versions through the My Bamboo area of the Bamboo Solutions web site.

When you activate product license keys for a newer SharePoint version, the keys for the older version become invalid after 60 days.

Bamboo Policy for Migrating License Keys

To receive a free SharePoint 2010 or SharePoint 2013 license key, you must have a valid Premium Support Contract for the product you are migrating to SharePoint 2010 or SharePoint 2013.

We support a 1:1 exchange of license keys. If your SharePoint 2007 farm had two WFE servers and your SharePoint 2010 farm has four WFE servers, you will need to purchase two additional SharePoint 2010 license keys. The same requirement holds for SharePoint 2010 farms you are migrating to SharePoint 2013.

How to get your new license keys

If you have a valid Premium Support Contract for the product you intend to migrate, follow these steps:

Step	Action
1.	Login to My Bamboo with the Bamboo account that made the original SharePoint 2007 Bamboo license key purchase or an account that can see the purchases.
2.	Click My Orders Product Licenses under the sectionlocated at the bottom of the page.
3.	On the Product Licenses tab of the My Orders page, each product purchased is listed. If an update is available, a Request SP 2013 License button is displayed in the Update Keys column. Click the button for the product you want to migrate. NOTES: 1. The Request SP 2010/2013 License button will not be available unless a Premium Support Contract is in place. 2. If you see something you think is wrong with your Product License listing, please contact your Bamboo Sales Representative at Sales@Bamboosolutions.com
4.	An order will be created automatically and you will be redirected to the order completion page, where you can retrieve the installation package. You will also receive an e-mail that provides you the link to the download package and your SharePoint 2013 License Keys. NOTE: If the text Not Available is displayed, this means either you do not have an active Premium Support contract or there is no SharePoint 2010 version of that product. Please contact your Sales Representative at Sales@bamboosolutions.com for additional assistance. For information about migrating the product, see these topics.

Migrate your Bamboo product from SharePoint 2010 to SharePoint 2013

Overview

This article outlines how to migrate Bamboo products from SharePoint 2010 to SharePoint 2013 (SharePoint Foundation 2013 & SharePoint Server 2013).

NOTE: In order to migrate a Bamboo product to SharePoint 2103 from a SharePoint 2010 environment, you need to ensure that the SharePoint 2010 farm has the appropriate version installed. If your Bamboo product version is older, you may need to upgrade the SharePoint 2010 version before migrating to SharePoint 2013. Please refer to information about the specific products that are installed on the farm you are migrating for possible additional steps needed or limitations of the migration (including whether the product is supported on SharePoint 2013 with the SharePoint 2010 look and feel).

For additional information about upgrading your existing SharePoint 2010 Farm to SharePoint 2013, read these TechNet articles:

Bamboo Solutions supports the Database Attach upgrade method for upgrading to SharePoint 2013. The migration of Bamboo products deployed on SharePoint 2007 environments directly to SharePoint 2013 Farms is not supported. These environments must be migrated to SharePoint 2010 first. Bamboo also does not support the downgrade of SharePoint editions during a migration. (i.e., SharePoint Server 2010 to SharePoint Foundation 2013)

Migration Steps

Step	Description
1.	Before migrating, update the Bamboo products you have in SharePoint 2010 to the latest available release.
2.	Uninstall any products that are not available on SharePoint 2013. Cross List is an example of a product that was not ported to SharePoint 2013. If you do not remove the Bamboo Cross List from the SharePoint 2010 farm before migrating, the migration will fail because the feature will not be available in the SharePoint 2013 farm.
3.	Retrieve the SharePoint 2013 installation package and license keys for the Bamboo products you are migrating. See Migrate your Bamboo Product License Key From one SharePoint version to another for additional details. Install the Bamboo products on the SharePoint 2013 farm.
4.	Backup the SharePoint 2010 content database and attach it to the SharePoint 2013 farm. If the database attach fails, see steps 1-3 above. IMPORTANT: Follow Microsoft’s Upgrade databases from SharePoint 2010 to SharePoint 2013 article to perform the database-attach migration.
5.	After the 2010 content databases have been successfully attached and upgraded to SharePoint 2013, you MUST retract and redeploy (or uninstall and reinstall) your Bamboo SharePoint 2013 products on the SharePoint 2013 farm. This process removes the SharePoint 2010 Web Part references and replaces them with SharePoint 2013 references in the newly attached content databases. This is not a Bamboo specific step. It must be performed for most 3rd party SharePoint software installations. If this step is skipped users will usually see errors when adding web parts to pages. IMPORTANT: If you have a staged migration that moves content databases in stages, you need to retract and re-deploy after each database (or group of databases are attached.
6.	Perform the permanent Visual Upgrade to upgrade your SharePoint 2010 site collections to the SharePoint 2013 Look and Feel. IMPORTANT: Bamboo does not support our SharePoint 2013 products running on a SharePoint 2013 server using the SharePoint 2010 Look and Feel.

Migrate your Bamboo product from SharePoint 2013 to SharePoint 2016

Overview

This article outlines how to migrate Bamboo products from SharePoint 2013 to SharePoint 2016.

NOTE: In order to migrate a Bamboo product to SharePoint 2106 from a SharePoint 2013 environment, you need to ensure that the SharePoint 2013 farm has the appropriate version installed. If your Bamboo product version is older, you may need to upgrade the SharePoint 2013 version before migrating to SharePoint 2016. Please refer to information about the specific products that are installed on the farm you are migrating for possible additional steps needed or limitations of the migration.

For additional information about upgrading your existing SharePoint 2013 Farm to SharePoint 2016, read these TechNet articles:

Bamboo Solutions supports the Database Attach upgrade method for upgrading to SharePoint 2016. The migration of Bamboo products deployed on SharePoint 2007 or SharePoint 2010 environments directly to SharePoint 2016 Farms is not supported. These environments must be migrated to SharePoint 2013 first.

Migration Steps

Step	Description
1.	Before migrating, update the Bamboo products you have in SharePoint 2013 to the latest available release.
2.	Uninstall any products that are not available on SharePoint 2016. Group Email is an example of a product that was not ported to SharePoint 2016. If you do not remove the Bamboo Group Email from the SharePoint 2013 farm before migrating, the migration will fail because the feature will not be available in the SharePoint 2016 farm.
3.	Retrieve the SharePoint 2016 installation package and license keys for the Bamboo products you are migrating. See Migrate your Bamboo Product License Key From one SharePoint version to another for additional details. Install the Bamboo products on the SharePoint 2016 farm.
4.	Backup the SharePoint 2013 content database(s) and attach it to the SharePoint 2016 farm. If the database attach fails, see steps 1-3 above. IMPORTANT: Follow Microsoft’s Upgrade databases from SharePoint 2013 to SharePoint 2016 article to perform the database-attach migration.
5.	After the 2013 content databases have been successfully attached and upgraded to SharePoint 2016, you MUST retract and redeploy (or uninstall and reinstall) your Bamboo SharePoint 2016 products on the SharePoint 2016 farm. This process removes the SharePoint 2013 Web Part references and replaces them with SharePoint 2016 references in the newly attached content databases. This is not a Bamboo specific step. It must be performed for most 3rd party SharePoint software installations. If this step is skipped users will usually see errors when adding web parts to pages. IMPORTANT: If you have a staged migration that moves content databases in stages, you need to retract and re-deploy after each database (or group of databases are attached.