Enterprise Software Thread, Exchange 2013 Management shell driving me crazy (won't work!) in Technical; I've just setup an Exchange 2013 server, it's all working wonderfully except for the management shell.
I can manage it ...
26th July 2013, 04:48 PM #1
Exchange 2013 Management shell driving me crazy (won't work!)
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
+ 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.
26th July 2013, 05:59 PM #2
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.
Last edited by mrbios; 26th July 2013 at 06:14 PM.
26th July 2013, 06:27 PM #3
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 ?
26th July 2013, 06:32 PM #4
Good point, sorry it was the less important of my worries while trying to fix both problems
Originally Posted by mac_shinobi
Accidentally cut off the last line but there's nothing more after the bit in brackets says (Microsoft.asyncResult)
Could not load file or assembly 'Microsoft.Exchange.Data.Directory, Version=126.96.36.199, 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/...-toolbox-error going to give it a go now
Last edited by mrbios; 26th July 2013 at 06:35 PM.
26th July 2013, 06:53 PM #5
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
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.
Last edited by mrbios; 26th July 2013 at 07:20 PM.
Thanks to mrbios from:
mac_shinobi (26th July 2013)
26th July 2013, 08:11 PM #6
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?
Last edited by mrbios; 26th July 2013 at 08:20 PM.
Thanks to mrbios from:
mac_shinobi (26th July 2013)
26th July 2013, 09:54 PM #7
Wish I could get exchange experience
Originally Posted by mrbios
27th July 2013, 01:44 PM #8
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
27th July 2013, 04:37 PM #9
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.
By nickjelly in forum AV and Multimedia Related
Last Post: 15th July 2013, 11:18 AM
By ihaveaproblem in forum Windows 7
Last Post: 13th January 2012, 06:00 AM
By andy_whitlock in forum Windows Server 2008 R2
Last Post: 18th August 2010, 09:48 PM
Last Post: 19th March 2009, 03:09 PM
By m1ddy in forum Network and Classroom Management
Last Post: 17th June 2008, 11:15 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)