barcodefield.com

Managing the mailbox and the public folder databases in .NET Printing barcode 3/9 in .NET Managing the mailbox and the public folder databases




How to generate, print barcode using .NET, Java sdk library control with example project source code free download:
Managing the mailbox and the public folder databases using vs .net tocompose 3 of 9 in asp.net web,windows application Data Matrix Encoding Data The Exchange Managem visual .net 3 of 9 barcode ent Shell provides a set of cmdlets for both mailbox and public folder database management. In this recipe, we will take a look at how you can use these cmdlets to create, change, or delete mailbox and public folder databases.

. How to do it... The process for mana VS .NET Code 3/9 ging mailbox and public folder databases is nearly identical: you just need to use the appropriate cmdlet for the job. Let"s start off with mailbox databases: 1.

To create a mailbox database, use the New-MailboxDatabase cmdlet, as shown in the following example:. New-MailboxDatabase -Name DB4 ` -EdbFilePath E:\Databases\DB4\DB4.edb ` -LogFolderPath E:\Databases\DB4 ` -Server EX01. 2. You can mount the .net framework barcode 3/9 database after it has been created using the Mount-Database cmdlet:.

Mount-Database -Identity DB4 3. The name of a dat bar code 39 for .NET abase can be changed using the Set-MailboxDatabase cmdlet:.

Set-MailboxDatabase -Identity DB4 -Name Database4 4. And, finally, you Visual Studio .NET 39 barcode can remove a mailbox database using the RemoveMailboxDatabase cmdlet:.

Remove-MailboxDatabase -Identity Database4 -Confirm:$false 6 . How it works... The New-MailboxDatab Code 3 of 9 for .NET ase cmdlet requires that you provide a name for your database and specify the server name where it should be hosted. In the previous example, you can see that we created the DB4 database on the EX01 server.

The EdbFilePath parameter specifies the location for your database file. Additionally, you can use the -LogFolderPath variable to identify the directory that should hold the transaction logs for this database. If no value is provided for either of these parameters, the database and log directories will be set to the default location within the Exchange installation directory.

Mounting a database is done as a separate step. If you want to create the database and mount it in one operation, pipe your New-MailboxDatabase command to the MountDatabase cmdlet, as shown in the following line of code:. New-MailboxDatabase -Name DB10 -Server EX01 Mount-Database The Mount-Database c mdlet can be used with both mailbox databases and public folder databases. The same is true for its counterpart, Dismount-Database, which allows you to dismount a mailbox or public folder database. As you saw previously, to rename a mailbox database we used the Set-MailboxDatabase cmdlet with the -Name parameter.

It"s important to note that, while this will change the database name in the Active Directory and therefore in Exchange, it does not change the filename or path of the database. Before running the Remove-MailboxDatabase cmdlet, you will need to move any regular mailboxes, archive mailboxes, or arbitration mailboxes to another database, using the NewMoveRequest cmdlet. Keep in mind that the removal of a database is only done logically in the Active Directory.

Later on, you will need to manually delete the files and directories used by the database running the Remove-MailboxDatabase cmdlet.. There"s more The process for addi ng, mounting, dismounting, renaming, and removing public folder databases is almost identical to the previous examples. For instance, to create a public folder database, use the following syntax:. New-PublicFolderData .net vs 2010 barcode 3/9 base -Name PFDB1 ` -EdbFilePath E:\Databases\PFDB1\PFDB1.edb ` -LogFolderPath E:\Databases\PFDB1 ` -Server EX01.

Mailbox and Public F older Databases Here you can see that we are using the same parameters that we used when creating a mailbox database. The only difference is that this time we are using the NewPublicFolderDatabase cmdlet. The same goes for the Set-PublicFolderDatabase and Remove-PublicFolderDatabase cmdlets that can be used to rename or remove a public folder.

The syntax is the same; you just need to use the appropriate cmdlet.. Understanding automatic mailbox distribution Exchange 2010 implem ents a new feature called automatic mailbox distribution. This allows you to omit the -Database parameter when creating or moving a mailbox and an agent determines the most appropriate target database based on a number of factors. The Mailbox Resources Management Agent, a cmdlet extension agent, is the application that runs in the background that handles this and it is enabled by default.

The benefit of this is that if you provision multiple mailboxes or move multiple mailboxes at one time without specifying a target database, the mailboxes will be distributed across all of the available mailbox databases in the current Active Directory site from where you are running the commands. Each mailbox database has two properties called IsExcludedFromProvisioning and IsSuspendedFromProvisioning. These control whether or not a database can be used for automatic mailbox distribution.

By default, both are set to $false, which means that every mailbox database you create is available for automatic distribution out of the box. If you intend to create a mailbox database used strictly for archive mailboxes or you don"t want mailboxes to be placed in a particular database automatically, you can exclude the database from being automatically used. To do so, use the following command syntax after the database has been created:.

Copyright © barcodefield.com . All rights reserved.