Many Powershell enthusiasts don't realize that when they are using commands like New-PsSession and streaming pipelines to a powershell runspace on a remote machine, they are actually writing a binary message wrapped in a SOAP envelope that leverages a protocol with the namesake of Windows Vista. Not much over a year ago I certainly wasn't. This set of knowledge all began with needing to transfer files from a linux machine to a windows machine. In a pure linux world there is a well known tool for this called SCP. In Windows we map drives or stream bytes to a remote powershell session. How do we get a file (or command for that matter) from one of these platforms to the other?

Provides cmdlets for automated administration of the vSphere environment.

Powershell script to check windows updates using NRPE/NSClient++

Checks:

• how many critical and optional updates are available
• whether the system is waiting for reboot after installed updates
  Features:
• properly handles NRPE's 1024b limitation in return packet
• hidden updates return OK state
• Performance data in return packet shows titles of available critical updates
• caches updates in file to reduce network traffic, also dramatically increases script execution speed

Return Values for NRPE:

• No updates available - OK (0)
• Hidden Updates only - OK (0)
• Updates already installed, reboot required - WARNING (1)
• Optional updates available - WARNING (1)
• Critial updates available - CRITICAL (2)
• Script errors - UNKNOWN (3)