Miscellaneous Exchange Online cmdlets that happen to be in the EXO V2 module are listed in the following table:

Install and maintain the EXO V2 module

You can download the EXO V2 module from the PowerShell gallery at https://www.powershellgallery.com/packages/ExchangeOnlineManagement/.

The procedures in this section explain how to install, update, and uninstall the EXO V2 module.

Supported operating systems for the EXO V2 module

The latest version of the EXO V2 module is officially supported in PowerShell 7 on Windows, Linux, and Apple macOS.

Specifically, version 2.0.4 or later of the EXO V2 module is supported in PowerShell 7.0.3 or later.

For more information about PowerShell 7, see Announcing PowerShell 7.0.

Apple macOS

The EXO V2 module is supported in the following versions of macOS:

• macOS 11 Big Sur or later
• macOS 10.15 Catalina
• macOS 10.14 Mojave

For instructions on installing PowerShell 7 on macOS, see Installing PowerShell on macOS.

Linux

The EXO V2 module is officially supported in the following distributions of Linux:

If you have trouble using the EXO V2 module on other distributions of Linux, send email to the following address: exocmdletpreview[at]service[dot]microsoft[dot]com . The email address is purposefully obfuscated to avoid spam.

For instructions on installing PowerShell 7 on Linux, see Installing PowerShell on Linux.

Windows

All versions of the EXO V2 module are supported in Windows PowerShell 5.1. PowerShell 7 on Windows requires version 2.0.4 or later of the EXO V2 module.

The EXO V2 module is supported in the following versions of Windows:

• Windows 10
• Windows 8.1 4
• Windows Server 2019
• Windows Server 2016
• Windows Server 2012 or Windows Server 2012 R2 4
• Windows 7 Service Pack 1 (SP1) 1, 2, 3
• Windows Server 2008 R2 SP1 1, 2, 3

1 This version of Windows has reached its end of support, and is now supported only in Azure virtual machines.

2 This version of Windows doesn’t support version 2.0.4 or later of the EXO V2 module. Only version 2.0.3 or earlier is supported.

3 Windows PowerShell 5.1 on this version of Windows requires the Microsoft .NET Framework 4.5 or later and the Windows Management Framework 5.1. For more information, see Windows Management Framework 5.1.

4 PowerShell 7 on this version of Windows requires the Windows 10 Universal C Runtime (CRT).

Prerequisites for the EXO V2 module

The settings described in this section are required in all versions of PowerShell on all operating systems.

PowerShell needs to be configured to run scripts, and by default, it isn’t. You’ll get the following error when you try to connect:

Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.

To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated PowerShell window (a PowerShell window you open by selecting Run as administrator):

For more information about execution policies, see About Execution Policies.

WinRM needs to allow Basic authentication (it’s enabled by default). We don’t send the username and password combination, but the Basic authentication header is required to send the session’s OAuth token, since the client-side WinRM implementation has no support for OAuth.

Note: You must temporarily enable WinRM to run the following commands. You can enable WinRM by running the command: winrm quickconfig .

To verify that Basic authentication is enabled for WinRM, run this command in a Command Prompt (not in PowerShell):

If you don’t see the value Basic = true , you need to run this command in a Command Prompt (not in PowerShell) to enable Basic authentication for WinRM:

Note: If you’d rather run the command in PowerShell, enclose this part of the command in quotation marks: ‘@‘ .

If Basic authentication for WinRM is disabled, you’ll get this error when you try to connect:

The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Online, or Exchange Online Protection.

Install the EXO V2 module

To install the EXO V2 module for the first time, complete the following steps:

Install or update the PowerShellGet module as described in Installing PowerShellGet.

Close and re-open the Windows PowerShell window.

Now you can use the Install-Module cmdlet to install the EXO V2 module from the PowerShell Gallery. Typically, you’ll want the latest public version of the module, but you can also install a Preview version if one is available.

To install the latest public version of the module, run one of the the following commands:

In an elevated PowerShell window (all users):

Only for the current user account:

To install a Preview version of the module, replace

Only for the current user account:

When you’re finished, enter Y to accept the license agreement.

For detailed syntax and parameter information, see Install-Module.

Update the EXO V2 module

If the module is already installed on your computer, you can run the following commands to see the version that’s currently installed and update it to the latest version from the PowerShell Gallery:

To see the version of the module that’s currently installed, run the following commands:

You can use the Update-Module cmdlet to update the EXO V2 module from the PowerShell Gallery. Typically, you’ll want the latest public version of the module, but you can also upgrade to a Preview version if one is available.

