PowerShell for Windows Admins


May 18, 2017  2:24 PM

Table or List

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

A question on the forum asked why a object is displayed in a table if it has 4 or fewer properties and as  a list if it  has more than 4 properties:

PS> [PSCustomObject]@{P1=1; P2=2; P3=3; P4=4}

P1 P2 P3 P4
-- -- -- --
 1  2  3  4


PS> [PSCustomObject]@{P1=1; P2=2; P3=3; P4=4; P5=5}


P1 : 1
P2 : 2
P3 : 3
P4 : 4
P5 : 5

This is a built in mechanism in PowerShell and is done automatically.

The quick way to get the output in table format is to use Format-Table

PS> [PSCustomObject]@{P1=1; P2=2; P3=3; P4=4; P5=5} | Format-Table

P1 P2 P3 P4 P5
-- -- -- -- --
 1  2  3  4  5

May 10, 2017  3:39 AM

PowerShell v6 beta

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

PowerShell v6 has reached a significant milestone – the release of the first PowerShell v6 beta version. There have been 18 releases of alpha code since August 2016 when the open source PowerShell v6 project started.

There is no indication of how many beta releases there will be before PowerShell v6 is ready to ship.

Code is available from https://github.com/PowerShell/PowerShell/releases


May 9, 2017  3:23 AM

Are your domain controllers real?

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Active Directory, CIM, Powershell

A question on the forum asked about discovering if domain controllers are physical or virtual machines. In other words Are your domain controllers real?

This will do the job:

foreach ($domain in (Get-ADForest).domains) {
 Get-ADDomainController -filter * -server $domain |
 sort hostname |
 foreach {
 Get-CimInstance -ClassName Win32_ComputerSystem -ComputerName $psitem.Hostname |
 select PSComputerName, Manufacturer, Model
 }
 }

Get the domains in your forest and then for each domain get the domain controllers. Get-ADDomainController outputs an object with a property of hostname – but you need a computername for Get-CimInstance. So, use a foreach-object and use the Hostname property as shown (you could create a property ComputerName on the pipeline object but its more work) and get the results. A virtual machine will show under the Model. You can sort or whatever once you have the results.


May 3, 2017  10:07 AM

OpenSSH

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

PowerShell v6 enables remoting over SSH between Linux and Windows machines. SSH connectivity is established using OpenSSH. You can use remoting over SSH in any of these scenarios:

Windows – Linux
Linux – Windows
Windows – Windows
Linux – Linux

You can also establish traditional WinRM remoting sessions and send commands to a mixture of WinRM and SSH based sessions.

A couple of new initiatives around OpenSSH need widespread participation.

First off – OpenSSH security testing

The PowerShell Team is getting OpenSSH production ready and as part of that are arranging for security testing. Details of how you can be involved are available from:

OpenSSH Security Testing Kick Off

Secondly – installing OpenSSH involves a significant number of manual steps. An OpenSSH Universal Installer is available for testing

https://cloudywindows.com/post/unveiling-the-openssh-universal-automated-installer/


May 1, 2017  3:33 PM

Positional parameters

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

Positional parameters have been around since the beginning of PowerShell. Positional parameters assume the parameter you mean from the position of the value in the command you supply. For instance you can do this:

Get-ChildItem -Path C:\test\ -Filter *.xml

Path and filter are the 2 positional parameters for Get-ChildItem (cmdlets can have 0, 1 or many positional parameters) so you can also do this:

Get-ChildItem C:\test\  *.xml

If you reverse the values you get an error

PS> Get-ChildItem *.xml  C:\test\
Get-ChildItem : Second path fragment must not be a drive or UNC name.
Parameter name: path2
At line:1 char:1
+ Get-ChildItem *.xml  C:\test\
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (C:\Scripts:String) [Get-ChildItem], ArgumentException
    + FullyQualifiedErrorId : DirArgumentError,Microsoft.PowerShell.Commands.GetChildItemCommand

You can find the position parameters by looking in the help file

PS> Get-Help Get-ChildItem -Parameter path

-Path <String[]>
    Specifies a path to one or more locations. Wildcards are permitted. The default location is the current directory
    (.).

    Required?                    false
    Position?                    0
    Default value                Current directory
    Accept pipeline input?       True (ByPropertyName, ByValue)
    Accept wildcard characters?  false

PS> Get-Help Get-ChildItem -Parameter filter

-Filter <String>
    Specifies a filter in the provider's format or language. The value of this parameter qualifies the Path parameter.
    The syntax of the filter, including the use of wildcards, depends on the provider. Filters are more efficient than
    other parameters, because the provider applies them when retrieving the objects, rather than having Windows
    PowerShell filter the objects after they are retrieved.

    Required?                    false
    Position?                    1
    Default value                None
    Accept pipeline input?       False
    Accept wildcard characters?  false

Notice the position values. A parameter that has to be named i.e. non-positional will have Named as the value for position:

PS> Get-Help Get-ChildItem -Parameter include

-Include <String[]>
    Specifies, as a string array, an item or items that this cmdlet includes in the operation. The value of this parameter qualifies the Path parameter. Enter a path element or pattern, such as *.txt. Wildcards are permitted.

    The Include parameter is effective only when the command includes the Recurse parameter or the path leads to the contents of a directory, such as C:\Windows\*, where the wildcard character specifies the contents of the  C:\Windows directory.

    Required?                    false
    Position?                    named
    Default value                None
    Accept pipeline input?       False
    Accept wildcard characters?  false

