Skip to main content

How to Remove a Failed Move Request for the Current Batch of Exchange 2013 to Office 365

1. MS Blog: https://docs.microsoft.com/en-us/office365/enterprise/powershell/connect-to-office-365-powershell

2. Open Powershell as an Administrator and install the AzureAD Powershell Modules on your Windows 10 machine.

3.  Install-Module -Name AzureAD (Doesn't seem to work on W2012 R2 Server)


4. Login with your Office365 Account (You have to be a Global admin). Type in Connect-AzureAD


5. After you type in the password you will get this screen:


6. Connect to Office 365 through PowerShell from the elevated prompt on your local Windows 10 Machine.

PS C:\Windows\system32> $UserCredential = Get-Credential

7. Sign-in to Office 365 with Administrator Account

8. Run this command so that you are connected via PowerShell (no there is no GUI):

PS C:\Windows\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

 9. Turn off the pain in the neck prompts:

 PS C:\Windows\system32> Import-PSSession $Session -DisableNameChecking

 10. Check your batch that is migrating:

 PS C:\Windows\system32> Get-MigrationBatch | fl

 11. Get your Move Request (See what's failed)

 PS C:\Windows\system32> Get-MoveRequest

 12.  Remove the Completed Jobs (Optional):

 PS C:\Windows\system32> Get-MoveRequest -movestatus completed | remove-moverequest

 13. Delete all of them:


PS C:\Windows\system32> Get-MoveRequest -MoveStatus Failed | Remove-MoveRequest

 14. Delete one at a time.

 PS C:\Windows\system32> Get-MigrationUser

 Kill the failed jobs:

 Bruce_Lee@insomniacloud.com                      Final2-12.12.2018              Failed


PS C:\Windows\system32> Remove-MigrationUser Bruce_Lee@insomniacloud.com

Confirm
Are you sure you want to perform this action?
Remove the migration user "Bruce_Lee@insomniacloud.com"?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): A



Reference Blogs:
https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell?view=exchange-ps

 https://glazenbakje.wordpress.com/2013/12/04/exchange-2013-remove-complete-moverequest-list-via-powershell/

 http://www.expta.com/2015/08/exchange-2013-migration-batch-completes.html

 https://practical365.com/exchange-server/completing-individual-move-requests-migration-batch/

 https://vkarps.wordpress.com/2017/04/05/o365-exchange-one-liners/



Popular posts from this blog

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of " The /storage/core filesystem is out of disk space or inodes" Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480 Step 2: Enable SSH and Bash Shell Step 3: Login as root and type "shell" at Command> shell Step 4: df -h (Check if it's out of space) /dev/mapper/core_vg-core               50G   50G     0 100% /storage/core Step 5: Stop the services of VCSA:  hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped) Step 6:  cd /storage/core Step 7: rm -rf *.tgz ( be CAREFUL ...do this in the wrong directory and you will be retrieving from a backup .) If you need help. Go to Cybercity ( http://www.cyberciti.biz/faq/delete-all-files-folder-linux/ )  Step 8: service vmware-vpxd restart Step 9: history -c Step 10:  Refresh the browser (https://ip address:5480). Now it's all green VMware KB
Read more

VMware Tools ISO Does Not Exist

1. You attempt to Install VMware Tools and you get the following error: The required VMware Tools ISO image does not exist or is inaccessible. vix error code = 21001 Unable to install VMware Tools. An error occurred while trayin got access image file "/user'/lib/vmware/isoimages/windows.iso" needed to install VMware Tools: 2 (no such file or directory). Please refer the product documentation or KB article 2129825 for details....blah blah blah you get the point. First...that KB article is wrong. It's 1036810: https://kb.vmware.com/s/article/1036810 2. Go to the latest VMware Tools of your OS (You don't need to be logged in): https://packages.vmware.com/tools/esx/latest/index.html 3. Download the ISO and then WinSCP the file or whatever method you want to use to copy the file to /usr/lib/vmware/isoimages/ The quick and easy way is to just mount it and then install the VMware Tools. If you want to get gritty! Follow on! 4. If you don't
Read more

How to Login to AWS using CLI with AzureSSO through Azure Active Directory

Testing on Windows 10 Release 1909  Prerequisite (Install Visual Studio Code and the AWS CLI if you don't have it already installed and your Azure Active Directory is already configured and processing authentication) 1. Install Node.Js https://nodejs.org/en/ (Use the LTS Edition/Version) 2. Check the node version in PowerShell or Windows Terminal: node --version && npm --version 3. npm install -g aws-azure-login *install will take about 15-20 minutes. Be patient and let it finish.  4. Configure your profile aws-azure-login --configure --profile=<<Name of your profile>> Example:  aws-azure-login --configure --profile=migrationking Pro Tip: It installs the profile on your machine under ~/.aws/config . You can edit the file with Visual Studio Code or Notepad++ #This will prompt to Enter the Azure AD details *** Azure Tenant ID: << Enter the Azure AD Tenant ID from the Azure AD application configuration for the AWS Account to be accessed>> Azure Tenant I
Read more