foreach ($i in (Get-Mailbox | Where
{$_.ExchangeVersion.ExchangeBuild.Major -eq 14})) {
New-MailboxExportRequest -Mailbox $i -FilePath
"\\AZUA\Exports\${$i.Alias).pst" }http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/Para llamarlo desde un csv: foreach ($i in (Import-Csv .\exports.csv)) {
New-MailboxExportRequest -Mailbox $i.Alias -FilePath
"\\AZUA\Exports\$($i.Alias).pst" }
Outlook 2003 has an automatic completion for any email address that you try to type into the To or CC fields. This feature does not pull from the contacts or address book, because you may have tried to email somebody that wasn’t in your contact list, and it will still add that to the auto complete list.
The problem comes in when you put in a bad address, and then every time you go to type in the email address, the incorrect one appears in the auto complete list.
To fix this problem, there are two ways around this. The easiest way is this:
The other way is by opening the profile folder and deleting the .nk2 file.
%APPDATA%\Microsoft\Outlook
This article investigates message queues in Exchange 2007. I begin by highlighting the differences in architecture between Exchange 2003 and 2007 in particular, discussing the fact that Exchange 2007 uses a queue database. I then discuss the new look queue viewer in Exchange 2007 and what it actually does! Finally I take a look at how the queue viewer is built on PowerShell and suggest some ways in which that could be useful!
So where does this database fit in? Well as mentioned briefly above, all queue activity now occurs in a new ESE database. The main database file is called mail.que and by default can be found here:
C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue
Figure 6: Folder containing queue database files
The other files are in the locations as described below:
You might wonder what happens with the logs in this scenario. Well, they are configured for circular logging with transaction logs being deleted after they have been committed.
Just before we move on to another area, it is worth stating how to move the queue databases. One important reason for moving the Queue DB and logs is performance. Another slightly less well known reason is that the drive on which the Queue DB and logs are stored must have 4GB or more free space otherwise the server will apply back pressure and start slowing the flow of messages!
When moving the DB, the usual rules for splitting transaction logs and DB files apply. To move the databases you must edit the EdgeTransport.exe.config file which by default is located at the location below and then stop and restart the msexchangetransport service:
C:\Program Files\Microsoft\Exchange Server\Bin\EdgeTransport.exe.config
The key thing to bear in mind before editing the config file is that the parent directory has the correct permissions as set up below; that way the directory will be created for you:
The relevant lines are shown below. To move the database, you should edit the line containing “QueueDatabasePath” and to move the logs, you should edit the line containing “QueueDatabaseLoggingPath”. You can see in Figure 7 that I have moved my DB and logs to H:
Figure 7: Editing the EdgeTransport.exe.config file (click to view a larger image)
Having looked at the Database it is now time to understand what it contains. There are various different queues:
When you use the move request cmdlets to move mailboxes, MRS processes the move process. As stated earlier, MRS resides on an Exchange 2010 Client Access server and is the service that moves mailboxes from the source database to the target database. In Exchange 2007, the mailbox move is performed by the Move-Mailbox cmdlet. By using a service as the agent of the move, mailboxes can be moved while simultaneously remaining accessible to users. During the move, you can view, cancel, and manage the move request from any Exchange 2010 server in your organization.
The following describes a remote mailbox move scenario:
New-MoveRequest -Identity 'tony@fourthcoffee.com' -TargetDatabase DBa -RemoteHo
stName 'CAS01.fourthcofee.com' -RemoteCredential (Get-Credential Atlanta\Admini
strator) -TargetDeliveryDomain 'mail.contoso.com'
When mailboxes are moved from an Exchange 2010 SP1 database to any other database, Exchange doesn't fully delete the mailbox from the source database immediately upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state. Mailbox data can be accessed during a mailbox restore operation using the MailboxRestoreRequest cmdlet set. The soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires or you use the Remove-StoreMailbox cmdlet to purge the mailbox.
http://technet.microsoft.com/en-us/library/dd298174.aspx
