mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 04:13:41 +00:00
Merging changes synced from https://github.com/MicrosoftDocs/windows-docs-pr (branch live)
This commit is contained in:
officedocspr
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10)
|
||||
description: How to Deploy the App-V Server Using a Script
|
||||
description: Information, lists, and tables that can help you deploy the App-V server using a script
|
||||
author: lomayor
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploying App-V (Windows 10)
|
||||
description: Deploying App-V
|
||||
description: App-V supports several different deployment options. Learn how to complete App-V deployment at different stages in your App-V deployment.
|
||||
author: lomayor
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to publish a package by using the Management console (Windows 10)
|
||||
description: How to publish a package by using the Management console.
|
||||
description: Learn how the Management console in App-V can help you enable admin controls as well as publish App-V packages.
|
||||
author: lomayor
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Change history for Application management in Windows 10 (Windows 10)
|
||||
description: View changes to documentation for application management in Windows 10.
|
||||
description: View new release information and updated topics in the documentation for application management in Windows 10.
|
||||
keywords:
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configure Windows 10 (Windows 10)
|
||||
description: Learn about configuring Windows 10.
|
||||
description: Apply custom accessibility configurations to devices for their users using the all the features and methods available with Windows 10.
|
||||
keywords: Windows 10, MDM, WSUS, Windows update
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -78,7 +78,7 @@ You can also use Group Policy to manage access to Microsoft Store.
|
||||
|
||||
1. Type gpedit in the search bar to find and start Group Policy Editor.
|
||||
|
||||
2. In the console tree of the snap-in, click **Computer Configuration**, click **Administrative Templates** , click **Windows Components**, and then click **Store**.
|
||||
2. In the console tree of the snap-in, click **Computer Configuration**, click **Administrative Templates**, click **Windows Components**, and then click **Store**.
|
||||
|
||||
3. In the Setting pane, click **Turn off the Store application**, and then click **Edit policy setting**.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Add and Remove Computers (Windows 10)
|
||||
description: Add and Remove Computers
|
||||
description: The Discover products function on the Volume Activation Management Tool (VAMT) allows you to search the Active Directory domain or a general LDAP query.
|
||||
ms.assetid: cb6f3a78-ece0-4dc7-b086-cb003d82cd52
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
@ -8,7 +8,8 @@ ms.author: greglin
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.pagetype: activation
|
||||
ms.date: 04/25/2017
|
||||
ms.topic: article
|
||||
|
||||
@ -67,11 +67,11 @@ For each device that will be deployed using user-driven deployment, these additi
|
||||
|
||||
## User-driven mode for hybrid Azure Active Directory join
|
||||
|
||||
Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
|
||||
Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid-joined to Azure Active Directory (Azure AD)](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).
|
||||
|
||||
### Requirements
|
||||
|
||||
To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
|
||||
To perform a user-driven hybrid Azure AD joined deployment using Windows Autopilot:
|
||||
|
||||
- A Windows Autopilot profile for user-driven mode must be created and
|
||||
- **Hybrid Azure AD joined** must be specified as the selected option under **Join to Azure AD as** in the Autopilot profile.
|
||||
@ -83,7 +83,7 @@ To perform a user-driven hybrid AAD joined deployment using Windows Autopilot:
|
||||
- Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is [configured to perform this action](https://docs.microsoft.com/intune/windows-autopilot-hybrid#increase-the-computer-account-limit-in-the-organizational-unit) on the user's behalf.
|
||||
- If using Proxy, WPAD Proxy settings option must be enabled and configured.
|
||||
|
||||
**AAD device join**: The hybrid AAD join process uses the system context to perform device AAD join, therefore it is not affected by user based AAD join permission settings. In addition, all users are enabled to join devices to AAD by default.
|
||||
**Azure AD device join**: The hybrid Azure AD join process uses the system context to perform device Azure AD join, therefore it is not affected by user based Azure AD join permission settings. In addition, all users are enabled to join devices to Azure AD by default.
|
||||
|
||||
### Step by step instructions
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: OData queries with Microsoft Defender ATP
|
||||
ms.reviewer:
|
||||
description: OData queries with Microsoft Defender ATP
|
||||
description: Use these examples of Open Data Protocol (OData) queries to help with data access protocols in Microsoft Defender ATP
|
||||
keywords: apis, supported apis, odata, query
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
@ -35,7 +35,7 @@ Not all properties are filterable.
|
||||
|
||||
### Example 1
|
||||
|
||||
- Get all the machines with the tag 'ExampleTag'
|
||||
Get all the machines with the tag 'ExampleTag'
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=machineTags/any(tag: tag eq 'ExampleTag')
|
||||
@ -76,7 +76,7 @@ Content-type: application/json
|
||||
|
||||
### Example 2
|
||||
|
||||
- Get all the alerts that created after 2018-10-20 00:00:00
|
||||
Get all the alerts that created after 2018-10-20 00:00:00
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/alerts?$filter=alertCreationTime+gt+2018-11-22T00:00:00Z
|
||||
@ -126,7 +126,7 @@ Content-type: application/json
|
||||
|
||||
### Example 3
|
||||
|
||||
- Get all the machines with 'High' 'RiskScore'
|
||||
Get all the machines with 'High' 'RiskScore'
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=riskScore+eq+'High'
|
||||
@ -167,7 +167,7 @@ Content-type: application/json
|
||||
|
||||
### Example 4
|
||||
|
||||
- Get top 100 machines with 'HealthStatus' not equals to 'Active'
|
||||
Get top 100 machines with 'HealthStatus' not equals to 'Active'
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=healthStatus+ne+'Active'&$top=100
|
||||
@ -208,7 +208,7 @@ Content-type: application/json
|
||||
|
||||
### Example 5
|
||||
|
||||
- Get all the machines that last seen after 2018-10-20
|
||||
Get all the machines that last seen after 2018-10-20
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=lastSeen gt 2018-08-01Z
|
||||
@ -249,7 +249,7 @@ Content-type: application/json
|
||||
|
||||
### Example 6
|
||||
|
||||
- Get all the Anti-Virus scans that the user Analyst@examples.onmicrosoft.com created using Microsoft Defender ATP
|
||||
Get all the Anti-Virus scans that the user Analyst@examples.onmicrosoft.com created using Microsoft Defender ATP
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machineactions?$filter=requestor eq 'Analyst@contoso.com' and type eq 'RunAntiVirusScan'
|
||||
@ -283,7 +283,7 @@ Content-type: application/json
|
||||
|
||||
### Example 7
|
||||
|
||||
- Get the count of open alerts for a specific machine:
|
||||
Get the count of open alerts for a specific machine:
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines/123321d0c675eaa415b8e5f383c6388bff446c62/alerts/$count?$filter=status ne 'Resolved'
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Live response command examples
|
||||
description: Learn about common commands and see examples on how it's used
|
||||
description: Learn to run basic or advanced live response commands for Microsoft Defender Advanced Threat Protection (ATP) and see examples on how it's used
|
||||
keywords: example, command, cli, remote, shell, connection, live, response, real-time, command, script, remediate, hunt, export, log, drop, download, file
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Planning Isolation Groups for the Zones (Windows 10)
|
||||
description: Planning Isolation Groups for the Zones
|
||||
description: Learn about planning isolation groups for the zones in Microsoft Firewall, including information on universal groups and GPOs
|
||||
ms.assetid: be4b662d-c1ce-441e-b462-b140469a5695
|
||||
ms.reviewer:
|
||||
ms.author: dansimp
|
||||
@ -25,7 +25,8 @@ ms.date: 04/19/2017
|
||||
|
||||
Isolation groups in Active Directory are how you implement the various domain and server isolation zones. A device is assigned to a zone by adding its device account to the group which represents that zone.
|
||||
|
||||
>**Caution:** Do not add devices to your groups yet. If a device is in a group when the GPO is activated then that GPO is applied to the device. If the GPO is one that requires authentication, and the other devices have not yet received their GPOs, the device that uses the new GPO might not be able to communicate with the others.
|
||||
> [!CAUTION]
|
||||
> Do not add devices to your groups yet. If a device is in a group when the GPO is activated then that GPO is applied to the device. If the GPO is one that requires authentication, and the other devices have not yet received their GPOs, the device that uses the new GPO might not be able to communicate with the others.
|
||||
|
||||
Universal groups are the best option to use for GPO assignment because they apply to the whole forest and reduce the number of groups that must be managed. However, if universal groups are unavailable, you can use domain global groups instead.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user