Archive for the 'Quest Migration Manager' Category

Migration Manager – Office 365 Preparation

Aug. 29th 2014

Migration Manager – Office 365 Preparation

Office 365 provides many services for organization wide communication and productivity.  With the growing maturity of the Office 365 product, many organizations are migrating their email and instant messaging services from on premise solutions to cloud (hosted) based solutions.  To aid in this migration, Dell Migration Manager is able to assist in performing the Exchange Migration from on premise Exchange to Office 365 successfully.

There are some preparations that are needed to the Office 365 Tenant before it may be used as part of a migration project within Dell Migration Manager.

Configure Domains in Office 365

This step will enable your migration domains as an accepted domain within the Office 365 Tenant.  With these domains present in the Office 365 configuration, Migration Manager will be able to propagate the source email address to the Office 365 mailbox.

The Steps in adding a managed domain in Office 365 are:

  1. Navigate to Admin->Office365->Domains->Add a domain
  2. Enter your domain name and click next
  3. Verify your domain ownership by creating a TXT record in your public facing DNS using the information provided in the wizard screen. (An MX record may be used instead of a TXT record, but the TXT record is the safer method)
  4. Once the DNS entry has been added and propagated, click the Done, Verify Now button.

You can also use the PowerShell cmdlet New-MsolDomain to add your domains.  See for information on how to use the cmdlet.

Create Admin Accounts

Migration Manager needs three Admin account to perform its tasks. The three Admin accounts are for provisioning accounts, synchronizing calendars, and migrating mailboxes. An Exchange Online license will be required for each of these accounts. The next step is to launch PowerShell and ensure that unsigned scripts may be executed. This is accomplished with the command:

Set-ExecutionPolicy -Execution Policy Unrestricted

If this command fails because of permissions, close PowerShell and run PowerShell as administrator.Now, the QMM module must be imported for usage. Navigate to <CD>\QMMEx ResKit\Scripts\CreateQSAdminAccountsInMSOL and execute the following command:

Import-Module .\CreateQSAdminAccountsInMSOLModule.ps1

Lastly, execute the following command to create the accounts from the CSV in Office 365:

Create-QSAdminAccountsInMSOL <CSV> <User> <Password> <Tenant domain>.onmicrosoft.comWhere <CSV> is the CSV file created containing the user accounts to be created. This must be specified fully qualified, i.e. C:\Temp\QMMAccounts.csv, or dot sourced, i.e. .\QMMAccounts.csv if the CSV is located in PowerShell’s current working directory.

The <User> and <Password> are credentials of a Global Administrator user that already exists in Office 365. The cmdlet will use these credentials to connect to and create the user accounts listed in the CSV.

Finally the <Tenant Domain> is the domain that is assigned to the Office365 tenant when it is created. All Office365 tenant have a domain such as this.

After executing this script, all the users specified in the CSV will be created in the Office 365 tenant with the Global Administrator and ApplicationImpersonation roles assigned.

NOTE: Three accounts is the minimum recommended number of accounts for an on premise to Office365 migration, but multiple account for the mailbox migration and calendar synchronization processes may be necessary for increasing the migration performance.


Configure Regional Settings for Admin Accounts

When the Global Admin accounts are created, they have no region information specified in them. If this is left un-configured, Migration Manager will report errors about the time zone being incorrect. This setting is assigned on a user by user basis and each of the Global Admin accounts above must be logged into individually to set their regional information. After the account is logged in, click the Outlook link at the top of the page and select the appropriate time zone and language for the account.


Disable Calendar Repair Assistant

When migrating with Migration Manager, the Calendar Repair Agent must be disabled for all mailboxes will be migrated for the entire duration of the migration. The following command will disable the CRA for all mailboxes in Office365:

Get-Mailbox -ResultSize Unlimited | Set-Mailbox -CalendarReparDisabled $true

The reason behind this step is that, because of Calendar Sync delay, the CRA will see that the user has accepted the meeting but the meeting does not appear on the users’ calendar.  Because of this, the CRA will add the meeting to the users’ calendar and this will result a duplicate calendar entry as soon as the sync creates the entry.

Of course the above command must be issued from the MSOL PowerShell interface

Once the steps above have been completed, the Office 365 Tenant will be ready for insertion into a QMMEX project as the destination.


Author: Russ Burden, Technical Architect, LeadThem Security

Posted by bc-admin | in Migration Manager for Exchange, Quest Migration Manager | Comments Off on Migration Manager – Office 365 Preparation

Migration Manager for Active Directory RUM Utility

Aug. 29th 2014

Resource Updating Utility (RUM)

To Move With or Without Agents that is the question


Perform the task remotely default is checked when moving a computer. What does it do?



If you uncheck what does that do?


We are mainly talking with in the moving feature of RUM.


Moving A computer with RUM when using rum to move a computer you have a choice of Agent vs Agentless. There is only one main thing to think of when deciding whether to use agent or agentless during your move process. Do you have Multiple Sites? Yes… you want to do an Agent Move; No… Either would be fine.


Agent Move

·         Is done on the local computer

·         Talks to the local Domain controllers closest to the computer

Agentless move

·         Is done on the RUM box

·         Talks to the Domain Controllers closest to the Rum Box


When you have a multisite AD installation you have to wait on replication by default can take between 15 and 45mins depending on the number of sites and replication partners. If you do an agentless and the rum server is in a different site then you will be waiting on replication. If you do an agent based move you add the computer to the site that the computer is on and will not have to wait on replication.

Author: Wayne Thompson, Technical Architect, LeadThem Security

Posted by bc-admin | in Quest Migration Manager | Comments Off on Migration Manager for Active Directory RUM Utility

Updating MAPI CDO

Aug. 21st 2013


Have you updated Exchange 2010 SP3? What about your MAPI CDO for you Quest boxes?  Most people forget about updating their MAPI CDO. With the latest installs I have done I have noticed that the latest updates for exchange 2010 SP3 are now requiring that you use the May 2013 update of MAPI CDO in order for MAPI CDO required programs to run.

To update MAPI CDO:

  1. Download the Latest update
  2. Stop all services that use MAPI CDO
  3. Uninstall old version of MAPI CDO
  4. Install new version of MAPI CDO
  5. Reboot
  6. Start Services that you stopped

Article By: Wayne Thompson, LeadThem Security Exchange Architect






Posted by bc-admin | in Quest Migration Manager | Comments Off on Updating MAPI CDO

QMM 8.9 Automation Error *FIX

Aug. 21st 2013


Here is the Fix for this error:

If you are encountering an error in the public folder sync for some of the PST files

“PowerShellCmdExec::Init  Error  440  Automation error”

QUEST Article 101427

This hotfix only applies to exchange agents MTA,MSA,CSA in order to fix public folder agents you must

  1. Apply The hotfix
  2. Stop all Quest Services on the box with the issue
  3. Reinstall MAPi CDO
  4. Run QMMExInstallAssemblies.bat in the QMM install directory
  5. Reboot QMM Box that has the issue

Article By: Wayne Thompson, Exchange Architect






Posted by bc-admin | in Quest Migration Manager | Comments Off on QMM 8.9 Automation Error *FIX