Can’t Move Mailbox In Exchange 2010…

MS Exchange

This is one of the questions which gets asked repeatedly these days in online forums and hence thought of writing about it. As more and more companies are moving from Exchange 2003 to 2010, you will be moving mailboxes using the 2010 EMC or Shell cmdlet New-MoveRequest. While you can successfully move a mailbox from 2003 to 2010 or within 2010 (any scenario involving 2010), problems starts when you try to move the mailbox again to a different database or server.

Let me explain this with the help of an example. I moved an account (Chakka Rajith) from one database in my 2010 server to another one successfully & when I tried to move the same mailbox to a different database, I didn’t get the “New Local Move Request” option in the EMC.

No_Option

I then tried the New-MoveRequest cmdlet to accomplish the task, but was greeted with the error below, which was more explanatory.

Shell_Error

The problem is that once a mailbox is moved to a 2010 mailbox server, the move request has to be cleared before the mailbox can be moved again. Removing the move request clears all move related properties from the mailbox. To do that, launch EMC, navigate to Recipient Configuration -> Move Requests node. Right click the mailbox in question & select “Clear Move Request”. You can select multiple mailboxes to clear the properties in a single task.

Clear_Move

Click OK to confirm.

Confirmation

You can also run the command below to clear the move request.

Remove-MoveRequest –identity “username”

Clear_All_Shell

If there are more number of mailboxes, run Get-MoveRequest –MoveStatus Completed | Remove-MoveRequest

Clear_All

Once the above tasks have been executed, you will be able to move the mailbox again!

Other Popular Articles


MS Exchange

Scripting Agent Initialization Failed: “File is not found” Error During Exchange 2016 Setup

MS Exchange

EAC Access While Co-Existing Exchange 2013 With 2010

MS Exchange

Delete All Calendar Entries In An Exchange 2010 Mailbox

  1. Active Directory operation failed on mb2.domain.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

    Reply
  2. Hi, I'm in to the process moving my exch 2003 to exch 2010. The problem is, I don't get to see the mailbox of 2003 (legacy mailbox), once I get to see the legacy mailbox only I'll be able to make the local move. Please help!

    Reply
  3. What do you do with mailbox's that have "some corruption" in them?

    I have two (so far) they have messages like this:

    12/3/2010 4:21:00 PM [lcua67] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.

    Reply
  4. Hi Rajith,
    when I try to move a legacy mailbox from Exchange 2003 server on my new 2010 (same forest) through EMC, I receive an error. Exchange cannot found the db of Exchange 2003.
    Any idea?
    Thank you.

    Flaviano

    Reply
  5. Thanks for getting back to me. That's part of the problem. Because of the new forest, its not working. Right now, I'm just testing with some test user mailboxes. But moving test.user5@contoso.com mailbox to the exchange 2010 server's test.user5@newcontoso.local has been problematic.

    What have I done so far: I have not touched our existing exchange and AD infrastructure. I simply stood up a new DC Windows Server 2008 R2 for the new domain newcontoso.local and then stood up another 2008 Server and installed Exchange 2010 on it as our exchange server. Both are virtual machines but that shouldn't make any difference. I started off by creating a few users on the new exchange server to play around with, created mailboxes for them that are functioning, and now I'm testing the move of mailbox across forests. And running into erros, which have made me doubt my new server mailbox move deployment strategy.

    Reply
  6. Hi Ababwa,

    Moving mailboxes cross forest is a totally different situation. I take that you have ADMT'd the users to the new AD? Does all the users have email address stamped as "@newcontoso.local"?

    The command is correct. Will be helpful if you explain what all you have done so far.

    Thanks,

    Reply
  7. Hi Deepak,

    My company has tasked me with moving mailboxes from Exchange 2003 to Exchange 2010. You say it's simple, but it has been anything but for me. I've read the technet library over and over, but I'm running into errors. I'm trying to move mailboxes from an Exchange 2003 server to an exchange 2010 server that's on a DIFFERENT FOREST than the Exchange 2003 one. Our current exchange 2003 forest does not contain a 2010 server at all. Any help maybe creating a quick and dirty guide with actual examples?

    I've gotten as far as this command in the EMC shell on 2010:

    New-MoveRequest -Identity 'test.user@contoso.com' -remoteLegacy -TargetDatabase 'Mailbox Database#######' -RemoteGlobalCatalog 'corp-exch.contoso.com' -RemoteCredential $Cred -TargetDeliveryDomain 'newcontoso.local'

    Please any help would be great. Thanks!

    Reply
  8. For Failed MoveRequests, you can usually just remedy the situation (if it is because of a Quota error, increase the database's or user's Quota) and the run Resume-MoveRequest.

    Yes, all MoveRequests have to be Removed before a new one can start. The MailboxReplicationService will not do this for you, it requires administrator action. It would be undesirable for requests to just disappear; this gives you an idea of how many your moves have completed by just running one simple command (Get-MoveRequest -MoveStatus Completed).

    Reply
  9. Thanks Deepak.

    Once you move all mailboxes as part of a transition from 2003/2007 to 2010, you can clear all requests by running Get-MoveRequest –MoveStatus Completed | Remove-MoveRequest

    I am not sure whether failed move requests have to be cleared. I will update when I come across one of those. I will check whether restarting the Mailbox Replication Service clears all requests automatically as well.

    Reply
  10. Great, well explained. Thanks for sharing, Ok so we have to remember to clear the move-request once it is completed. Would be better if system checked for completed status and removed old request and created new one with a warning messages and confirmation prompt.

    What happens when there is an error in move mailbox(for corrupted messsages and other reason) and we have to run it again. Do we have to remove move request and redo it? or we could just resume the move request or retry? Not sure if you come across this.

    thanks

    Reply

