How can I update the MAPI profile on a user's desktop after mailbox objects are migrated to a differ (NETIQKB1100)

  • 7701100
  • 02-Feb-2007
  • 19-May-2009


Exchange Migrator 2.x
Exchange Migrator 1.x


How do I export a file that contains the Distinguished Name (DN) of all the migrated mailboxes?

How do I use the EMProfile Update utility to import a list of migrated mailboxes and updates the appropriate profiles on the client computers?

How do I use EMProfileUpdate to redirect the local Exchange profiles to the target Exchange server?

How do I pass the Microsoft Outlook switches through the EMPROFILEUPDATE utility?

How do I run EMPROFILEUPDATE for Remote Users?


To update a client's MAPI profile, complete the following steps:

Updating Migrated Client Profile

When you have completed your migration using Exchange Migrator, profiles on the client computers continue to point to the source Exchange server instead of reflecting the new target Exchange server.  To redirect client profiles, use the profile update utility named EMProfileUpdate that is included with Exchange Migrator.  EMProfileUpdate is located under \Program Files\NetIQ\Exchange Migrator as EMProfileUpdate.exe.  EMProfileUpdate imports a list of migrated mailboxes and updates the appropriate profiles on the client computers. You can use EMProfileUpdate on any of the following client operating systems:

          The EMProfile Update utility correctly updates mailbox profiles for users running the following email clients and operating systems:

§         Microsoft Outlook 97 running on Microsoft Windows 98

§         Microsoft Outlook 97 running on Microsoft Windows NT 4.x SP 6a

§         Microsoft Outlook 98 running on Microsoft Windows 98

§         Microsoft Outlook 98 running on Microsoft Windows NT 4.x SP 6a

§         Microsoft Outlook 2000 running on Microsoft Windows 98SE

§         Microsoft Outlook 2000 running on Microsoft Windows NT 4.x SP 6a

§         Microsoft Outlook 2000 running on Microsoft Windows 2000

§         Microsoft Outlook XP running on Microsoft Windows ME

§         Microsoft Outlook XP running on Microsoft Windows XP

§         Microsoft Outlook 2003 running on Microsoft Windows 2000 SP 3

§         Microsoft Outlook 2003 running on Microsoft Windows XP

EMProfileUpdate Pre-requisites

To use EMProfileUpdate you must make sure that the following pre-requisites have been met:

  • Migrate your Exchange mailboxes using Exchange Migrator.
  • Use Exchange Migrator to export a 'list' of migrated mailboxes that will be used as the input source for EMProfileUpdate.
  • Ensure that the users associated with migrated mailboxes have permissions to modify their Exchange profiles

Exporting the Migrated Mailboxes List

Exchange Migrator lets you export a file that contains the Distinguished Name (DN) of all the migrated mailboxes.  EMProfileUpdate inputs this list to ensure that the program modifies only the profiles of migrated mailboxes.

To export a list of migrated mailboxes from the Exchange Migrator MMC interface:

  1. Start Exchange Migrator.
  2. Select a project.
  3. Click Action on the menu bar.
  4. Click Export Migrated Objects on the Action menu.
  5. Save the file.

The file is named by default but you can change this name.  For ease of use, save the file in the folder where the EMProfileUpdate.exe file is located.  If you installed Exchange Migrator in the default location, the EMProfileUpdate.exe file is located in Program Files/NetIQ/Exchange Migrator.

Running EMProfileUpdate

