Модуль exchange для windows powershell

PowerShell это основное средство администрирования как on-premises организаций Exchange Server, так и облачного Exchange Online в Microsoft 365. В этой статье мы покажем, как установить PowerShell модуль Exchange Online PowerShell v2 (EXO V2) в Windows, как подключиться к вашем тенанту Exchange Online и управлять ящиками и другими почтовыми объектами в Micrtosoft 365.

Обратите внимание, что сейчас одновременно существуют два модуля для управления Exchange Online: Exchange Online PowerShell v1 и современный Exchange Online PowerShell v2 (EXO v2). Если нет четких оснований использовать старый модуль (legacy скрипты и т.д.), старайтесь всегда использовать EXO v2: он работает быстрее (как и новый модуль Azure AD, он основан на REST API в реализации Microsoft Graph), командлеты оптимизированы для обработки множества объектов, вместо Basic используется Modern аутентификация, поддерживается MFA аутентификация, версии ExchangeOnlineManagement 2.0.4 и выше работают в версиях PowerShell Core 6.x, 7x и macOS, Ubintu 18.04/20.04.

Установка модуля Exchange Online PowerShell V2 (EXO V2))

Для установки модуля Exchange Online PowerShell в Windows нужна версия PowerShell 5.x (PowerShell Core поддерживается, начиная с версии модуля ExchangeOnlineManagement 2.0.4).

Настройки политики запуска скриптов PowerShell на компьютере должны разрешать запуск локальных PS файлов:

Set-ExecutionPolicy RemoteSigned

Установите и обновите модуль PowershellGet:

Install-Module PowershellGet -Force

Update-Module PowershellGet

Для установки модуля EXOv2 (ExchangeOnlineManagement) из галереи скриптов PowerShell для всех пользователей компьютера, выполните:

Install-Module -Name ExchangeOnlineManagement -Force -Scope AllUsers

Теперь модуль можно импортировать в сессию:

Import-Module ExchangeOnlineManagement

Проверьте, что модуль установлен. Также отображается его версия (2.0.5 в моем случае):

Get-Module ExchangeOnlineManagement

Картинка с сайта: winitpro.ru

Для обновления модуля EXOv2 используйте команду:

Update-Module ExchangeOnlineManagement

Подключение к Exchange Online с помощью PowerShell

Для подключения к вашему тенанту Microsoft 365 с помощью модуля Exchange Online, исопльзуется командлет Connect-ExchangeOnline. Например, можно указать UPN пользователя с правами глобального администратора тенанта:

Connect-ExchangeOnline -UserPrincipalName [email protected] -ShowProgress $true

Картинка с сайта: winitpro.ru

Укажите пароль пользователя и подтвердите вход через MFA (удобнее всего использовать приложение Microsoft Authenticator на смартфоне).

Если у вашего аккаунта есть доступ к нескольким тенантам Azure, можно указать имя с помощью параметра DelegatedOrganization:

Connect-ExchangeOnline -UserPrincipalName [email protected] -ShowProgress $true -DelegatedOrganization winitprotest2.onmicrosoft.com

Если для аккаунта отключен Modern Authentication, можно подключится так:

$cred = Get-Credential
Connect-ExchangeOnline -Credential $cred -UserPrincipalName [email protected] -ShowProgress $true

Вы можете проверить, что в системе есть активное подключение к Exchange Online так:

Get-PSSession| ft –AutoSize

В нашем примере подключение к outlook.office365.com активно (State=Opened)

Картинка с сайта: winitpro.ru

После завершения работы с Exchange Online не забывайте корректно закрывать свою сессию с помощью командлета Disconnect-ExchangeOnline. Дело в том, что Exchange Online поддерживает максимум 5 одновременных PowerShell сессий. Если вы попробуете открыть шестую сессию, появится ошибка:

Fail to create a runspace because you have exceeded the maximum number of connections allowed.

Следующий код можно использовать в ваших PowerShell скриптах для проверки, что подключение к Exchange Online через модуль EXOv2 уже активно. Это позволит избежать создания лишних удаленных PowerShell сессий к Microsoft 365.

