Fortunately, the cmdlets required to initiate a remote Exchange Online PowerShell are downloaded automatically when you create a remote PowerShell session. You should download and install special components before you can open a remote Office 365 session. The process of initiating a remote PowerShell session for Office 365 and Exchange Online is slightly different. ![]() In this case, the console is called remote PowerShell or PowerShell Remoting. However, you can use the built-in PowerShell console to manage remote cloud infrastructures. You can connect to Exchange Online PowerShell, but this process is more complicated than using PowerShell for managing a local Exchange Server. Set-User -Identity -RemotePowerShellEnabled $true Working Principle You can manually enable access to connect to Exchange Online PowerShell for the particular user with the command: Access to Exchange Online PowerShell must be enabled for the current user (by default such access is enabled for administrators).TCP port 80 must be opened to connect from your local machine to the destination host. NET Framework 4.5 or later in addition to installing an updated version of Windows Management Framework 3.0, 4.0, or 5.1. You should use PowerShell on Windows 7 SP1, or newer desktop Windows versions and Windows Server 2008 R2 SP1, or newer server Windows versions. ![]() There are some requirements that must be met to connect to Exchange Online PowerShell.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |