PowerShell Core – Power BI Gateway Management CmdLets

November 6, 2019

Keep in mind that these cmdlets are PowerShell CORE only !

First you need to check the availability of the PS CORE version on your system.

I had  6.1 preview 3 installed

image

So I opened the Cmd line using Admin privileges

Next started PWSH.exe

Next I run this command :

Install-Module -Name DataGateway

image

Next Check the available cmdlets

Get-Command -Module DataGateway*

image

Next I ran this command

Import-Module DataGateway

image

But it says my version of PS Core needs to be minimum 6.2.2 Sad smile

So first get an upgrade from here :

https://github.com/PowerShell/PowerShell

image

After upgrading your can check the version using

$PSVersionTable

image

Next run these commands again :

import-module DataGateway
import-module DataGateway.profile

image

No errors now Smile

Run this command to login :

Login-DataGateway

It opens the browser and return this message

image

image

Next run this command to get your Cluster ID

Get-DataGatewayCluster

Next check the Gateway Status like this

Get-DataGatewayClusterStatus

image

So far so good Smile 

Enjoy !!


Windows 10 – Running ASP.NET Core 2.0 on Mono

August 5, 2018

 

After installing Mono on Ubuntu using Windows 10 WSL, see here

You can start cross compiling you ASP .NET Core 2.0 Apps to run on Mono

 

1. Publush for Linux

Use this command : dotnet publish -r linux-x64 -c Release

image

2. Install DotNet Core on Ubuntu :

First in widows go to the project folder where you find the published project see step 1.

image

And start the WSL there. Open command prompt in that folder and run BASH

image

Run these commands to install .Net Core Framework on Mono :

curl https://packages.microsoft.com/keys/microsoft.asc | gpg –dearmor > microsoft.gpg

sudo mv microsoft.gpg /etc/apt/trusted.gpg.d/microsoft.gpg

sudo sh -c ‘echo “deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-ubuntu-xenial-prod xenial main” > /etc/apt/sources.list.d/dotnetdev.list’

sudo apt-get update

sudo apt-get install dotnet-sdk-2.1.3

 

3. Install and Configure Web Server Nginx

sudo apt-get install nginx

It runs on PORT 80 by default, so stop other windows webservers if needed.

image

next run this command :

sudo service nginx start

And test it by opening a browser in windows, you should see this webpage.

 

clip_image002

To stop the webserver run :

sudo service nginx stop

 

4. Configure nginx as reverse proxy server

 

Go in Windows to the Linux installation folder …

Open the file in Notepad++ and make the make the following changes in the DEFAULT file:

clip_image002[6]

C:\Users\xxxx\AppData\Local\lxss\rootfs\etc\nginx\sites-available

Change the default port from 80 to whatever you like, example 81

Comment out this line : #try_files $uri $uri/ =404;

Add this line proxy_pass line : proxy_pass http://localhost:5000;

 

image

You can also use the VI editor in Linux if you like this :

sudo vi /etc/nginx/sites-available/default

Now test the config changes are working :

sudo nginx -t

If you did not stop the server you can do a reload :

sudo nginx -s reload

 

6. Test the .Net Core App in WSL using Bash

Open Bash in the Published folder

clip_image002[8]

And TEST the Linux .Net Core application like this :

dotnet FirstMvc.dll

image

 

I get an error because the Linux is CASE Sensitive. So try again using the correct command.

And the SQL Database location is not found.

Because I started it not from the default folder location, which should be C:\CoreIoT\ASPnetRazorSQLiteWsAPI\Data

 

image

But all runs well, so the .NET Core App is a try cross platfrom framework Smile

Enjoy!


PowerShell Core – Installation on Windows 10 – Ubuntu WSL

July 4, 2018

Here you can find the correct installation instructions for Ubuntu 16 (and many more like Raspbian, …)

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-linux?view=powershell-6

1. Open Bash on Windows 10

image

2. Install PowerShell Core

These are the commands needed to get it installed.

# Import the public repository GPG keys
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -

# Register the Microsoft Ubuntu repository
sudo curl -o /etc/apt/sources.list.d/microsoft.list https://packages.microsoft.com/config/ubuntu/16.04/prod.list