$psSessions = Get-PSSession | Select-Object -Property State, Name
If (((@($psSessions) -like '@{State=Opened; Name=ExchangeOnlineInternalSession*').Count -gt 0) -ne $true) {
Connect-ExchangeOnline -UserPrincipalName [email protected] }

Управление Exchange Online с помощью командлетов модуля ExchangeOnlineManagement

Список доступных командлетов в модуле EXO v2 можно вывести командой:

Get-Command -Module ExchangeOnlineManagement

На данный момент доступно 23 командлета:

• Connect-ExchangeOnline
• Connect-IPPSSession
• Disconnect-ExchangeOnline
• Get-WrappedCommand
• IsCloudShellEnvironment
• UpdateImplicitRemotingHandler
• Get-EXOCasMailbox
• Get-EXOMailbox
• Get-EXOMailboxFolderPermission
• Get-EXOMailboxFolderStatistics
• Get-EXOMailboxPermission
• Get-EXOMailboxStatistics
• Get-EXOMobileDeviceStatistics
• Get-EXORecipient
• Get-EXORecipientPermission
• Get-MyAnalyticsFeatureConfig
• Get-OwnerlessGroupPolicy
• Get-UserBriefingConfig
• Get-VivaInsightsSettings
• Set-MyAnalyticsFeatureConfig
• Set-OwnerlessGroupPolicy
• Set-UserBriefingConfig
• Set-VivaInsightsSettings

Картинка с сайта: winitpro.ru

Обратите внимание, что названия некоторых команндлетов в модуле Exchange Online изменились. У большинства из них появился суффикс EXO. Например, вместо Get-Mailbox нужно использовать
Get-EXOMailbox
, вместо Get-MailboxPermission —
Get-EXOMailboxPermission
и т.д. Поэтому, если у вас остались скрипты для EXOv1, придется внимательно их переписать под EXOv2.

Можно вывести список ящиков в вашем тенанте Exchange или информацию о конкретном ящике:

Get-EXOMailbox |ft
Get-EXOMailbox kbuldogov

Картинка с сайта: winitpro.ru

Вывести пользователей, у которых разрешен POP и IMAP доступ:

Get-EXOCasMailbox -PropertySets Imap,pop

Вывести размер всех ящиков:

Get-EXOMailbox | Get-EXOMailboxStatistics

Размеры всех общих ящиков:

Get-EXOMailbox | Where-Object{$_.RecipientTypeDetails -eq "SharedMailbox"} | Get-EXOMailboxStatistics

Обратите внимание, что в модуле ExchangeOnlineManagement нет, например, командлета Set-Mailbox. Дело в том, что остальные доступные командлеты Exchange Online (более 750) импортируются в вашу PowerShell сессию после подключения к тенанту. Сначала вам нужно получить имя сессии:

Get-PSSession| select ConfigurationName,CurrentModuleName

По сгенерированному имени сессии можно получить список доступных командлетов:

Get-Command -Module tmp_4mpa2wak.dga

Картинка с сайта: winitpro.ru

Т.е. чтобы изменить SMTP адрес пользователя, можно использовать команду:

Get-EXOMailbox kbuldogov | Set-Mailbox -EmailAddresses @{Add='kbuldogov2 @winitpro.ru'}

In Exchange Server, we can load Exchange Management Shell module in Windows PowerShell ISE. This way, we can run Exchange cmdlets in PowerShell ISE just like we are used to in Exchange Management Shell. But, is there another way to connect to Exchange Server with PowerShell? This article will teach you how to load Exchange Management Shell snapin in PowerShell ISE.

Information

Microsoft PowerShell ISE stands for Integrated Scripting Environment. Why do we like to use Windows PowerShell ISE if it comes to running scripts or cmdlets?

• Works more comfortable with the editor
• It shows you the cmdlets as you type
• Better interface (GUI)

Error when running Exchange cmdlet in PowerShell ISE

If you run an Exchange cmdlet in PowerShell ISE, you will get an error. Let’s use the Get-Mailbox cmdlet.

Get-Mailbox

The output shows the error below.

Get-Mailbox : The term 'Get-Mailbox' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the 
name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-Mailbox
+ ~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-Mailbox:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

You did get this error because you don’t have Exchange Management Module imported in Windows PowerShell ISE.

Import Exchange Management Module in PowerShell ISE

We want to import the Exchange module in PowerShell ISE on the Exchange Server. We also like to do the same on another server with Exchange Management Tools installed.

To load Exchange snapin in PowerShell ISE, you can run the following cmdlets. After that, run the Get-Mailbox cmdlet to verify that it’s working.

Add Exchange Management snapin Exchange 2010

Run PowerShell ISE as administrator. Add the Microsoft Exchange Management snapin.

Add-PSsnapin Microsoft.Exchange.Management.PowerShell.E2010

Add Exchange Management snapin Exchange 2013/2016/2019

Run PowerShell ISE as administrator. Add the Microsoft Exchange Management snapin.

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

We have a management server, and we want to connect to the Exchange Server with PowerShell ISE. If you open it on another server without Exchange Management Tools installed, it will not work.

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

You get the error below because you have to install Exchange Management Tools. After that, run the snapin cmdlet to import Exchange Management Tools.

Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 5.
At line:1 char:1
+ Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (Microsoft.Excha...werShell.SnapIn:String) [Add-PSSnapin], PSArgumentException
    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand

Connect to Exchange Servers with remote PowerShell

The above Exchange snapin cmdlets will work fine. Is there another way to load the Exchange module in PowerShell? Yes, there is.

In three steps, we can create a remote PowerShell connection to Exchange Server:

1. Enter credentials
2. Provide required connection settings
3. Import Exchange cmdlets

You can connect from Exchange Server itself or another server. For example, a Management Server. The good thing is that you can run this without installing Exchange Management Shell on the remote server. But, some cmdlets will not give you the correct output. For example, the Get-ExchangeCertificate cmdlet will not give you all the properties.

Note: We do recommend to install the Exchange Management Tools on any server to administer Exchange Servers.

Run PowerShell ISE as administrator and run Get-ExecutionPolicy cmdlet to check if it’s correctly set.

Get-ExecutionPolicy

If it’s not set as RemoteSigned, run the command below.

Set-ExecutionPolicy RemoteSigned

1. Enter the credentials

Run the command below.

$UserCredential = Get-Credential

A prompt will show. Fill in the account UPN with admin privileges.

2. Provide required connection settings

Replace EX01-2016.exoip.local to your Exchange server FQDN. The connectionUri is http and not https.

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://EX01-2016.exoip.local/PowerShell/ -Authentication Kerberos -Credential $UserCredential

3. Import Exchange cmdlets

Import the Exchange cmdlets in the Windows PowerShell session so you can administer Exchange.

Import-PSSession $Session -DisableNameChecking

If you get errors when connecting to the PowerShell virtual directory, read Recreate virtual directories in Exchange Server.

Verify it’s working

Run the Get-Mailbox cmdlet and see the results.

Get-Mailbox

If you are finished with your work, don’t forget to sign off.

Remove-PSSession $Session

You did connect to Exchange Server from another server or from Exchange server itself. This time with remote PowerShell. Did this load Exchange cmdlets in PowerShell ISE for you?

Read more: Install Exchange Online PowerShell module »

Conclusion

You learned how to load Exchange Management Shell in PowerShell ISE. The next time you connect to the Exchange Server, you can connect with remote PowerShell and not load the Exchange snapin. Both ways will work.

It’s best to Install Exchange Management Tools on any server to administer Exchange Servers. After that, import the Exchange snapin in PowerShell ISE. This way, all the Exchange cmdlets are available.

Did you enjoy this article? You may also like Install Exchange Cumulative Update. Don’t forget to follow us and share this article.

To install the Exchange Online PowerShell module, use the command below in your PowerShell prompt:

Install-Module -Name ExchangeOnlineManagement

Prerequisites

Understanding PowerShell Versions

Before diving into the installation process, it’s essential to understand which versions of PowerShell are compatible with the Exchange Online PowerShell module. Microsoft generally recommends using Windows PowerShell 5.1 or PowerShell Core 7 and above. Upgrading to the latest version not only enhances security but also optimizes performance, providing you with better command execution capabilities.

Required Access Permissions

To successfully install the Exchange Online PowerShell module, you need to have certain permissions. It’s crucial to have permissions akin to an Azure AD Administrator or similar roles that allow you to install components from the PowerShell Gallery. This ensures you can execute the necessary commands without encountering access issues.

Картинка с сайта: powershellcommands.com

Update Exchange Online PowerShell Module: A Quick Guide

Installing the Exchange Online PowerShell Module

Accessing Windows PowerShell

To get started, you need to launch PowerShell on your system. This can be done in different ways depending on your Windows version. Once open, it’s a good practice to check your PowerShell version to confirm compatibility:

$PSVersionTable.PSVersion

This command outputs the version number, ensuring you have the correct setup for the installation.

Running the Installation Command

Once you have verified compatibility, you can initiate the installation of the Exchange Online PowerShell module. Simply execute the following command in your PowerShell window:

Install-Module -Name ExchangeOnlineManagement

This command pulls the ExchangeOnlineManagement module from the PowerShell Gallery and installs it on your local machine. It’s straightforward, but it’s important to understand what this command does—Install-Module is the cmdlet that lets you get modules from online repositories, and -Name specifies the module you want to install.

Handling Untrusted Repository Issues

If it’s your first time installing a module, you might encounter a warning regarding untrusted repositories. If PowerShell prompts you about this, you can resolve the issue by adjusting your execution policy. To allow the installation to proceed, run:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

This command sets the execution policy to allow scripts downloaded from the Internet that are signed by a trusted publisher. Please exercise caution and understand the implications of changing execution policies, as it could affect your system’s security posture.

Картинка с сайта: powershellcommands.com

Disconnect Exchange Online PowerShell Made Easy

Verifying the Installation

Checking Installed Modules

After completing the installation, verifying that the module has been successfully added to your system is crucial. You can do this by executing:

Get-InstalledModule -Name ExchangeOnlineManagement

If the installation was successful, you will see details about the module, including the installed version and other metadata.

Importing the Module

To start using the Exchange Online cmdlets, you need to import the module into your current PowerShell session:

Import-Module ExchangeOnlineManagement

This command makes all commands in the module available for use in your PowerShell session. If you face any issues, ensure that you have the required permissions and that the module is indeed installed.

Картинка с сайта: powershellcommands.com

Mastering PowerShell: Install MSOnline with Ease

Connecting to Exchange Online

Using Modern Authentication

With the module imported, you can now connect to your Exchange Online environment. Modern authentication is recommended for secure connections. Execute the following:

Connect-ExchangeOnline -UserPrincipalName yourUser@domain.com

Replace yourUser@domain.com with your actual Exchange Online account. This command initiates a connection, prompting you for credentials and allowing you to manage Exchange Online through PowerShell.

Troubleshooting Connection Issues

If you encounter any connection issues, common errors may include login failures or authentication errors. Ensure your credentials are correct and that your account has sufficient permissions. You might also want to check your network connection and ensure you are not behind a restrictive firewall.

Картинка с сайта: powershellcommands.com

Mastering the Install-MsolService PowerShell Module

Updating the Exchange Online PowerShell Module

Keeping Your Module Updated

To ensure your module has the latest features and security patches, regularly check for updates. You can update the Exchange Online module by running:

Update-Module -Name ExchangeOnlineManagement

By executing this command, you can keep your environment current and secure.

Managing Multiple Versions

In cases where you have multiple versions of the module installed, you might need to manage which version you are using actively. PowerShell allows you to use specific versions by specifying them in the import command in your script.

Картинка с сайта: powershellcommands.com

Find Exchange Version PowerShell: A Quick Guide

Conclusion

In this article, we have thoroughly explored how to install the Exchange Online PowerShell module. From confirming your prerequisites to connecting to Exchange Online, you are now equipped with the fundamental steps and commands necessary for effective PowerShell usage in managing your Exchange Online environment. Feel free to experiment further with the cmdlets available in this module to streamline your administrative tasks.

Картинка с сайта: powershellcommands.com

Connect to Exchange Server PowerShell: A Quick Guide

Additional Resources

For more detailed information, consider checking the official Microsoft documentation on PowerShell and Exchange Online. Joining PowerShell training courses or communities can also significantly enhance your skills and keep you informed about best practices.