Activating Your Bamboo Product License

Overview of Licensing and and Product Activation

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

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

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

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

Active Directory Account Options

Configuring WF Conductor General Settings

Define the default account options for all new accounts created with Active Directory (AD) widgets.

When using the Create AD Account widget, the choices for this widget are as follows:

Cannot change password – the end user cannot change his own password so only the administrator can.
Password never expires – the user’s password remains active at all times without any expiration time.
Change password at next login – the user must change his password the next time he logs in.
Disable account – this option disables the user’s account.

General Settings

Active Directory Settings

Configuring WF Conductor General Settings

Configure available LDAP paths for managing Active Directory users with Workflow Conductor widgets and set default account options for new Active Directory accounts.

NOTE: If you don’t plan to use the AD widgets, you don’t need to configure this. See xxx for more information about hiding the AD widgets from Studio users.

LDAP Paths: Click the Add New LDAP Path button to enter a new Active Directory LDAP path. Active Directory users and groups in this path can be managed by Active Directory widgets in Conductor Studio.

LDAP Path: Enter a valid LDAP connection string using RFC 4516 format: ldap://host:port/DN?attributes?scope?filter?extensions
- Example 1: ldap://ldap.example.org/dc=example,dc=org
- Example 2: ldap://ldap.example.org/ou=ChildOU,ou=ParentOU,dc=example,dc=org
- Example3: ldap://ldapserver/ou=ChildOU,ou=ParentOU,dc=example,dc=org
LDAP Display Name: Enter the display name for the LDAP path in Active Directory widgets.
User Name/Password: Enter the account information for an account with permission to modify objects in this LDAP path. Active Directory widgets will run with the permission of this user.
Users and groups: Enter a list of users and groups who will be able to see this LDAP path in Active Directory widgets. Separate multiple entries with a semicolon (;). Users must be entered in the format DOMAINuser. Groups must be entered in the format [Group] (including the surrounding brackets).
Allow custom LDAP paths in widgets: Select this option to allow Conductor Studio designers to enter custom LDAP paths in Active Directory widgets.

General Settings

How to activate a Bamboo Site Collection Feature

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

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

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

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

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

Step

Action

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

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

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

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

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

Workflow Conductor Deployment Methods

Workflow Deployment

In Workflow Conductor 2.0 and higher, there are two deployment methods available for Conductor workflows. The method you select determines how the workflow is deployed from Conductor Studio to the SharePoint farm and where it is available for association to lists and libraries. The choice of deployment methods is a global option set in the Workflow Conductor Control Panel General Settings section, which is accessed through SharePoint Central Administration.

Each deployment method name and its features is detailed below. You can switch deployment methods at any time without affecting workflows that are already deployed, but new workflows will be deployed using the method currently selected in the Workflow Conductor Control Panel.

Solution Deployment

The Solution Deployment method is the only deployment option available for versions of Workflow Conductor prior to 2.0. This method has the following features and limitations:

Features	Limitations
Workflows are deployed to the SharePoint farm as a solution package (.wsp), like Visual Studio workflows. The solution is activated as a site collection feature for the site collection where the workflow was created. The workflow is automatically associated to the list where it was created. Each workflow can be associated to any list or library in all site collections in the Web application (after the site collection feature is activated) without using the Conductor Studio. Optionally configure workflow deployments for immediate workflow deployment or for scheduled workflow solution deployment.	Because the workflow is deployed as a farm solution, the application pool is recycled during the deployment. There may be a brief interruption in site availability during deployment. In order to use the Solution Deployment Method to deploy workflows using Workflow Conductor on Windows Server 2008, you must disable User Account Control (UAC) Admin Approval Mode or turn off UAC. UAC is a security component that allows an administrator to enter credentials during a non-administrator’s user session to perform occasional administrative tasks. Simple Publishing Method does NOT require a modification to UAC. See Configuring UAC for Workflow Conductor for more information. To deploy a new version of a workflow, you must either use a different name than the existing workflow or retract and then remove the existing workflow solution from the farm. Site workflows are not supported with this method.

Features

Limitations

Workflows are deployed to the SharePoint farm as a solution package (.wsp), like Visual Studio workflows. The solution is activated as a site collection feature for the site collection where the workflow was created.
The workflow is automatically associated to the list where it was created.
Each workflow can be associated to any list or library in all site collections in the Web application (after the site collection feature is activated) without using the Conductor Studio.
Optionally configure workflow deployments for immediate workflow deployment or for scheduled workflow solution deployment.

Because the workflow is deployed as a farm solution, the application pool is recycled during the deployment. There may be a brief interruption in site availability during deployment.
In order to use the Solution Deployment Method to deploy workflows using Workflow Conductor on Windows Server 2008, you must disable User Account Control (UAC) Admin Approval Mode or turn off UAC. UAC is a security component that allows an administrator to enter credentials during a non-administrator’s user session to perform occasional administrative tasks. Simple Publishing Method does NOT require a modification to UAC. See Configuring UAC for Workflow Conductor for more information.
To deploy a new version of a workflow, you must either use a different name than the existing workflow or retract and then remove the existing workflow solution from the farm.
Site workflows are not supported with this method.

Simple Publishing

Simple Publishing is a workflow deployment option introduced in Workflow Conductor 2.0. This method has the following features and limitations:

Features	Limitations
Workflow publishing does not require application pool recycling and therefore does not impact site availability. The workflow is automatically associated to the list where it was created, if published to the list. If published to the site or site collection, you can choose whether to associate it with the list where it was created. Workflows published to the site or site collection can be associated to specific content types when published (SharePoint 2010/2013 only). New versions of a workflow can be published with the same name without affecting current versions that are still running. In SharePoint 2010/2013, workflows can be published to a site or site collection, as well as a single list/library. Workflows can be published as a site workflow. Workflows published to a site or site collection can be reused in other lists in the same site or site collection without using the Conductor Studio.	A workflow may take slightly longer to start the first time while the workflow is compiled. After the workflow is compiled during the first run, subsequent runs should be slightly faster. For SharePoint 2007, workflows cannot be published to a site or site collection or as a site workflow. They can be published to a list only. For SharePoint 2010/2013, workflow reusability is limited by the scope you select (list, site, or site collection) when you publish the workflow.

Features

Limitations

Workflow publishing does not require application pool recycling and therefore does not impact site availability.
The workflow is automatically associated to the list where it was created, if published to the list. If published to the site or site collection, you can choose whether to associate it with the list where it was created.
Workflows published to the site or site collection can be associated to specific content types when published (SharePoint 2010/2013 only).
New versions of a workflow can be published with the same name without affecting current versions that are still running.
In SharePoint 2010/2013, workflows can be published to a site or site collection, as well as a single list/library.
Workflows can be published as a site workflow.
Workflows published to a site or site collection can be reused in other lists in the same site or site collection without using the Conductor Studio.

A workflow may take slightly longer to start the first time while the workflow is compiled. After the workflow is compiled during the first run, subsequent runs should be slightly faster.
For SharePoint 2007, workflows cannot be published to a site or site collection or as a site workflow. They can be published to a list only.
For SharePoint 2010/2013, workflow reusability is limited by the scope you select (list, site, or site collection) when you publish the workflow.

About Workflow Publishing Scopes

There are four different workflow scopes available for the Simple Publishing method, depending on your SharePoint version. You can allow any or all of the following scopes for workflow designers:

Scope	Description
Publish to List	When you publish a workflow to a list, the workflow is only associated to the list where the workflow was created. It is not reusable and cannot be associated to other lists. If you want to use the same workflow on another list, you can publish the workflow template again to the new list.
Publish to Site	When you publish a workflow to the site, it can be associated to any list or library in the site where the workflow was created. It is reusable. To associate a workflow to another list after it is published, use the Workflow Settings option in the List/Library ribbon or Settings page. NOTES: Publishing a workflow to a site is not the same as publishing a site workflow, which is a workflow that is associated to a site instead of a list. This scope is available in Workflow Conductor for SharePoint 2010 or 2013 only.
Publish to Site Collection	When you publish a workflow to the site collection, it can be associated to any list or library in any site in the site collection where the workflow was created. It is reusable. To associate a workflow to another list after it is published, use the Workflow Settings option in the List/Library ribbon or Settings page. NOTES: To publish a workflow to a site collection, Conductor Studio must be started from a list or library in the top-level/root site of the site collection. If you are on another site, the Publish to Site Collection option will be disabled. This scope is available in Workflow Conductor for SharePoint 2010 or 2013 only.
Publish as Site Workflow	When you publish a workflow as a site workflow, it is associated to the site where the workflow was created. It is not reusable and cannot be associated to other sites. If you want to use the same workflow on another site, you can publish the workflow template again to the new site. NOTES: Site workflows cannot use Current Item or Current List lookups, since they are not associated to a list and are not started on items. However, most other widget and workflow functionality can be used in a site workflow. This scope is available in Workflow Conductor for SharePoint 2010 or 2013 only. See an example of a site collection workflow using the Collect Data From User widget.

Access SP via REST

The Access SP via REST widget allows the workflow to read from and update items in an external SharePoint list and store the results in a workflow variable. The external site must have the Bamboo MashPoint REST Extensions installed, at which point the site is accessible as a REST service.

NOTE: Workflow Conductor widgets can access items in any site collection in the current Web application. Use the Access SP via REST widget only if you need access to items in other Web applications or other SharePoint farms.

SharePoint 2007 Server Administrator:: The Bamboo MashPoint REST Extensions installation package is available in the Workflow Conductor for SharePoint 2007 Setup application. To install the MashPoint REST Extensions, click on it in the Components list, and then click the Install button. Follow the installation instructions. After the MashPoint REST Extensions are installed, you can connect to the server using the Access SP via REST widget. For detailed installation instructions, refer to the section Installing the Product, or read the Bamboo Knowledge Base article KB.12582 – HOWTO: Install the Bamboo MashPoint REST Extensions.

SharePoint 2010 Server Administrator: The MashPoint REST Extensions are available for SharePoint 2010, but are no longer included in the Workflow Conductor Setup package. The Access SP via REST widget is disabled by default in Workflow Conductor for SharePoint 2010. For instructions to download and install the MashPoint REST Extensions and enable the Access SP via REST widget in Workflow Conductor, read the Bamboo Knowledge Base article KB.12582 – HOWTO: Install the Bamboo MashPoint REST Extensions.

Widget Limitations:** The MashPoint REST Extensions do not support FBA accounts.

The Access SP via REST widget connects to Bamboo MashPoint REST services only. Connection to SharePoint 2010 REST services is not currently supported.

Widget Properties:

Column	Description
REST Service Method (Required):	Click the button to define the connection properties and action to be taken on the external SharePoint list:
REST URL:	Enter the URL of an external SharePoint site where the MashPoint REST Extensions are installed. For example: http://server/mashpoint/1/
Username/Password/Domain:	By default, the widget will use the credentials of the workflow initiator to access the external SharePoint site. If this is the desired behavior of your workflow, leave these fields blank. Otherwise, you can enter specific login information for the widget to use to connect to the site. Any login information you enter is stored with the widget and used any time the workflow runs. Lists: After you enter a REST URL, click the Get List button to retrieve a set of available lists from the external SharePoint server. Select a list for the widget to use.
Action:	Available REST actions include: Get: This action returns a single field value from the selected list. Select the list field to get, and then select criteria to use to find the item in the list by choosing a field and providing a criteria value in the Equals box. The value can be explicitly defined or it can be defined using a lookup. For example: Get Field Where Field Equals Value Add: This action creates a new item in the selected list. Select a field, provide the desired value for the field, and then click Add. Do this for each field in the external SharePoint list for which you want to provide a value. Any values you provide can be explicitly defined or can be defined using a lookup. Update: This action updates one or more fields in a single item in the selected list. Select a field in the external SharePoint list that you want to update and provide a new value for the field. Do this for each field in the item that you want to update. Any value you provide can be explicitly defined or can be defined using a lookup. You must also select criteria to use to find the item in the list to be updated by choosing a field and providing a criteria value in the Equals box. For example: Update Field(s) to NewValue(s) Where Field Equals Value Delete: This action deletes a single item from an external SharePoint list. Select criteria to use to find the item in the list to delete by choosing a field and providing a criteria value in the Equals box. The value can be explicitly defined or it can be defined using a lookup. For example: Delete Where Field Equals Value
Variable Set To (Required):	Select a workflow variable with a Text data type to store the results from the REST call. Create variables in the Workflow Settings tab in the settings pane, or click the Create new variable link next to the variable list.
Click Apply to save the widget settings.

Example of Using Access SP via REST Widget

Return to External Data Widgets

About Workflow Conductor

Overview of Workflow Conductor Control Panel

To determine the release of Workflow Conductor that you have installed on your SharePoint farm, check either of these locations:

Workflow Conductor Control Panel
Workflow Conductor Studio

NOTE: The information from each location is slightly different. If you are having an issue with Workflow Conductor and a Bamboo Support Engineer asks you for the release information of your Workflow Conductor, send the information from both pages.

Top

From the Workflow Conductor Control Panel

Step	Action
1.	In SharePoint Central Administration, click the Workflow Conductor link to go to the Workflow Conductor Control Panel.
2.	In the Workflow Conductor Control Panel page, click About Workflow Conductor. The version information will be displayed.

Step

Action

In SharePoint Central Administration, click the Workflow Conductor link to go to the Workflow Conductor Control Panel.

In the Workflow Conductor Control Panel page, click About Workflow Conductor. The version information will be displayed.

About WFC.jpg

Top

From the Workflow Conductor Studio

Step	Action
1.	In the Workflow Conductor Studio ribbon click About.
2.	The Workflow Conductor release information will be displayed.

Step

Action

In the Workflow Conductor Studio ribbon click About.

About option in Conductor Studio ribbon.jpg

The Workflow Conductor release information will be displayed.
About WFC from ConductorStudio.jpg

About the Installation Files

Options for Installing

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

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

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

A license error occurs after successful license activation

SYMPTOM

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

license error on web part page.png

CAUSE

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

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

RESOLUTION

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

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

Step

Action

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

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

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

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

About Bamboo product Release Numbers

Overview

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

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

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

Where to find Release Notes

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

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

SharePoint 2007 (WSSv3/MOSS) Release Numbers

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

R1.2.3.0

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

SharePoint 2010 Release Numbers

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

10.2.3.0

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

SharePoint 2013 Release Numbers

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

10.2.3.2013

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