Exchange Server 2010
Posted on 2010-01-05
I have downloaded the Ms Exchange 2010 just from the MSDN.
I have 2 Servers
Server No-1 Domain Controller Windows Server 2003 SP2.
Server N0-2 Exchange 2010 with Windows Server 2008 SP2.
I Have installed the First Exchange 2010 in the fresh enviroment in windows server 2008 SP2, there is not any other exchange servers are installed in the current enviroment.
Installation was successful without any problem.
I have installed all the Roles of exchange 2010 in Server No-2 .
After installation i can not open the Exchange management Console , I was getting following error (The error i am getting in the local machine of the exchange)
( " Connecting to remote server failed with the following error message : The WinRM client cannot process the
request. It cannot determine the content type of the HTTP response from the destination computer. The content type is a
bsent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) , PSRemotingTransportExc
+ FullyQualifiedErrorId : PSSessionOpenFailed " )
I have installed the Exchange 2010 Withe the Default Domain Administrator Account and during the instllation i did not got any error.
So I found in the one of the blog that you have to enable the (Enable Remote Exchange Management Shell for a User.) with the following command
(Set-User remuse -RemotePowerShellEnabled $True ) in the Exchange management shell.
When i am opening the Exchange management shell again i am getting (Connecting Remtoe server error and when i am issuing the Set-User command i am getting
error that ,
( The term 'set-user' is not recognized as a cmdlet, function, operable program,
or script file. Verify the term and try again.
At line:1 char:9
+ set-user <<<<
+ CategoryInfo : ObjectNotFound: (set-user:String) , CommandNot
+ FullyQualifiedErrorId : CommandNotFoundException )
So is this is bug or its a beta or RC version of Exchange.
I have downloaded this version from the MSDN.
Can u pl Solve this issue.