Leave a Comment

Disable Windows Copilot Using Intune

Windows Copilot is Microsoft’s take on making life easier for Windows users using the power of AI. This article explains how to disable the feature using Intune, if your organization is not ready yet to walk into the AI world.

Disable Windows Copilot Using Intune

We need to create a Configuration Profile for Windows devices in the Intune portal to disable Windows Copilot. Below are the steps that we need to create the profile.

Launch the Intune Portal and login as a Global Admin or Intune Admin.

Navigate to Devices -> Windows -> Configuration Profiles.

Windows Configuration Profile Intune

Click on Create -> New Policy.

Select Windows 10 & later as the platform and Settings Catalog as the profile type & click on the Create button.

Settings Catalog Intune CoPilot

Give the policy a meaningful name & description and click Next.

Policy Name Disable CoPilot

Within the configuration settings, click on the Add Settings option.

Add Settings Disable CoPilot

Search for ‘copilot’, Windows AI will come up as the category. Click on Windows AI and the Turn off Copilot in Windows (User) setting will come up. Check the box and click Next.

Turn off CoPilot Setting Intune
Turn off CoPilot Setting Intune Summary 1

Specify scope tags if required and click Next.

Select tags CoPilot Intune

Select who this policy should apply to in the Assignments section. I have selected to add all users. If you want to test the setting, you can create a test group and select that group here.

Similarly, you can also exclude certain group from disabling AI (say IT team) if required.

Add all users disable copilot intune

A summary of selected settings will be displayed. Click on the Create button to setup the policy to disable Windows Copilot.

Create configuration policy disable CoPilot Intune 1

Wait for the replication to complete in the cloud backend and login to your machine. Your chatty Copilot should now be disabled.

Disable Windows Copilot On Windows 11 Pro

Follow the steps below to disable Copilot on a personal Windows 11 Pro machine (say your own laptop).

Search for ‘group’ in Windows 11 and click on Edit Group Policy option.

Group Policy Windows 11 Disable Copilot

Navigate to User Configuration -> Administrative Templates -> Windows Components -> Windows Copilot.

Windows Copilot GPO setting

Double click on Turn off Windows Copilot setting on the right pane.

Select Enabled and click OK.

Turn off copilot gpo Windows 11 Pro 1

Close the Group Policy Editor. This will disable Windows Copilot on a Windows 11 Pro machine.

Summary

We have learned to disable Windows Copilot using Intune and Group Policy on Windows 11 machines.

Please let me know if you have any questions in the comments section.

Promote Windows Server 2025 To Domain Controller

Domain controllers are the backbone of any Active Directory domains in the Microsoft world. Any Windows server can be promoted to be a domain controller. In this article, we will go through the steps of promoting a Windows 2025 Server to be a domain controller.

Windows Server 2025

The latest version of the server operating system has been named Windows Server 2025. You can start with a 2025 Server & create an AD domain or you can promote a member server that is already a part of a domain.

The Windows Server 2025 needs to be installed on a machine before it can be promoted to be a domain controller.

Promote Windows Server 2025 To Domain Controller

If you have been working with Windows servers long enough, everything starts with the Server Manager app. Promoting a server to a domain controller is no different.

Launch ‘Server Manager’ & click on Add roles and features.

Windows 2025 Server Manager

You land on the summary page that explains what is required to run this wizard successfully. Click Next.

Windows Server 2025 Add Remove Roles

Select Role-based or Feature-based installation and click Next.

Windows Server 2025 Role Based Install

Select the server that needs to be promoted and click Next.

Windows Server 2025 Destination Server

Select Active Directory Domain Services (second option) and click on Add Features.

Windows Server 2025 AD Domain Services

Go with the default options for features that need to be installed.

