Getting Started (PowerShell) - Revision history

Sstrutt: /* Scripts */ Add "Scheduled Tasks"

2019-05-07T12:55:25Z

Scripts: Add "Scheduled Tasks"

@@ Line 231: / Line 231: @@
 Stop-Transcript
 </source>
 == Call External Process ==

Sstrutt: /* Installation */ Added profile

2018-09-19T06:30:03Z

Installation: Added profile

@@ Line 21: / Line 21: @@
 # Go to '''Internet Options''', and then '''Advanced'''
 # Then under '''Security''' uncheck ''Check for publisher's certificate revocation''
 == Execution Policy ==

Sstrutt: /* Installation */ Added V4 download link

2015-01-18T08:09:19Z

Installation: Added V4 download link

← Older revision		Revision as of 08:09, 18 January 2015
Line 6:		Line 6:
	** [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 Windows PowerShell V3]		** [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 Windows PowerShell V3]
	*** Requires .NET v4 to be installed - [http://www.microsoft.com/en-gb/download/details.aspx?id=17718 .NET v4 Standalone]		*** Requires .NET v4 to be installed - [http://www.microsoft.com/en-gb/download/details.aspx?id=17718 .NET v4 Standalone]
			** [http://www.microsoft.com/en-gb/download/details.aspx?id=40855 Windows PowerShell V4]
	* Documentation		* Documentation
	** http://powershell.com/cs/ - Good all-round help		** http://powershell.com/cs/ - Good all-round help

Sstrutt: /* Execution Policy */ Another

2013-08-09T16:15:03Z

Execution Policy: Another

← Older revision		Revision as of 16:15, 9 August 2013
Line 41:		Line 41:
	<source lang="powershell">		<source lang="powershell">
	Get-ExecutionPolicy		Get-ExecutionPolicy
			</source>

			To run a script, without tinkering with the Execution Policy first, run from a command prompt

			<source lang="dos">
			powershell.exe -executionpolicy remotesigned .\Example.ps1
	</source>		</source>

Sstrutt: /* Execution Policy */ Minor update

2013-08-09T15:45:38Z

Execution Policy: Minor update

← Older revision		Revision as of 15:45, 9 August 2013
Line 28:		Line 28:
	* <code> Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied. </code>		* <code> Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied. </code>

	So if you're using Windows 7, for example, you'll need to start the Powershell console as an administrator (right-click ''Run as administrator''), regardless of whether you're currently logged in as an admin). ~~If you have no admin rights over the PC you're using, then you'll need to select the Suspend option rather than Yes (sets just for your current session, doesn't try to write to the registry).~~		So if you're using Windows 7, for example, you'll need to start the Powershell console as an administrator (right-click ''Run as administrator''), regardless of whether you're currently logged in as an admin).
	<source lang="powershell"> Set-ExecutionPolicy RemoteSigned </source>		<source lang="powershell"> Set-ExecutionPolicy RemoteSigned </source>
	It is possible to bypass the Execution Policy entirely (though you do so at your own risk, should only be used to run a script you trust where you haven't the time to fix the underlying problem, and should be reverted afterwards)...		It is possible to bypass the Execution Policy entirely (though you do so at your own risk, should only be used to run a script you trust where you haven't the time to fix the underlying problem, and should be reverted afterwards)...
	<source lang="powershell"> Set-ExecutionPolicy Bypass </source>		<source lang="powershell"> Set-ExecutionPolicy Bypass </source>

			'''If you have no admin rights''' over the PC you're using, then can try to use ''Suspend'' option rather than ''Yes'' (sets just for your current session, doesn't try to write to the registry), this doesn't work in all cases. Alternatively you can hack the Environment variable that controls the Execution Policy (again, this isn't permanent, and may not work in all versions)...
			<source lang="powershell">
			$env:PSExecutionPolicyPreference = "RemoteSigned"
			</source>

			To see your current execution policy use...
			<source lang="powershell">
			Get-ExecutionPolicy
			</source>

	== Installed Version ==		== Installed Version ==

Sstrutt: /* Installation */ Added .NET v4 install link

2013-04-10T10:32:47Z

Installation: Added .NET v4 install link

