Exchange mailbox move

I am having a problem moving a mailbox from powershell on my Client Access Server with Exchange 2013. I type the command. The command works on one of the DAG servers, but i need it on my CAS.

New-moverequest -identity "user" -targetdatabase "Database"

It comes up with this error

New-MoveRequest : The call to 'net.tcp://servercas1.domain.loc/Microsoft.Exchange.MailboxReplicationService' failed because no
service was listening on the specified endpoint. Error details: Could not connect to
net.tcp://server1cas.domain.loc/Microsoft.Exchange.MailboxReplicationService. The connection attempt lasted for a time span of
00:00:02.0313634. TCP error code 10061: No connection could be made because the target machine actively refused it
[::1]:808.  --> No connection could be made because the target machine actively refused it [::1]:808
falconcurtAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
"The command works on one of the DAG servers, but i need it on my CAS."

What do you mean by that?
A move mailbox command is not connected to a specific server. It is an org setting, so can be run from anywhere. Furthermore the move actually takes place on the mailbox servers as it is uses the replication system within Exchange to move the mailbox.

Simon.
0
falconcurtAuthor Commented:
That's what I don't understand. If I run that command on the server1cas under powershell ise, I get the error message.. The command works perfect when I run the command from one of my mailbox servers.  The mailbox move works fine to from the gui from anywhere.
0
Will SzymkowskiSenior Solution ArchitectCommented:
That's what I don't understand. If I run that command on the server1cas under powershell ise

That is your issue right there. ISE (Integrated Scripting Editor) is not the same as EMS. If you are using the ISE defaults do not import Exchange Snapins nor does it import external modules like activedirectory module.

What I would recommend is actually using the EMS on the CAS server. Or import the snapins into your ISE session then run the command. snapin commands are below for each version of Exchange...

E2007: add-pssnapin microsoft.exchange.management.powershell.admin
E2010: add-pssnapin microsoft.exchange.management.powershell.E2010
E2013: add-pssnapin microsoft.exchange.management.powershell.E2013

Once you have done this you should be able to run those commands from the ISE.

Will.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

falconcurtAuthor Commented:
Well Will you got me on the right path. I have only these registered snappins available

Description : Register cmdlets for Juno

Name        : Microsoft.Exchange.Management.PowerShell.E2010
PSVersion   : 1.0
Description : Admin Tasks for the Exchange Server

Name        : Microsoft.Exchange.Management.PowerShell.Setup
PSVersion   : 1.0
Description : Setup Tasks for the Exchange Server

Name        : Microsoft.Exchange.Management.PowerShell.SnapIn
PSVersion   : 1.0
Description : Admin Tasks for the Exchange Server

Name        : Microsoft.Exchange.Management.Powershell.Support
PSVersion   : 1.0
Description : Support Tasks for the Exchange Server

Name        : SearchCorePSSnapIn
PSVersion   : 2.0
Description : Register cmdlets for SearchCore


So i used the Name        : Microsoft.Exchange.Management.PowerShell.SnapIn one and thats what i was using to run the command. I went back to the E2010: add-pssnapin microsoft.exchange.management.powershell.E2010 and the command now works. Do you know why i dont have the E2013 snappin  available? I mean its working but still am curious why i do not have it.
0
Will SzymkowskiSenior Solution ArchitectCommented:
My mistake for Exchange 2013 it should be like below...
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

Which you already have.

Will.
0
Simon Butler (Sembee)ConsultantCommented:
Why aren't you using the Exchange 2013 EMS? You only need to do anything else if you are running the commands from somewhere else.

This TechNet article explains what happens:
https://technet.microsoft.com/en-us/library/dd335083(v=exchg.150).aspx

However that is simply a lot of work for no gain on the server itself - just start EMS.

Simon.
0
Will SzymkowskiSenior Solution ArchitectCommented:
@Simon
I do agree with you Simon but sometimes it is much easier and helpful to use the ISE when you are creating scripts in regards to proper formatting and also help with syntax. Although the scripts can be created from here and then run in the ESM later the user can also run the script directly from the ISE as well. In this case they need to have the proper snapin applied to the session.

Will.
0
falconcurtAuthor Commented:
I am testing a script out. What's weird Will is that I try the Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn from the beginning but it gives me that error message. Like I said it works perfect when I run it on any of the DAG Database servers. The command works find on the CAS server when I run the Add-PSSnaping Microsoft.Exchange.Management.PowerShell.E2010 command. Weird....
0
Will SzymkowskiSenior Solution ArchitectCommented:
Glad that it is working. Personally i have not seen this happen before and not sure as to why it would be working. I have done some searching but cannot find anything related to this weird symptom.

I will see if I can reproduce this in my lab.

Will.
0
falconcurtAuthor Commented:
We did upgrade from Exchange 2010 to 2013. we created new VM's to upgrade. Just fyi.
0
Will SzymkowskiSenior Solution ArchitectCommented:
Do you still have Exchange 2010 in your environment? Was it decommissioned properly?

Will.
0
falconcurtAuthor Commented:
Should have been decommissioned properly. We had the upgrade contracted out.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.