#remote powershell

Merhaba, bu yazımda sizlere remote PowerShell ile uygulama kaldırma işlemini anlatacağım. PowerShell kullanarak uzaktan bir bilgisayardan uygulama kaldırmak için aşağıdaki adımları izleyebilirsiniz. Bu işlem için bilgisayarlar arasında gerekli izinlerin ve ağ erişiminin olduğundan emin olun. Uzaktan Bilgisayara Bağlanma İlk olarak, uzaktan bilgisayara bağlanmak için gerekli izinlere sahip…

Enable-OrganizationCustomization is only available in the Cloud-based Exchange Online & Exchange Online Online Protection products

Status of your tenant – Enable-OrganizationCustomization

Errors that occur with the configuring and deployment of RBAC, rules or coexistence technologies hydration status of your tenant at Office 365.

Each Office 365 tenant is not “hydrated” by default,…

New Post has been published on http://o365info.com/connecting-to-office-365-with-remote/

Connecting to Office 365 with Remote PowerShell – PowerShell Nuggets

In this article we will learn how to use remote PowerShell for connecting to Office 365. This article is tagged under “PowerShell Nuggets”, meaning the style is KIS (Keep It Simple!) In case that you want to read more detailed explanation, use the following link: How to use Remote PowerShell for managing Office 365

Step 1: Download and install required components

Before we can start the remote PowerShell session to Office 365, we need to download the required cmdlets. Additional pre-requirement is to: install the: Office 365 sign in assistant.

You can find the required software component using the following links:

1.1 Office 365 Sign-In Assistant

Microsoft Online Services Sign-In Assistant for IT Professionals RTW

1.2 Office 365 PowerShell cmdlets

Windows Azure Active Directory Module for Windows PowerShell After the installation of PowerShell cmdlets, we will find a new icon on the desktop named: Microsoft Online Services Module for Windows PowerShell.

Step 2: First time configurations

2.1 – Run as Administrator

Right click on the PowerShell Console icon and chose the option: Run as administrator.

2.2- Setting the PowerShell Execution Policy

To change the Execution policy open the Microsoft Online Services Module for Windows PowerShell and type the command:

Set-ExecutionPolicy unrestricted

Step 3: Creating Remote session to Office 365

Open the Microsoft Online Services Module for Windows PowerShell and Type (or copy and paste) the following command:

Connect-MsolService

A pop out windows will appear. Type your credentials by using the UPN (user Principal name) format. For example: [email protected]

Note – the User name should have Global administrator rights in the Office 365 environment.

New Post has been published on http://o365info.com/using-remote-powershell-to-manage_8596/

Using Remote PowerShell to manage Office 365 | Part 3/3

Expand All Headers Collapse All Headers

Part 3: Connect to Exchange Online by using Remote PowerShell

In The former part, we review the steps that we need to use for creating remote PowerShell to Office 365(Windows Azure Active Directory). Connecting to Exchange Online is a little bit different.

(If you prefer to get more “Straight forward version of: Connect to Exchange Online by using Remote PowerShell, you go use the link: Connecting to Exchange Online with Remote PowerShell– PowerShell Nuggets )

We need to use more “complicated” PowerShell command for creating the remote session.

There is no need for download or install pre-requirement software, the Exchange Online cmdlets will be downloaded locally as part of the remote session

we can use the built-in PowerShell console ( no need to use the Microsoft Online Services Module for Windows PowerShell shortcut)

Using Copy & Paste option.

When we manually type PowerShell command, the command may include a syntax or spelling errors. To avoid these scenarios, we can use the Copy/Paste option. For example: when a PowerShell command displayed in the article, you can copy the command. Open the PowerShell console, right click on the console and chose the option: “Paste”

Step 1: First time configurations

1 – Run as Administrator.

To change the PowerShell Execution Policy, we need to run the Windows PowerShell, by using the option: Run as administrator. Right click on the PowerShell Console icon and chose the option: Run as administrator.

2- Change the default PowerShell Execution Policy

By default the PowerShell console will not allow us to run a script. We can enable script execution by changing the default PowerShell Execution Policy to: Unrestricted. (The default mode is: Restricted).

To change the Execution policy open the PowerShell console and type the command:

Set-ExecutionPolicy Unrestricted

To execute PowerShell command, we use the “ENTER” key.

Step 2: Creating remote session to Exchange Online

For creating the remote connection we will need to use a set of three PowerShell commands. Each command perform different task and include variable that serve as a “container” for information such as: user credentials, URL etc..

The first command will cause the PowerShell console to display a “pop out” Authentication window. After entering the required credential, the information will be “delivered” to the “next” command.

The second command include the “Target URL” of the Exchange Online server that will accept our authentication request. The URL that we use function as a “focal point” for all Office 365 customers. Based on the credentials that we provide (that include our domain name), the request will be redirected to the specific Exchange Online server that hosts our organization mailboxes.

The thread command will download the Exchange Online cmdlets to the local host (the desktop that we use for creating the remote PowerShell session.

copy the following “Block” of PowerShell commands and paste it on the PowerShell console:

PowerShell command Example

$cred = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic –AllowRedirection Import-PSSession $Session

A pop out windows will appear. Type your credentials by using the UPN (user Principal name) format. For example: [email protected]

Note – the user name should have global administrator rights in Office 365.

After executing the command, the following message appears:

“WARNING: Your connection has been redirected to the following URI: “https://pod51013psh.outlook.com/PowerShell-LiveID?PSVersion=2.0 ” WARNING: Your connection has been redirected to the following URI: https://dbxprd0312psh.outlook.com/PowerShell-LiveID?PSVersion=2.0 ”

The URL that we use in the command: “https://ps.outlook.com/powershell” serves as a “general address”. Using the credential information that was provided in the former step, the remote session will be redirected to the specific Exchange Online server that host the mailbox of the user that create the session ( in our example the Exchange Online server address is: dbxprd0312psh.outlook.com)

In the last screen we can see the process of the import Exchange Online cmdlets

Congratulations! You are now connected to the Exchange Online.

Step 3: Verifying the remote connection

Q: How can we know if the remote session was successfully created? A: To verify that we are connected, we type the name of Exchange Online cmdlets such as: Get-Mailbox This command will display a list all the mailboxes that was created. In the screenshot you can see the list of Exchange Online mailboxes.

Step 4: Disconnecting the Remote PowerShell session

Remote PowerShell session to Exchange Online, have built in limitation:

The extinction of the remote PowerShell session - The maximum time for inactive (idle) remote PowerShell session is 15 minutes (this limitation is quite flexible because I manage to continue a PowerShell session that was idle for more than 15 minutes).

The amount of data that can be transferred in the remote PowerShell “Channel” (throttling) – Exchange Online environment include a predefined restriction for the amount of data that can be transferred in one time. This limitation is implemented by using “throttling Policy”.

The number of concurrent remote PowerShell session - The maximum number of concurrent PowerShell session that we can use simultaneously is: three

The best practice is to disconnect a remote PowerShell session after we have finished using the required management tasks. For disconnecting the remote PowerShell session use the following command:

Remove-PSSession $Session

The PowerShell indication for successful execution of commands is a little bit poor. The fact that we didn’t receive an error message imply that the operation of “disconnecting the remote PowerShell Session” was successfully complete.

Q: How can know if the remote session was successfully disconnected? A: To verify that the remote session was successfully disconnected you can try to type Exchange Online PowerShell cmdlets such as: Get-Mailbox

The following error will appear:

“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.”

This is actually a good sign (the error was expected). After disconnecting the PowerShell session, the PowerShell cmdlets for Exchange Online are no longer available.

Part 4: working with PowerShell cmdlets – basic introduction

In former articles we review the way for creating a remote PowerShell session to the Office 365 and Exchange Online. In The last part we review the some basic PowerShell commands that will help us to get familiar with the cmdlets and the PowerShell command syntax.

Display list of the cmdlets

Office 365 and Exchange Online include a different set of cmdlets

1. Office 365 cmdlets

To view a list of available Office 365 cmdlets, use following PowerShell command: get-command -module msOnline The name of the Office 365 cmdlets include the string “msol” (Microsoft Online). We can use this naming convention for displaying a list of Office 365 cmdlets, so additional option is to use the command: Get-command *msol*

You can view a reference of Office 365 cmdlets by using the following link: Windows PowerShell cmdlets for Office 365

2. Exchange Online cmdlets

Displaying a list of Exchange Online cmdlets are a little bit different form the way that we use for displaying the Office 365 cmdlets. When we create the remote PowerShell session to Exchange Online all of the cmdlets is dynamically downloaded to the local host. In addition the Exchange Online cmdlets don’t have a specific name convention like the Office 365 cmdlets. To view a list of available Exchange Online cmdlets, use following PowerShell command: Get-Command –Module tmp* You can view a reference of Exchange Online cmdlets by using the following link: Reference to Available PowerShell Cmdlets in Exchange Online

Using the AutoComplete feature

The PowerShell console has a very useful feature named: AutoComplete as the name implies, we can use this feature for automatic compilation of PowerShell commands by typing the first letters of command name is using the TAB key. The AutoComplete option enables us to work quickly and efficiently and in addition help us to avoid from the need to memorize the complete name of the PowerShell command (and avoid from typing syntax mistakes).

Example 1: AutoComplete with Remote PowerShell session to Exchange Online

We want to use the AutoComplete option for the command: Get-Mailbox

Type the command Get-M and hit the TAB key. You will see that the command is completed automatically to: Get-Mailbox

Example 2: AutoComplete with Remote PowerShell session to Office 365

We want to use the AutoComplete option for the command:Get-MsolUser

type the command Get-Msoland hit the TAB key. You will see that the command is completed automatically to: Get-MsolAccountSku This is not the command that we wanted. The Office 365 cmdlets set include couple of cmdlets that begin with the name “Get-Msol“. Using the TAB key, we can browse through all the cmdlets until we will reach to the required cmdlets. In our example we will need to hit the TAB key couple of time until the “right” command (Get-MsolUser) will be displayed.

Additional option that we could use for helping the PowerShell console to “understand” better what we need is: Typing the command Get-Msolu, the addition of the “u” letter will get us to the exact command that we need.

Using PowerShell help

Using the PowerShell is based on a specific syntax that we need to use. One of the distinct advantage of the PowerShell environment is the good help reference for each of the PowerShell cmdlets. To get information about specific cmdlets when can use the following command: Get-Help For example: to learn about the way we use the Get-MsolUser cmdlets type the following command Get-Help Get-MsolUser

If you need more information or examples about how to use the command, we can add the “Detailed” option: Get-Help Get-MsolUser -Detailed

An additional option that we can use is displaying help information in HTML format. We can use this nice trick by adding the option “Online”. For example: Get-help Get-mailbox –Online

Note – in the current time the “Online option” is available only for the Exchange Online environment.

Summary

In this 3 parts article series we learn about:

Why do we need to use PowerShell for managing the Office 365 cloud environment.

How to use remote PowerShell for managing Office 365 and Exchange Online

How to use PowerShell Basic introduction: using PowerShell cmdlets, using the AutoComplete feature and how to get information about the cmdlets that available for us.

I hope you enjoy reading and, May the force of PowerShell will be with you!

Additional reading

The Power of PowerShell

PowerShell

New Post has been published on http://o365info.com/using-remote-powershell-to-manage_212/

Using Remote PowerShell to manage Office 365 | Part 2/3

In this article we will learn how to use remote PowerShell for connecting to Office 365 (Windows Azure Active Directory).

(If you prefer to get more “Straight forward version of: Connect to Office 365 by using Remote PowerShell, you go to: Connecting to Office 365 with Remote PowerShell– PowerShell Nuggets )

To be able to optimize the navigation in the article, you can use the collapse and expand option.

Expand All Headers Collapse All Headers

Step 1: Download and install required components

Before we can start the remote PowerShell session to Office 365, we need to download the required cmdlets. Additional pre-requirement is to: install the: Office 365 sign in assistant.

You can find the required software component using the following links:

1. Office 365 Sign-In Assistant Microsoft Online Services Sign-In Assistant for IT Professionals RTW

2. Office 365Powershell Windows Azure Active Directory Module for Windows PowerShell After the installation of PowerShell cmdlets, we will find a new icon on the desktop named: Microsoft Online Services Module for Windows PowerShell. (An additional option is to use: start menu > All Programs > Microsoft online services> Microsoft online service module for windows PowerShell

Microsoft Online Services Module for Windows PowerShell

The Microsoft Online Services Module for Windows PowerShell shortcut, include a command the will import Office 365 cmdlets to the PowerShell console. Technically we don’t have to use this shortcut. We can manually import the 365 cmdlets to the PowerShell console by using the command: Import-Module MSOnline

Step 2: First time configurations

I must admit that the First-time configurations is a little a bit “Naggers”, but after creating the required settings, the next time will be easier. The PowerShell remote connection requires the following configuration settings:

PowerShell Execution Policy – the connection to the Office 365 is implemented by using remote session commands. PowerShell console relates to this command as “running a script”. To enable script execution, we need to change the PowerShell Execution policy (loosen up to Execution/security policy).

Run as administrator – the command that we use for changing the PowerShell Execution Policy will try to set a new value in the local registry. To be able to create this change in the registry key, we will need to run the PowerShell console by using the option: “Run as administrator”.

WinRM 2.0 – PowerShell is built on top of the Windows Management Framework component, which contains the correct version of Windows PowerShell v2 and WinRM 2.0. If your computer is running Windows 7, you don’t have to install anything, The Windows Management Framework is already installed. In case that you use windows XP workstation, you can download the required software by using the following link:

Windows Management Framework Core package

1 – Run as Administrator

To be able to change the PowerShell Execution Policy, we need to run PowerShell console, by using the option: Run as administrator.

Right click on the Microsoft Online Services Module for Windows PowerShell icon and chose the option: Run as administrator.

2 – Setting the PowerShell Execution Policy

PowerShell security policy (“Execution policy”) can be defined by using one of the following options (modes): Restricted, AllSigned, RemoteSigned, and Unrestricted. (The default mode is: Restricted). To change the Execution policy open the Microsoft Online Services Module for Windows PowerShell and type the command:

Set-ExecutionPolicy Unrestricted

To execute PowerShell command, we use the “ENTER” key.

Step 3: Connect to Office 365 by using Remote PowerShell

Open the Microsoft Online Services Module for Windows PowerShell and Type (or copy and paste) the following command:

Connect-MsolService

A pop out windows will appear. Type your credentials by using the UPN (user Principal name) format. For example: [email protected]

Note – the user name should have global administrator rights in the Office 365 environment.

Congratulations! You are now connected to the Office 365.

PowerShell Interface is a little bit “stingy” in providing Indication such as: “you are now connected”. In the PowerShell environment, the fact that we did not get any error message indicates that “everything is O.K” (most of the times).

Step 4: Verifying the remote connection

Q: How can we know if the remote session was successfully created? A: To verify that we are connected, we can use the most basic Office 365 cmdlets:

Get-Msoluser

This command will display a list all Office 365 users. In the screenshot you can see a list of Office 365 users

Summery

In this article we review the following items:

The pre-requirement software component

PowerShell console – First time configuration

How to create remote PowerShell session to Office 365 + verify the remote PowerShell session

Next step

in part 3 we will learn how to crate Remote PowerShell for managing Exchange:

Part 3: Connect to Exchange Online by using Remote PowerShell Part 4: working with PowerShell cmdlets – Basic introduction

Additional reading

Manage Windows Azure Active Directory by using Windows PowerShell

Watch the Video: Connect to Office 365 by – using Remote PowerShell

New Post has been published on http://o365info.com/using-remote-powershell-to-manage_26/

Using Remote PowerShell to manage Office 365 | Part 1/3

Did you ever find yourself struggling with the PowerShell console trying to connect to the Office 365 services? Did the thought “what the heck I need to use command line interface for managing a modern cloud environment” ever pass in your mind? If the answer is “Yes,” you came to the right place!

Table of content

Part 2/4: How to use Remote PowerShell for managing Office 365

Part 3/4: How to use Remote PowerShell for managing Exchange Online

Q: Why should I use the “boring” command line interface instead of using the friendly web interface? A: PowerShell is a very powerful tool. By using PowerShell, we can execute bulk operations. The meaning of the term “bulk” is: using a single command for creating configuration settings for a large group of objects such as users and mailboxes. Additionally, although we can perform many functions using the Web interface, a significant part of the management tasks can be performed only by using PowerShell.

Note – if we want to be more processes, the PowerShell serves as a platform for the entire Office 365 infrastructure. Each time we use the Web interface, the “selection” is translated to PowerShell command.

Office 365 and PowerShell Basic Terms

Office 365

Office 365 is a suite of cloud application/services that includes: Exchange Online, LYNC Online, SharePoint Online + Administration environment for managing: users, groups, licensing, domains etc.

Office 365 management

Along the article, we will mention the term “Office 365 management” or “connecting to Office 365”. The meaning is: connecting to the Office 365 parts that serve as an “envelope” of all other Office 365 Services/Applications (such as Exchange Online, SharePoint Online and LYNC Online). This part includes components such as: user and group object (Azure Active Directory), Domain name’s management, mail migration, SSO (Single sign on), subscription and license management and more.

Exchange Online management

Exchange Online is the Microsoft cloud version of Exchange server 2013 (This information was correct for the time when the article was written). The management of Exchange Online is implemented by using the Web interface (ECP – Exchange control panel) and of course, by using PowerShell. Exchange Online management includes tasks such as: mailbox management (Mailbox permissions, sharing calendars, etc.), Transport Role, Retention Policy, archive mailbox and more.

PowerShell console

The PowerShell console is a built-in component in all the modern Microsoft OS such as windows 7/8 and Windows server 2008/2012. In case that you use “older” OS such as windows XP, you will need to download and install the PowerShell and additional components.

cmdlets

PowerShell commands are called: cmdlets. The cmdlets are small or “mini application” that serves for management of specific objects such as: users, group, file, service, etc. The OS PowerShell includes a predefined set of cmdlets for OS management, but if we want to use PowerShell cmdlets for a specific application, we need to download a dedicated set of cmdlets that was created for the specific software or service (such as Office 365 or Exchange Online).

Remote PowerShell

Most of the time, we use the PowerShell for managing local or domain member’s machines. But what about the option of managing remote infrastructures such as the cloud? The ability to use local PowerShell console for managing remote infrastructure such as Office 365 and Exchange Online, described as: Remote PowerShell or PowerShell Remoting. This article is all about how the use remote PowerShell for connecting to Office 365.

Remote PowerShell: Office 365 verses Exchange Online

It’s important to understand that we use remote PowerShell for managing two environments. We need to use different sets of PowerShell cmdlets for each of the infrastructures, and the way that we implement the remote PowerShell session for each of the environments is different. For example, when we use remote PowerShell session for managing the Exchange Online environment, all of the required cmdlets will be downloaded in “real time,” time”, to the local host as part of the remote PowerShell session. The process of creating a remote session to Office 365 requires downloading and installing specific cmdlets before we can create the remote session.

New Post has been published on http://o365info.com/connecting-to-exchange-online-with/

Connecting to Exchange Online with Remote PowerShell – PowerShell Nuggets

In this article we will learn how to use Remote PowerShell for connecting to office 365 Exchange Online

This article is tagged under “PowerShell Nuggets”, meaning the style is KIS (Keep It Simple!) In case that you want to read more detailed explanation, use the following link: Using Remote PowerShell to manage Office 365 | Part 3/3

Step 1: First time configurations

1.1 – Run as Administrator

Right click on the PowerShell Console icon and chose the option: Run as administrator.

1.2- Setting the PowerShell Execution Policy

To change the Execution policy open the Microsoft Online Services Module for Windows PowerShell and type the command:

Set-ExecutionPolicy unrestricted

Step 2: Creating remote session to Exchange Online

For creating the remote connection we will need to use  a set of three PowerShell commands. Each command perform different task and include variable that serve as a “container” for information such as: user credentials, URL etc..

Using Copy & Paste option. When we manually type PowerShell command, the command may include a syntax or spelling errors. To avoid these scenarios, we can use the Copy/Paste option. For example: when a PowerShell command displayed in the article, you can copy the command. open the PowerShell console, right click on the console and chose the option: “Paste” copy the following “Block” of PowerShell commands and paste it on the PowerShell console:

$cred = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic –AllowRedirection Import-PSSession $Session

A pop out windows will appear. Type your credentials by using the UPN (user Principal name) format. For example: [email protected]

Note – the user name should have global administrator rights in the office 365 environment.

Step 3: Disconnecting the remote connection

For disconnecting the remote PowerShell session use the following command:

Remove-PSSession $Session