Power Shell - Revision history

Sstrutt: Typo fix

2016-10-04T15:37:17Z

Typo fix

← Older revision		Revision as of 15:37, 4 October 2016
Line 1:		Line 1:
	#REDIRECT [[~~:Category~~:Category:PowerShell]]		#REDIRECT [[:Category:PowerShell]]

Sstrutt: Deleted page contents, redirect to Category

2016-10-04T15:37:04Z

Deleted page contents, redirect to Category

Show changes

Sstrutt: Added Depreciated template

2012-04-20T14:20:32Z

Added Depreciated template

← Older revision		Revision as of 14:20, 20 April 2012
Line 1:		Line 1:
			{{Depreciated\|category=PowerShell}}

	See also...		See also...
	* '''[[PowerShell Examples]]''' - Example scripts		* '''[[PowerShell Examples]]''' - Example scripts
Line 956:		Line 958:
	* '''VMware PowerCLI 64 bit'''		* '''VMware PowerCLI 64 bit'''
	** Due to a bug you can't launch background jobs against VMware vSphere (VI4) hosts in a 64-bit environment, PowerShell will crash. Its probably a bug in PowerCLI, and will hopefully be fixed in a future release (bug exists in v4.1u1 and possibly other versions). You can run scripts in 32-bit (see [[#Useful_One-Liners\|Useful One-Liners]] on how to detect in your script).		** Due to a bug you can't launch background jobs against VMware vSphere (VI4) hosts in a 64-bit environment, PowerShell will crash. Its probably a bug in PowerCLI, and will hopefully be fixed in a future release (bug exists in v4.1u1 and possibly other versions). You can run scripts in 32-bit (see [[#Useful_One-Liners\|Useful One-Liners]] on how to detect in your script).

	~~[[Category:PowerShell]]~~
	~~[[Category:WMI]]~~

Sstrutt: /* Getting Started */ Added "Slow Start-Up"

2012-04-19T15:08:49Z

Getting Started: Added "Slow Start-Up"

← Older revision		Revision as of 15:08, 19 April 2012
Line 30:		Line 30:
	=== Installed Version ===		=== Installed Version ===
	To check the main installed version use the following command...		To check the main installed version use the following command...
	<source lang="powershell"> get-host \| select version </source>.		<source lang="powershell"> get-host \| select version </source>
	However, if you might have installed something other than the normal RTM or GA release version you'll need to the registry key <code>HKLM\Software\Microsoft\PowerShell\1</code>, which will have the following values of interest...		However, if you might have installed something other than the normal RTM or GA release version you'll need to the registry key <code>HKLM\Software\Microsoft\PowerShell\1</code>, which will have the following values of interest...
	{\|class="vwikitable"		{\|class="vwikitable"
Line 46:		Line 46:
	=== Help Commands ===		=== Help Commands ===
	<source lang="powershell">Get-Help <cmd> # Provides help for CmdLets, use wildcards to broaden results.		<source lang="powershell">Get-Help <cmd> # Provides help for CmdLets, use wildcards to broaden results.
	<object> \| Get-Member # Provides information about an object		$object \| Get-Member # Provides information about an object (variable)
	~~<variable>~~.gettype() # Provides variable type info (string, array, etc)</source>		$object.gettype() # Provides variable type info (string, array, etc)</source>

	=== Include Files ===		=== Include Files ===
Line 54:		Line 54:
	. .\lib\include_file.ps1		. .\lib\include_file.ps1
	</source>		</source>

			=== Slow Start-Up ===
			PowerShell isn't the fastest thing in the world to start, the fact that a basic PowerShell command prompt uses of 50MB of RAM gives some indication that its not lean and mean (but once up and running, and when running efficient script it can be ''very'' fast). However if its taking minutes rather than seconds to start then there is something going wrong.

			Normally this is due to the fact that the machine you're running from has no (or limited) internet access. To workaround the problem you need to disable Certificate Revocation Checking...

			# In '''Control Panel''', open '''Internet Options'''
			# Go to the '''Advanced''' tab, and scroll down to the '''Security''' section
			# Untick the '''>Check for publisher's certificate revocation'''

			There is no increased security risk imposed by doing this on a machine with no/limited internet access, as the checks were previously timing-out and being bypassed anyway.

	== Useful One-Liners ==		== Useful One-Liners ==

Sstrutt: /* Scope */ Updated to include declaring a variable within a function

2012-04-11T08:20:17Z

Scope: Updated to include declaring a variable within a function

@@ Line 179: / Line 179: @@
 Global-Add "Text message THREE"
 $List.Length                           # List now contains two entries
 </source>

Sstrutt: /* Scope */ Correction

2012-04-11T06:47:54Z

Scope: Correction

← Older revision		Revision as of 06:47, 11 April 2012
Line 165:		Line 165:
	<source lang="powershell">		<source lang="powershell">
	function Local-Add($text) {		function Local-Add($text) {
	$~~script:~~List += $text		$List += $text
	}		}

Sstrutt: /* Strings */ Terminology error correction

2012-03-19T13:04:11Z

Strings: Terminology error correction

← Older revision		Revision as of 13:04, 19 March 2012
Line 240:		Line 240:

	<br>'''Replace''' <br>		<br>'''Replace''' <br>
	Basic find and replace can be done with ~~the~~ Replace ~~CmdLet~~, eg to replace "\" with "\\" in the $query variable...		Basic find and replace can be done with a string's Replace method, eg to replace "\" with "\\" in the $query variable...
	<source lang="powershell"> $query = $query.Replace("\", "\\") </source>		<source lang="powershell"> $query = $query.Replace("\", "\\") </source>
	For proper regular expressions support, use the following syntax		For proper regular expressions support, use the following syntax

Sstrutt: Update table formatting

2012-02-24T16:29:42Z

Update table formatting

← Older revision		Revision as of 16:29, 24 February 2012
Line 32:		Line 32:
	<source lang="powershell"> get-host \| select version </source>.		<source lang="powershell"> get-host \| select version </source>.
	However, if you might have installed something other than the normal RTM or GA release version you'll need to the registry key <code>HKLM\Software\Microsoft\PowerShell\1</code>, which will have the following values of interest...		However, if you might have installed something other than the normal RTM or GA release version you'll need to the registry key <code>HKLM\Software\Microsoft\PowerShell\1</code>, which will have the following values of interest...
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Value !! Data !! Meaning		! Value !! Data !! Meaning
	\|-		\|-
Line 56:		Line 56:

	== Useful One-Liners ==		== Useful One-Liners ==
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Command !! Description		! Command !! Description
	\|-		\|-
Line 80:		Line 80:

	'''Data types'''		'''Data types'''
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Notation !! Data Type		! Notation !! Data Type
	\|-		\|-
Line 249:		Line 249:

	=== Escape Characters ===		=== Escape Characters ===
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Text !! Description		! Text !! Description
	\|-		\|-
Line 373:		Line 373:

	Useful formatting examples...		Useful formatting examples...
	{\|~~cellpadding~~="~~2" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! uFormat Specifier !! Example		! uFormat Specifier !! Example
	\|-		\|-
Line 388:		Line 388:

	Useful formatting examples...		Useful formatting examples...
	{\|~~cellpadding~~="~~2" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! ToString Method Specifier !! UK-Centric Example Output		! ToString Method Specifier !! UK-Centric Example Output
	\|-		\|-
Line 427:		Line 427:
	=== Macros / Built-in Variables ===		=== Macros / Built-in Variables ===

	{\|~~cellpadding~~="~~4" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Variable !! Description		! Variable !! Description
	\|-		\|-
Line 472:		Line 472:
	== Conditional Operators ==		== Conditional Operators ==
	== Comparison ==		== Comparison ==
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Operator !! Description		! Operator !! Description
	\|-		\|-
Line 502:		Line 502:

	=== Logic ===		=== Logic ===
	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Operator !! Description		! Operator !! Description
	\|-		\|-
Line 713:		Line 713:
	To control how a script behaves as a result of an exception, modify the <code> $ErrorActionPreference </code> variable, if required. '''In the default continue mode, an error will output to the screen, then the script will continue. By outputting the error to the screen PowerShell CmdLets consider the exception to have been handled! If you want the opportunity to <code>catch</code> or <code>trap</code> you must append <code>-ErrorAction:Stop</code> to the CmdLet you expect might fail.'''		To control how a script behaves as a result of an exception, modify the <code> $ErrorActionPreference </code> variable, if required. '''In the default continue mode, an error will output to the screen, then the script will continue. By outputting the error to the screen PowerShell CmdLets consider the exception to have been handled! If you want the opportunity to <code>catch</code> or <code>trap</code> you must append <code>-ErrorAction:Stop</code> to the CmdLet you expect might fail.'''

	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Value !! Effect		! Value !! Effect
	\|-		\|-
Line 729:		Line 729:
	Provides a list of recent errors experienced - which can be invaluable for properly identifying and investigating errors. The object is the same as found in a pipeline when an exception has occurred.		Provides a list of recent errors experienced - which can be invaluable for properly identifying and investigating errors. The object is the same as found in a pipeline when an exception has occurred.

	{\|~~cellpadding~~="~~1" cellspacing="0" border="1~~"		{\|class="vwikitable"
	\|- ~~style="background-color:#bbddff;"~~		\|-
	! Property !! Description !! Example (VC login error)		! Property !! Description !! Example (VC login error)
	\|-		\|-

Sstrutt: /* Variables */ Added NULL stuff

2011-11-01T13:02:38Z

Variables: Added NULL stuff

← Older revision		Revision as of 13:02, 1 November 2011
Line 136:		Line 136:

	It's not uncommon for objects provided by API's to provide methods that are in fact objects themselves, you can end up with a lot of information being available once you're capable of drilling into them.		It's not uncommon for objects provided by API's to provide methods that are in fact objects themselves, you can end up with a lot of information being available once you're capable of drilling into them.

			==== NULL ====
			Checking whether a variable is NULL or not can be problematic. In that the easiest test doesn't always work.

			Basic test for whether a variable exists or not, works in most cases...
			<source lang="powershell">
			if (!$var) {
			"Variable is null"
			}
			</source>

			If you expect your variable to be NULL or contain a positive number...
			<source lang="powershell">
			if ($var -gt 0) {
			"Variable is NOT null"
			}
			</source>

			Last resort test...
			<source lang="powershell">
			if ($var.gettype().ToString() -eq "System.DBNull") {
			"Variable is null"
			}
			</source>

	=== Scope ===		=== Scope ===

Sstrutt: /* Arrays */ Added Array Types

2011-09-06T09:00:54Z

Arrays: Added Array Types

@@ Line 305: / Line 305: @@
 > $array |?{$_.h1 -eq "esx2"} | Select -ExpandProperty h2
 HBA1
 </source>