To upgrade to the latest public version of the module, run one of the following commands based on how you originally installed the module (in an elevated PowerShell window vs. Scope CurrentUser ):

In an elevated PowerShell window (all users):

Only for the current user account:

To upgrade to a Preview version of the module, replace

Only for the current user account:

When you’re finished, enter Y to accept the license agreement.

To confirm that the update was successful, run the following commands to check the version information of the module that’s installed:

For detailed syntax and parameter information, see Update-Module.

Troubleshoot installing the EXO V2 module

If you receive the following error:

The specified module ‘ExchangeOnlineManagement’ with PowerShellGetFormatVersion ‘ ‘ is not supported by the current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, ‘ExchangeOnlineManagement’.

Update your installation of the PowerShellGet module to the latest version as described in Installing PowerShellGet. Be sure to close and re-open the PowerShell window before you attempt to update the ExchangeOnlineManagement module again.

As of April 2020, the PowerShell Gallery only supports connections using TLS 1.2 or later. For more information, see PowerShell Gallery TLS Support.

To check your current settings in the Microsoft .NET Framework, run the following command in Windows PowerShell:

As described in the PowerShell Gallery TLS Support article, to temporarily change the security protocol to TLS 1.2 to install the PowerShellGet or ExchangeOnlineManagement modules, run the following command in Windows PowerShell before you install the module:

To permanently enable strong cryptography in the Microsoft .NET Framework version 4.x or later, run one of the following commands based on your Windows architecture:

For more information, see SchUseStrongCrypto.

Uninstall the EXO V2 module

To uninstall the module, run one of the following commands based on how you originally installed the module (in an elevated PowerShell window vs. Scope CurrentUser ):

In an elevated PowerShell window (all users):

Only for the current user account:

For detailed syntax and parameter information, see Uninstall-Module.

Properties and property sets in the EXO V2 module

Traditional Exchange Online cmdlets return all possible object properties in their output, including many properties that are often blank or aren’t interesting in many scenarios. This behavior causes degraded performance (more server computation and added network load). You rarely (if ever) need the full complement of properties in the cmdlet output.

The Get-EXO* cmdlets in the module have categorized output properties. Instead of giving all properties equal importance and returning them in all scenarios, we’ve categorized specific related properties into property sets. Simply put, these property sets are buckets of two or more related properties on the cmdlet.

In the biggest and most used Get-EXO* cmdlets:

Property sets are controlled by the following parameters:

• PropertySets: This parameter accepts one or more available property set names separated by commas. The available property sets are described in Property sets in Exchange Online PowerShell V2 cmdlets.
• Properties: This parameter accepts one or more property names separated by commas.

You can use the PropertySets and Properties parameters together in the same command.

We’ve also included a Minimum property set that includes a bare minimum set of required properties for the cmdlet output (for example, identity properties). The properties in the Minimum property sets are also described in Property sets in Exchange Online PowerShell V2 cmdlets.

• If you don’t use the PropertySets or Properties parameters, you automatically get the properties in the Minimum property set.
• If you use the PropertySets or Properties parameters, you get the specified properties and the properties in the Minimum property set.

Either way, the cmdlet output will contain far fewer properties, and the time it takes to return those results will be much faster.

For example, after you connect to Exchange Online PowerShell, the following example returns only the properties in the Minimum property set for the first ten mailboxes.

In contrast, the output of the same Get-Mailbox command would return at least 230 properties for each of the first ten mailboxes.

Although the PropertySets parameter accepts the value All, we highly discourage using this value to retrieve all properties, because it slows down the command and reduces reliability. Always use the PropertySets and Properties parameters to retrieve the minimum number of properties that are required for your scenario.

For more information about filtering in the EXO V2 module, see Filters in the Exchange Online V2 module.

Release notes

Unless otherwise noted, the current release of the EXO V2 module contains all features of previous releases.

Current release: Version 2.0.4

PowerShell 7 is officially supported in Windows, Linux, and Apple macOS as described in the Prerequisites for the EXO V2 module section in this article.

The EXO V2 module in PowerShell 7 supports browser-based single sign-on (SSO) and other sign in methods. For more information, see PowerShell 7 log in experiences.

The Get-UserAnalyticsConfig and Set-UserAnalyticsConfig cmdlets have been replaced by the Get-MyAnalyticsConfig and Set-MyAnalyticsConfig.Additionally, you can configure access at feature level. For more information, see Configure MyAnalytics.

Real-time policy and security enforcement in all user based authentication. Continuous Access Evaluation (CAE) has been enabled in EXO V2 Module. Read more about CAE here.

