Export Mailbox to PST

To export a mailbox to PST is relatively a simple process but there are a few steps to do before you jump into this. Here are the steps:

  1. Grant the User access to the Role as by default there are not users assigned to the Import/Export Management role.
  2. Create a Network Share and Grant the Exchange Trusted Subsystem Read/Writes.
  3. Exporting the Mailbox
  4. Monitoring the Export

Granting Access to the Role:

  • New-ManagementRoleAssignment –Role “Mailbox Import Export” –User User

Granting Access to the Share:

granting access

Exporting the Mailbox:

  • New-MailboxExportRequest -Mailbox User -FilePath \\fileserver\pst\User.pst

Monitoring the Mailbox Export:

  • Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

If you want to Export a Users Mailbox Archive you need to include the “-IsArchive” option at the end of the command:

  • New-MailboxExportRequest -Mailbox User -FilePath \\fileserver\pst\User.pst -IsArchive

Hope it helps.

Advertisements

Error accessing mailbox that was re-connected

If you disable a user’s mailbox in Exchange 2010 it moves to the Disconnected Mailbox Container under Recipient Configuration in Exchange. Now when you re-connect the mailbox to the AD user and you try send an email to the account you get the following error:

#554-5.2.1 mailbox disabled 554 5.2.1 STOREDRV.Deliver.Exception:AccountDisabledException.MapiExceptionMailboxDisabled; Failed to process message due to a permanent exception with message Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group.

Solution:

Run the following command from Exchange powershell:

  • Clean-MailboxDatabase “databasename”

After this you should be able to send mails to the user and login to the mailbox.

Hope it helps.

Check Exchange 2010 internal and external URL’s

If you want to get a quick overview of all the URL’s of your virtual directories in Exchange 2010 you can run the following command:

  • Get-ActiveSyncVirtualDirectory | ft server,*lur* -AutoSize
  • Get-AutodiscoverVirtualDirectory | ft server,*lur* -AutoSize
  • Get-ClientAccessServer | ft name, *lur* -AutoSize
  • Get-EcpVirtualDirectory | ft server,*lur* -AutoSize
  • Get-OabVirtualDirectory | ft server,*lur* -AutoSize
  • Get-OwaVirtualDirectory | ft server,*lur* -AutoSize
  • Get-WebServicesVirtualDirectory | ft server,*lur* –AutoSize

Hope it helps

Install Exchange Remote Management tools on Windows 7 x64

Prerequisites List (Windows 7 x64):

  • Windows 7 Features:

Supported Operating Systems for running Exchange Management Tools:

  • Windows Vista 64-bit with Service Pack 2
  • Windows 7 64-bit
  • Windows Server 2008 64-bit with Service Pack 2
  • Windows Server 2008 R2

Installing Windows features:

Open up the control panel, click on Programs and then click on “Turn windows features On or Off:

setup1

Install the following features:

  • IIS 6 Management Console
  • IIS MetaBase and IIS 6 Configuration Compatibility.
  • Microsoft .NET Framework 3.5.1

Copy the Setup Files of Exchange 2010 to the windows 7 machine and extract it.

Right click on the setup file and choose “Run As Administrator”

setup2

  • Click Next to continue.

setup3

  • Accept the License Agreement and then click Next.

setup4

  • Make your selection and then click Next.

setup5

  • Click on Custom Exchange Server Installation, the box will indent.
  • Make sure the tick box is NOT selected and then click Next.

setup6

  • Select Management Tools as shown above, make sure the “Automatically install Windows roles” tick box is NOT selected.
  • Click Next.

setup7

  • Once the readiness checks have completed click the Install button. If there are any errors first fix those.
  • When the installation is complete click on the Finish button.
  • To Launch the Management Console click on Start -> All Programs -> Microsoft Exchange Server 2010 menu.

Installing Exchange 2010 Management Tools on Windows 7 x64 Error:

setup8

  • If you get the above error then make sure you didn’t select the tick box to install the server features.
  • Try launch the setup with “Run As Administrator” to get rid of this error.

Hope it helps.

Repair Exchange 2010 EDB to Access to Corrupted Mailbox Data

MS Exchange Server, an email server developed by Microsoft, is a contact manager-cum-calendaring software, which being a part of the Microsoft server line of products, runs on Windows server operating systems. Among the various versions of the Exchange Sever available today, Exchange Server 2010 is the most popular one. Nevertheless, it takes immense care to work efficiently.

Just like its previous versions, Exchange Server 2010 also possesses an EDB file (i.e. Exchange Database file) to store user’s Outlook mailbox data, including emails, contacts, calendar, tasks, notes, and other valuable information. Since the EDB file contains complete Outlook mailbox, you can actually figure out how significant it can be at the corporate level. Continue reading

Export Exchange 2010 Database into PST format with default utility

export pst

Importing data from or exporting data to .pst file format is extremely easy using   MailboxImportRequest and MailboxExportRequest cmdlet. These both sets are part of Exchange Management Shell, after user has submitted the request of Import or export, the process is carried out by Mailbox Replication Service (MRS). The Exchange Mailbox Replication Service is available in Exchange 2010 Client Access servers. The MRS is the sole application or service that is responsible for transferring mailboxes and importing and exporting .pst files. Let us focus upon the possible causes that prompt user to go for Importing or Exporting mailbox data: Continue reading

DPM 2012 SP1 Exchange Job Failed

Today I upgraded one of my branches DPM 2012 evaluation to SP1. After upgrading all agents I ran consistency checks and all passed except one, Exchange. The server gave the following error:

“Cannot create a recovery point because of a transient problem. (ID 215 Details: VssError: The shadow copy provider had an error. Check the System and Application event logs for more information. (0x80042306))

So the first thing I did was check the writers from a command prompt on the problem server, all good. I then ran Windows Update and RU2 for DPM was available. I installed this rollup, rebooted the server and then upgraded all the Agents again.

After this I ran a consistency check and it returned with an OK status now.

Hope it helps

Mailbox Exports stuck in a Queued Status

Today I am exporting mail to PST so I can start consolidating my Exchange Servers and when running the New-MailboxExportRequest command you might find that the mailboxes just stay in a queued status without processing. You can check this by running the following command:

Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

To fix the problem above simply open up Services.msc and restart the Microsoft Exchange Replication Service, give it a few min and if you run the above command you will see the Percentage Completed Column start showing you info instead of 0%.

Hope it helps

Windows 7 & Outlook 2007/2010 Password Prompts

Since the upgrade of Exchange 2010 from SP2 to SP3 and running office 2010 x64 on Windows 7 x64 I notice that outlook keeps prompting a handfull of users for their username and passwords. Some of the culprits I have picked up are as follows:

  • Windows 7 Credential Manager is not updating the information when a user updates their domain passwords.
  • Outlook 2010 is not set to NTLM password authentication.
  • In a hidden folder, Outlook stores multiple folders with passwords, if removed it prompts once and not again.

To fix the above, simply update credential manager with the new password, if you look at the date it will show when last it was updated.

Change the authentication for outlook to NTLM, close and open outlook.

Remove all the hidden folders and let outlook create them again.

Some might say it is an autodiscover issue but if you hold down CTRL and right click on the outlook icon next to the clock in the taskbar and test Email AutoConfiguration it should show the correct URL’s, if not then their is your problem.

Hope it helps.