In my recent post about getting server information from a IIS web server I said I post about getting similar information from later machines. You still have the root\MirosoftIISv2 namespace available if you install the IIS 6.0 tools but one question to keep in mind – how long will they continue to be available? […]
Archive for March, 2016
European PowerShell Conference 2016–few places left
Posted by: richardsiddaway | March 31, 2016 Comments Off on European PowerShell Conference 2016–few places left |There are still a few places left at the European PowerShell conference next month – http://www.psconf.eu/ There’s a terrific line up of speakers and I really recommend you get there if you can
IIS 6.0 server information
Posted by: richardsiddaway | March 30, 2016 Comments Off on IIS 6.0 server information |A question of the forum asked about getting data from IIS 6.0 servers One of the ways to access this data is to use CIM (WMI). IIS 6.0 has the root\MicrosoftIIsV2 namespace. Later versions of Windows server also have a root\webadministration namespace which is preferred. The original question asked about IIS 6.0 – […]
Breaking CIM sessions
Posted by: richardsiddaway | March 22, 2016 Comments Off on Breaking CIM sessions |A CIM session is analogous to a PowerShell remoting session but for CIM based cmdlets – the CIM cmdlets themselves and any CDXML based cmdlets e.g. the networking cmdlets By default a CIM session uses WSMAN as its transport protocol – the same as remoting. You do have the choice to create a CIM session […]
LocalAccounts module
Posted by: richardsiddaway | March 21, 2016 Comments Off on LocalAccounts module |I’m running Windows 10 and I’m on the fast ring for new Windows 10 builds. Sometimes that’s a good thing and other times its not. I decided to update help and after the update got a message: Failed to update Help for the module(s) ‘Microsoft.PowerShell.LocalAccounts’ That was a new one to me I […]
Module Name change NetworkSwitch to NetworkSwitchManager
Posted by: richardsiddaway | March 20, 2016 Comments Off on Module Name change NetworkSwitch to NetworkSwitchManager |Just been caught out by a module name change in WMF 5.0 The NetworkSwitch module has been renamed to NetworkSwitchManager. Still has the same functionality Disable-NetworkSwitchEthernetPort Disable-NetworkSwitchFeature Disable-NetworkSwitchVlan Enable-NetworkSwitchEthernetPort Enable-NetworkSwitchFeature Enable-NetworkSwitchVlan Get-NetworkSwitchEthernetPort Get-NetworkSwitchFeature Get-NetworkSwitchGlobalData Get-NetworkSwitchVlan New-NetworkSwitchVlan Remove-NetworkSwitchEthernetPortIPAddress Remove-NetworkSwitchVlan Restore-NetworkSwitchConfiguration Save-NetworkSwitchConfiguration Set-NetworkSwitchEthernetPortIPAddress Set-NetworkSwitchPortMode Set-NetworkSwitchPortProperty Set-NetworkSwitchVlanProperty One of these days I should read the realease notes
PowerShell Community in action
Posted by: richardsiddaway | March 19, 2016 Comments Off on PowerShell Community in action |In response to this post – ttps://richardspowershellblog.wordpress.com/2016/02/29/csv-file-with-in-headers/ Japp Brasser wrote a function to automate header name replacements. You can find the function at https://github.com/jaapbrasser/UtilityScripts/blob/master/Import-CsvFixHeader.ps1 Enjoy
Network adapter Index
Posted by: richardsiddaway | March 18, 2016 Comments Off on Network adapter Index |A few years ago I wrote a post about setting the IP metric on a connection – https://richardspowershellblog.wordpress.com/2012/01/01/changing-ip-connection-metric/ I was recently asked if the Index’s associated with network adapters were consistent acros machines. The answer – unfortunately- is no they’re not as a rule. I used the function from the original post function […]
Been testing things for my container talk at the Summit and opened Internet Explorer on my Server 2012 R2 machine to be greeted by “Microsoft recommends upgrading to Windows 10” Forget Server 2016 guys all you need is Windows 10
PowerShell package management on PowerShell 3 and 4
Posted by: richardsiddaway | March 9, 2016 Comments Off on PowerShell package management on PowerShell 3 and 4 |PowerShell 5.0 introduced PackageManagement (Oneget) – for managing software installation packages and PowerShellGet for managing PowerShell modules. Those features are now available on PowerShell 3 and 4 https://blogs.msdn.microsoft.com/powershell/2016/03/08/package-management-preview-march-2016-for-powershell-4-3-is-now-available/
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