Applies to: Exchange Server 2007 SP3, Exchange Server
2007 SP2, Exchange Server 2007 SP1
Topic Last Modified: 2009-09-01
Use the Remove-PublicFolderDatabase cmdlet to delete public folder databases.
Syntax
Remove-PublicFolderDatabase -Identity
<DatabaseIdParameter> [-Confirm [<SwitchParameter>]]
[-DomainController <Fqdn>] [-RemoveLastAllowed
<SwitchParameter>] [-WhatIf [<SwitchParameter>]]
|
Parameters
Parameter | Required | Type | Description |
---|---|---|---|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter |
The Identity parameter specifies a public folder database. You can use the following values:
If you do not specify the server name, the cmdlet will search for databases on the local server. If you have multiple databases with the same name, the cmdlet will retrieve all databases with the same name in the specified scope. |
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm parameter causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm parameter. |
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
To specify the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to the Active Directory directory service, include the DomainController parameter in the command. |
RemoveLastAllowed |
Optional |
System.Management.Automation.SwitchParameter |
If included, the RemoveLastAllowed parameter enables removal of the last public folder database in the organization. |
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf parameter instructs the command to simulate the actions that it would take on the object. By using the WhatIf parameter, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf parameter. |
Detailed Description
Caution: |
---|
Removing a public folder database can have a broad range of
serious consequences. (This is particularly true when removing the
last public folder database in the organization.) For a detailed
discussion about the effects of removing a public folder database
and guidance on best practices, see How to Remove a Public
Folder Database. If you want to remove the last public folder database on a specific Exchange 2007 server, you must move all the replicated public folders to another store by using the MoveAllReplicas.ps1 script. The MoveAllReplicas.ps1 script changes the server in the replica list for all public folders to another server. After the folders have been replicated, you can remove the public folder database from the Exchange 2007 server. If you delete replicated public folders before you move the public folders, the deleted public folders may replicate before the public folder database can be deleted. In this case, the public folder data is also deleted from the other public stores. |
To use the Remove-PublicFolderDatabase cmdlet, the account you use must be delegated the following:
- Exchange Organization Administrator role
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
Input Types
Return Types
Errors
Error | Description |
---|---|
|
Exceptions
Exceptions | Description |
---|---|
|
Example
This example demonstrates how to remove the database named "MyServer\Second Storage Group\Public Folder Database" after all the prerequisites for removing the database have been satisfied.
Copy Code | |
---|---|
Remove-PublicFolderDatabase "MyServer\Second Storage Group\Public Folder Database" |