Wiki source code of Windows Defender mit Powershell in einem Client Command aktivieren

Last modified by Jannis Klein on 2024/08/13 08:19

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	160
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
2.1	7	= Initial situation =
1.1	8
2.1	9	You can use a Client Command to install and deploy programs to all your Clients. This can be useful, for example, if you need to react quickly to security risks, such as deploying an antivirus program. With Client Commands you are not hindered by the physical distance between your employees and can control a programme centrally and in a targeted manner.
1.1	10
2.1	11	This use case describes how you can use a Client Command to install and enable the Windows //Defender antivirus// feature. The //Windows Server 2016// operating system is used in this example to show a way to include or exclude different operating systems.
	12	Follow the steps below:
1.1	13
2.1	14	== Select Script ==
1.1	15
2.1	16	1. Navigate to the //Client Commands// > //Create //module.
	17	1. Click //Add //on the ribbon bar. The Client Command Editor will open and you will need to decide whether it is a Console or Client Script. In this case select Client Script.
1.1	18
2.1	19	== Select and edit the //PowerShell Script //Command ==
1.1	20
2.1	21	1. Choose //Processes and Shell// > //Execute PowerShell script//.
	22	1. Double click to open the Command.
	23	1. Switch to the //General //tab.
	24	1. In the //Action description// box, type a name, for example, „Install Microsoft Defender Antivirus“.
	25	1. Switch to the //Details //tab.
	26	1. In the text area, type the Commands that you want to run as a PowerShell Script.
	27	In this case, you need to type „//Install-WindowsFeature -Name Windows-Defender//“ in the first line.
	28
1.1	29	{{aagon.infobox}}
2.1	30	You can copy the text area from an existing script or type it manually. Only ASCII characters can be used.
1.1	31	{{/aagon.infobox}}
	32
	33	{{figure}}
	34	(% style="text-align:center" %)
	35	[[image:65_Use Case Client Commands_Microsoft Defender Antivirus installieren_478.png]]
	36
	37	{{figureCaption}}
2.1	38	Inserting PowerShell Script
1.1	39	{{/figureCaption}}
	40	{{/figure}}
	41
2.1	42	7. Finish your work on the Command by clicking //OK//.
1.1	43
2.1	44	== Inserting and customising the //If operating system is (not) //Command ==
1.1	45
2.1	46	1. Load the //If operating system is (not) (Conditions) //Command into the Script by double clicking it in the Command List, just like the previous Command.
	47	1. Ensure that the "If operating system ist" option is selected in the //Details //tab.
	48	1. Select the required operation system from the //Settings//.
	49	In this example, Windows Server 2016 is selected.
	50	1. Switch to the //General //tab.
	51	1. Enter a meaningful description of the action, e.g. "The operating system is "Windows Server 2016"".
	52	1. Click //OK// to complete the Command.
1.1	53
	54	{{figure}}
	55	(% style="text-align:center" %)
	56	[[image:65_Use Case Client Commands_Betriebssystem auswählen_484.png]]
	57
	58	{{figureCaption}}
2.1	59	Select operating system
1.1	60	{{/figureCaption}}
	61	{{/figure}}
	62
2.1	63	== Insert and edit the //Execute PowerShell Script //Command ==
1.1	64
2.1	65	1. Choose //Processes and Shell// > //Execute PowerShell Script//.
	66	1. Double click the Command to open it.
1.1	67
	68	{{aagon.infobox}}
2.1	69	Indent this Command by using either the quick selection bar or the CTRL+right arrow shortcut so that it appears below the previous Command. When adding this Command, you can also simply drag it to the operating system line, which will insert it correctly.
1.1	70	{{/aagon.infobox}}
	71
2.1	72	3. Type the Commands that you want to run as PowerShell Scripts in the text area.
	73	4. In this case, you need to type "//Install-WindowsFeature-Name Windows-Defender-GUI" //in in the line.
1.1	74
	75
	76	{{aagon.infobox}}
2.1	77	You can copy the text area from an existing script or type it manually. Only ASCII characters can be used.
1.1	78	{{/aagon.infobox}}
	79
2.1	80	5. Switch to the //General //tab.
	81	6. Enter a name under //Action description//, for example "Enable GUI".
1.1	82
	83	{{figure}}
	84	(% style="text-align:center" %)
	85	[[image:65_Use Case Client Commands_Execute PowerShell script.png]]
	86
	87	{{figureCaption}}
2.1	88	Enter a Defender GUI
1.1	89	{{/figureCaption}}
	90	{{/figure}}
	91
2.1	92	7. Close the Command by clicking //OK//.
1.1	93
2.1	94	Save your Client Command and name it. In this case, we have named this example "Activate Microsoft Defender using PowerShell".
1.1	95
	96	{{figure}}
	97	(% style="text-align:center" %)
	98	[[image:65_Use Case Client Commands_Microsoft Defender über PowerShell aktivieren_1083.png]]
	99
	100	{{figureCaption}}
2.1	101	Client Command Editor: Enable Defender via a Client Command
1.1	102	{{/figureCaption}}
	103	{{/figure}}
	104
2.1	105	== Running through Client Command phases ==
1.1	106
2.1	107	Before you can use the Client Command, you must go through the [[//Test//>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command testen.WebHome]], [[//Synchronize//>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command synchronisieren.WebHome]], [[//Release// >>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command freigeben.WebHome]]and [[Execute>>doc:ACMP.65.ACMP-Solutions.Client Commands.Client Command ausführen.WebHome]] phases. Only then can you install and enable Microsoft Defender on the selected Clients.