mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
fix: MD005/list-indent
Inconsistent indentation for list items at the same level
This commit is contained in:
Nick Schonning
parent
5089cbb88d
commit
536872ec34
@ -97,5 +97,5 @@ If you insert a USB thumb drive with a provisioning package into one of the USB
|
||||
|
||||
 <br>
|
||||
|
||||
4. Follow the instructions to complete first time Setup.
|
||||
4. Follow the instructions to complete first time Setup.
|
||||
|
||||
|
||||
@ -61,8 +61,8 @@ The following steps show you how to create a deployment share for Windows 10 tha
|
||||
>[!NOTE]
|
||||
>As of SDA version 1.96.0405, SDA will install only the components of the Windows ADK that are required for deployment, as follows:
|
||||
> * Deployment tools
|
||||
> * User State Migration Tool (USMT)
|
||||
> * Windows Preinstallation Environment (WinPE)
|
||||
> * User State Migration Tool (USMT)
|
||||
> * Windows Preinstallation Environment (WinPE)
|
||||
|
||||
> [!NOTE]
|
||||
> As of SDA version 1.96.0405, SDA will install and use MDT 2013 Update 2. Earlier versions of SDA are compatible only with MDT 2013 Update 1.
|
||||
@ -75,11 +75,11 @@ The following steps show you how to create a deployment share for Windows 10 tha
|
||||
|
||||
- **Local Path** – Specify or browse to a location on the local storage device where you would like to store the deployment share files for the Windows 10 SDA deployment share. For example, **E:\\SDAWin10\\** is the location specified in Figure 3.
|
||||
|
||||
- **Share Name** – Specify a name for the file share that will be used to access the deployment share on this server from the network. For example, **SDAWin10** is the deployment share name shown in Figure 3. The local path folder is automatically shared by the SDA scripts under this name to the group **Everyone** with a permission level of **Full Control**.
|
||||
- **Share Name** – Specify a name for the file share that will be used to access the deployment share on this server from the network. For example, **SDAWin10** is the deployment share name shown in Figure 3. The local path folder is automatically shared by the SDA scripts under this name to the group **Everyone** with a permission level of **Full Control**.
|
||||
|
||||
- **Windows 10 Deployment Services**
|
||||
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://technet.microsoft.com/library/jj648426.aspx) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://technet.microsoft.com/library/jj648426.aspx) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
|
||||
- **Windows 10 Source Files**
|
||||
|
||||
|
||||
@ -13,52 +13,42 @@ ms.prod: w8
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
# How to Manually Install the Application Virtualization Client
|
||||
|
||||
|
||||
There are two types of Application Virtualization Client components: the Application Virtualization Desktop Client, which is designed for installation on desktop computers, and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services), which you can install on Remote Desktop Session Host (RD Session Host) servers . Although the two client installer programs are different, you can use the following procedure to manually install either the Application Virtualization Desktop Client on a single desktop computer or the Application Virtualization Client for Remote Desktop Services on a single RD Session Host server. In a production environment, you most likely will install the Application Virtualization Desktop Client on multiple desktop computers with an automated scripted installation process. For information about how to install multiple clients by using a scripted installation process, see [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md).
|
||||
|
||||
**Note**
|
||||
1. If you are installing the Application Virtualization Client for Remote Desktop Services software on a RD Session Host server, advise users who have an open RDP or ICA client session with the RD Session Host server that they must save their work and close their sessions. In a Remote Desktop session, you can install the client the client manually. For more information about upgrading the client, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
|
||||
|
||||
2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
|
||||
|
||||
1. If you are installing the Application Virtualization Client for Remote Desktop Services software on a RD Session Host server, advise users who have an open RDP or ICA client session with the RD Session Host server that they must save their work and close their sessions. In a Remote Desktop session, you can install the client the client manually. For more information about upgrading the client, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
|
||||
|
||||
2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
|
||||
|
||||
**Note**
|
||||
For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL is installed in the Windows\\system32 directory. If the App-V client is installed on a 64-bit system, SFTLDR\_WOW64.DLL is installed in the Windows\\SysWOW64 directory.
|
||||
|
||||
|
||||
|
||||
**To manually install Application Virtualization Desktop Client**
|
||||
|
||||
1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
|
||||
1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
|
||||
|
||||
2. Choose the folder in which to save the files, and then open the folder after the files have been copied to it.
|
||||
2. Choose the folder in which to save the files, and then open the folder after the files have been copied to it.
|
||||
|
||||
3. Review the Release Notes if appropriate.
|
||||
3. Review the Release Notes if appropriate.
|
||||
|
||||
4. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
|
||||
4. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
|
||||
|
||||
5. The wizard checks the system to ensure that all prerequisite software is installed, and if any of the following are missing, the wizard will automatically prompt you to install them:
|
||||
5. The wizard checks the system to ensure that all prerequisite software is installed, and if any of the following are missing, the wizard will automatically prompt you to install them:
|
||||
|
||||
- Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
|
||||
- Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
|
||||
|
||||
- Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
|
||||
- Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
|
||||
|
||||
- Microsoft Application Error Reporting
|
||||
- Microsoft Application Error Reporting
|
||||
|
||||
**Note**
|
||||
For App-V version 4.6 and later, the wizard will also install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
|
||||
|
||||
For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see <https://go.microsoft.com/fwlink/?LinkId=150700> (https://go.microsoft.com/fwlink/?LinkId=150700).
|
||||
For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [https://go.microsoft.com/fwlink/?LinkId=150700](https://go.microsoft.com/fwlink/?LinkId=150700).
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
|
||||
~~~
|
||||
If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
|
||||
|
||||
6. When the **Microsoft Application Virtualization Desktop Client – InstallShield Wizard** is displayed, click **Next**.
|
||||
|
||||
@ -76,88 +66,66 @@ If prompted, click **Install**. Installation progress is displayed, and the stat
|
||||
|
||||
12. On the **Application Virtualization Data Location** screen, click **Next** to accept the default data locations or complete the following actions to change where the data is stored:
|
||||
|
||||
1. Click **Change**, and then browse to or, in the **Global Data Location** field, enter the destination folder for the global data location, and click **OK**. The Global Data Directory is where the Application Virtualization Desktop Client caches data shared by all users on the computer, like OSD files and SFT file data.
|
||||
1. Click **Change**, and then browse to or, in the **Global Data Location** field, enter the destination folder for the global data location, and click **OK**. The Global Data Directory is where the Application Virtualization Desktop Client caches data shared by all users on the computer, like OSD files and SFT file data.
|
||||
|
||||
2. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
|
||||
2. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
|
||||
|
||||
3. Enter a new path to store the user-specific data in the **User-specific Data Location** field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications.
|
||||
3. Enter a new path to store the user-specific data in the **User-specific Data Location** field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications.
|
||||
|
||||
**Note**
|
||||
This path must be different for every user, so it should include a user-specific environment variable or a mapped drive or something else that will resolve to a unique path for each user.
|
||||
|
||||
|
||||
|
||||
4. When you have finished making the changes, click **Next**.
|
||||
4. When you have finished making the changes, click **Next**.
|
||||
|
||||
13. On the **Cache Size Settings** screen, you can accept or change the default cache size. Click one of the following radio buttons to choose how to manage the cache space:
|
||||
|
||||
1. **Use maximum cache size**. Enter a numeric value from 100–1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache.
|
||||
1. **Use maximum cache size**. Enter a numeric value from 100–1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache.
|
||||
|
||||
2. **Use free disk space threshold**. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is currently unused.
|
||||
2. **Use free disk space threshold**. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is currently unused.
|
||||
|
||||
**Important**
|
||||
To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
|
||||
**Important**
|
||||
To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
|
||||
14. In the following sections of the **Runtime Package Policy Configuration** screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:
|
||||
|
||||
1. **Application Source Root**. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.
|
||||
1. **Application Source Root**. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.
|
||||
|
||||
2. **Application Authorization**. When **Require User authorization even when cached** is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application.
|
||||
2. **Application Authorization**. When **Require User authorization even when cached** is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application.
|
||||
|
||||
3. **Allow streaming from file**. Indicates whether streaming from file will be enabled, regardless of how the **Application Source Root** field is used. If not checked, streaming from files is disabled. This must be checked if **Application Source Root** contains a UNC path in the form \\\\server\\share.
|
||||
3. **Allow streaming from file**. Indicates whether streaming from file will be enabled, regardless of how the **Application Source Root** field is used. If not checked, streaming from files is disabled. This must be checked if **Application Source Root** contains a UNC path in the form \\\\server\\share.
|
||||
|
||||
4. **Automatically Load Application**. Controls when and how automatic background loading of applications occurs.
|
||||
4. **Automatically Load Application**. Controls when and how automatic background loading of applications occurs.
|
||||
|
||||
**Note**
|
||||
When you install the App-V client to use with a read-only cache, for example, with a VDI server implementation, set **What applications to Auto Load** to **Do not automatically load applications** to prevent the client from trying to update applications in the read-only cache.
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
|
||||
15. On the **Publishing Server** screen, select the **Set up a Publishing Server now** check box if you want to define a publishing server, or click **Next** if you want to complete this later. To define a publishing server, specify the following information:
|
||||
|
||||
1. **Display Name**—Enter the name you want to display for the server.
|
||||
1. **Display Name**—Enter the name you want to display for the server.
|
||||
|
||||
2. **Type**—Select the server type from the drop-down list of server types.
|
||||
2. **Type**—Select the server type from the drop-down list of server types.
|
||||
|
||||
3. **Host Name** and **Port**—Enter the host name and the port in the corresponding fields. When you select a server type in the drop-down list, the port field will automatically fill with the standard port numbers. To change a port number, click the server type in the list and change the port number according to your needs.
|
||||
3. **Host Name** and **Port**—Enter the host name and the port in the corresponding fields. When you select a server type in the drop-down list, the port field will automatically fill with the standard port numbers. To change a port number, click the server type in the list and change the port number according to your needs.
|
||||
|
||||
4. **Path**—If you have selected either **Standard HTTP Server** or **Enhanced Security HTTP Server**, you must enter the complete path to the XML file containing publishing data in this field. If you select either **Application Virtualization Server** or **Enhanced Security Application Virtualization Server**, this field is not active.
|
||||
4. **Path**—If you have selected either **Standard HTTP Server** or **Enhanced Security HTTP Server**, you must enter the complete path to the XML file containing publishing data in this field. If you select either **Application Virtualization Server** or **Enhanced Security Application Virtualization Server**, this field is not active.
|
||||
|
||||
5. **Automatically contact this server to update settings when a user logs in**—Select this check box if you want this server to be queried automatically when users log in to their account on the Application Virtualization Client.
|
||||
5. **Automatically contact this server to update settings when a user logs in**—Select this check box if you want this server to be queried automatically when users log in to their account on the Application Virtualization Client.
|
||||
|
||||
6. When finished with the configuration steps, click **Next**.
|
||||
6. When finished with the configuration steps, click **Next**.
|
||||
|
||||
16. On the **Ready to Install the Program** screen, click **Install**. A screen is displayed that shows the progress of the installation.
|
||||
|
||||
17. On the **Install Wizard Completed** screen, click **Finish**.
|
||||
|
||||
**Note**
|
||||
If the installation fails for any reason, you might need to restart the computer before trying the install again.
|
||||
|
||||
|
||||
**Note**
|
||||
If the installation fails for any reason, you might need to restart the computer before trying the install again.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
|
||||
|
||||
[Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ manager: dansimp
|
||||
- LastErrorDescription
|
||||
- SyncStatusDescription
|
||||
- SyncProgress
|
||||
- Sync
|
||||
- Sync
|
||||
- PublishXML
|
||||
- AppVDynamicPolicy
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
## Enable a policy
|
||||
|
||||
1. Find the policy from the list [ADMX-backed policies](policy-configuration-service-provider.md#admx-backed-policies). You need the following information listed in the policy description.
|
||||
- GP English name
|
||||
- GP English name
|
||||
- GP name
|
||||
- GP ADMX file name
|
||||
- GP path
|
||||
|
||||
@ -44,7 +44,7 @@ The MDM security baseline includes policies that cover the following areas:
|
||||
For more details about the MDM policies defined in the MDM security baseline and what Microsoft’s recommended baseline policy values are, see:
|
||||
- [MDM Security baseline for Windows 10, version 1903](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1903-MDM-SecurityBaseLine-Document.zip)
|
||||
|
||||
- [MDM Security baseline for Windows 10, version 1809](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1809-MDM-SecurityBaseLine-Document-[Preview].zip)
|
||||
- [MDM Security baseline for Windows 10, version 1809](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1809-MDM-SecurityBaseLine-Document-[Preview].zip)
|
||||
|
||||
For information about the MDM policies defined in the Intune security baseline public preview, see [Windows security baseline settings for Intune](https://docs.microsoft.com/intune/security-baseline-settings-windows)
|
||||
|
||||
|
||||
@ -387,12 +387,12 @@ Specifies whether device lock is enabled.
|
||||
> [!Important]
|
||||
> **DevicePasswordEnabled** should not be set to Enabled (0) when WMI is used to set the EAS DeviceLock policies given that it is Enabled by default in Policy CSP for back compat with Windows 8.x. If **DevicePasswordEnabled** is set to Enabled(0) then Policy CSP will return an error stating that **DevicePasswordEnabled** already exists. Windows 8.x did not support DevicePassword policy. When disabling **DevicePasswordEnabled** (1) then this should be the only policy set from the DeviceLock group of policies listed below:
|
||||
> - **DevicePasswordEnabled** is the parent policy of the following:
|
||||
> - AllowSimpleDevicePassword
|
||||
> - MinDevicePasswordLength
|
||||
> - AlphanumericDevicePasswordRequired
|
||||
> - MinDevicePasswordComplexCharacters
|
||||
> - DevicePasswordExpiration
|
||||
> - DevicePasswordHistory
|
||||
> - AllowSimpleDevicePassword
|
||||
> - MinDevicePasswordLength
|
||||
> - AlphanumericDevicePasswordRequired
|
||||
> - MinDevicePasswordComplexCharacters
|
||||
> - DevicePasswordExpiration
|
||||
> - DevicePasswordHistory
|
||||
> - MaxDevicePasswordFailedAttempts
|
||||
> - MaxInactivityTimeDeviceLock
|
||||
|
||||
|
||||
@ -190,21 +190,21 @@ To do this, follow these steps:
|
||||
|
||||
3. Add one of the following registry values to configure Automatic Update.
|
||||
|
||||
* NoAutoUpdate (REG_DWORD):
|
||||
* NoAutoUpdate (REG_DWORD):
|
||||
|
||||
* **0**: Automatic Updates is enabled (default).
|
||||
* **0**: Automatic Updates is enabled (default).
|
||||
|
||||
* **1**: Automatic Updates is disabled.
|
||||
* **1**: Automatic Updates is disabled.
|
||||
|
||||
* AUOptions (REG_DWORD):
|
||||
* AUOptions (REG_DWORD):
|
||||
|
||||
* **1**: Keep my computer up to date is disabled in Automatic Updates.
|
||||
* **1**: Keep my computer up to date is disabled in Automatic Updates.
|
||||
|
||||
* **2**: Notify of download and installation.
|
||||
* **2**: Notify of download and installation.
|
||||
|
||||
* **3**: Automatically download and notify of installation.
|
||||
* **3**: Automatically download and notify of installation.
|
||||
|
||||
* **4**: Automatically download and scheduled installation.
|
||||
* **4**: Automatically download and scheduled installation.
|
||||
|
||||
* ScheduledInstallDay (REG_DWORD):
|
||||
|
||||
|
||||
@ -62,29 +62,29 @@ This page explains how to create an AAD application, get an access token to Micr
|
||||
|
||||
4. Allow your Application to access Microsoft Defender ATP and assign it 'Read alerts' permission:
|
||||
|
||||
- On your application page, click **API Permissions** > **Add permission** > **APIs my organization uses** > type **WindowsDefenderATP** and click on **WindowsDefenderATP**.
|
||||
- On your application page, click **API Permissions** > **Add permission** > **APIs my organization uses** > type **WindowsDefenderATP** and click on **WindowsDefenderATP**.
|
||||
|
||||
- **Note**: WindowsDefenderATP does not appear in the original list. You need to start writing its name in the text box to see it appear.
|
||||
- **Note**: WindowsDefenderATP does not appear in the original list. You need to start writing its name in the text box to see it appear.
|
||||
|
||||
|
||||
|
||||
|
||||
- Choose **Delegated permissions** > **Alert.Read** > Click on **Add permissions**
|
||||
- Choose **Delegated permissions** > **Alert.Read** > Click on **Add permissions**
|
||||
|
||||
|
||||
|
||||
|
||||
- **Important note**: You need to select the relevant permissions. 'Read alerts' is only an example!
|
||||
- **Important note**: You need to select the relevant permissions. 'Read alerts' is only an example!
|
||||
|
||||
For instance,
|
||||
For instance,
|
||||
|
||||
- To [run advanced queries](run-advanced-query-api.md), select 'Run advanced queries' permission
|
||||
- To [isolate a machine](isolate-machine.md), select 'Isolate machine' permission
|
||||
- To determine which permission you need, please look at the **Permissions** section in the API you are interested to call.
|
||||
- To [run advanced queries](run-advanced-query-api.md), select 'Run advanced queries' permission
|
||||
- To [isolate a machine](isolate-machine.md), select 'Isolate machine' permission
|
||||
- To determine which permission you need, please look at the **Permissions** section in the API you are interested to call.
|
||||
|
||||
- Click **Grant consent**
|
||||
- Click **Grant consent**
|
||||
|
||||
**Note**: Every time you add permission you must click on **Grant consent** for the new permission to take effect.
|
||||
**Note**: Every time you add permission you must click on **Grant consent** for the new permission to take effect.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Write down your application ID and your tenant ID:
|
||||
|
||||
@ -102,42 +102,42 @@ For more details on AAD token, refer to [AAD tutorial](https://docs.microsoft.co
|
||||
- Copy/Paste the below class in your application.
|
||||
- Use **AcquireUserTokenAsync** method with the your application ID, tenant ID, user name and password to acquire a token.
|
||||
|
||||
```
|
||||
namespace WindowsDefenderATP
|
||||
{
|
||||
using System.Net.Http;
|
||||
using System.Text;
|
||||
using System.Threading.Tasks;
|
||||
using Newtonsoft.Json.Linq;
|
||||
```csharp
|
||||
namespace WindowsDefenderATP
|
||||
{
|
||||
using System.Net.Http;
|
||||
using System.Text;
|
||||
using System.Threading.Tasks;
|
||||
using Newtonsoft.Json.Linq;
|
||||
|
||||
public static class WindowsDefenderATPUtils
|
||||
{
|
||||
private const string Authority = "https://login.windows.net";
|
||||
public static class WindowsDefenderATPUtils
|
||||
{
|
||||
private const string Authority = "https://login.windows.net";
|
||||
|
||||
private const string WdatpResourceId = "https://api.securitycenter.windows.com";
|
||||
private const string WdatpResourceId = "https://api.securitycenter.windows.com";
|
||||
|
||||
public static async Task<string> AcquireUserTokenAsync(string username, string password, string appId, string tenantId)
|
||||
{
|
||||
using (var httpClient = new HttpClient())
|
||||
{
|
||||
var urlEncodedBody = $"resource={WdatpResourceId}&client_id={appId}&grant_type=password&username={username}&password={password}";
|
||||
public static async Task<string> AcquireUserTokenAsync(string username, string password, string appId, string tenantId)
|
||||
{
|
||||
using (var httpClient = new HttpClient())
|
||||
{
|
||||
var urlEncodedBody = $"resource={WdatpResourceId}&client_id={appId}&grant_type=password&username={username}&password={password}";
|
||||
|
||||
var stringContent = new StringContent(urlEncodedBody, Encoding.UTF8, "application/x-www-form-urlencoded");
|
||||
var stringContent = new StringContent(urlEncodedBody, Encoding.UTF8, "application/x-www-form-urlencoded");
|
||||
|
||||
using (var response = await httpClient.PostAsync($"{Authority}/{tenantId}/oauth2/token", stringContent).ConfigureAwait(false))
|
||||
{
|
||||
response.EnsureSuccessStatusCode();
|
||||
using (var response = await httpClient.PostAsync($"{Authority}/{tenantId}/oauth2/token", stringContent).ConfigureAwait(false))
|
||||
{
|
||||
response.EnsureSuccessStatusCode();
|
||||
|
||||
var json = await response.Content.ReadAsStringAsync().ConfigureAwait(false);
|
||||
var json = await response.Content.ReadAsStringAsync().ConfigureAwait(false);
|
||||
|
||||
var jObject = JObject.Parse(json);
|
||||
var jObject = JObject.Parse(json);
|
||||
|
||||
return jObject["access_token"].Value<string>();
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
return jObject["access_token"].Value<string>();
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Validate the token
|
||||
@ -156,16 +156,17 @@ Sanity check to make sure you got a correct token:
|
||||
- The Expiration time of the token is 1 hour (you can send more then one request with the same token)
|
||||
|
||||
- Example of sending a request to get a list of alerts **using C#**
|
||||
```
|
||||
var httpClient = new HttpClient();
|
||||
|
||||
var request = new HttpRequestMessage(HttpMethod.Get, "https://api.securitycenter.windows.com/api/alerts");
|
||||
```csharp
|
||||
var httpClient = new HttpClient();
|
||||
|
||||
request.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
|
||||
var request = new HttpRequestMessage(HttpMethod.Get, "https://api.securitycenter.windows.com/api/alerts");
|
||||
|
||||
var response = httpClient.SendAsync(request).GetAwaiter().GetResult();
|
||||
request.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);
|
||||
|
||||
// Do something useful with the response
|
||||
var response = httpClient.SendAsync(request).GetAwaiter().GetResult();
|
||||
|
||||
// Do something useful with the response
|
||||
```
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -34,30 +34,30 @@ The following steps guide you on how to create roles in Microsoft Defender Secur
|
||||
|
||||
3. Enter the role name, description, and permissions you'd like to assign to the role.
|
||||
|
||||
- **Role name**
|
||||
- **Description**
|
||||
- **Permissions**
|
||||
- **View data** - Users can view information in the portal.
|
||||
- **Alerts investigation** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- **Manage portal system settings** - Users can configure storage settings, SIEM and threat intel API settings (applies globally), advanced settings, automated file uploads, roles and machine groups.
|
||||
- **Role name**
|
||||
- **Description**
|
||||
- **Permissions**
|
||||
- **View data** - Users can view information in the portal.
|
||||
- **Alerts investigation** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Active remediation actions** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- **Manage portal system settings** - Users can configure storage settings, SIEM and threat intel API settings (applies globally), advanced settings, automated file uploads, roles and machine groups.
|
||||
|
||||
>[!NOTE]
|
||||
>This setting is only available in the Microsoft Defender ATP administrator (default) role.
|
||||
> [!NOTE]
|
||||
> This setting is only available in the Microsoft Defender ATP administrator (default) role.
|
||||
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, create and manage custom detections, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, create and manage custom detections, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
|
||||
- **Live response capabilities** - Users can take basic or advanced live response commands. <br>
|
||||
- Basic commands allow users to:
|
||||
- Start a live response session
|
||||
- Run read only live response commands on a remote machine
|
||||
- Advanced commands allow users to:
|
||||
- Run basic actions
|
||||
- Download a file from the remote machine
|
||||
- View a script from the files library
|
||||
- Run a script on the remote machine from the files library take read and write commands.
|
||||
- **Live response capabilities** - Users can take basic or advanced live response commands.
|
||||
- Basic commands allow users to:
|
||||
- Start a live response session
|
||||
- Run read only live response commands on a remote machine
|
||||
- Advanced commands allow users to:
|
||||
- Run basic actions
|
||||
- Download a file from the remote machine
|
||||
- View a script from the files library
|
||||
- Run a script on the remote machine from the files library take read and write commands.
|
||||
|
||||
For more information on the available commands, see [Investigate machines using Live response](live-response.md).
|
||||
For more information on the available commands, see [Investigate machines using Live response](live-response.md).
|
||||
|
||||
4. Click **Next** to assign the role to an Azure AD group.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user