.png)
Remove-SPManagedPath
Published: May 12, 2010
Deletes the specified managed path from the specified host header or Web application.
Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]
Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> -HostHeader <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]
Parameters
1Parameter | Required | Type | Description | ||
Identity | Required | Microsoft.SharePoint.PowerShell.SPPrefixPipeBind | Specifies the name of the managed path to delete. For example, in the URL http://sitename/sites/site1, "sites" is the name of the managed path. | ||
WebApplication | Required | Microsoft.SharePoint.PowerShell.WebApplicationPipeBind | Specifies the identity of the Web application that hosts the managed path to delete. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid Web application name (for example, WebApplication1212); or a valid name, in the form WebApp2423. | ||
AssignmentCollection | Optional | Microsoft.SharePoint.PowerShell.SPAssignmentCollection | Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
| ||
Confirm | Optional | System.Management.Automation.SwitchParameter | Prompts you for confirmation before executing the command. For more information, type the following command: get-help about_commonparameters | ||
WhatIf | Optional | System.Management.Automation.SwitchParameter | Displays a message that describes the effect of the command instead of executing the command. For more information, type the following command: get-help about_commonparameters |
Note: Parameter | Required | Type | Description | ||
Identity | Required | Microsoft.SharePoint.PowerShell.SPPrefixPipeBind | Specifies the name of the managed path to delete. For example, in the URL http://sitename/sites/site1, "sites" is the name of the managed path. | ||
HostHeader | Required | System.Management.Automation.SwitchParameter | Specifies that the Identity is a host header managed path. | ||
AssignmentCollection | Optional | Microsoft.SharePoint.PowerShell.SPAssignmentCollection | Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
| ||
Confirm | Optional | System.Management.Automation.SwitchParameter | Prompts you for confirmation before executing the command. For more information, type the following command: get-help about_commonparameters | ||
WhatIf | Optional | System.Management.Automation.SwitchParameter | Displays a message that describes the effect of the command instead of executing the command. For more information, type the following command: get-help about_commonparameters |
Detailed Description
This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and you may not combine parameters from different parameter sets. For more information about how to use parameter sets, see Cmdlet Parameter Sets.
The Remove-SPManagedPath cmdlet deletes the managed path specified by the Identity parameter from the host header or the Web application. The Identity must be the partial URL of the managed path to be deleted.
If you are using host headers, specify the HostHeader parameter. To delete a HostHeader managed path, provide the HostHeader switch. Otherwise, you must specify the Web application that contains the managed path to be deleted.
Input Types
Return Types
----------------------EXAMPLE 1----------------------------
Remove-SPManagedPath "sites" –HostHeader
This example removes the sites managed path from the list of HostHeader managed paths.
Depending on the confirmation level of the local system, the preceding example can prompt prior to execution.
------------------EXAMPLE 2-----------------------
Get-SPWebApplication | Remove-SPManagedPath "personal" –confirm:$false
This example removes the personal managed path from all Web applications in the farm. This command does not prompt for confirmation.
Change History
| Date | Description | Reason |
|---|---|---|
|
May 12, 2010 |
Initial publication |
|
