Microsoft Office Tutorials and References
In Depth Information
Preparing the Windows PowerShell environment
As an introduction to Windows PowerShell terminology, be aware that the most basic
object in Windows PowerShell is a cmdlet (pronounced command-let). To use most of the
commands, you will need administrative rights in Office 365 and a workstation configured
to run Windows PowerShell commands.
Preparing the Windows PowerShell environment
In this section of the chapter, we will cover what is needed to use Windows PowerShell from
a workstation to facilitate performing Office 365 tasks.
Windows PowerShell pre-configured for the workstation or
server
We need to validate or prepare a version of the Windows operating system to support
Windows remoting to use features discussed in this chapter. The ability to remotely administer
services is not new to Microsoft. It was first introduced in the .NET Framework in 2002.
To run Windows PowerShell cmdlets on remote systems, you need to prepare your
workstation or server by completing the following tasks:
Configure your environment to run using administrator privileges.
Get the most current Help files.
Import the Office 365 Windows PowerShell module.
Windows PowerShell cmdlets are commonly issued from an administrator’s workstation.
Windows PowerShell commands are issued to Office 365 through a technology called
Windows Remote Management (WinRM).
WinRM includes a scripting application programming interface (API) used to obtain data
from remote computers that follow the Windows Server Management (WS-Management)
protocol, which is why you will sometimes hear Windows PowerShell in Office 365 referred
to as remote Windows PowerShell. In the simplest definition, WinRM has a listener service
that runs on both the administrator’s workstation and the remote server the commands are
sent to. Without WinRM installed and correctly configured, the scripts will not run.
Search JabSto ::




Custom Search