Migrator for Notes to Exchange & Coexistence Manager for Notes

Global Default Settings -> [DefaultAdminIni] DefaultAdminIniStatus


Can't find anything in the documentation about the parameter DefaultAdminIniStatus under [DefaultAdminIni] and [DefaultCommonIni] in the Global Default Settings.

We are running MNE with 25 MIG-servers (Windows Server 2012 R2, Outlook 2013 pro SV(Swedish) 32-bit, Notes 9.0.1).

The first MIG-server has Microsoft SQL server 2014. And for test purpose we have also installed SQL on a second server.

The instance on the first server has DefaultAdminIniStatus=Unloaded and the second server SQL instance has DefaultAdminIniStatus=loaded.

Can anyone give us some information about this parameter?

Thanks in advance.

The reason why we setup the second SQL instance, is that we presume that the first instance does not work properly. The filtering seemed not to work as it should. Renaming UserFolderPrefix=Mappar (Swedish for Folders) does not work and so on.

And one of the main problems is that MNE does not create “default” folders like inbox, Sent, Calendar, Contacts, Tasks, Drafts, Outbox, Journal, Junk E-mail with Swedish language?


/Lars Viding






  • Hi Lars,

    Thank you for posting in the Migrator for Notes to Exchange (MNE) community forum. I do want to assure you that the [DefaultAdminIni] and [DefaultCommonIni] parametes have no effect on any of the migration tasks. These are an internal housekeeping parameters that are used in product install and upgrade scenarios and should not be modified.

    The Global Default Settings are loaded from the database and should show all of the current settings. Any Migrator for Notes to Exchange (MNE) migration server connected to the same NME40DB database should show the same Global Default Settings.

    One item to note is that if there are any migration "Configuration Templates" in use, these can be out of sync with the current Global Default Settings. The Configuration Template only includes the Global Default Settings that were in place at the time that the Configuration Template was originally saved/created and do not update automatically. In this case, you can create a new Configuration Template or enable "Advanced Wizard Settings", edit the existing template, then click the new "Edit" button to manually change the INI file for this existing template.

    In regards to your issues migrating Swedish "default mailbox folders:

    Is the Swedish language installed in both Windows and Outlook on the MNE migration server? I believe you mentioned that Outlook 2013 has the Swedish language pack.

    What are the language and location settings of the MNE migration server? The following KB article discusses that the locale should be set in Windows to the target language:


    Here is a section in the MNE Administrator's Guide that discusses setting up MNE to migrate non-English languages:


    If you are still experiencing issues with the "default" mailbox folders not being created in Swedish, then we may need to investigate further. This may require a creating a Service Request so that we can review the MNE migration log files.

    Please let me know if you have any additional questions or need any additional clarification.


    Trevor Taegder
  • Hi Trevor,

    I did discover yesterday when looking in the log file that the migration job (template) did not load the Default Global Settings. And did choose the advance wizard and edit the settings. With your information about that template do not update automatic. All make sense now. Thanks.

    About the language of the default mailbox folders. We have hade a couple of migrations with correct results but somewhere in the beginning of December 2016 MNE change to English for these folders. Very disturbing. We have checked and double checked all settings and reinstalled Outlook2013 but with no change. In Exchange online the mailboxes do have the right language and regional settings. Did also discover that we could get the right language with the following powershell command.

    Set-MailboxRegionalConfiguration -Identity <> -LocalizeDefaultFolderName

    So if we can’t get it to right language when migrating we will go for this command to correct this afterword.

  • Hi Lars,

    Thanks for the update. If I understand you correctly, everything was migrating with the correct language until sometime in December. That is an interesting observation and brings up a few questions:

    1.) Did you upgrade Migrator for Notes to Exchange (MNE) during that time frame?

    2.) Are you migrating to on-premise Exchange, or Office 365?

    3.) If you are migrating to on-premise Exchange, were any updates applied during this time frame?