Connecting To Exchange 2010 Using Remote Powershell…

MS Exchange

Remote Powershell (Windows Powershell v2) allows you to connect to an Exchange 2010 organization from a client without having the 2010 management tools installed. You should install Windows Management Framework, which includes Powershell V2 and Windows Remote Management on the client. Download it here. Make sure that you select the correct version (x86 or X64) depending on the client you use.

The clients should be either Vista SP1+ or Windows 2008 SP1+ (x86 or x64). Uninstall any previous versions of Management Framework, if you have it. Instructions are here.

In order to connect to an Exchange 2010 organization from a client with windows management framework installed and no 2010 management tools, we need to follow certain steps.

  • Store the login details of an account that has permissions to remote in. By default, the account that was used to install Exchange 2010 will have the permissions already.
  • If you want another user to be able to initiate a remote powershell session, run Set-User –identity username –RemotePowershellEnabled $True
  • Store the session details in a variable
  • Import the session defined. It will take a while.
  • Run exchange cmdlets / administer the 2010 environment.
  • Once you have finished your work, remove the session.

Let’s get to business. Once the framework is installed, launch Windows Powershell V2

Run $user = Get-Credential to store the login account details. A login box gets prompted, fill in the details and click OK. The account details are now in the variable “user”.


Run $session = New-PSSession -Configurationname Microsoft.Exchange –ConnectionUri http://hew-dc/powershell -Credential $user


This stores the session details including the account used for remoting.

Run Import-PSSession $session to import the server-side powershell session to the client side one.


It takes some time to import the exchange cmdlets. Once it is completed, you can use all exchange cmdlets in your Windows Powershell session.


Run Remove-PSSession $session once you have completed your work.


That’s it for now!

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. Tried to connect with an exchange server in another forest with Authentication kerberos returned with error 1311. Error message:”Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: There are currently no logon servers available to service the logon request.”
    Have you received this type of error

    • Hi Bijo,

      WinRM issues are common, run winrm /quickconfig in an elevated command prompt, followed by an iisreset.

  2. The following command doesn’t work on my system & network. The first few until
    Run $session.. command works fine.
    BUT the…
    Import-PSSession $session – Doesnt work; Gives the following output in RED.
    Import-Module : There were errors in loading the format data file:
    Microsoft.PowerShell, , C:\Users\bartender\AppData\Local\Temp\tmp_a60c23a2-372b-4f7e-b49b-372b07fb2421_kxwmt4fr.jo1\tmp
    _a60c23a2-372b-4f7e-b49b-372b07fb2421_kxwmt4fr.jo1.format.ps1xml : File skipped because of the following validation exc
    eption: File C:\Users\bartender\AppData\Local\Temp\tmp_a60c23a2-372b-4f7e-b49b-372b07fb2421_kxwmt4fr.jo1\tmp_a60c23a2-3
    72b-4f7e-b49b-372b07fb2421_kxwmt4fr.jo1.format.ps1xml cannot be loaded because the execution of scripts is disabled on
    this system. Please see “get-help about_signing” for more details..
    Microsoft.PowerShell, , C:\Users\bartender\AppData\Local\Temp\tmp_5315cd91-f04f-429a-a2e6-ce04770076ce_ky1b04bf.i0o\tmp
    _5315cd91-f04f-429a-a2e6-ce04770076ce_ky1b04bf.i0o.format.ps1xml : File skipped because of the following validation exc
    eption: File C:\Users\bartender\AppData\Local\Temp\tmp_5315cd91-f04f-429a-a2e6-ce04770076ce_ky1b04bf.i0o\tmp_5315cd91-f
    04f-429a-a2e6-ce04770076ce_ky1b04bf.i0o.format.ps1xml cannot be loaded because the execution of scripts is disabled on
    this system. Please see “get-help about_signing” for more details..
    At line:3 char:30
    + Import-Module <<<< -Name $name -Alias * -Function * -Prefix $prefix -DisableNameChecking:$disableNam
    eChecking -PassThru -ArgumentList @($session)
    + CategoryInfo : InvalidOperation: (:) [Import-Module], RuntimeException
    + FullyQualifiedErrorId : FormatXmlUpateException,Microsoft.PowerShell.Commands.ImportModuleCommand

      • Even considering that the last activity on this topic was almost one year ago, just for the record, it seems that Xtrait issue can be solved using the following command:

        Set-ExecutionPolicy RemoteSigned

  3. Hi,
    I execute C:WindowsSystem32WindowsPowerShellv1.0powershell.exe -noexit -command “. ‘C:Program FilesMicrosoftExchange ServerV14binRemoteExchange.ps1′; Connect-ExchangeServer -auto” command from javaprogram but fail ‘emoteExchange.ps1” is not recognized as an internal or external command.
    Can you help me?

    Source java

    String[] command = new String[4];

    command[0] = “cmd”;

    command[1] = “C:WindowsSystem32WindowsPowerShellv1.0powershell.exe -noexit -command ”. ‘C:Program FilesMicrosoftExchange ServerV14binRemoteExchange.ps1′; Connect-ExchangeServer -auto”";

    command[2] = “$Temp = ConvertTo-SecureString 123456 -asPlainText –Force”;
    command[3] = “New-Mailbox -Name tuandm -UserPrincipalName -OrganizationalUnit -Database metfone -Password $Temp | Set-Mailbox -IssueWarningQuota 136314889 -ProhibitSendReceiveQuota 157286400 -UseDatabaseQuotaDefaults $false”;
    Process p = Runtime.getRuntime().exec(command );

  4. Hi Rajith

    Thanks for your reply .yes $user have admin rights.
    Rajith my problem has been resolved by changing this "localhost" to my FQDN in New-PSSession command.

    Best regards,
    Cute Devil

  5. Hi Rajith Jose Enchiparambil,

    when i executed the following command

    "[PS] C:Windowssystem32>$session = New-PSSession -Configurationname -ConnectionUri http://localhost/powershell?serializationLevel=Full -Credential $user"
    i confronted with the following error

    [localhost] Connecting to remote server failed with the following error message : The WinRM client cannot process the r
    equest. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (localhost:80) r
    eturned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or sp
    ecify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as
    the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To u
    se Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name
    and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubl
    eshooting Help topic.
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
    + FullyQualifiedErrorId : PSSessionOpenFailed

    any help regarding this issue would be appreciated

    thanks in advance


Leave a Comment

Set Microsoft Edge As Default Browser Using Intune

The video below goes through the process of setting up Microsoft Edge as the default browser on a Windows 11 machine using Intune.

Set Microsoft Edge As Default Browser On Windows 11 Using Intune

Getting Started With Entra ID

The video below is aimed at complete beginners who can master the Identity portion of Entra ID in about 90 minutes.

Getting Started With Entra ID - Complete Beginner's Guide

How To Remove Teams Sharing Toolbar While Presenting

The new version of Microsoft Teams bring the ‘annoying’ sharing toolbar in the top middle of the screen while you are presenting in a Teams meeting. There is no way to remove the toolbar which come in between various tabs in a browser or applications that you want to move around.

The video below explains a workaround to remove this sharing toolbar for good while presenting. Hopefully Microsoft will add an option within the app to remove this in the near future.

How To Remove Teams Sharing Toolbar While Presenting