PowerShell for Windows Admins:

December, 2017


December 31, 2017  2:30 PM

PowerShell in 2018

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

So what is going to happen for PowerShell in 2018? In April we have the Summit. Our biggest ever Summit with many more speakers, more sessions and new things including Iron Scripter. We’ll be starting the build up in early January so keep an eye on powershell.org. PowerShell v6 will be GA...

December 30, 2017  6:58 AM

Cross platform PowerShell remoting

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

An interesting article on the Scripting Guy blog - 0 Comments     RSS Feed     Email a friend


December 28, 2017  10:34 AM

2017 – a year of PowerShell

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

This is a good time to review what happened in the PowerShell community in 2017. It’s my perspective so is obviously biased based on my experiences. The 2017 PowerShell Summit was an early highlight of the year. We sold out in early February and all registrations were for the whole f0ur days....


December 21, 2017  12:08 PM

Windows Updates CIM classes

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
CIM, Powershell, WSUS

When Windows 10 and Server 2016 were released they contained a new CIM namespace - ROOT/Microsoft/Windows/WindowsUpdate This contained a CIM class MSFT_WUOperationsSession that had 2 very useful methods – ScanForUpdates and ApplyApplicableUpdates. These methods enabled you to find and...


December 19, 2017  12:19 PM

Test-Path -PathType

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

Test-Path is a useful cmdlet for testing the validity of a path. You get a True/False return depending on if the path exists or not. There’s also a way to add to the test by determining if the path points to a container (folder) or a leaf (file) using the –PathType parameter. Here’s...


December 16, 2017  9:20 AM

PowerShell v6: #9 Release candidate 2 features

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

A couple of features of PowerShell v6 release candidate 2 need commenting on. Firstly, I was surprised when installing RC 2 on a Windows 10 machine (Insider build) that RC1 was removed. In the past you’ve been able to run numerous versions of PowerShell v6 side-by-side. This has consequences...


December 15, 2017  2:28 PM

PowerShell v6: #8 Release candidate 2

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

Release candidate 2 for PowerShell v6 is available for download from - https://github.com/PowerShell/PowerShell/releases One worrying point is the the OpenSSH implementation...


December 13, 2017  9:51 AM

Using the Where method

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

You don’t usually see people using the where method. A recent question on the forums highlighted using the where method. PowerShell deals in collections and will automatically create a collection of objects if the are multiple objects returned for instance $procs = Get-Process Iterating...


December 10, 2017  7:30 AM

Avoid the truncation in the display

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

A question came up regarding my recent post about using the file system COM object to get folder sizes. The question was about the folder path and how you could see the whole path. In other words how to avoid the truncation in the display and the three dots. When PowerShell displays objects it...


December 6, 2017  9:19 AM

PowerShell v6: #7 Module paths

Richard Siddaway Richard Siddaway Profile: Richard Siddaway
Powershell

There is a very significant gap between the functionality available in PowerShell v6 as opposed to PowerShell v5.1. In part this is due to the underlying version of .NET but mainly to the defined module paths in the two versions. In PowerShell v5.1 I have: PS> $env:PSModulePath -split...


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: