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 in […]
Archive for December, 2017
PowerShell in 2018
Posted by: richardsiddaway | December 31, 2017 Comments Off on PowerShell in 2018 |Cross platform PowerShell remoting
Posted by: richardsiddaway | December 30, 2017 Comments Off on Cross platform PowerShell remoting |An interesting article on the Scripting Guy blog – https://blogs.technet.microsoft.com/heyscriptingguy/2017/12/29/cross-platform-powershell-remoting-in-action/ discusses using SSH remoting in PowerShell v6. Some of the code needs tightening up but its a good first step for combining v6 and v5.1
2017 – a year of PowerShell
Posted by: richardsiddaway | December 28, 2017 Comments Off on 2017 – a year of 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. This was […]
Windows Updates CIM classes
Posted by: richardsiddaway | December 21, 2017 Comments Off on Windows Updates CIM classes |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 install updates from the Windows Update site or a WSUS server if you’d configured […]
Test-Path -PathType
Posted by: richardsiddaway | December 19, 2017 Comments Off on Test-Path -PathType |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 […]
PowerShell v6: #9 Release candidate 2 features
Posted by: richardsiddaway | December 16, 2017 Comments Off on PowerShell v6: #9 Release candidate 2 features |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 if the behaviour continues into […]
PowerShell v6: #8 Release candidate 2
Posted by: richardsiddaway | December 15, 2017 Comments Off on PowerShell v6: #8 Release candidate 2 |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 which is required for remoting to and from Linux systems doesn’t appear to be any where near a release candidate – https://github.com/PowerShell/Win32-OpenSSH/releases. The latest release as of this writing is 0.0.24.0. The steps […]
Using the Where method
Posted by: richardsiddaway | December 13, 2017 Comments Off on Using the Where method |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 over a process can take time. PowerShell introduced 2 […]
Avoid the truncation in the display
Posted by: richardsiddaway | December 10, 2017 Comments Off on Avoid the truncation in the display |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 will […]
PowerShell v6: #7 Module paths
Posted by: richardsiddaway | December 6, 2017 Comments Off on PowerShell v6: #7 Module paths |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 ‘;’ C:\Scripts\Modules C:\Users\Richard.MANTICORE\Documents\WindowsPowerShell\Modules C:\Program Files\WindowsPowerShell\Modules C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules […]
Categories
- .NET
- Active Directory
- Architecture
- Azure
- Bash
- BITS
- Books
- CDXML
- CIM
- Cloud
- COM
- Containers
- Deep Dive
- Desired State Configuration
- DevOps
- DHCP
- DNS
- DSC
- European Summit
- Events
- Exchange
- File System
- Firewall
- General
- General IT Matters
- Hyper-V
- IIS
- Infrastructure
- IT Community
- IT Security
- Learning PowerShell
- Linux
- Math
- Microsoft
- Modules
- Nano Server
- Networking
- Office 2010
- Office 2013
- Open Source
- Opinion
- Outlook
- Philosophy
- PowerShell
- PowerShell 7
- PowerShell and .NET
- PowerShell and Active Directory
- PowerShell and CIM
- PowerShell and Exchange 2007
- PowerShell and IIS
- PowerShell and SQL Server
- PowerShell and WMI
- PowerShell Basics
- PowerShell original
- PowerShell Summit
- PowerShell User Group
- PowerShell User Group 2
- PowerShell v2
- PowerShell V3
- PowerShell v4
- PowerShell v5
- PowerShell v6
- PowerShell.org
- PowerShellGet
- PowerShellV2
- PSAM
- Rant
- Registry
- Scripting
- Scripting Games
- Scripting Games 2104
- Security
- SQL Server
- Storage
- Strings
- Summit
- Technology
- Uncategorized
- Virtualization
- Windows 10
- Windows 2012 R2
- Windows 7
- Windows 8
- Windows 8 Server
- Windows 8.1
- Windows Server
- Windows server 1709
- Windows Server 2008
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- WMFv5
- WPF
- WSUS