Windows Powershell - Revision history

Pio2pio: /* nfs-client */

2020-11-04T13:16:36Z

nfs-client

← Older revision		Revision as of 15:16, 4 November 2020
Line 63:		Line 63:
	== Install Windows feature ==		== Install Windows feature ==
	=== nfs-client ===		=== nfs-client ===
	{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is work by www.citi.umich.edu [http://www.citi.umich.edu/projects/nfsv4/windows/readme.html nfsv4/windows] alternative or this project [https://github.com/kofemann/ms-nfs41-client to compile your own client] }}		{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is work by www.citi.umich.edu [http://www.citi.umich.edu/projects/nfsv4/windows/readme.html nfsv4/windows] alternative or this project [https://github.com/kofemann/ms-nfs41-client ms-nfs41-client] to compile your own client }}

Pio2pio: /* nfs-client */

2020-11-04T13:15:57Z

nfs-client

← Older revision		Revision as of 15:15, 4 November 2020
Line 63:		Line 63:
	== Install Windows feature ==		== Install Windows feature ==
	=== nfs-client ===		=== nfs-client ===
	{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is work by www.citi.umich.edu [http://www.citi.umich.edu/projects/nfsv4/windows/readme.html nfsv4/windows] alternative or this project [https://github.com/kofemann/[ms-nfs41-client to compile your own client]}}		{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is work by www.citi.umich.edu [http://www.citi.umich.edu/projects/nfsv4/windows/readme.html nfsv4/windows] alternative or this project [https://github.com/kofemann/ms-nfs41-client to compile your own client] }}

Pio2pio: /* Install Windows feature */

2020-11-04T13:15:34Z

Install Windows feature

← Older revision		Revision as of 15:15, 4 November 2020
Line 63:		Line 63:
	== Install Windows feature ==		== Install Windows feature ==
	=== nfs-client ===		=== nfs-client ===
	{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is alternative https://github.com/kofemann/ms-nfs41-client to compile your own client}}		{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is work by www.citi.umich.edu [http://www.citi.umich.edu/projects/nfsv4/windows/readme.html nfsv4/windows] alternative or this project [https://github.com/kofemann/[ms-nfs41-client to compile your own client]}}

Pio2pio: /* nfs-client */

2020-11-04T12:57:06Z

nfs-client

← Older revision		Revision as of 14:57, 4 November 2020
Line 63:		Line 63:
	== Install Windows feature ==		== Install Windows feature ==
	=== nfs-client ===		=== nfs-client ===
			{{note\|[https://docs.aws.amazon.com/efs/latest/ug/limits.html EFS doesn't support mounting from Windows EC2 instances] although there is alternative https://github.com/kofemann/ms-nfs41-client to compile your own client}}


	<syntaxhighlightjs lang="powershell">		<syntaxhighlightjs lang="powershell">
	# example based on Windows 2012 R2		# example based on Windows 2012 R2

Pio2pio: /* Install Windows feature */

2020-11-04T09:20:26Z

Install Windows feature

← Older revision		Revision as of 11:20, 4 November 2020
Line 64:		Line 64:
	=== nfs-client ===		=== nfs-client ===
	<syntaxhighlightjs lang="powershell">		<syntaxhighlightjs lang="powershell">
			# example based on Windows 2012 R2
	PS C:\> Get-WindowsFeature nfs		PS C:\> Get-WindowsFeature nfs
	Display Name Name Install State		Display Name Name Install State
Line 75:		Line 76:
	------- -------------- --------- --------------		------- -------------- --------- --------------
	True No Success {Client for NFS}		True No Success {Client for NFS}
			</syntaxhighlightjs>


			Access the exported location, once the client is installed and NFS exports available on the network:
			<syntaxhighlightjs lang="powershell">
			# File explorer, once discovered network drive will be showed with the label of the NFS exported directory
			\\10.1.1.1 # eg. label '\nas'
	</syntaxhighlightjs>		</syntaxhighlightjs>

Line 82:		Line 90:
	Install-WindowsFeature -name Web-Server -IncludeManagementTools #IIS		Install-WindowsFeature -name Web-Server -IncludeManagementTools #IIS
	</syntaxhighlightjs>		</syntaxhighlightjs>

	=== [[ Hyper-V#Powershell_install_Hyper-V_feature ]]===		=== [[ Hyper-V#Powershell_install_Hyper-V_feature ]]===

Pio2pio: /* rewrite rules using back references */

2020-08-06T16:59:19Z

rewrite rules using back references

← Older revision		Revision as of 18:59, 6 August 2020
Line 283:		Line 283:

	== rewrite rules [http://www.iis.net/learn/extensions/url-rewrite-module/url-rewrite-module-configuration-reference#Using_back-references_in_rewrite_rules using back references] ==		== rewrite rules [http://www.iis.net/learn/extensions/url-rewrite-module/url-rewrite-module-configuration-reference#Using_back-references_in_rewrite_rules using back references] ==
	Regex pattern~~, as~~ per docs: 'When an ECMAScript pattern syntax is used, a back-reference can be created by putting parenthesis around the part of the pattern that must capture the back-reference.'		The rewrite module for IIS can be used to execute 2 actions:
			* <code>rewrite</code> - the URL stays the same but the content is loaded from somewhere else
			* <code>redirects</code> - when the user’s browser is taken to a new URL


			Regex pattern capture groups in <code><rule ..><match url="^(.*)$ />"</rule></code> can be reused in your actions. These are called '''back references'''. As per docs: 'When an ECMAScript pattern syntax is used, a back-reference can be created by putting parenthesis around the part of the pattern that must capture the back-reference.'


	Example regex pattern:		Example regex pattern:

Pio2pio: /* IIS - create a website */

2020-08-06T16:53:13Z

IIS - create a website

@@ Line 257: / Line 257: @@
   Get-ADPrincipalGroupMembership username| select name
-= IIS - create a website =
+= IIS =
 Tested on Server 2012 R2 Data Centre in Azure
 <syntaxhighlightjs lang="powershell">
@@ Line 280: / Line 281: @@
 Start-WebSite  -Name $SiteName
 </syntaxhighlightjs>
 = File content =

Pio2pio: /* Install Hyper-V feature */

2019-08-01T07:19:45Z

Install Hyper-V feature

@@ Line 82: / Line 82: @@
 Install-WindowsFeature -name Web-Server -IncludeManagementTools #IIS
 </syntaxhighlightjs>
-===Install Hyper-V feature===
+=== [[ Hyper-V#Powershell_install_Hyper-V_feature ]]===
 = Download a file =

Pio2pio: /* Install Hyper-V feature */

2019-05-30T14:05:45Z

Install Hyper-V feature

← Older revision		Revision as of 16:05, 30 May 2019
Line 99:		Line 99:


	;Allow Hyper-V and VirtualBox to coexist		;Allow Hyper-V and VirtualBox to coexist by creating Windows Boot entries
	Hyper-V is enabled during boot process, so creating a additional BCDEDIT entry will be the solution. Open PS in Admin mode, and run as follows:		Hyper-V is enabled during boot process, so creating a additional BCDEDIT entry will be the solution. Open PS in Admin mode, and run as follows:
	<syntaxhighlightjs lang="powershell">		<syntaxhighlightjs lang="powershell">
Line 110:		Line 110:
	* restart and hold down <code>shift</code> on the keyboard while clicking Restart with the mouse		* restart and hold down <code>shift</code> on the keyboard while clicking Restart with the mouse
	* on a boot menu select <tt>Use another operating system</tt> > <tt>Windows 10 - No hypervisor</tt>		* on a boot menu select <tt>Use another operating system</tt> > <tt>Windows 10 - No hypervisor</tt>


			Anoter option is to enable/disable Hyper-V feature
			#Open the command prompt as an Administrator.
			#Run the command with no argument: <code>bcdedit</code>
			#After you run the above command, you will see that the property hypervisorlaunchtype is set Auto by default.
			#Disable Hyper-V by running the command: <code>bcdedit /set hypervisorlaunchtype off</code>
			#Restart your PC system to use VirtualBox.
			#To turn Hyper-V back on, run the command: <code>bcdedit /set hypervisorlaunchtype auto</code>
			#You will need to reboot the system to use Hyper-V.

	= Download a file =		= Download a file =

Pio2pio: /* Install an application */

2019-05-23T23:06:33Z

Install an application

← Older revision		Revision as of 01:06, 24 May 2019
Line 149:		Line 149:
	$splunk_forwarder_file=""		$splunk_forwarder_file=""
	Start-Process msiexec.exe -ArgumentList "/i $tmpPath\$splunk_forwarder_file RECEIVING_INDEXER=splunk.acme.com:9997 DEPLOYMENT_SERVER=splunk.acme.com:8089 AGREETOLICENSE=Yes", "/quiet" -Wait		Start-Process msiexec.exe -ArgumentList "/i $tmpPath\$splunk_forwarder_file RECEIVING_INDEXER=splunk.acme.com:9997 DEPLOYMENT_SERVER=splunk.acme.com:8089 AGREETOLICENSE=Yes", "/quiet" -Wait
	#Without wait, following commands fail as Splunk Forwarder would not be fully installed		#Without -wait, following commands fail as Splunk Forwarder would not be fully installed
	C:\"Program Files"\SplunkUniversalForwarder\bin\splunk set servername ${tf_hostname} -auth admin:changeme		C:\"Program Files"\SplunkUniversalForwarder\bin\splunk set servername ${tf_hostname} -auth admin:changeme
	C:\"Program Files"\SplunkUniversalForwarder\bin\splunk set default-hostname ${tf_hostname} -auth admin:changeme		C:\"Program Files"\SplunkUniversalForwarder\bin\splunk set default-hostname ${tf_hostname} -auth admin:changeme
Line 158:		Line 158:
	== References ==		== References ==
	*[https://stackoverflow.com/questions/39407004/positional-parameter-error-in-powershell-script Positional error in PS scripts]		*[https://stackoverflow.com/questions/39407004/positional-parameter-error-in-powershell-script Positional error in PS scripts]

	= Modules =		= Modules =
	Load ActiveDirectory module to have access to AD, pre-requirement to execute most commands below		Load ActiveDirectory module to have access to AD, pre-requirement to execute most commands below