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:
||Version deployed for SP2013/SP2016
||Version deployed for SP2010
(previously, version 2012.3.1016.35 was deployed)
(previously, version 2011.2.915.35 was deployed)
(previously, version 2012.3.1016.35 was deployed)
(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.
<assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" culture="neutral" />
<bindingRedirect oldVersion="2012.3.1016.35" newVersion="2016.3.1027.45" />
Best Practices for a successful install
Follow these guidelines to ensure a successful installation:
||Back up your system.
||Make sure that your system meets the requirements listed in the System_Requirements section.
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.
||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.
||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.
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.
||Review the Options for Installing.
Return to Installing for the first time
Overview of the new Bamboo product Logging
In April 2017, Bamboo released Bamboo.Logging v184.108.40.206 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.
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
Location of Installation
IMPORTANT: As of April 2017, Bamboo has changed the installation process for Bamboo components. The Setup Program has been replaced by an updated process. Please see Overview of the Updated Installation Process for Bamboo components and Uninstalling using the updated process for details.
If you are installing a Bamboo product in a SharePoint farm environment, make sure to start the installation on the correct server. The required installation location is listed in the Setup/Installation program interface in the description for each component. See Overview of the Setup Program from more information.
Most Bamboo products are installed on a farm server running the Microsoft SharePoint Foundation Web Application service (or the Windows SharePoint Services Web Application if you are using SharePoint 2007), but some are installed on a farm server running the Central Administration service. Refer to SharePoint Central Administration -> System Settings -> Servers -> Manage servers on this farm for a list of farm servers running these services. If you are using SharePoint 2007, find the list of farm servers in Central Administration > Operations > Servers in Farm.
During the install process, the component will be automatically deployed to all Web front-end servers by the SharePoint Timer service via SharePoint Solution Deployment. There is no need to run the Setup/Installation program on more than one server in the farm.
Refer to Required Installation Permissions for information about the level of permission the installation account requires.
Essentials Suite Highlights
With over 20 components and tools, Essentials Suite gives you instant access to critical functionality missing from out-of-the-box SharePoint. With the power of Essentials Suite, you’re just a few clicks away from the instant data aggregation, visualization, and user/file management you’ll need to get real work done in SharePoint. We’ve designed Essentials Suite to meet the most urgent needs of real-world SharePoint users. With instant access to color-coded calendars, alert management, and a wide range of custom, purpose-driven list columns, site owners and end users alike will discover entirely new ways to take full advantage of your SharePoint infrastructure.
Essentials Suite Releases
NOTE: Release Notes will open in a new browser tab
|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.
Bamboo Solutions has also begun releasing Bamboo Apps to the SharePoint Store, for additional details, see the SharePoint Apps & Mobile products page where you can get the latest info about each of our Apps as they release to the Microsoft Store.
A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles:
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.
Complementary Products for Essentials Suite
You will find many of our products complement each other quite nicely saving you the time and trouble to write custom code. With Bamboo at the heart of your SharePoint investment, you gain access to a huge catalog of enhancements, components, and accessories that add the critical functionality your business requires.
The same components can be easily used in future applications and they all come from a single, trusted vendor, ensuring an easy purchase process and support you can count on. That’s the Bamboo Way!
Before you uninstall
IMPORTANT: Before you uninstall a Bamboo product, make sure that it is no longer in use on any site in your farm. If a web part resides on a page and you uninstall the web part, an error will be displayed for users that visit that page. The uninstall process does not update individual pages in your SharePoint portal.
Also, if you uninstall Workflow Conductor (WFC) and some workflows built with WFC are still active, those workflows will fail.
You have several choices for how to uninstall your Bamboo product:
|Use the Updated Uninstall Process for Bamboo components
Based on feedback from our customers, Bamboo introduced updated install/uninstall processes for component products (web parts). Instead of the Setup.exe Installation Application, we now supply two PowerShell scripts – one for Install/Upgrade and the other for Uninstall – to be used to install, upgrade, or uninstall the product.
For more information, see Overview of the Updated Installation Process for Bamboo components.
|Bamboo Installation Package
IMPORTANT: As of April 2017, Bamboo no longer includes the Installation/Setup program in product download packages.
You can use the Bamboo product installation package that you used to install the product to uninstall. This is the preferred method, because it performs some automated system checks to help ensure the uninstall will be successful. It also steps you through each component, so its easier to make sure everything is uninstalled. See Using the Setup program to Uninstall for more information.
|SharePoint Central Administration
||Many Bamboo products are deployed as SharePoint solutions, so you can retract and remove them from Central Administration. See Uininstalling from SharePoint Central Administration for more information.
||Some Bamboo products are packaged with a PowerShell script that you can use to uninstall. See Manually uninstall using PowerShell for more information.
||If you prefer, you can use stsadm commands to retract and delete Bamboo SharePoint solutions. See Manually uninstall using stsadm for more information.
||Some Bamboo products include components that are installed using an EXE or MSI installer. See Uninstalling a Bamboo .msi or .exe for more information.
Depending on the uninstall method you choose, there may be a solution left behind after the install. This is intentional, as several Bamboo products use some of the same components. See What is left behind after uninstalling? for more information and steps for how to uninstall completely.
About the Installation Files
When you extract the product EXE to a location on your SharePoint server, several folders are created that contain installation files and Setup program configuration files. The root level of the extracted file system includes the file Setup.bat, which launches the Setup program. The list below shows the installation files for the Tree View Web Part, as an example.
For manual installation, you will access the following folders that contain installation files:
- Component.wsp: There may be several folders with names ending in .wsp, depending on your product. Each WSP folder contains the installation files for a specific SharePoint Solution. One or more SharePoint Solutions may be installed for each product component.
- docs: Contains the Installation and Licensing Quick Start Guide.
- misc: The MISC folder includes miscellaneous files, including PowerShell scripts for manually installing or uninstalling the product.
- msi: If a MSI folder exists for your product, it could contain multiple files ending in .msi. Each is an installation executable. Some MSI installers in the msi installation folder have both a 32-bit and a 64-bit version. The 64-bit version will include .x64 in the file name. Run the version of the MSI that is appropriate for your operating system. Do not install both.
- res: Contains files required by the Setup program but not necessarily needed during a manual install.