Using the Exchange Management Shell, it pretty easy to use Powershell and find your Exchange Server build numbers and release dates.  Listed below is the command you can run to find your current Exchange Build and release number.

Below we have checked the build for an Exchange Server 2013.

Exchange Server 2016

Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

Exchange Server 2013

Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

 Exchange Server 2010

Get-Command ExSetup | ForEach {$_.FileVersionInfo}

You can use the information in this topic to verify the version of Exchange that is running in your organization.

Compare your Build and release to the current Microsoft Exchange Server Updates and build numbers:

The post Find your Exchange Server build numbers – and release dates first appeared on Cloud Engineer - Everton Collins.

[adrotate banner=”5″]

PowerShell (including Windows PowerShell and PowerShell Core) is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework used to Connect to Exchange Online using Windows PowerShell.

Exchange Online using Windows PowerShell

1. On your local computer, open Windows PowerShell and run the following command.
   • $UserCredential = Get-Credential
     In the Windows PowerShell Credential Request dialog box, type your Office 365 user name and password, and then click OK.
2. Run the following command.

   1. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 
      https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication 
      Basic -AllowRedirection
      
      
      
      

3. Run the following command.

   1. Import-PSSession $Session
      

   2. Connect-MsolService -Credential $UserCredential.

   3. Be sure to disconnect the remote PowerShell session when you’re finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you’ll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command.

      Remove-PSSession $Session

4. How do you know this worked?

   1. After Step 3, the Exchange Online cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don’t receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet, for example, Get-Mailbox, and see the results. (shows the Server your on and Quota)
      

      If you receive errors, check the following requirements:

      • A common problem is an incorrect password. Run the steps again and pay close attention to the user name and password you enter in Step 1.
      • To help prevent denial-of-service (DoS) attacks, you’re limited to three open remote PowerShell connections to your Exchange Online organization.
      • The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see Enable or disable access to Exchange Online PowerShell.
      • TCP port 80 traffic needs to be open between your local computer and Office 365. It’s probably open, but it’s something to consider if your organization has a restrictive Internet access policy.

       

A few Sample Commands to Test with your Connection

Below are a few other commands you can try out once your connected to Microsoft Exchange Online (Connect to Exchange Online using Windows PowerShell).

5. Get-MsolUser – Lists all users

6. Remove-MsolUser -UserPrincipalName name@domain.com   – Remove User/s
   

The post Connect to Exchange Online using Windows PowerShell first appeared on Cloud Engineer - Everton Collins.