The LastUserActionTime and LastInteractionTime properties are now available in the output of the Get-EXOMailboxStatistics cmdlet.

The interactive sign-in process now uses a more secure method to fetch access tokens using safe reply URLs.

Previous releases

Version 2.0.3

• General availability of certificate based authentication (CBA), which enables using modern authentication in unattended scripting or background automation scenarios. The available certificate storage locations are:
  • Remote in the Azure Key Value (the Certificate) parameter. This option enhances security by fetching the certificate only at runtime.
  • Local in the CurrentUser or LocalMachine certificate store (the CertificateThumbprint parameter).
  • Local in an exported certificate file (the CertificateFilePath and CertificatePassword parameters). For more information, see the parameter descriptions in Connect-ExchangeOnline and App-only authentication for unattended scripts in the EXO V2 module.
• Connect to Exchange Online PowerShell and Security Compliance Center PowerShell simultaneously in a single PowerShell window.
• The new CommandName parameter allows you to specify and restrict the Exchange Online PowerShell cmdlets that are imported in a session. This option reduces the memory footprint for high usage PowerShell applications.
• Get-EXOMailboxFolderPermission now supports ExternalDirectoryObjectID in the Identity parameter.
• Optimized latency of the first V2 cmdlet call. Lab results show the first call latency has been reduced from 8 seconds to approximately 1 second. Actual results will depend on the cmdlet result size and the tenant environment.

Version 1.0.1

• General Availability (GA) version of the EXO V2 module. It is stable and ready for use in production environments.
• Get-EXOMobileDeviceStatistics cmdlet now supports the Identity parameter.
• Improved reliability of session auto-reconnect in certain cases where a script was running for

50 minutes and threw a «Cmdlet not found» error due to a bug in auto-reconnect logic.

Version 0.4578.0

• Added support for configuring the Briefing Email for your organization at the user level with Set-UserBriefingConfig and Get-UserBriefingConfig cmdlets.
• Support for session cleanup using Disconnect-ExchangeOnline cmdlet. This cmdlet is the V2 equivalent of Get-PSSession | Remove-PSSession . In addition to cleaning up session object and local files, it also removes the access token from cache, which is used for authenticating against V2 cmdlets.
• You can now use FolderId as an identity parameter in Get-EXOMailboxFolderPermission. You can get the FolderId value using Get-MailboxFolder. For example: Get-MailboxFolderPermission -Identity : Get-MailboxFolderPermission -Identity :\
• Improved reliability of Get-EXOMailboxStatistics as certain request routing errors which led to failures have been resolved.
• Optimized memory usage when a session is created by re-using any existing module with a new session instead of creating a new one every time session is imported.

Version 0.4368.1

• Added support for Security & Compliance Center PowerShell cmdlets using the Connect-IPPSSession cmdlet.
• Hiding the announcement banner is available using the ShowBanner switch ( -ShowBanner:$false ).
• Terminate cmdlet execution on client exception.
• Remote PowerShell contained various complex data types which were intentionally not supported in EXO cmdlets to improve performance. Differences in non-complex data types between remote PowerShell cmdlets and V2 cmdlets have been resolved to allow seamless migration of management scripts.

Version 0.3582.0

• Support for prefix during session creation.
  • You can create only 1 session at a time that contains prefixed cmdlets.
  • Note that the EXO V2 cmdlets will not be prefixed as they already have the prefix EXO, so don’t use EXO as a prefix.
• Use EXO V2 cmdlets even if WinRM Basic Auth is disabled on client machine. Note that remote PowerShell cmdlets require WinRM Basic Auth, and they won’t be available if it’s disabled.
• Identity parameter for V2 cmdlets now supports Name and Alias as well. Note that using Alias or Name slows down the performance of V2 cmdlets, so we don’t recommend using them.
• Fixed issue where the data type of attributes returned by V2 cmdlet was different from remote PowerShell cmdlets. We still have few attributes which have differing data types, and we plan to handle them in coming months.
• Fixed bug: Frequent sessions reconnects issue when Connect-ExchangeOnline was invoked with Credentials or UserPrincipalName

Version 0.3555.1

• Fixed a bug where piped cmdlets were failing with the following error due to an authentication issue:

Cannot invoke the pipeline because the runspace is not in the Opened state. Current state of the runspace is ‘Closed’.

Вам также может понравиться

Windows или Linux: Что лучше выбрать?

Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux

Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux

Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux

ИТ База знаний Курс по Asterisk Полезно — Узнать IP —