Windows Server 2025 AD Domain Services Features

A summary of AD DS pops up next, click next to continue.

Windows Server 2025 AD DS

Select Restart the server automatically if required and click Install.

Windows Server 2025 AD Restart Server

You get to keep an eye on the progress of the installation.

Windows Server 2025 AD Install Progress

Once the role has been installed, you will find an exclamation mark on the top right corner of the Server Manager. Click on that and select Promote this server to be a domain controller.

Windows Server 2025 AD Install Continue

You get an error straight away (which you have never seen before) – Error determining whether the target server is already a domain controller. Role change is in progress or this computer needs a restart.

Windows Server 2025 Domain Controller Setup Error

We never needed to restart the server after installing the role in the DC promotion process. Given that it is an insider build of Server 2025, I am hoping that this will get fixed before the public release.

Restart the server, launch Server Manager and click on the Promote this server to be a domain controller option again.

Windows Server 2025 AD Install Continue 1

I am setting up a brand new AD forest and hence I select the third option (Add a new forest) and enter my root domain name.

Windows Server 2025 Add a forest

Next window brings the option to set your forest & domain functional level and the DSRM password. In the insider build, it shows what looks like a variable (the Windows server version on which the you are working).

Windows Server 2025 Forest Functional Level

You can leave the default options in the DNS options wizard and click next.

Windows Server 2025 DNS Options

Enter the netbios name of the domain in the next window and click next.

Windows Server 2025 Netbios Domain Name

You can stick with the default paths for the AD database, log & sysvol folder or pick a location of your choice.

Windows Server 2025 AD Paths

Review the selections that you have made so far and click next.

Windows Server 2025 Options Review

Wait for the green check mark on the prerequisites page and click next.

Windows Server 2025 Pre reqs Check

Click Install in the final window & wait for the magic to happen. Once the machine gets restarted (which it will do automatically), you will have a brand new domain controller based on Windows Server 2025.

Windows Server 2025 AD Snap In

Summary

Promoting a Server 2025 to a domain controller follows pretty much the same steps as previous operating systems. The Insider build has few errors that needs to be fixed, but hey, it is an insider build!

Please let me know if you have any questions in the comments section.

Install Windows Server 2025 – Full Guide

Microsoft has released an insider preview of it’s next server operating system named Windows Server 2025. We will have a look at the installation steps involved in setting up a 2025 server.

Windows Server 2025

Microsoft has gone with the same look and feel of Windows 11 operating system in it’s current server operating system – Windows Server 2025. As the product is in insider preview, there might be slight changes before it hits the public shelves.

It is refreshing to see a ‘modern’ feel in the installation process of a server operating system. Gone are the days where the installation of a consumer based OS felt much better compared to it’s server counterpart.

Installing Windows Server 2025

Let’s take a look at the steps involved in setting up a Windows Server 2025 machine. First step is to download the ISO from the Windows Insider portal.

Next step is to boot the virtual / physical machine from the ISO which will kick off the installation of Server 2025.

First option to select is the language settings. Pick the one based which relates to you and click next.

Windows Server 2025 language settings

Select the keyboard settings in the next screen and click next.

Windows Server 2025 keyboard

You get the option to select whether you want to Install Windows Server or Repair the installation. The bottom left corner also has the option to go to the previous version of setup.

Windows Server 2025 setup option

You are asked to enter the product key, which is available in the Windows Insider portal.

Windows Server 2025 product key

Next option to choose is the type of image you want to install – Windows 2025 core or full blown desktop experience.

Windows Server 2025 Desktop

You need to agree to the licensing terms to move forward in the next step.

Windows Server 2025 Agreement License

Select the partition on which the server OS should be installed and click next. You also have the option to slice the partitions the way you see fit in the same screen.

Windows Server 2025 Disk Partitions

The Ready to Install window comes up, click the install button.

Windows Server 2025 Install 1

Installation of Server 2025 is underway and you get to see the progress.

Windows Server 2025 Install Progress

Once the installation is complete, you need to enter an administrator password of your choice to finalize the setup.

Windows Server 2025 Password

And there you go! You see a Windows 11 login screen staring at you ;-)

Windows Server 2025 Login Screen

After logging in, you get to set the options around sending diagnostic data to Microsoft, which I always set as ‘required only’.

Windows Server 2025 Diagnostic Data

The Windows Server 2025 desktop looks similar, doesn’t it? ;-)

Windows Server 2025 Desktop Feel scaled

Now that the server is up and running, you can promote it to be a domain controller.

Summary

The Windows Server 2025 has the same look and feel as a Windows 11 operating system. The installation options also provide that modern ‘feel’ and makes it a bit soothing to the eyes!

Please let me know if you have any questions in the comments section.