# Update the list of products
sudo apt-get update

# Install PowerShell
sudo apt-get install -y powershell

# Start PowerShell
pwsh

3. Installation process

It looks like this on Windows 10 – Bash

image

4. Test PowerShell

image

5. Let’s connect to O365 – Exchange Online

image

Get-Mailbox

image

Other Commands

Make sense work fine … Get-Service doesn’t work because it is a Windows Command Winking smile

image

All seems OK Smile

Enjoy !


PowerShell Core – How to install the Windows Compatibility Pack

July 3, 2018

First find the correct PowerShell Core Module

Find-Module -Name PSCoreWindowsCompat | ft -a 

 

As you can see it only runs on Windows x64 bit !

clip_image002

Keep in mind that this Windows Compatibility Pack is a Temporary solution from MS, and will not stay forever :

http://lunarfrog.com/blog/windows-compatibility-pack-net-core

Windows Compatibility Pack for .NET Core is not a permanent solution which will stay in codebase forever. Intention of the pack is to build a temporary bridge, allowing adoption of .NET Core to a greater extend. However, in the long term the goal stays the same – replace outdated APIs and features of .NET with newer .NET Standard-compatible alternatives.

You can download it before installing using this command

Save-Module -Name PSCoreWindowsCompat -Repository PSGallery -Path C:\Temp\ -Force 

 

Or install it directly

Install-Module -Name PSCoreWindowsCompat -Repository PSGallery -Verbose -Force 

 

As you can see it needs Administrator Privileges

clip_image004

 

Import the Module PSCoreWindowsCompat

Import-Module -Name PSCoreWindowsCompat 

 

You have to use the DotNet Classes instead of Cmdlets.

For instance the Compatibility pack contains the System.DirectoryServices so you can script against AD.

Like this :

$dom = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()

$root = $dom.GetDirectoryEntry()

$search = [System.DirectoryServices.DirectorySearcher]$root

$search.Filter = "(&(objectclass=user)(objectcategory=user))"

$search.SizeLimit = 3000

$result = $search.FindAll()

foreach ($user in $result){

$user.Properties.distinguishedname 

} 

Compared to Windows PowerShell

Get-ADUser -Filter * | select DistinguishedName 

 

But it works perfectly … Smile

image

 

For .Net Core Applications see here :

https://www.nuget.org/packages/Microsoft.Windows.Compatibility

Run this command :

dotnet add package Microsoft.Windows.Compatibility –version 2.0.0

Enjoy !


PowerShell Core – Connecting to O365 Exchange Online

July 3, 2018

Now that we have PowerShell running on Windows 10… let’s see if we can get use it to get access to O365 Exchange Online.

 

First you need to load the MSOnline Windows PowerShell  Modules in PowerShell Core.

This is done using these 3 Lines :

Install-Module WindowsPSModulePath -Force -Scope CurrentUser 
 
Add-WindowsPSModulePath

Import-Module MsOnline

 

image

If you don’t use the first 2 lines you will get an error. Because PS Core doesn’t have the MSOline Module available.

So we grab it from the Windows PowerShell.

 

let’s set the credentials

$UserCredential = Get-Credential

image

Next create the remote session to load the module

 

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

image

 

Test it using some commands

image

Get-User

image

 

For Mac see here :

https://www.cgoosen.com/2017/03/connecting-to-exchange-online-with-remote-powershell-from-a-mac/

For the other O365 Services see here :

https://www.michev.info/Blog/Post/1954/powershell-core-and-office-365

Enjoy !


PowerShell Core – Running on Windows IoT using a RPI3

July 2, 2018

As mentioned on this post

I was planning to test PowerShell Core on Windows IoT running on an ARM platform using RPI3….

PS Core Version 6.x claims to be a cross platform Smile

It is still experimental as mentioned here :

https://docs.microsoft.com/en-us/powershell/scripting/setup/powershell-core-on-arm?view=powershell-6

So let’s take a look :

1. Download the correct ZIP

https://github.com/PowerShell/PowerShell/releases

Windows IoT running on RPI3 is a 32bit version (if you are using the free version)

image

2. Open the ZIP

This contains all the modules needed to run on your RPI3

image

Extract and copy all files over to your destination RPI3 folder.

 

image

For example c:\pscore

 

3. Setup Remoting on RPI3

Run this command and see PS notes :

You’ll get an error message and will be disconnected from the device because it has to restart WinRM

 

image

 

# Be sure to use the -PowerShellHome parameter otherwise it'll try to create a new
# endpoint with Windows PowerShell 5.1
.\Install-PowerShellRemoting.ps1 -PowerShellHome .
# You'll get an error message and will be disconnected from the device because it has to restart WinRM

 

4. Connect to the PS Core on your RPI3

# Be sure to use the -Configuration parameter.  If you omit it, you will connect to Windows PowerShell 5.1
Enter-PSSession -ComputerName <deviceIp> -Credential Administrator -Configuration powershell.6.0.2

image

 

5. How to run Windows PowerShell modules in PowerShell Core

Run these 2 commands to get access to the Windows PS modules

 

Install-Module WindowsPSModulePath -Force -Scope CurrentUser 

Add-WindowsPSModulePath

 

image

Or this way for a custom module

Import-Module "C:\Program Files (x86)\AutoIt3\AutoItX\AutoItX.psd1"
Get-Command *au3*

 

image

image

6. Test PS Core on your RPI3

image

All runs as expected Smile

 

But keep in mind that not all functions are supported (yet)

image

 

Even if it says so see help Sad smile

image

 

Running PowerShell Core on Linux or Mac see here to get started :

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-linux?view=powershell-6

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-macos?view=powershell-6

Enjoy !


PowerShell Core – Installing and Testing

July 2, 2018

PowerShell Core has reached version 6.1xxx at this moment …

 

Why do you need PS Core v6.1.x

https://blogs.msdn.microsoft.com/powershell/2018/01/10/powershell-core-6-0-generally-available-ga-and-supported/

https://docs.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-core-60?view=powershell-6

https://blogs.msdn.microsoft.com/powershell/2018/01/24/powershell-core-6-1-roadmap/

 

How to install

Since PS Core is a cross platform distribution, just pick the one you need Smile

https://github.com/PowerShell/PowerShell/releases

 

Download and run for a Windows 10 SxS installation

 

image

 

Select Open PS Core

or start is manually

image

Testing

In order to run PS Core you need to use the pwsh.exe commandline and not powershell.exe !

Check the PS Core version :

run pswh.exe –v

image

Or the famous command

$psversiontable

 

image

PowerShell core does not have all the modules of the full blown version available.

But it has already a lot… run

get.command 

it will list about 425 commands

image

 

If you need more :

Windows PowerShell Compatibility Pack

With the announcement of the Windows Compatibility Pack for .NET Core for .NET Core, PowerShell Core will regain some APIs that had been dropped in the transition to .NET Core.  This means we can re-enable some cmdlets that weren’t part of the PowerShell Core 6.0 release: WMI, EventLog, and PerfCounters.  In addition, some highly requested APIs will be available which means that some existing Windows PowerShell modules might just work in PowerShell Core 6.0.  This module will replace the WindowsPSModulePath module to add the Windows PowerShell $env:PSModulePath to PowerShell Core 6.0.  Finally, we can use this module to optionally add back some aliases that we removed from PowerShell Core 6.0 that exist in Windows PowerShell.

Example it allows you to run encrypted commands as well out of the box… Smile

image

 

For a full list of command line options run pwsh.exe /? (or –h or –help or …. Winking smile )

Most relevant are :

pwsh -NoExit -Command Get-Date

image

 

Some of the commands you need to run using Administrator privileges or you get this error :

image

pwsh -Command {Get-WinEvent -LogName security} or pwsh -command “& {Get-WinEvent -LogName security}”

image

 

You can run Windows PowerShell modules in PowerShell Core on Windows

 

Install-Module WindowsPSModulePath -Force -Scope CurrentUser 

Add-WindowsPSModulePath

 

Next episode I will test it the PS Core on an RPI3 running Windows IoT, see here

Enjoy!