Use EMProfileUpdate to redirect the local Exchange profiles to the target Exchange server.  EMProfileUpdate is executed from the Command Line Interface, where represents the name of the mailbox list file that was exported.  EMProfileupdate.exe is located on the Exchange Migrator console within the 'c:\program files\netiq\Exchange Migrator' directory by default.  You can either run EMProfileupdate.exe from that directory or copy it to a specific directory anywhere in your environment as long as the appropriate share permissions are set.

  1. Log on to the local computer with the user account associated with the migrated mailbox.
  2. If you have shared the folder containing EMProfileUpdate.exe and the migrated mailboxes list (, use the following syntax at the command prompt:


  3. If EMProfileUpdate.exe exists on the local computer, navigate to the folder containing EMProfileUpdate and the migrated mailboxes list and enter EMProfileUpdate.exe at the command prompt.

Using a Logon Script to Run EMProfileUpdate

You can use a logon script to run EMProfileUpdate to minimize user interaction with the EMProfileUpdate utility.

  1. Copy EMProfileUpdate.exe, your exported mailbox list, and the batch file you have created, to the default NETLOGON share on the domain c.
    ontroller.  You must also specify the logon script name in the user settings or in the Group Policy Object.

    • On a Windows NT4 primary domain controller, the NETLOGON share corresponds to the \WINNT\system32\Repl\Import\scripts folder.
    • On a Windows 2000 domain controller, the NETLOGON share corresponds to the \WINNT\SYSVOL\sysvol\DomainNamespace\scripts folder.

  2. Ensure the folder is shared and that Everyone has read permission.
  3. Create a batch file modeled on the following example:
    rem Example Logon Script Batch File
    rem Replace Computer with the name of the domain
    rem controller containing the share
    rem Replace Share with the name of the share. For
    rem example, replace Share with NETLOGON.
    rem Replace ExportedListName with the name of the
    rem exported mailbox list


For more information about creating logon scripts, see the Windows NT or Windows 2000 Help.

Additional Information

Formerly known as NETIQKB1100

In order to pass the Microsoft Outlook switches (Outlook 97Outlook 98Outlook 2000Outlook 2002) through the emprofileupdate utility you will need to do the following:  ( The following applies to Exchange Migrator 2.2 SP1 HF21235 and later.)  You can use the Microsoft Outlook switches to fix items such as reminders, reset mailbox folders, etc.  Search Microsoft Technet for further details about the available Microsoft switches available for your version outlook.

  1. Verify that the Microsoft Switches fix the problem on at least one problem mailbox without using Exchange Migrator.
  2. Run EMProfileUpdate with the appropriate switches on a few other problem mailboxes to be sure that the Outlook switches are passed correctly.
    • You will need to use the "-reprocess" switch if you have already tried running EMProfileUpdate on a mailbox.
  3. Once you are satisfied that it works correctly, then you can deploy the new command line text via the login script.

EMPROFILEUPDATE SYNTAX with the Microsoft /cleanreminders outlook switch:

  • EMPROFILEUPDATE [filename] [-RunOutlook | -RunOutlookAll][-OutlookOp "<options>"][-KeepOutlookOpen | -CloseOutlookAfterDelay <seconds>][-reprocess][-Help | -?]
  • Example at the command prompt:
    • C:\Program Files\NetIQ\Exchange Migrator> Emprofileupdate -RunoutlookAll -OutlookOp "/cleanReminders" -keepOutlookOpen -verbose - reprocess


  • [filename] - Specifies TAB file to use
  • -RunOutlook - Starts Outlook for each mailbox with an updated client profile
  • -RunOutlookAll- Starts Outlook for each client profile.  This is essentially a reprocess switch for the Outlook switches
  • -OutlookOp - Specifies command line options to pass to Outlook. If more than one option is provided, enclose set of options in quotation marks.
  • -KeepOutlookOpen - Leaves Outlook open after profile has been updated with Outlook command-line parameters. The default is for Outlook to close after 5 seconds.
  • -CloseOutlookAfterDelay - Specifies the delay time, in seconds, used to allow Outlook to process. The default value is 5 seconds.
  • -reprocess - Use this switch if you are trying to run EMProfileUpdate again on a mailbox that EMProfileUpdate was already run against.

Be sure that you have at least version of the EMPROFILEUPDATE.EXE utility if you have Outlook 97 clients.  When you run EMProfileUpdate.exe, the version will be shown in the command line interface window at the beginning of the processing.

How to run EMPROFILEUPDATE for Remote Users:

Possibility 1

  • Send an email noticification twice to the mailboxes that you are migrating prior to the migration, about one week ahead of time and then again the day before the migration. 
    • Let the end-users know that they must not run the batch file until after they have been migrated and that you will notify them prior to the date the mailbox will be migrated.
    • This email should contain a link to the location of the batch file you previously created.
    • Instruct the remote user to run the batch file from the link before trying to access email but after the mailbox migration.  Assure the remote users that even if they do access their email before they run the batch file it will not cause any damage.
      • Please note that if the remote user sends an email to someone before running the batch file, then the person that the recipient will see if they try to reply to the email.  This reply-to email address will only be temporary until the remote user runs the batch file.  Then the reply-to email address will be the correct email address (  
      • Note also that the remote user should not have to worry about the reply emails because those emails will still get to the target migrated mailbox successfully.
  • Migrate the mailbox.
  • The remote users should logon to a VPN or Dial up client and follow the steps in the email that you sent out prior to the migration.

Possibility 2:

  • Have the batch file automatically run when the end user logins to the VPN server.  This is dependent upon your VPN server having the capability to run a batch file and you are able to configure it.  NetIQ Technical Support cannot support the configuration of your VPN server.

Possibility 3:

  • Schedule a period of time (2 weeks to a month) in which the remote users can stop by the office, or ship their laptop in to be migrated with their profiles.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.