You can also identify positional parameters from the syntax listing

Get-ChildItem [[-Path] <String[]>] [[-Filter] <String>] [-Attributes {ReadOnly | Hidden | System | Directory | Archive | Device | Normal | Temporary | SparseFile | ReparsePoint | Compressed | Offline | NotContentIndexed | Encrypted | IntegrityStream | NoScrubData}] [-Depth <UInt32>] [-Directory] [-Exclude <String[]>] [-File] [-Force]
[-Hidden] [-Include <String[]>] [-Name] [-ReadOnly] [-Recurse] [-System] [-UseTransaction] [<CommonParameters>]

The name of positional parameters are surrounded by square brackets

A question on the forum noted that the help file about_parameters states that positional parameters are numbers 1,2,3… and named parameters are effectively numbered 0 BUT the help file for Get-ChildItem numbers the positional parameters as 0 & 1

What’s happening?

If I remember correctly originally positional parameters were numbered from 1 but that was changed so 0 didn’t mean named. Looks like the about file didn’t get updated.

We can test this this with a function:

function test-pp {
 [CmdletBinding()]
 param (
   [Parameter(Position=0)]
   [int]$x,

   [Parameter(Position=1)]
   [string]$y
 )

 "$x is a number"
 "$y is a string"
}

PS> test-pp -x 2 -y abc
2 is a number
abc is a string

PS> test-pp 2 abc
2 is a number
abc is a string

So using position 0 works for positional parameters. What if we number them 1 & 2

function test-pp {
 [CmdletBinding()]
 param (
   [Parameter(Position=1)]
   [int]$x,

   [Parameter(Position=2)]
   [string]$y
 )

 "$x is a number"
 "$y is a string"
}

PS> test-pp -x 2 -y abc
2 is a number
abc is a string

PS> test-pp 2 abc
2 is a number
abc is a string

Works as well.

I’d recommend starting your positional parameter numbering from 0 and assume that about_parameters needs updating


April 30, 2017  1:26 PM

ISE or VS code?

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

When PowerShell v2 shipped with the ISE it was seen as a great step forward. We now had a decent editor for creating PowerShell code and running that code. You could also invoke the debugger. Some extensions to ISE have occurred, most notably  Show-Command, but its essentially the same editor as in PowerShell v2

Visual Studio Code – now at version 1.11.2 – offers an interesting alternative. It manages a host of other languages as well as PowerShell. I currently have the extensions for Docker, Markdown, SQL, PowerShell, JSON and XML loaded. Many others are available as open source projects.

You can also open a terminal window which can be a command prompt, PowerShell or WSL bash – you could have all 3 open simultaneously if required.

The other big plus is that VS Code is cross platform so I can use the same editor on Windows and Linux. A big plus in these days of heterogeneous environments.

I’m going to try using VS Code instead of ISE for a while to see if it suits the way I work. If so it’ll become my default editor


April 30, 2017  9:58 AM

IT Professional?

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Opinion

Way back when we were known as Administrators. Then the term IT Professional (often irritatingly shortened to IT Pro) appeared. We’re doing the same job but have a fancy new title.

Are System Administrators really professionals in the true sense of the word.

I would argue no.

– We don’t have universally recognised certification/qualification requirement

– We don’t have a professional body

– We don’t have an continuous learning requirement to maintain the title

– We don’t have a recognised body of knowledge that accurately defines how and what we should do

You may argue with these points and say for instance that you do keep learning – congratulations – you’re in the minority that does.

We have partial answers to my points for instance vendor certifications and best practice documentation but at the moment its all very piecemeal.

If IT wants to be treated as a profession its practitioners have to behave as professionals and at the moment I don’t think that happens in the vast majority of cases. There are exceptions and hopefully over time that behaviour will become the norm. Until then I’m going to stick with Administrators.


April 29, 2017  1:24 PM

DevOps ebook

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
DevOps

DevOps is the latest “big thing” in IT. Whether it will make a difference or be dropped as everyone rushes to embrace the next “big thing” only time will tell.

For now, there’s a free ebook from the DevOps Collective (the people who bring you the PowerShell Summit) that looks at DevOps from the OPs perspective:

https://www.gitbook.com/book/devopscollective/devops-the-ops-perspective/details


April 29, 2017  12:31 PM

DSC Configuring Sharing

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Desired State Configuration

A new set of repositories on Github document a process for sharing end-to-end scenario based DSC configurations

https://blogs.msdn.microsoft.com/powershell/2017/04/28/dsc-configuration-sharing/

These are open to community involvement


April 28, 2017  2:22 PM

Mass dismount VHDs

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell, Virtual Disk

I’m going to be creating, using and discarding a number of VHDs for my diskpart and PowerShell series. When I have a number of them mounted I want a quick way to dismount them. Assuming I consistently keep them in the same folder then this very nicely does the job

Get-ChildItem -Path C:\test\ -Filter *.vhdx | Dismount-VHD

Why does it work?

Because Get-ChildItem emits System.IO.FileInfo objects that have a Path property and Dismount-VHD accepts pipeline input for the Path of the VHD to dismount:

-Path <String[]>
Specifies one or more virtual hard disk files for which the corresponding virtual hard disks are to be dismounted.

Required?                    true
Position?                    1
Default value                none
Accept pipeline input?       true (ByValue, ByPropertyName)
Accept wildcard characters?  false


Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: