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.

Modifying the PMC Message Configuration web part

PMC's portfolio warning message
The message displayed in the PMC Message Configuration Web Part, found on the home pages of the Portfolio and Project sites, is tied to mandatory items in the site’s Configuration Checklist.

When working with the PMC Message Configuration Web Part, keep in mind:

When there are Open items with a Mandatory priority in the Configuration Checklist the web parts Warning Message will be displayed.
When all mandatory items have been marked Completed the web part will display the Completed text.
The message text found on the home page of Department sites is not displayed with the PMC Message Configuration web part and cannot be modified.

Step	Action
1.	Click Edit Page in the ribbon on the site’s home page
2.	From the PMC Message Configuration Web Part click Edit Web Part. Prior to PMC 4.3 this web part was called the Bamboo Project Central Configuration Warning Message Web Part.
3.	Expand the Warning Configuration section in the tool pane.
4.	Click the desired text field, then click the ellipsis to open the text editor.
5.	Make the desired edits and click OK to close the pop up window.
6.	Click OK to save your changes and close the configuration tool pane.

Migrating PM Central 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	40.1.135	Minimum SharePoint 2013 Product Release	40.1.109.2013

Database Attach Upgrade Method
Issues	The Project Management Central migrates without any errors or additional steps required, except it does not support the SP2010 Look and Feel. You must convert your SP2013 PMC sites to the SP2013 Look and Feel.
Resolution	N/A

Migrating PM Central fromSharePoint 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.1.12	Minimum SharePoint 2010 Product Release	20.1.12

In-Place Upgrade
Issues	Project Management Central migration is not supported through this upgrade method.
Resolution	N/A
Database Attach Upgrade Method
Issues	Project Management Central migrates with limitations and some additional steps required. To view the additional steps and the limitations for migrating PM Central, please see the following KB Article
Resolution	To view the additional steps and the limitations for migrating PM Central, please see the following KB Article

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.

Manually Install using PowerShell

Options for Installing

IMPORTANT: As of April 2017, Bamboo no longer includes ManualInstallation.ps1 or DisableAllBambooTimerJobDefinitions.bat 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.

Perform the actions below to manually install or repair a product.

NOTE: Pay close attention to where a command should be run. Some commands must be run on either ONE or ALL Web front-end servers (WFE). A WFE is a server running the Microsoft SharePoint Foundation Web Application service. Refer to the System Settings > Manage Servers on this farm page in Central Administration for a list of servers running this service.

Step	Action
1.	Shut down the application pools for each Web application where you are installing the product. This will prevent other users from accessing sites and locking files that the installation script needs to update. NOTE: If you are using SharePoint 2010 and not Claims Based Authentication (CBA), instead of shutting down the app pools, you can stop the World Wide Web Publishing Service to prevent users from accessing sites and locking files. You should NOT stop the WWW Publishing service in SP2013 or in a CBA environment.
2.	On one Web front-end server (WFE), run the product .EXE file to extract its installation files. Browse to the misc folder. NOTE: If you do not see the misc folder or a file called ManualInstallation in this folder, your Bamboo product does not support this type of install.
3.	Right-click on the file DisableAllBambooTimerJobDefinitions.bat and choose Run as administrator. This script stops the timer job services for all Bamboo products installed on the farm, helping to put the farm in a quiescent state for the install. NOTE: If this script is not present in the misc folder for your Bamboo product, skip this step.
4.	On all WFE servers in the farm, perform the following actions: Run the command iisreset. Restart the SharePoint 2013 Timer (or SharePoint 2010) service.
5.	On the WFE where you extracted the product folders, right-click on the PowerShell application in the Start menu and choose Run as administrator. You can use Windows PowerShell or SharePoint 2013 Management Shell.
6.	Change to the misc folder in the extracted product installation files and enter the following command to start the manual installation script: `.ManualInstallation.ps1`
7.	When prompted, enter the Web application URL and choose whether you want to automatically activate the product features in the site collection(s). NOTE: To allow the installation script to run without prompting for input, edit the miscManualInstallation.ps1 script file and replace Read-Host with the highlighted text shown below: The script file installs Bamboo.Core.V2.wsp and Bamboo.Logging.V2.wsp, if they are not already in the solution store, and any required product components.
8.	Return to the misc folder. Right-click on EnableAllBambooTimerJobDefinitions.bat and choose Run as administrator. This enables all Bamboo timer job services. NOTE: If this script is not present in the misc folder for your Bamboo product, skip this step.
9.	Re-start the Application pools.
10.	Manually Activate the Product Feature(s) in the appropriate Site Collection(s) If you didn’t choose to activate site collection features automatically in step 7 above, don’t forget to activate those features in the site collections where you want to use them. After a Bamboo product solution is deployed to a Web Application, it’s feature(s) must be activated in the site collection before it can be used. When you are ready to activate the site collection feature, please see Activating a Bamboo Site Collection Feature. NOTE: You must be a Site Collection Administrator to activate site collection features.

Manually Install using stsadm

Options for Installing

These instructions use the stsadm.exe command, which can be found in the following location:

SharePoint 2007: %PROGRAMFILES%Common FilesMicrosoft SharedWeb Server Extensions12BIN
SharePoint 2010: %PROGRAMFILES%Common FilesMicrosoft SharedWeb Server Extensions14BIN
SharePoint 2013: %PROGRAMFILES%Common FilesMicrosoft SharedWeb Server Extensions15BIN

NOTE: Your product may include several SharePoint solutions in multiple [Component].wsp installation folders. Follow all steps for each solution to install the product for the first time.

Step	Description
1.	Review Best practices_for_a_successful_intstall to learn which servers to install on and what services to stop or restart.
2.	Add the solution to the SharePoint solution store. Run this command on the appropriate server in your farm and be sure you are running the command with an account that is a member of the local server Administrators group. The appropriate servers are typically those running the Foundation Web Application service or the Microsoft SharePoint Foundation Web Application service (or Windows SharePoint Services Web Application if you are using SharePoint 2007). Refer to Location of Install Files for more information. `stsadm.exe -o addsolution -filename [path][Component].wspcab[Component].wsp` where: [path] – the path to the extracted installation folders [Component] – the name of the component you are installing, as shown in the installation folder. The name of the component in the cab sub-folder may be slightly different than the installation folder name.
3.	Deploy the SharePoint solution. After adding the solution to the SharePoint solution store on your farm, it must be deployed to one or more Web Applications. This can be accomplished via Central Administration (see Deploying a Bamboo solution to a new Web Application for more information) or by running one of the following commands on the same server where you added the solution in Step 1 above. To deploy to a specific Web Application, run this command: `stsadm.exe -o deploysolution -name [Component].wsp -immediate -url [http://WebApplicationUri:portNumber] -allowGacDeployment -allowCasPolicies` where: [Component] – the name of the component you installed, as shown in the cab installation sub-folder [http://WebApplicationUri:portNumber] – the URL and Port for the target Web Application. Repeat this command for each web app you need to deploy to. OR To deploy to all Web applications EXCEPT the Central Administration Web application, run this command: `stsadm.exe -o deploysolution -name [Component].wsp -immediate -allcontenturls -allowGacDeployment -allowCasPolicies` where: [Component] – the name of the component you installed, as shown in the cab installation sub-folder
4.	Execute the deployment job(s). This is an optional step. The SharePoint Timer job will take care of the deployment eventually, but if you don’t want to wait for it, you can run this command. NOTE: This command needs to be run on every server on the farm that runs the Foundation Web Application service (or the Windows SharePoint Services Web Application service if you are using SharePoint 2007): `stsadm.exe -o execadmsvcjobs`
5.	Manually Activate the Product Feature(s) in the appropriate Site Collection After the Bamboo product solution is deployed to a Web Application, it must be activated in the site collection before it can be used. When you are ready to activate the site collection feature, please see Activating a Bamboo Site Collection Feature. NOTE: You must be a Site Collection Administrator to activate site collection features.

Manually uninstall using stsadm

A single Bamboo product may include a combination of one or more SharePoint solutions (WSPs) and components installed using an MSI installer. Refer to the original installation files from your product for information about the components that may have been installed.

To manually uninstall a Bamboo SharePoint solution, follow the steps below. If you need to uninstall a component that was installed using an MSI installed, see Manually Uninstalling a Bamboo .msi.

NOTE: The steps in these instructions use the stsadm.exe command, which can be found in the BIN folder of the 12/14/15 hive of a SharePoint server. For example, on a SharePoint 2010 farm, that would be %PROGRAMFILES%Common FilesMicrosoft SharedWeb Server Extensions14BIN

NOTE: You can also retract and remove a SharePoint solution from SharePoint Central Administration. To uninstall your Bamboo product this way, see Uninstalling from SharePoint Central Admin.

Step	Action
1.	Locate your stsadm.exe command utility. These instructions use the stsadm.exe command, which can be found in the BIN folder of the 12/14/15 hive of a SharePoint server. For example, on a SharePoint 2010 farm, that would be %PROGRAMFILES%Common FilesMicrosoft SharedWeb Server Extensions14BIN
2.	Schedule the solution Retraction. You can schedule the solution to be retracted from one web application at a time: `stsadm.exe -o retractsolution -name [Component].wsp -immediate -url [http://WebApplicationUri:Port]` or from all web applications at once: `stsadm.exe -o retractsolution -name [Component].wsp -immediate -allcontenturls` Where: [Component] is the name of the installed component (i.e., Bamboo.TreeView.wsp), as shown in the cab installation sub-folder or in the list of solutions in the Manage Farm Solutions page of SharePoint Central Administration. [http://WebApplicationUri:portNumber] is the URL and Port for the web application where the solution is installed.
3.	Execute the solution retraction. NOTE: This command needs to be run on each Web front-end (WFE) server in the farm. `stsadm.exe -o execadmsvcjobs`
4.	Remove the solution. Delete the solution from the SharePoint solution store only AFTER the retraction job is complete. `stsadm.exe -o deletesolution -name [Component].wsp` Where: [Component] is the name of the installed component (i.e., Bamboo.TreeView.wsp), as shown in the cab installation sub-folder or in the list of solutions in the Manage Farm Solutions page of SharePoint Central Administration.
5.	Repeat steps 2-4 for each solution included in the product. NOTE: There are two solutions that are common across multiple Bamboo products. They are: Bamboo AJAX Config (SP2007 only) and Bamboo Core. Do NOT uninstall them unless you are sure there are no other Bamboo products remaining on your farm. If there are no other Bamboo products on your farm, uninstall these two solutions last.

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.

CA-Manage Servers on this farm.png
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.

Localize Bamboo Web Parts for your Language

Overview of the localization process for Bamboo Products

Applies to:

All Bamboo Web Part components
Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007
SharePoint Foundation 2010 and SharePoint Server 2010
SharePoint Foundation 2013 and SharePoint Server 2013

Bamboo products can be configured to display product menus, user interface text, and settings in your local language. You can also customize the default text provided with the product. To change the language or text a product displays, perform the steps described in this page. Click a link below for detailed information about each step.

About the Language Files
Editing Text in Language Files
Selecting a New Language File for a Product

Top

About the Language Files

There are four language files included with Bamboo products. Their name and location may differ by product.

Setting	Older Products	Newer Products
Web Part Language Settings		Newer products will show the language choices in the Web Part settings using the abbreviated [language]-[COUNTRY] format (e.g. “en-US”)
Language File Names	1033.English.xml (the default) 1031.German.xml 1034.Spanish.xml 1036.French.xml	Bamboo.[Product].en-US.resx (the default) Bamboo.[Product].de-DE.resx Bamboo.[Product].es-ES.resx Bamboo.[Product].fr-FR.resx
Language File Location	These files are located in the wpresources folder. This folder and its associated language files may be located under one of the following paths on each SharePoint server: servernamedriveInetpubwwwrootwss VirtualDirectoriesportwpresources[Product] servernamedriveInetpubwwwrootwss VirtualDirectoriesportwpresources[Product] LanguageFiles servernamedriveProgram FilesCommon FilesMicrosoft Sharedweb server extensionswpresources[Product]	Depending on your version of SharePoint, your localization files may be found in the following locations. servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions15CONFIGAdminResources (SharePoint 2013) servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions14CONFIGAdminResources (SharePoint 2010)

Setting

Older Products

Newer Products

Web Part Language Settings

Newer products will show the language choices in the Web Part settings using the abbreviated [language]-[COUNTRY] format (e.g. “en-US”)

Language File Names

1033.English.xml (the default)
1031.German.xml
1034.Spanish.xml
1036.French.xml

Bamboo.[Product].en-US.resx (the default)
Bamboo.[Product].de-DE.resx
Bamboo.[Product].es-ES.resx
Bamboo.[Product].fr-FR.resx

Language File Location

These files are located in the wpresources folder. This folder and its associated language files may be located under one of the following paths on each SharePoint server:

servernamedriveInetpubwwwrootwss
VirtualDirectoriesportwpresources[Product]
servernamedriveInetpubwwwrootwss
VirtualDirectoriesportwpresources[Product] LanguageFiles
servernamedriveProgram FilesCommon FilesMicrosoft Sharedweb server extensionswpresources[Product]

Depending on your version of SharePoint, your localization files may be found in the following locations.

servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions15CONFIGAdminResources (SharePoint 2013)
servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions14CONFIGAdminResources (SharePoint 2010)

The German, Spanish and French files have not yet been translated; although the file name suggests otherwise, their content is English. Edit these files to provide your own text or translation of the product user interface and settings.

IMPORTANT: If you do not rename the files you modify, your customizations will be overwritten when you upgrade to a new Bamboo product release.

To make sure that your customizations do not get overwritten when you upgrade the product, follow these steps:

Step	Action
1.	Copy the default file for the appropriate language and rename the copy. For example, you might save a localized French language file as CompanyName.1036.French.xml or Copy.Bamboo.ProductName.fr-FR.resx. NOTE: When you next upgrade the product, the default file (i.e., 1036.French.xml) will be overwritten with the new version. Your file will not. You can use any file name, as long as the file extension is .xml (or .resx for newer products). To create language files for languages other than German, English, Spanish, or French, copy one of the existing language files and rename it. Then edit the file to provide your own translation.
2.	When you upgrade your Bamboo product, the installation/setup application will not remove or overwrite language files you created if you saved them with a name other than the default. However, product upgrades may require that you merge new resource strings for the new product release. NOTE: If you forget to add new resource strings to your custom language file, you may see strange things in the user interface. The product will display missing resource string IDs instead of text. Copy these new resource string IDs from a default language file to your custom file and make any desired translations.

Step

Action

Copy the default file for the appropriate language and rename the copy. For example, you might save a localized French language file as CompanyName.1036.French.xml or Copy.Bamboo.ProductName.fr-FR.resx.

NOTE: When you next upgrade the product, the default file (i.e., 1036.French.xml) will be overwritten with the new version. Your file will not. You can use any file name, as long as the file extension is .xml (or .resx for newer products).

To create language files for languages other than German, English, Spanish, or French, copy one of the existing language files and rename it. Then edit the file to provide your own translation.

When you upgrade your Bamboo product, the installation/setup application will not remove or overwrite language files you created if you saved them with a name other than the default. However, product upgrades may require that you merge new resource strings for the new product release.

NOTE: If you forget to add new resource strings to your custom language file, you may see strange things in the user interface. The product will display missing resource string IDs instead of text.

Copy these new resource string IDs from a default language file to your custom file and make any desired translations.

Top

Editing Text in Language Files

IMPORTANT: Before making any changes to any file, back up your original file and put it in a safe place.

To change text in a language file, follow these steps:

Step	Action
1.	Open the language file in a text editor and locate the text you want to change.
2.	Edit the text between the <resource></resource> tags but do not edit the tags. NOTE: Do NOT modify the resource id value. Modify only the text between the <resource></resource> tags. If you want to remove text completely, delete only the text; do not delete the <resource> entry from the file, or the product interface will display an error message. In the example below, the text you can modify is highlighted in gray.
3.	When you are finished with your changes, save the file and copy it to the appropriate resources folder on all Web front-end servers in your SharePoint farm.
4.	Follow the instructions below to select your new language file in the product settings.

Top

Selecting a New Language File for a Product

The instructions below for changing language file settings apply to Bamboo products with settings configured in the Web Part tool pane or Web Part Settings pop-up page. If you have multiple instances of a product in your portal, you must make the same change for each instance that requires the change.

Change the Language Settings in the Web Part Tool Pane:

Step	Action
1.	Click the edit drop-down menu on the Web Part title bar and select Edit Web Part (or Modify Shared Web Part if you are using SharePoint 2007). See the example from the Group Email Web Part.
2.	In the Language Settings section of the Web Part tool pane, select the language file you want to use. See the example from the Group Email Web Part. If you have created a new file (i.e., Copy.Bamboo.ProductName.fr-FR.resx), it should appear in the list as a valid selection.
3.	Click Apply and then OK in the Web Part tool pane to apply your changes.

Change the Language Settings in the Web Part Settings Pop-up Page:

Step	Action
1.	Click the edit drop-down menu on the Web Part title bar and select Edit Web Part (or Modify Shared Web Part if you are using SharePoint 2007).
2.	Click the [Product] Settings button in the Web Part tool pane.
3.	Click Language Settings in the Web Part Settings page and select the language file you want to use. If your product does not have a Language Settings section, look for the Select a Language drop-down list in General Settings instead. If you have created a new language file (i.e., Copy.Bamboo.ProductName.fr-FR.resx), it should appear in the list as a valid selection.
4.	Click the Save & Close button to save the Web Part settings.
5.	Click Apply and then OK in the Web Part tool pane to apply your changes.

Localize Bamboo Applications or Custom Columns

Overview of the localization process for Bamboo Products

Bamboo applications and custom columns are slightly different than web parts when it comes to localizing/translating. The user interface isn’t confined to a web part, but can exist as site definitions or other custom pages. For example, the configuration of a Bamboo custom column is within the SharePoint list settings area.
The text strings that require translation are located in different files than the strings that appear in a web part.

Changing the language or text for an application or custom column is a multi-step process:

About the Language files
Editing text in resource files
Applying Language File Updates

Top

About the Language Files

Text displayed in a Bamboo application may be included in one or both of the following locations:

Provisioning Resources. These resources are located in the 12, 14, or 15 “Hive”, in the Resources folder. The number of the Hive depends on the version of SharePoint you are using (e.g., SP2007 has a 12 Hive, SP2010 has a 14 Hive, and SP2013 has a 15 Hive).

The Bamboo.*.resx files include text used in site features, site definitions, list definitions, and other provisioning resource elements. Any changes you make in these files will apply to new product instances only.
Application/Runtime Resources. These are also located in the 12, 14, or 15 Hive, but in the CONFIGResources folder.The Bamboo.*.resx file in the CONFIG folder is different than the one included in the Resource folder. This one includes text used in application pages, custom site menu actions, navigation elements, and other runtime resources. Any changes you make will apply to new and existing product instances only.

In each location, there may be multiple versions of Bamboo.*.resx files with identical content. The different files are provided for English (en-US), German (de-DE), French (fr-FR), and Spanish (es-ES). The content of all files is in English until you translate it to your language. If your site is configured to use a language that does not have a corresponding Bamboo product .resx file, copy an existing file and rename it to include the culture name for that language pack. For example, create a file for Italian by saving the default file as Bamboo.[Product].it-IT.resx. Make your changes to this new file. If your site is configured to use a specific language but you do not have a culture-specific file, the product will use the default Bamboo.[Product].resx file instead.

IMPORTANT: If you customize one of the default resource files provided with the product, your changes will be overwritten when you upgrade.

To avoid losing customizations, copy the customized file to a different location (not the same folder) before upgrading. After the upgrade is finished, compare the new file with your customized file to incorporate any new entries. Then copy the merged file to the Resources folder. Culture-specific files created for languages that are not provided with the product will not be overwritten during an upgrade, but you still need to incorporate new resource entries.

Top

Editing text in resource files

IMPORTANT: Before making any changes, back up your original file to a different folder.

To change text in a resource file, open it in a text editor and locate the text you want to change. Editable text is usually found between the <value></value> tags, as shown in the screen shot below. Do not modify the data tag. If you want to remove text completely, delete only the text; do not delete the <data> or <value> entries from the file, or the server will display an error message. In the example below, the editable text is highlighted in gray.

When you are finished with your changes, save the file and copy it to the appropriate Resources *folder on *all Web front-end servers in your SharePoint farm. Follow the instructions below to make your changes take effect.

Top

Applying Language File Updates

To apply changes to Provisioning Resource Files:

If you modified the provisioning resources file, apply your changes by restarting Web services with the following command on all Web front-end servers.

iisreset

NOTE: changes to provisioning resources affect new instances of the Bamboo product only; existing instances of the product are not updated.

To apply changes to Application/Runtime Resource Files:

If you modified the application/runtime resources file, apply your changes by executing the following stsadm command on all Web front-end servers. This command copies the updated resource file to the App_GlobalResources folder of each Web application. Changes apply to existing product instances and any new instances you create.

stsadm -o CopyAppBinContent

NOTE: Changes apply to EXISTING product instances AND any new instances you create.

Is there a way to find a lost or unknown Bamboo product license key?

If your Bamboo Product License is invalidated because of a change to the hardware profile of a server, the license key used to activate it previously will not be shown in the Bamboo Web License Manager in SharePoint Central Administration.

You should be able to find the license keys associated with your purchase in the My Bamboo area of the Bamboo Solutions web site.

Step	Action
1.	Login to My Bamboo.
2.	Click the My Orders link from the Home page.
3.	On the Product Licenses tab of the My Orders page, the license keys associated with the products you’ve purchased are listed. NOTE: If you don’t see your orders listed on the page, please contact your Bamboo Sales Representative at Sales@bambooosolutions.com

Step

Action

Click the My Orders link from the Home page.

Mb-Home squares.jpg

On the Product Licenses tab of the My Orders page, the license keys associated with the products you’ve purchased are listed.

MB-MyOrders blurred.jpg

NOTE: If you don’t see your orders listed on the page, please contact your Bamboo Sales Representative at Sales@bambooosolutions.com

Using the PM Central Issues list

Overview of PM Central Hierarchy	Overview of the Project Site

When working with Issues keep in mind:

Active issues associated with active projects are rolled up and displayed on the Portfolio site and applicable Department sites.
By default, the number of overdue issues will be used by the Issues Status Key Performance Indicator in the Project Health list.
The My Active Issues display, found under the My Summary tab at all levels of the PM Central hierarchy, will show issues assigned to the logged in user.

To create a new issue:

Step	Action	Result
1.	Click Add New Issue in the Central Actions drop down Or From the Issues tab, under Issues and Risks, click Add New Item above the All Active Issues data view.
2.	Enter a Title and Assigned To Keep in mind: If Alert Plus alerts have been enabled in the PM Central portfolio the assignee will receive an Alert notifying them of the assignment. Additional reminder notifications are also available.
3.	Provide information about the issue including; Priority, Description, Category, Related Issues and Related Tasks
4.	Enter a Due Date for the issue.
5.	Click Save	Issues with an Active Issue Status will be displayed in the All Active Issues data-view under on the Issues page

Overview of PM Central Hierarchy	Overview of the Project Site

PM Central Portfolio – Issues Tab

Overview of the PM Central Hierarchy	Overview of the Portfolio Site

The Issues page displays the active issues associated with the portfolio’s active projects, and Issue Summary charts.

NOTE: The Web Parts shown on the Issues page of department sites are the same as those on the portfolio site. The content displayed in the Web Parts will be determined by the department site’s filter configuration.

	Name / Web Part	Description
1.	All Active Issues Bamboo Data-Viewer Web Part	The Issues tab shows the active issues associated with Active projects in the portfolio. The Data-Viewer Web Part uses the All Active Issues list rollup schema as its data source.
2.	SharePoint Navigators	The Issues tab defaults to a display of the Issue Summary chart associated with Active Projects. Users can view Pending Project, Completed Projects, Cancelled Projects and All Project views by clicking their respective icons. The My Projects displays offer similar views, but only for projects where the logged-in user has been assigned as the project manager
3.	Issue Summary Bamboo Chart Plus Web Part	The Issue Summary displays, in chart form, the number and percentage of issues by status (Active, Deferred and Closed). The Chart Plus Web Part uses the Summary List as its data source. The summary list is updated by the Bamboo Update Summary List timer job.

Name / Web Part

Description

All Active Issues

Bamboo Data-Viewer Web Part

The Issues tab shows the active issues associated with Active projects in the portfolio.
The Data-Viewer Web Part uses the All Active Issues list rollup schema as its data source.

SharePoint Navigators

The Issues tab defaults to a display of the Issue Summary chart associated with Active Projects. Users can view Pending Project, Completed Projects, Cancelled Projects and All Project views by clicking their respective icons.

The My Projects displays offer similar views, but only for projects where the logged-in user has been assigned as the project manager

Issue Summary

Bamboo Chart Plus Web Part

The Issue Summary displays, in chart form, the number and percentage of issues by status (Active, Deferred and Closed).

The Chart Plus Web Part uses the Summary List as its data source. The summary list is updated by the Bamboo Update Summary List timer job.

Overview of the PM Central Hierarchy	Overview of the Portfolio Site

Installing the Bamboo Web License Manager

Overview of Licensing and and Product Activation

If you need to activate your Bamboo product license, you most likely need the Bamboo Web License Manager installed on your farm. If you need to activate a Bamboo Desktop application, please see Activating a Bamboo Desktop Product Using the License Manager

NOTE: If you are running with a free trial license, there is no need to install this component.

Install the Bamboo Web License Manager on one of the servers in the SharePoint farm that is running the Central Administration service. The component will be automatically deployed to all Central Administration Web applications by the SharePoint timer service.

NOTE: You must be a member of the local server Administrators group and have the db_owner role for the SharePoint configuration database to install and run the Bamboo Web License Manager.

Step	Action
1.	On the server running the Central Administration service, run the Setup program for any Bamboo product. NOTES: 1. Refer to System Settings in SharePoint Central Administration for a list of servers running this service. 2. Although every product Setup package includes the Web License Manager, it is necessary to install it only once on the farm.
2.	From the Setup interface, click the Bamboo Web License Manager component. Verify that the installation location is correct. Verify that the you have the required installation permissions. Click the Install button. The installation for the Web License Manager will begin.
3.	Click Next to continue.
4.	The install will run through some system checks. If they pass, click Next. NOTE: The Web License Manager expects Bamboo Logging V1 to have been previously installed. If you have installed a Bamboo product before installing the Web License Manager, this Prerequisite Component will already be installed.
5.	Read and accept the Bamboo End-User License Agreement. When you check the box labeled “I accept the terms in the License Agreement”, the Next button will be enabled. Click it to continue.
6.	The Web Application where Central Administration is running should be displayed in the Deployment Targets page. Check the box at the bottom to automatically activate the feature during the install. NOTE: If desired, you can always activate the feature manually in Central Administration.
7.	Monitor the progress of the install. When its complete, click Next.
8.	A Summary of the installation is presented. Click Close to complete the process.
9.	After a successful installation of the Web License Manager, you should see a Bamboo Solutions entry on the main page of SharePoint Central Administration on the main page.

Installing the Microsoft Project Add-In for PM Central

The Microsoft Project Add-in for Microsoft Project 2010 or Project 2013 allows you to import, export, and synchronize tasks between your PM Central project sites and Microsoft Project. It is an optional component.

The Microsoft Project Add-in can be installed to work with either Microsoft Project 2010 or 2013 (32 bit and 64 bit). The Microsoft Project Add-in works with SharePoint 2010 or SharePoint 2013. With the installer included with PM Central release 4.1 and higher, the Microsoft Project Add-in component will install successfully whether Microsoft Project 2010/2013 is installed on your desktop or not. Previous installation required MS Project to be installed prior to the installation of the add-in.

Follow these steps to install the add-in:

Step	Action
1.	The Microsoft Project Add-in installation package is included in the misc subfolder of the PM Central installation package. Generally, you will not install this add-in on the SharePoint server but on a PC where you have Microsoft Project installed. You can download the entire PM Central installation package to the PC where you want to install the add-in or you can browse to the /misc folder in the installation files on your server and copy Bamboo.MSProjectAddInSetup.exe to the PC where you want to install the add-in. NOTE: This install works with both versions of Microsoft Project 2010/2013 (32 bit or 64 bit).
2.	If you downloaded the whole PM Central installation package, run the Setup.bat and highlight Microsoft Project Add-In in the Components list. Verify the Installation Location and the Permissions and when ready, click Install. Otherwise, if you copied the Bamboo.MSProjectAddInSetup.exe file to your PC, double-click it to start the install. Using either method, the installation will begin.
3.	Click Next > to continue.
4.	Decide where you want to install the Add-In and then click Next >to continue.
5.	When the Add-In is successfully installed, a message will be displayed. Click Finish.
6.	Check MS Project and ensure that the PM Central Add-In toolbar is there. NOTE: If you would like other users (in addition to the one who installed it) to use the Add-In please see Allowing Other Users to Use the MS Project Add-in. The Add-In is not licensed, so there are no other steps required before you begin to use it.

Installing using the updated install 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 install using the updated install process, please follow these steps (Warning.. Installs should be performed in Non-Peak hours as your farm will temporarily go offline):

No.	Function
1.	Download the install package from My Bamboo.
2.	Extract the contents of the package.
3.	Run the Install.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 install them in alpha order. Rather than deploying the solution immediately after its installed, the script schedules deployment time for 1 minute in the future so multiple installs won’t collide. IMPORTANT: By default, the script deploys solutions to all content web applications. If you don’t want to do this, please update the script for your needs.
5.	When the deployment completes, check Central Administration to confirm deployment completion.
6.	Activate in the desired Site Collections. See Activating a Bamboo Site Collection Feature for details.

Options for Installing

Option	When or Why to use this?
Use the Updated Installation 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.
Use the Bamboo Installation/Setup program	IMPORTANT: As of April 2017, Bamboo no longer includes the Installation/Setup program in product download packages. This is an easy option for small to medium sized farms with not too many web applications and/or WFE servers. The program will automatically check certain conditions, ask which Web Applications you want to deploy to, and then ask if you want to automatically activate site collection features. These are things that are easy to forget when installing any other way. For more information, see Overview of the Setup Program and How to run the Installation/Setup program. NOTE: You may decide NOT to use the Installation/Setup Program if your farm has several web front end servers (WFEs) or Web Applications. The installation and/or the solution deployment may timeout trying to deploy to a very large farm. In this case, it may be best to manually install the product on your farm.
Manually Install	Extra care must be used when installing a product manually because the series of automated checks performed by the Bamboo Installation program will not be available. Unexpected behavior during product configuration, licensing, or use may occur if some steps are skipped. About the Installation Files Important Notes About Manual Installation How to use the Installation-Setup program to install a single WSP Manually Install using PowerShell Manually Install using stsadm Manually Installing a Product MSI

Option

When or Why to use this?

Use the Updated Installation 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.

Use the Bamboo Installation/Setup program

IMPORTANT: As of April 2017, Bamboo no longer includes the Installation/Setup program in product download packages.

This is an easy option for small to medium sized farms with not too many web applications and/or WFE servers. The program will automatically check certain conditions, ask which Web Applications you want to deploy to, and then ask if you want to automatically activate site collection features. These are things that are easy to forget when installing any other way.

For more information, see Overview of the Setup Program and How to run the Installation/Setup program.

NOTE: You may decide NOT to use the Installation/Setup Program if your farm has several web front end servers (WFEs) or Web Applications. The installation and/or the solution deployment may timeout trying to deploy to a very large farm. In this case, it may be best to manually install the product on your farm.

Manually Install

Extra care must be used when installing a product manually because the series of automated checks performed by the Bamboo Installation program will not be available. Unexpected behavior during product configuration, licensing, or use may occur if some steps are skipped.

Generating Activation Keys using My Bamboo

All Bamboo products that deploy to SharePoint can be activated online and the license(s) managed using Bamboo Web License Manager. Bamboo Web License Manager is included with the Setup program for every Bamboo product. You only need to install it once on your farm to manage all Bamboo products that have been or will be installed. After installation, it is accessed via SharePoint Central Administration.

If you are activating a Bamboo product on a server that does not have Internet access, you can activate your license offline and send the License Key and Machine Key to the Bamboo Support Team.
Alternatively, you can generate the Activation Key yourself via the My Bamboo area of the Bamboo Solutions website.

To generate the Activation Code yourself, follow these instructions.

Step	Action
1.	On a computer with Internet access, log in to My Bamboo with any valid account. In the My Orders tab, click Manage License.
2.	On the Manage License tab, enter the License Key and Machine Key. NOTE: See Activating My Bamboo Product License Offline to get the Machine Key. Click the Generate button to generate the activation key. Copy this key and put it in a safe place. You will need it in the next step. NOTE: If you are unable to successfully generate an activation key, send the License Key and the associated Machine Key to the Bamboo Support Team via Support@bamboosolutions.com. They will send the Activation Key to you via Email.
3.	Return to the Bamboo Web License Manager Offline Activation page in SharePoint Central Administration. Paste the activation key in the Activation Key box, and then click Activate.
4.	Your Bamboo product is now Active and is ready for use, as shown by the Status column. If you ever need to check which license key you used to activate each server, the license key used is shown on this status page.

I am having trouble adding the product Web Part to a page

Verify that the associated product feature is active in the site collection by following the instructions for Activating a Bamboo Site Collection Feature. If you are wondering which Site Collection Feature to activate for your product, refer to.
If the product feature is active but you still have problems adding it to the site, deactivate it and then activate it again.
If the product feature is not available to the site collection, verify that the product was successfully deployed to the Web Application. Deployment status can be verified in SharePoint Central Administration > System Settings > Manage Farm Solutions. If you are using WSSv3/MOSS, its in SharePoint Central Administration > Operations > Solution Management.
If the product does not appear in the list of Farm Solutions in Central Administration, it hasn’t yet been installed on the farm.
If the product shows a status of “Error” in the Farm Solutions list in Central Administration, Retract and then Remove the solution before running the Installation/Setup Program again to reinstall it. Refer to How to run the Installation-Setup Program for more information.

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

APPLIES TO:

Bamboo Farm deployed products that use Telerik. See Bamboo products that use Telerik for a list.
SharePoint Foundation 2010 and SharePoint Server 2010 have Bamboo.core.wsp and Bamboo.core.v1.wsp.
SharePoint 2007 has Bamboo.core.wsp

SYMPTOM:

Errors occur and you can not access your sites after manually retracting and removing bamboo.core.v1.wsp or Bamboo.core.wsp from your SharePoint farm.

CAUSE:

If you need to remove all of your Bamboo products from the farm, and you run the installers that come with the products and select the option to “remove”, the bamboo.core.wsp and/or bamboo.core.v1.wsp is intentionally left behind.

This is because during installation and deployment, the bamboo.core.v1.wsp (or bamboo.core.wsp) solution puts specific versions of the Telerik.web.ui and Telerik.web.ui.Skins assemblies into the Global Assembly Cache (GAC). The associated bamboo.telerik.config.wsp solution programmatically adds Telerik-related entries into the web.config for the web application(s) selected during the install. These entries refer to specific versions of Telerik.web.ui* assemblies. Web.config files should not be modified manually.

When the product(s) and solutions are uninstalled, the changes to the web.config file regarding Telerik.web.ui are not removed. This is because there may be other SharePoint solutions from sources other than Bamboo that use this version of Telerik. For the same reason, the bamboo.core.v1.wsp (or bamboo.core.wsp) is left deployed because uninstalling it removes some specific versions of Telerik.web.ui* assemblies from the GAC.

If you remove bamboo.core.v1.wsp (either manually via Central Administration, PowerShell, or stsadm), then the Telerik.web.ui* assemblies will be removed from the GAC but the entries will remain in the web.config files. This may leave you unable to access your web pages.

If you are sure there are no other solutions that rely on Telerik on your farm, it will be OK to retract and remove the bamboo.core.v1.wsp (or bamboo.core.wsp) solution. However, you must be sure to also remove the Telerik entries from the various web.config files where they have been added.

RESOLUTIONS:

Leave the bamboo.core.v1.wsp deployed. Do not uninstall it.

If you must remove the bamboo.core.v1.wsp (or bamboo.core.wsp), remove it by retracting and then removing the solution from the Manage Solutions page in Central Admin. See Uininstalling from SharePoint Central Administration for more information.

After it is successfully removed, please use PowerShell to remove the Telerik entries from the web application(s) web.config file. This will ensure that changes to the web.config are saved in the database. For more information, see How to Remove a web.config Modification Using PowerShell

How to run 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 Overview of the Updated Installation Process for Bamboo components for information about the updated process.

To access the Setup program:

Note: The minimum screen resolution to view the Setup program is 1024×768.

Step	Action
1.	Download the self-extracting product EXE (i.e., HW03.R1.7.SP2010.SL.exe) and save it to a local folder on the appropriate SharePoint server (see Location of Install Files if you are unsure about which SharePoint server to install on).
2.	Double-click the product EXE file to extract the contents of the product download. The Setup program will automatically start (see example screen shot below). See Overview of the Setup Program for more information. If you aren’t ready to install, click the X in the upper right corner to close it. To start the Setup program manually later, double-click the Setup.bat file in the root folder where the product files were extracted.

Step

Action

Download the self-extracting product EXE (i.e., HW03.R1.7.SP2010.SL.exe) and save it to a local folder on the appropriate SharePoint server (see Location of Install Files if you are unsure about which SharePoint server to install on).

Double-click the product EXE file to extract the contents of the product download.
The Setup program will automatically start (see example screen shot below). See Overview of the Setup Program for more information.

If you aren’t ready to install, click the X in the upper right corner to close it. To start the Setup program manually later, double-click the Setup.bat file in the root folder where the product files were extracted.

To Run the Setup:

Step	Action
1.	Review Recommendations for a successful install
2.	Run the Installation/Setup program and highlight a component to install. It’s best to install components in the order they are listed, if more than one is listed.
3.	Verify the installation location and required permissions for the selected component. They will be listed on the right side of the screen and could change for different selected components.
4.	Click the Install button that appears in the lower right corner. The install process will begin. During the install process, you will be asked: to verify that the system checks pass successfully. Some products have more checks than others. If some checks display an error, you will not be able to proceed until the error is resolved. Abort the install and try again once the issue is resolved. to read and accept the Bamboo Solutions End-User License Agreement (EULA). In the Deployment Targets screen, select the Web Application(s) on the farm where you want to deploy the product. If you are a Site Collection Administrator for all the site collections in the selected Deployment Targets (web apps), it’s OK to leave the Automatically activate features… option checked, otherwise uncheck it. NOTE: If you prefer that Site Collection Administrators activate product features as they are needed, uncheck the Automatically activate features option, then read How to activate a Bamboo Site Collection Feature to understand how to manually activate these features at a later time.
5.	When the installation is complete, a Summary will be displayed. Some Bamboo product components install several features. The install routine does not abort the installation if one feature fails to install. It continues to install the next feature. For this reason, be sure to review this summary carefully to make sure the install completed without error. You may need to scroll up to review the entire summary. NOTE: If one or two features failed, you can reinstall the failed features individually at a later time (after resolving any issues described in the log file). This may save you time if the installation was successful for all but a few components. See How to use the Installation-Setup program to install a single WSP for more information.
6.	Repeat Steps 2-5 for each required component listed. Required components are designated with a red asterix. Install optional components as needed. NOTE: It is not necessary to install the Bamboo Web License Manager if it is already installed on your SharePoint farm. This component is included with every Bamboo product, but only needs to be installed once.
7.	When all desired components are installed, restart the World Wide Web Publishing Service or the App Pools, depending on which you may have stopped.
8.	If you didn’t automatically activate features in site collections during the install, be sure to activate the site collection feature(s) in the appropriate site collection before adding the web part to a page. See Activating a Bamboo Site Collection Feature for more information.

Return to Options for Installing

How to Remove a web.config Modification Using PowerShell

Background

Some custom SharePoint products make changes to the web.config file for a Web application via SPWebConfigModification objects to support their features. Bamboo products sometimes make changes like this during installation. Please see How to modify a web.config file using PowerShell for some additional background information.

You may need to remove these changes for a particular Web application, if the product is no longer used on that Web application. It’s not a good idea to manually edit the file to remove the text, because the web.config would no longer match what has been set in the SharePoint configuration database and might cause future problems on your farm.

Resolution

Follow the steps below to remove web.config settings using PowerShell.

NOTE: The commands in this article work with both SharePoint 2010 Foundation and Server. Be extra careful when making changes to the web.config. Back up the file before making any changes. Do not remove a modification unless you are absolutely sure what it is.

Step	Action
1.	First, open SharePoint 2010 Management Shell. From the Start menu on a SharePoint WFE Server, select All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell
2.	Next, list all of the SPWebConfigModification objects that have been applied to the Web application. These objects are stored in the WebConfigModifications property of the Web application. `1: $webApp = Get-SPWebApplication WebApplicationURL 2: $webApp.WebConfigModifications` In this example, you can see some of the modifications added by Bamboo products to support Telerik:
3.	Now, we can identify a particular modification and remove it using the commands shown below. `1: $config = $webApp.WebConfigModifications \| Where-Object {condition_to_identify_the_object} 2: $webApp.WebConfigModifications.Remove($config) 3: $webApp.Update() 4: $webApp.Parent.ApplyWebConfigModifications()` In this example, we’ll remove the modification with the name “add[@name=[‘Session’]” and path “configuration/system.webServer/Modules”.
4.	The ApplyWebConfigModifications() method applies this change across the farm for the specific web application, so we don’t need to worry about each physical web.config file at the server-level. That is one of the main advantages of using PowerShell to update web.config modifications. If there are multiple modifications we need to remove, we can use a loop to do that. The following example removes all of the modifications added by Bamboo Telerik Config in a particular Web application (they all have the same Owner value): `1: $BambooConfigs = $webApp.WebConfigModifications \| Where-Object {$_.Owner -eq "Bamboo.SP2010.Config"} 2: foreach ($config in $BambooConfigs) { 3: $webApp.WebConfigModifications.Remove($config) 4: } 5: $webApp.Update() 6: $webApp.Parent.ApplyWebConfigModifications()`

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

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

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

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

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

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

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

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

How to move your Bamboo Product License to a new server

Overview of Licensing and and Product Activation

You must have a Bamboo product license for each Web Front-end (WFE) server in the SharePoint farm that serves web content. If you replace a server with another physical device, you can move the license from the old server to a new one. To do so, first deactivate the license and then re-activate by following the instructions below.

Step	Action
1.	Go to Central Administration and under the Bamboo Solutions section, click Manage My License Keys. NOTE: If you are using SharePoint 2007, in Central Administration, go to the Bamboo Solutions Corporation heading on the main page and click Bamboo Web License Manager. Locate the product that you need to deactivate and click the product name link. The license Status Page will be displayed. Each server that is licensed for that product is listed on the page. NOTE: If the License Key is not listed on the license status page, see Is there a way to find a lost or unknown Bamboo product license key.
2.	In the Status Page, copy the license key from the server that will be deactivated to a safe location so you can use it on the new server (see Step 4 below). Then, click the Active status link. The Activation Page will be displayed.
3.	On the Activation Page, click the Deactivate button. Your license is now deactivated on that server. NOTE: If your SharePoint WFE server doesn’t have access to the Internet, you will not be able to deactivate from this page. However, it is important to deactivate the license. Please see How to deactivate your Bamboo Product License if your server doesn’t have access to the Internet for a way to deactivate from a PC that does have access to the Internet.
4.	When the new server is ready, see Activating Your Bamboo Product License for information about activating the license key for that server. Use the license key you copied to a safe location in Step 2 above to activate the product on the new server.

Manually uninstall using PowerShell

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

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

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

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

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

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

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

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

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

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

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

How to find the release of PM Central

To locate the file versions of the products contained in PM Central:

Step	Action
1.	Navigate to the portfolio site’s PM Central Control Panel. NOTE: You need to be a user with the appropriate level of permission on the site in order to see this option on the Central Actions menu.
2.	On the right side of the PM Control Panel, the release number or version is displayed beneath the heading PM Central Information. The File Version is the version of PM Central that is installed on your farm.
3.	To see the release numbers (or versions) of the components included in PM Central, click the Product Version link in the PM Central Help section of the Control Panel to see the versions of web parts included in PM Central. A list of each product, the assembly name, and the file version is displayed. The version number that is displayed next to the product Bamboo Project Central(assembly name: Bamboo.ProjectCentral.dll) corresponds with the release version of Project Management Central that is installed on your server. NOTE: If you are running SharePoint 2010 or SharePoint 2013, the first digit of the version number will have an extra 0. Please see About Bamboo product Version Numbers.

Step

Action

Navigate to the portfolio site’s PM Central Control Panel.

NOTE: You need to be a user with the appropriate level of permission on the site in order to see this option on the Central Actions menu.

PMCentral control panel link.png

On the right side of the PM Control Panel, the release number or version is displayed beneath the heading PM Central Information. The File Version is the version of PM Central that is installed on your farm.
PMC version in panel.jpg

To see the release numbers (or versions) of the components included in PM Central, click the Product Version link in the PM Central Help section of the Control Panel to see the versions of web parts included in PM Central.
PMC product version link in panel.jpg

A list of each product, the assembly name, and the file version is displayed. The version number that is displayed next to the product Bamboo Project Central(assembly name: Bamboo.ProjectCentral.dll) corresponds with the release version of Project Management Central that is installed on your server.

PMC product versions.png

NOTE: If you are running SharePoint 2010 or SharePoint 2013, the first digit of the version number will have an extra 0. Please see About Bamboo product Version Numbers.

How to find the release number of a Bamboo web part

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

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

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

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

Follow the steps below:

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

How to check the status of your trial license

Overview of Licensing and and Product Activation

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

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

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

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

Overview of Licensing and and Product Activation

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

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

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

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

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

How to Add a web.config Modification Using PowerShell

Background

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

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

Resolution

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

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

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

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

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

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

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

Step

Action

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

Next, create the SPWebConfigModification object for the assembly binding

Where:

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

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

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

How to activate a Bamboo Site Feature

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

Step

SharePoint 2007

SharePoint 2010/2013

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

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

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

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

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

Overview of Licensing and and Product Activation

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

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

Highlights of PM Central

Easy Setup: Project Management Central makes it easy to create a new project – or an entirely new top level portfolio site – thanks to its use of standard SharePoint site templates. Simply create a new site the same way you always do, and select the Project Management Central Portfolio site template. In just a few moments, you’ll have a pre-configured project management application at your fingertips, ready for you to add projects to.

Simple Administration: Managing your users, projects, and data in Project Management Central is easy, thanks to its seamless integration with your existing SharePoint infrastructure. It’s easy to create new resources, import existing users from the User Information List, and apply standard, out of the box SharePoint permissions for simple, reliable security trimming.

Powerful User Interface: Project Management Central’s dedicated tools for project management make it easy to perform everyday project tasks online. Inline editing in task lists, intuitive controls for filtering and sorting data, and a clean, simple look and feel all contribute to fast, friendly user experience you won’t find in homemade SharePoint solutions.

Overview of the Gantt View of Active Projects

Found on the Overview tab on the Portfolio and Department sites, the Gantt View of Active Projects (Gantt View) displays the timeline of the active projects as well as the color code for the progress bar.

Gantt View Basics

The Gantt View of Active Projects is a widget in the Project Portfolio Dashboard (PPD) solution.

The Gantt View uses the Project Portfolio Dashboard list found on the Portfolio site as its data source
When the Project Portfolio Dashboard list is empty, or there are no active projects identified in the Portfolio Dashboard list, the Gantt View of Active Projects will not display any content.

To have content displayed in the widget the following events need to occur:

	Description
1.	From the Portfolio sites PM Central Control Panel click the Update Portfolio Dashboard Mapping link OR Click the Update Portfolio Dashboard Mapping button found on the Overview page of the Portfolio site NOTE: The Update Portfolio Mapping links are not available on Department sites. Prior to PMC 4.3 the Update Portfolio Dashboard Mapping button/link was labelled Refresh data on Gantt View
2.	The destination page displays the contents of the Bamboo Project Dashboard Data Mapping list. By default this list will contain a single item that references the current Portfolio site. Pre configured mappings between fields in the Project Health list and the Portfolio Dashboard list are defined in this default item
3.	Click Refresh to update the contents of the Bamboo Project Dashboard Data Mapping list with any recently added projects. Important: You must manually click the Refresh button to update the contents of the mapping list
4.	With all the projects identified in the Bamboo Project Dashboard Data Mapping list wait for the next runtime of the Update Dashboard List timer job. This timer job runs every 30 minutes by default.
6.	When the timer job runs it will populate/update the Project Portfolio Dashboard list. Projects with an Active status will be displayed in the Gantt View of Active Projects.

Generate PM Central Resource Reports

Overview of Portfolio PMC Control Panel	Overview of Portfolio Resource Center

Default Resource Report Behavior

The majority of the resource reports available under the Resource Allocation and Capacity Planning tab are configured to obtain data from the Report Information list, found on the local site.

This Report Information list is updated by the Bamboo Reporting Calculation Timer Job V4 and the Bamboo Top Site Calculation Timer jobs respectively, which are, by default, scheduled to start running every day at 11.45PM.

Portfolio Resource Reports are security trimmed, and are generated for individual users “by request”.
Users who have not previously submitted a “request” item in the Report Information list will see this message on the Report page and will need to wait need to wait for the next run time of the timer jobs to see the report contents.

Default message when there is no content report content to display

Report Request screen A request item for a specific report will be entered in the Report Information list for each logged in user who:

Clicks on a report page under the Resource Allocation and Capacity Planning tab

Selects the report from the Report Requests page, accessed from the “here” hyperlink in the message text.
The Report Requests tool was added in PM Central 4.3

NOTE: A one time email notification will be sent to users who have submitted new report requests, if the reminder notification was Enable in Alert Plus by the site administrator.

The following configuration options are available:

1.Generate resource reports using the System Account:
This configuration setting will allow all users with access to the Report Center to see Resource Allocation and Capacity details for users assigned to all projects

2.Configure the reports to “Run Now
This option removes the wait time associated with the default configuration by referencing content from List Rollup rather than the Report Information list.

Important: This option can result in page time out errors.

NOTE: The Run Now option is only available for resource reports on the portfolio and department sites.

Error Log Files

Applies To

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

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

This directory is located at C:WindowsTempBambooSolutions

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

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

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

To determine which servers on the farm run these services:

SharePoint 2007:

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

SharePoint 2010:

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

SharePoint 2013:

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

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

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

Completing the Enterprise Resource Pool form

Overview of Portfolio PMC Control Panel	Overview of Portfolio Resource Center

The Enterprise Resource Pool (ERP) is a centralized list of resources available to be assigned to work on projects. Information from the ERP is used throughout the PM Central, but the fields in the ERP form that need to be populated will be determined by the PM Central features you require.

Enterprise Resource Pool list form - Edit View

What fields NEED to be populated:

1.
The following fields must be populated for each user:

Last Name
First Name
Full Name
Account
E-mail Address
Maximum Unit

NOTE: The Maximum unit field has a default value of 100%.

2. Completing the Department, Project Manager and Role fields will allow Resource Reports to be generated that:

Group users by their identified Department
Group users by their identified Project Manager
Allow you to find available resources by Role

3. If you are going to track (human) resource costs in PM Central the Standard Rate field must be populated.

NOTE: PM Central uses the calculation
Standard Rate x Work to determine the cost of a task.

4. When using PM Central with Bamboo’s Time Tracking and Management (TTM) application these fields must be populated to allow users to submit timesheets:

Primary Timesheet Manager
Secondary Timesheet Manager
Allow Overview

More information on integrating PM Central with TTM is available here

Overview of Portfolio PMC Control Panel	Overview of Portfolio Resource Center

Deploying PM Central 1.8 or Newer to a New Web Application

You can deploy PM Central on a new Web application without having to reinstall the product. For information on creating a new Web application, read the following Microsoft articles:

To deploy PM Central R1.8 or newer on a new Web application follow these steps:

Step	Action
1.	After you have created your new Web application, navigate to Central Administration > System Settings > Manage Farm Solutions.
2.	The list of solutions deployed on your SharePoint farm is shown. Find the solution called bamboo.projectcentral.wsp, select it, and click Deploy Solution on the page that appears.
3.	In the Deploy To? section, select the new Web application from the drop-down menu and click OK.
4.	Repeat steps 2-3 for each solution listed below. (need list of solutions here)
5.	(check this) After you deploy all of the solutions, reset Internet Information Services (IIS). To reset IIS using IIS Manager: Go to Start > Administrative Tools > IIS Manager. In the Connections pane on the left, expand and select the node for the server you want to restart. In the Actions pane on the right, select Restart. To reset IIS using the command-line utility (must be a member of the Administrators group on the local computer): Go to Start and click Run. In the Open box, type cmd and click OK. At the command prompt, type `iisreset /noforce computername` and press Enter.
6.	Activate the PM Central Web application features. Navigate to Central Administration > Application Management > Web Applications > Manage Web Applications. Select the new Web application and then from the Web Applications ribbon, select Manage Features In the Web Application Features list, activate the following features for PM Central: Bamboo Update Summary Project List Bamboo Update Task, Issue, Project Health Lists Bamboo Update Dashboard List Timer Job Bamboo Reporting Services Bamboo Alert Plus Timer Job NOTE: The Bamboo Alert Plus Timer job is an optional install and may not be used on your farm. It is needed only if you want to use the alerting features of PM Central.
7.	Create a new site collection for your PM Central portfolio. See Create a new Site Collection and PM Central portfolio for more information.

Deploying a Bamboo solution to a new Web Application

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

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

CSS Overview

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

Calendar Plus

CSS for Calendar Plus

Chart Plus

Cross List

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

Navigators

Password Change

CSS for Password Change Web Part

PM Central

PMC Skin Templates

Team Calendar

CSS for Team Calendar

Virtual Map View

CSS for Virtual Map View

Create a PM Central Portfolio/Top Level site

Configuring PM Central	Getting Started with PM Central

When creating a PM Central Portfolio or Stand-alone site keep in mind:

PM Central’s portfolio site templates are not available from SharePoint’s New Site tool.
To create a portfolio site administrators, must use the Create New Site link from the Site Actions menu.

Step	Description
1.	From the site where you want to create the PM Central portfolio site click Create New Site in the Site Actions drop-down menu. NOTE: If this option is not available under Site Actions you will need to activate the PM Central Create Site site collection feature.
2.	Enter the Title, Description and the URL for the new site
3.	Select a template for the site from the Template Name drop down menu. NOTES 1. The Bamboo PM Central Top Level Site – Custom Template and the Bamboo PM Central Top Level site templates are made available in the drop down menu by default. There is NO difference in the functionality offered by these templates. The sole difference is the appearance of the site on creation. Click here for a preview. 2. Other templates, such as the Stand Alone template, and Portfolio Site Lite can be made available when the respective features are activated in Site Collection features.
4.	Choose what permissions will be associated with the site
5.	Click Create. Wait while the Portfolio site is created.

Create PM Central Project or Department sites

Getting started with PM Central

PM Central uses Site Creation Plus to create project and department sites in a portfolio to simplify the site creation process.

Keep in mind:

PM Central project and department sites should not be created using the SharePoint New Site dialog box

To create a PM Central Project or Department site:

Step	Action	Result
1.	On the Portfolio site click the Create New Project… button on the Portfolio home page OR From the Central Actions drop down menu, click Add New Project	These options will only be visible to users with Full Control permission levels or the Create Sub site permission
2.	Enter a Title for the site The text entered here will become the URL for the site.
3.	Choose the permissions for the site. NOTE: This area may have been hidden.
4.	Select the template from the available options.
5.	If a project site template was selected, you will be able to enter any other known information about the project into the Project Health list
6.	Click Create	You will be taken to the home page of the new site

Create a PM Central Project site

Getting started with PM Central

PM Central uses Site Creation Plus to create project and department sites in a portfolio to simplify the site creation process.

Keep in mind:

PM Central project and department sites should not be created using the SharePoint New Site dialog box

To create a PM Central project site:

Step	Action	Result
1.	On the Portfolio site click the Create New Project… button on the Portfolio home page OR From the Central Actions drop down menu, click Add New Project	These options will only be visible to users with Full Control permission levels or the Create Sub site permission
2.	Enter a Title for the site The text entered here will become the URL for the site.
3.	Choose the permissions for the site. NOTE: This area may have been hidden.
4.	Select the template from the available options.
5.	Enter any other known information about the project into the Project Health list
6.	Click Create	You will be taken to the home page of the new project site

Create a PM Central Department site

Getting started with PM Central

PM Central uses Site Creation Plus to simplify the process of creating the project and department sites that will be associated with a PM Central portfolio.

Keep in mind:

PM Central project and department sites should not be created using the SharePoint New Site dialog box
After the first department site is created the All Department Sites Web Part will be visible on the Portfolio home page

The All Department Sites Web Part

To create a PM Central Department site:

Step	Action	Result
1.	On the Portfolio site click the Create New Project… button on the Portfolio home page OR From the Central Actions drop down menu, click Add New Project	These options will only be visible to users with Full Control permission levels or the Create Sub site permission On SharePoint 2013 click the icon to access the Central Actions menu.
2.	Enter a Title for the site The text entered here will become the URL for the site.
4.	Select the template from the available options.
5.	Click Create	You will be taken to the home page of the new department site where you can configure the site to display details about specific projects.

Bamboo Policy for Migrating License Keys

How to get your new license keys

Overview

Migration Steps

Overview

Migration Steps

Applies to:

About the Language Files

Editing Text in Language Files

Selecting a New Language File for a Product

About the Language Files

Editing text in resource files

Applying Language File Updates

To create a new issue:

APPLIES TO:

SYMPTOM:

CAUSE:

RESOLUTIONS:

To access the Setup program:

To Run the Setup:

Background

Resolution

Background

Resolution

Gantt View Basics

To have content displayed in the widget the following events need to occur:

Default Resource Report Behavior

The following configuration options are available:

Applies To

Calendar Plus

Chart Plus

Cross List

Data-Viewer

List Rotator

List Search

Mini Calendar

Navigators

Password Change

PM Central

Team Calendar

Virtual Map View

To create a PM Central Project or Department site:

To create a PM Central project site:

To create a PM Central Department site: