Rename-WebConfigurationLocation
Renames a configuration location.
Syntax
Rename-WebConfigurationLocation
-Name <String>
-NewName <String>
[-Recurse]
[[-PSPath] <String[]>]
[-WhatIf]
[-Confirm]
[<CommonParameters>]
Description
The Rename-WebConfigurationLocation cmdlet renames the specified configuration location with the new name provided.
Examples
Example 1: Rename a configuration location
IIS:\> Rename-WebConfigurationLocation -Name "Default Web Site/oldApp" -NewName "Default Web Site/newApp" -PSPath "IIS:\"
This command renames a configuration location on the default website from oldApp to newApp.
Parameters
-Confirm
Prompts you for confirmation before running the cmdlet.
Type: | SwitchParameter |
Aliases: | cf |
Position: | Named |
Default value: | False |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Name
Specifies the current name of the configuration location.
Type: | String |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | True |
Accept wildcard characters: | False |
-NewName
Specifies the new name of the configuration location.
Type: | String |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | True |
Accept wildcard characters: | False |
-PSPath
Specifies an IIS configuration path to the location.
Type: | String[] |
Position: | 1 |
Default value: | None |
Required: | False |
Accept pipeline input: | True |
Accept wildcard characters: | False |
-Recurse
Indicates that the cmdlet renames location tags defined lower in the location hierarchy.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Type: | SwitchParameter |
Aliases: | wi |
Position: | Named |
Default value: | False |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Related Links
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour