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. 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. 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): |
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 
). The Assembly Name licensed with this key will be displayed. Ensure it is the product you expect and then click Deactivate.
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.
User Account Setup allows SharePoint users designated by an IT administrator to add users on their own rather than relying on IT personnel to create the accounts. You can create a new authentication provider account (ADS, NT, and SQL Membership) and at the same time add the account to defined SharePoint groups in different sites. With the Active Directory authentication provider, you also can customize the information collected by defining additional attributes to be populated in both ADS and SharePoint.
SharePoint 2013:
User Manager for Sites also has a Settings menu on its tool bar. This button is only available to Site Collection administrators. It is hidden for all other users. Once these settings are configured, they are global for all User Manager for Sites web parts within a Site Collection.
You will find many of our products complement each other quite nicely saving you the time and trouble to write custom code. With Bamboo at the heart of your SharePoint investment, you gain access to a huge catalog of enhancements, components, and accessories that add the critical functionality your business requires.
When a new account is created, User Account Setup can assign the new account to Active Directory security groups at the same time. Check the option Add user to Active Directory security group to enable this feature. When you select this option, the following additional settings are available:
Check this option to allow the requestor to choose the OU to add the account to. You can provide a list of several possible OUs.
. The OU will be removed from the displayed list.
) button.
The Automatically Create Columns in SharePoint User Information List option is enabled only if the User Account Setup Web Part instance is installed on a SharePoint Foundation 2013 site. When User Account Setup Web Part creates an account, it will attempt to copy account attributes in the Account Details list to a column with the same name in the SharePoint User Information List. The account information is then visible in the SharePoint profile. If a column with the same name does not exist, User Account Setup Web Part can create the column automatically in the User Information List.
The Account Details section lets you define the account attributes to enter in User Account Setup. The minimum attributes required to create an account in Active Directory are configured by default.
To add a new attribute to the User Account Setup Web Part form, click the Add a Field button above the attribute list and define the attribute properties.
If User Account Setup is configured to use the Active Directory Services authentication provider, the Active Directory Services settings tab is active in the Web Part Settings page, and the following additional settings are available to define account attributes, group membership, and SharePoint groups and permissions for Active Directory Services accounts:
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.
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.
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.