Import-Mailbox fails occasionally

To import data from a .pst file, you must run the Import-Mailbox cmdlet from a 32-bit computer that has the following installed;

# 32-bit version of the Exchange management tools (download link : )
# Microsoft Office Outlook 2003 Service Pack 2 (SP2) or later versions

a few good articles ;

Check info:

1.      Please add parameter “-verbose” at the end of the Import-Mailbox and reproduce the issue, which can give us more info to narrow down the cause
2.      Is there any related error or warning event in the application log on the both client and exchange server?
3.    Make sure the mailboxes has been exported on the same version Outlook as you use on your import machine


1. Please make sure that outlook and any MAPI connections are closed prior to running the Import-Mailbox
2. Use outlook 2003 instead of outlook 2007 on the workstation if outlook is to remain open during the process
3. If using outlook 2007, ensure that outlook is logged in using the same credentials as the Import-Mailbox PowerShell window
4. Do not launch PowerShell under the “Run As” method. Instead log into Windows as the desired account with permission to the mailbox and launch PowerShell normally
5. If running Windows XP and getting the error: “PowerShell.EXE has encountered a problem and needs to close.  We are sorry for the inconvenience” – Make sure it dosent get connected to a READ-ONLY domain controller. It will not show up in the log of a XP computer, but trying the same on a Windows 7 and it will show that it connects several times during the import, but if it at one point hits a RODC, Powershell will crash. easy solution just add static entries for the domain to your hosts file.

ConfigMgr 2007 Maintenance Tasks

Common Daily Maintenance Tasks

Some common daily maintenance tasks are listed below:

  • Verify that predefined maintenance tasks scheduled to run daily are running successfully.
  • Check Configuration Manager 2007 site database status.
  • Check site server status.
  • Check Configuration Manager 2007 site system inboxes for backlogs.
  • Check site systems status.
  • Check client status.
  • Check the operating system event logs on site systems.
  • Check the SQL Server error log.
  • Check system performance.

Common Weekly Maintenance Tasks

Some common weekly maintenance tasks are listed below:

  • Verify that predefined maintenance tasks scheduled to run weekly are running successfully.
  • Delete unnecessary files from site systems.
  • Produce and distribute end-user reports if required.
  • Back up application, security, and system event logs and clear them.
  • Check the site database size and verify that there is enough available disk space on the site database server to allow the site database to grow.
  • Perform SQL Server database maintenance on the site database according to your SQL Server maintenance plan.
  • Check available disk space on all site systems.
  • Run disk defragmentation tools on all site systems.

Common Periodic Maintenance Tasks

Some common periodic maintenance tasks are listed below:

  • Review the security plan for any needed changes.
  • Change accounts and passwords if necessary according to your security plan.
  • Review the maintenance plan to verify that scheduled maintenance tasks are scheduled properly and effectively depending on configured site settings.
  • Review the Configuration Manager 2007 hierarchy design for any needed changes.
  • Check network performance to ensure changes have not been made that affect site operations.
  • Verify Active Directory settings affecting site operations have not changed. For example, you should ensure that subnets assigned to Active Directory sites used as boundaries for a Configuration Manager 2007 site have not changed.
  • Review the disaster recovery plan for any needed changes.
  • Perform a site recovery according to the disaster recovery plan in a test lab using a backup copy of the most recent backup snapshot created by the Backup ConfigMgr Site Server maintenance task.
  • Check hardware for any errors or hardware updates available.
  • Check overall health of site.

Delete all packages from DP

Delete all packages? This should do it.

(replace MyLABServer) with site servername, and LAB with site code (in powershell 2.0):

$pkgs = gwmi sms_package -computer MyLabServer -namespace rootsmssite_LAB

$pkgs | % {$_.Delete()}

This does all classic packages.  If you want to do others, you’ll have to change the class – sms_DriverPackage, sms_ImagePackage, etc…