← Older revision		Revision as of 10:32, 10 April 2013
Line 5:		Line 5:
	** [http://support.microsoft.com/kb/968929 Windows PowerShell V2]		** [http://support.microsoft.com/kb/968929 Windows PowerShell V2]
	** [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 Windows PowerShell V3]		** [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 Windows PowerShell V3]
			*** Requires .NET v4 to be installed - [http://www.microsoft.com/en-gb/download/details.aspx?id=17718 .NET v4 Standalone]
	* Documentation		* Documentation
	** http://powershell.com/cs/ - Good all-round help		** http://powershell.com/cs/ - Good all-round help

Sstrutt: /* Installation */ Minor formatting

2013-03-13T21:00:00Z

Installation: Minor formatting

← Older revision		Revision as of 21:00, 13 March 2013
Line 1:		Line 1:
	== Installation ==		== Installation ==
	Subject specific useful links are listed in the sections below, the following provide links to installers and general documentation		Subject specific useful links are listed in the sections below, the following provide links to installers and general documentation...
	* [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx Windows PowerShell V1]		* '''Downloads'''
	* [http://support.microsoft.com/kb/968929 Windows PowerShell V2]		** [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx Windows PowerShell V1]
	* [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 PowerShell V3]		** [http://support.microsoft.com/kb/968929 Windows PowerShell V2]
	* http://powershell.com/cs/ - Good all-round help		** [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 Windows PowerShell V3]
	* http://technet.microsoft.com/en-us/library/bb978526.aspx - TechNet!		* Documentation
			** http://powershell.com/cs/ - Good all-round help
			** http://technet.microsoft.com/en-us/library/bb978526.aspx - TechNet!

	Whilst '''Win2008''' ships with Powershell V2, it isn't necessarily available, to install...		Whilst '''Win2008''' ships with Powershell V2, it isn't necessarily available, to install...

Sstrutt: /* Installation */ Added V3 link

2013-03-13T20:57:45Z

Installation: Added V3 link

Sstrutt: /* Execution Policy */ Added expected error messages

2012-11-05T21:13:25Z

Execution Policy: Added expected error messages

← Older revision		Revision as of 21:13, 5 November 2012
Line 18:		Line 18:

	== Execution Policy ==		== Execution Policy ==
	On the first run you need to allow Powershell to scripts (you need to run ~~this~~ command as an administrator, so if you're using Windows 7, for example, you'll need to start the Powershell console as an administrator, regardless of whether you're currently logged in as an admin). If you have no admin rights over the PC you're using, then you'll need to select the Suspend option rather than Yes (sets just for your current session, doesn't try to write to the registry).		On the first run you need to allow Powershell to scripts to execute, otherwise you'll get an error that contains the following when trying to run a script...
			* <code> cannot be loaded because the execution of scripts is disabled on this system.</code>

			'''You need to run the command below as an administrator''', otherwise you'll get an error like...
			* <code> Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied. </code>

			So if you're using Windows 7, for example, you'll need to start the Powershell console as an administrator (right-click ''Run as administrator''), regardless of whether you're currently logged in as an admin). If you have no admin rights over the PC you're using, then you'll need to select the Suspend option rather than Yes (sets just for your current session, doesn't try to write to the registry).
	<source lang="powershell"> Set-ExecutionPolicy RemoteSigned </source>		<source lang="powershell"> Set-ExecutionPolicy RemoteSigned </source>
	It is possible to bypass the Execution Policy entirely (though you do so at your own risk, should only be used to run a script you trust where you haven't the time to fix the underlying problem, and should be reverted afterwards)...		It is possible to bypass the Execution Policy entirely (though you do so at your own risk, should only be used to run a script you trust where you haven't the time to fix the underlying problem, and should be reverted afterwards)...

Sstrutt: /* Process Priority */ Added scheduled tasks priority note

2012-08-16T09:17:22Z

Process Priority: Added scheduled tasks priority note

← Older revision		Revision as of 09:17, 16 August 2012
Line 131:		Line 131:
	! BelowNormal		! BelowNormal
	\| Ensures that the process will yield to most other processes running on the system (good for background tasks).		\| Ensures that the process will yield to most other processes running on the system (good for background tasks).
			By default, scheduled tasks run as Below Normal (in Win2008, and maybe others)
	\|-		\|-
	! Normal		! Normal

← Older revision		Revision as of 20:57, 13 March 2013
Line 3:		Line 3:
	* [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx Windows PowerShell V1]		* [http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx Windows PowerShell V1]
	* [http://support.microsoft.com/kb/968929 Windows PowerShell V2]		* [http://support.microsoft.com/kb/968929 Windows PowerShell V2]
			* [http://www.microsoft.com/en-gb/download/details.aspx?id=34595 PowerShell V3]
	* http://powershell.com/cs/ - Good all-round help		* http://powershell.com/cs/ - Good all-round help
	* http://technet.microsoft.com/en-us/library/bb978526.aspx - TechNet!		* http://technet.microsoft.com/en-us/library/bb978526.aspx - TechNet!

	Whilst '''Win2008''' ships with Powershell it isn't necessarily available, to install...		Whilst '''Win2008''' ships with Powershell V2, it isn't necessarily available, to install...
	# Go to '''Server Manager'''		# Go to '''Server Manager'''
	# Go into '''Features''', then '''Add Features'''		# Go into '''Features''', then '''Add Features'''
Line 12:		Line 13:
	''Normally a restart isn't required''		''Normally a restart isn't required''

	If you're running scripts from a machine that does not have (or has dodgy) internet access, you need to disable certificate checking		If you're running scripts from a machine that does not have (or has dodgy) internet access, then running PowerShell scripts can mean a very long wait before they start to run. In which case you need to disable certificate checking (its the checking for certificate revocation that needs to time-out before a script will run)...
	# In '''Internet Explorer'''		# In '''Internet Explorer'''
	# Go to '''Internet Options''', and then '''Advanced'''		# Go to '''Internet Options''', and then '''Advanced'''