#powershell SNMP Services Administration (Part 3)

Working with the “Security” tab in the SNMP service is similar to that for the “Traps” tab discussed before. Let us start off with the simple task to toggle the “Send authentication trap” option. This matches the registry item property EnableAuthenticationTraps located in:
Read more “#powershell SNMP Services Administration (Part 3)”

#powershell SNMP Services Administration (Part 2)

Multiple “Community name” and the matching “Trap destinations” can be defined using the Traps tab in the SNMP service. Each community name exists in its own key (node) under:

HKLM:\System\CurrentControlSet\Services\SNMP\Parameters\TrapConfiguration

within which one or more trap destinations are stored as properties (REG_SZ) in this registry location.
Read more “#powershell SNMP Services Administration (Part 2)”

#powershell SNMP Services Administration (Part 1)

This blog series explores the administration of SNMP configuration settings in Windows through PowerShell, a network monitoring protocol where it continues to be widely adopted.

Of interest are the Agent, Traps and Security tabs of the SNMP service when the properties are inspected using the services.mmc snap-in. These configurable items are stored in the Windows registry.
Read more “#powershell SNMP Services Administration (Part 1)”

#powershell Local Certificate Store Inventory (Windows)

#requires -version 3.0
###############################################################################
# Copyright (c) 201x-2018 leedesmond.com
# All Rights Reserved. Use at your own risk and responsibility.
# Version 1.00
#
# Get a list of certificates installed in the local certificate store remotely
# across 1 or more machines (Certificates \ Personal \ Certificates)
#
# REQUIREMENTS: PowerShell Remoting enabled on target hosts
#
###############################################################################
Read more “#powershell Local Certificate Store Inventory (Windows)”

#powershell Always Up-to-date Hardware Inventory (Windows)

#requires -version 3.0
###############################################################################
# Copyright (c) 201x-2018 leedesmond.com
# All Rights Reserved. Use at your own risk and responsibility.
# Version 1.00
#
# Any Windows Server – Always Up-to-date Hardware Inventory (Core)
#
# REQUIREMENTS: PowerShell Remoting enabled on target hosts & firewall
# ports (WMI calls)
###############################################################################
Read more “#powershell Always Up-to-date Hardware Inventory (Windows)”

#skype4b #powershell Always Up-to-date Infrastructure Inventory (Topology)

#requires -version 3.0
###############################################################################
# Copyright (c) 201x-2018 leedesmond.com
# All Rights Reserved. Use at your own risk and responsibility.
# Version 1.00
#
# Skype for Business Server – Always Up-to-date Inventory (Topology)
# Gathers core #skype4b infrastructure inventory (topology), supporting
# server roles, file stores and SQL backend databases.
#
# NOTE – change SiteId where appropriate
###############################################################################
Read more “#skype4b #powershell Always Up-to-date Infrastructure Inventory (Topology)”

#WindowsServer2016 Build 1709 (Server Core) Enable Remote Management

Except for a few control panel applets (and dialog boxes), Windows Server 2016 Build 1709 runs exclusively in Server Core text mode. This means that familiar graphical user tools are not available whether you sign-in right in front of the machine or connect from a distance over Remote Desktop.

Basic configuration such as domain/workgroup membership, computer name and network settings, etc. can be realized using the provided VB Script in the form of %windir%\system32\sconfig.cmd. Nevertheless, you can continue to use common GUI MMC legacy tools such as Event Viewer or services.msc to remotely connect to a Windows Server 2016 Build 1709 box.

Since Windows Server 2012 R2, PowerShell remoting is activated out-of-the-box, a feature which is dependent on Windows Remote Management (WinRM). This is what Server Manager relies on primarily to remotely manage Windows Server 2012 and higher versions. Server Manager remote administration of previous Windows Server versions continue to work over Distributed Component Object Model (DCOM)*.

Consequently, setting “4) Configure Remote Management” to “1) Enable Remote Management” via sconfig.cmd is only part of the story (WinRM portion). Read more “#WindowsServer2016 Build 1709 (Server Core) Enable Remote Management”

#skype4b #powershell *-CsDatabase Common Error Messages (and Fix) II

Running Test-CsDatabase can produce different output for ExpectedVersion and InstalledVersion against one or more backend SQL databases in your Skype for Business Server infrastructure. Depending on the host where this cmdlet is executed, Read more “#skype4b #powershell *-CsDatabase Common Error Messages (and Fix) II”

#pscore6 v.s. #powershell 5.x Modules (Part III)

You must have already noticed discrepancies in modules and corresponding commands[1] between PowerShell versions and releases. How can I keep abreast with constant changes in today’s ever fast-pace cloud technologies now that PowerShell is cross-platform commencing with version 6.x?

One way to find out yourself is illustrated here, paying attention to compare apples to apples i.e. Windows Desktop v.s. Windows Desktop. Otherwise, a big difference is to be expected between Windows Server 2016 and Windows 10 Desktop platforms running PowerShell 5.1.x for instance. Read more “#pscore6 v.s. #powershell 5.x Modules (Part III)”

#pscore6 v.s. #powershell 5.x Modules (Part II)

In the default installation of PowerShell Core 6.0 and Windows PowerShell 5.10 (PS5) with 13 and 89 modules discovered respectively, both PS versions have overlapping module names as illustrated:

CimCmdlets
Microsoft.PowerShell.Archive
Microsoft.PowerShell.Diagnostics
Microsoft.PowerShell.Host
Microsoft.PowerShell.Management
Microsoft.PowerShell.Security
Microsoft.PowerShell.Utility
Microsoft.WSMan.Management
PackageManagement
PowerShellGet
PSDesiredStateConfiguration
PSDiagnostics
PSReadline

An output with similar module names does not always mean that the number and type of commands in each of these modules correspond (see Part I of this blog series). Read more “#pscore6 v.s. #powershell 5.x Modules (Part II)”