Exchange 2013 Management shell driving me crazy (won't work!)

[mrbios]

I've just setup an Exchange 2013 server, it's all working wonderfully except for the management shell.

 

I can manage it with the management center perfectly fine, but trying to use either the management shell or the toolbox fails.

 

When loading the management shell i get this:

VERBOSE: Connecting to exchange.Archway.local.

New-PSSession : [exchange.archway.local] Connecting to remote server exchange.archway.local failed with the following

error message : The connection to the specified remote host was refused. Verify that the WS-Management service is

running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more

information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1

+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin

gTransportException

+ FullyQualifiedErrorId : CannotConnectWinRMService,PSSessionOpenFailed

 

I've tried 3 pages worth of google results, and every supposed "fix" i can find, but nothing works, has anyone else had this problem and have anything to suggest?

 

This is Exchange 2013 CU2 running in coexistence with exchange 2010 SP3.

[mrbios]

ohhhhh fml it's down to the winhttp proxy settings, soon as i added *.domain.local to the bypass list in winhttp proxy settings it's solved.

 

EDIT: actually it fixed the problem with the management shell, but the toolbox still crashes with some MMC snap in error.

Edited July 26, 2013 by mrbios

[mac_shinobi]

Screen grab of the mmc snap in error - not that I will be able to help but may be a bit more precise with regards to what the error message is as apposed to saying some mmc snap in error ??

@Arthur or someone else with regards to this ?

[mrbios]

Screen grab of the mmc snap in error - not that I will be able to help but may be a bit more precise with regards to what the error message is as apposed to saying some mmc snap in error ??

@Arthur or someone else with regards to this ?

 

Good point, sorry it was the less important of my worries while trying to fix both problems

 

Accidentally cut off the last line but there's nothing more after the bit in brackets says (Microsoft.asyncResult)

 

 

and

 

FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

Could not load file or assembly 'Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

 

Google isn't much help here as this: http://support.microsoft.com/kb/2020789 doesn't appear to be an issue, although I'm yet to try this one: http://social.technet.microsoft.com/Forums/exchange/en-US/26e61306-e3b8-4ca0-9622-6f9abec392ea/opening-exchange-2013-toolbox-error going to give it a go now

Edited July 26, 2013 by mrbios

[mrbios]

Ah fixed it.

 

Had to change the IIS path for the powershell virtual application from:

C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\powershell

 

To this:

C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell

 

Why on earth would i need to do that!?

 

Powershell, toolbox and admin center all working swimmingly now

 

EDIT: nope, time for a new frustration.

 

I'm running the exchange management shell on my 2013 server, and for some reason all the commands i run on it are trying to run on the old 2010 server!? If i do "Get-ExchangeServer" it returns my 2010 server.

 

EDIT2: never mind fixed that now too, just had to delete something out of roaming appdata and registry relating to the MMC for the other server.

Edited July 26, 2013 by mrbios

[mrbios]

Get the feeling it's not working as it though (the powershell part) because I can't even do "Get-ExchangeServer" it just doesn't see that as a command?

 

.....Fixed it by adding a whole load of roles to organisation management, which is odd becuase I've never changed those settings prior for them to have been removed?

Edited July 26, 2013 by mrbios

[mac_shinobi]

Get the feeling it's not working as it though (the powershell part) because I can't even do "Get-ExchangeServer" it just doesn't see that as a command?

 

.....Fixed it by adding a whole load of roles to organisation management, which is odd becuase I've never changed those settings prior for them to have been removed?

 

Wish I could get exchange experience

[mrbios]

New question!

 

Currently this is what's happening:

 

Sending emails from and to....

Exchange 2010 to 2010 - OK

Exchange 2013 to 2013 - OK

Exchange 2013 to 2010 - BAD

Exchange 2010 to 2013 - OK

External to 2010 - BAD

External to 2013 - OK

2013 to external - OK

2010 to external - OK

 

Those are the scenarios I've got currently, I can't understand though why i can't at least get email from 2013 to 2010 working, would it be down to a receive connector config or something? I can happily deal with not being able to send mail from external to the 2010 one for now, as once the internal mail works fine i'll just start the migration of all my accounts

[mrbios]

In case anyone else runs into this problem while migrating mailboxes, if you find your migration gets stuck on "StalledDueToCI" for a long period of time or is generally slower than expected, look no further than here: Content Index status of all or most of the mailbox databases in the environment shows "Failed"

 

Just had that problem and Method 1 fixed it perfectly.