mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merge branch 'master' into Tp-updateTinaMcNaboe
This commit is contained in:
commit
502a7b8f9a
File diff suppressed because it is too large
Load Diff
@ -73,7 +73,7 @@ The topics in this library have been updated for Windows 10 Holographic for Busi
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) | Replaced the instructions for upgrading to Windows Holographic for Business using Microsoft Intune with a link to the new Intune topic.
|
||||
[Unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md) | Replaced the instructions for upgrading to Windows Holographic for Business using Microsoft Intune with a link to the new Intune topic.
|
||||
|
||||
## December 2017
|
||||
|
||||
|
@ -18,7 +18,7 @@ manager: dansimp
|
||||
You can manage multiple Microsoft HoloLens devices simultaneously using solutions like [Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business). You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies).
|
||||
|
||||
>[!NOTE]
|
||||
>Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
>Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
## Requirements
|
||||
|
||||
|
@ -198,7 +198,7 @@ Use the following snippet in your kiosk configuration XML to enable the **Guest*
|
||||

|
||||
|
||||
>[!NOTE]
|
||||
>The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has a [license to upgrade to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
>The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has a [license to upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**.
|
||||
|
||||
|
@ -36,7 +36,7 @@ The HoloLens wizard helps you configure the following settings in a provisioning
|
||||
- Upgrade to the enterprise edition
|
||||
|
||||
>[!NOTE]
|
||||
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
- Configure the HoloLens first experience (OOBE)
|
||||
- Configure Wi-Fi network
|
||||
@ -90,7 +90,7 @@ After you're done, click **Create**. It only takes a few seconds. When the packa
|
||||
## Create a provisioning package for HoloLens using advanced provisioning
|
||||
|
||||
>[!NOTE]
|
||||
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
>Settings in a provisioning package will only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
|
||||
|
||||
1. On the Windows Configuration Designer start page, select **Advanced provisioning**.
|
||||
2. In the **Enter project details** window, specify a name for your project and the location for your project. Optionally, enter a brief description to describe your project.
|
||||
@ -186,7 +186,7 @@ In Windows Configuration Designer, when you create a provisioning package for Wi
|
||||
| --- | --- |
|
||||
| **Certificates** | Deploy a certificate to HoloLens. |
|
||||
| **ConnectivityProfiles** | Deploy a Wi-Fi profile to HoloLens. |
|
||||
| **EditionUpgrade** | [Upgrade to Windows Holographic for Business.](hololens-upgrade-enterprise.md) |
|
||||
| **EditionUpgrade** | [Upgrade to Windows Holographic for Business.](hololens1-upgrade-enterprise.md) |
|
||||
| **Policies** | Allow or prevent developer mode on HoloLens. [Policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies) |
|
||||
|
||||
>[!NOTE]
|
||||
|
@ -22,7 +22,7 @@ This article includes:
|
||||
- Instructions for remote device management
|
||||
- Options for application deployment
|
||||
|
||||
This guide assumes basic familiarity with HoloLens. Follow the [get started guide](./hololens-setup.md) to set up HoloLens for the first time.
|
||||
This guide assumes basic familiarity with HoloLens. Follow the [get started guide](hololens1-setup.md) to set up HoloLens for the first time.
|
||||
|
||||
## Infrastructure for managing HoloLens
|
||||
|
||||
|
@ -15,7 +15,7 @@ manager: dansimp
|
||||
# Manage updates to HoloLens
|
||||
|
||||
>[!NOTE]
|
||||
>HoloLens devices must be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md) to manage updates.
|
||||
>HoloLens devices must be [upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md) to manage updates.
|
||||
|
||||
For a complete list of Update policies, see [Policies supported by Windows Holographic for Business](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#a-href-idhololenspoliciesapolicies-supported-by-windows-holographic-for-business).
|
||||
|
||||
|
@ -51,7 +51,7 @@ Feature | Details
|
||||
Localized Chinese and Japanese builds | Use HoloLens with localized user interface for Simplified Chinese or Japanese, including localized Pinyin keyboard, dictation, and voice commands.
|
||||
Speech Synthesis (TTS) | Speech synthesis feature now supports Chinese, Japanese, and English.
|
||||
|
||||
[Learn how to install the Chinese and Japanese versions of HoloLens.](hololens-install-localized.md)
|
||||
[Learn how to install the Chinese and Japanese versions of HoloLens.](hololens1-install-localized.md)
|
||||
|
||||
|
||||
## Windows 10, version 1803 for Microsoft HoloLens
|
||||
@ -60,7 +60,7 @@ Speech Synthesis (TTS) | Speech synthesis feature now supports Chinese, Japanese
|
||||
|
||||
Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. This update introduces the following changes:
|
||||
|
||||
- Previously, you could only verify that upgrade license for Commercial Suite had been applied to your HoloLens device by checking to see if VPN was an available option on the device. Now, **Settings** > **System** will display **Windows Holographic for Business** after the upgrade license is applied. [Learn how to unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md).
|
||||
- Previously, you could only verify that upgrade license for Commercial Suite had been applied to your HoloLens device by checking to see if VPN was an available option on the device. Now, **Settings** > **System** will display **Windows Holographic for Business** after the upgrade license is applied. [Learn how to unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md).
|
||||
|
||||
- You can view the operating system build number in device properties in the File Explorer app and in the [Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq).
|
||||
|
||||
|
@ -79,7 +79,7 @@ When you place an app window or app launcher, it will stay put until you remove
|
||||
|
||||
## Move, resize, and rotate apps
|
||||
|
||||
Moving and resizing apps on HoloLens works a bit differently than it does on a PC. Instead of dragging the app, you'll use your gaze, along with a [gesture](https://support.microsoft.com/help/12644/hololens-use-gestures) or the [clicker](hololens-clicker.md). You can also rotate an app window in 3D space.
|
||||
Moving and resizing apps on HoloLens works a bit differently than it does on a PC. Instead of dragging the app, you'll use your gaze, along with a [gesture](https://support.microsoft.com/help/12644/hololens-use-gestures) or the [clicker](hololens1-clicker.md). You can also rotate an app window in 3D space.
|
||||
|
||||
> [!TIP]
|
||||
> Rearrange apps using your voice - gaze at an app and say "Face me," "Bigger," or "Smaller." Or have Cortana move an app for you: say "Hey Cortana, move \**app name\** here."
|
||||
|
@ -28,9 +28,8 @@ ms.date: 07/14/2019
|
||||
|
||||
| Guide | Description |
|
||||
| --- | --- |
|
||||
| [Get started with HoloLens](hololens-setup.md) | Set up HoloLens for the first time. |
|
||||
| [Get started with HoloLens](hololens1-setup.md) | Set up HoloLens for the first time. |
|
||||
| [Deploy HoloLens in a commercial environment](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management. |
|
||||
| [Install and manage applications on HoloLens](hololens-install-apps.md) |Install and manage important applications on HoloLens at scale. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Get support](https://support.microsoft.com/products/hololens) |Connect with Microsoft support resources for HoloLens in enterprise. |
|
||||
|
||||
@ -45,7 +44,7 @@ ms.date: 07/14/2019
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens. |
|
||||
| [Install localized version of HoloLens](hololens-install-localized.md) | Configure HoloLens for different locale. |
|
||||
| [Install localized version of HoloLens](hololens1-install-localized.md) | Configure HoloLens for different locale. |
|
||||
|
||||
## Related resources
|
||||
|
||||
|
@ -153,16 +153,18 @@ Requirements:
|
||||
- Enterprise AD must be integrated with Azure AD.
|
||||
- Ensure that PCs belong to same computer group.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803 or version 1809. To fix the issue, follow these steps:
|
||||
> [!IMPORTANT]
|
||||
> If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803 or version 1809. To fix the issue, follow these steps:
|
||||
> 1. Download:
|
||||
> 1803 -->[Administrative Templates (.admx) for Windows 10 April 2018 Update (1803)](https://www.microsoft.com/download/details.aspx?id=56880) or
|
||||
> 1809 --> [Administrative Templates for Windows 10 October 2018 Update (1809)](https://www.microsoft.com/download/details.aspx?id=57576).
|
||||
> 1809 --> [Administrative Templates for Windows 10 October 2018 Update (1809)](https://www.microsoft.com/download/details.aspx?id=57576) or
|
||||
> 1903 --> [Administrative Templates for Windows 10 May 2019 Update (1903)](https://www.microsoft.com/download/details.aspx?id=58495)
|
||||
> 2. Install the package on the Primary Domain Controller (PDC).
|
||||
> 3. Navigate, depending on the version to the folder:
|
||||
> 1803 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 April 2018 Update (1803) v2**, or
|
||||
> 1809 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 October 2018 Update (1809) v2**
|
||||
> 4. Copy policy definitions folder to **C:\Windows\SYSVOL\domain\Policies**.
|
||||
> 1803 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 April 2018 Update (1803) v2**, or
|
||||
> 1809 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 October 2018 Update (1809) v2** or
|
||||
> 1903 --> **C:\Program Files (x86)\Microsoft Group Policy\Windows 10 May 2019 Update (1903) v3**
|
||||
> 4. Copy policy definitions folder to **C:\Windows\SYSVOL\domain\Policies** .
|
||||
> 5. Restart the Primary Domain Controller for the policy to be available.
|
||||
> This procedure will work for any future version as well.
|
||||
|
||||
@ -172,10 +174,8 @@ Requirements:
|
||||
4. Filter using Security Groups.
|
||||
5. Enforce a GPO link.
|
||||
|
||||
> [!NOTE]
|
||||
> Version 1903 (March 2019) is actually on the Insider program and doesn't yet contain a downloadable version of Templates (version 1903).
|
||||
|
||||
## Troubleshoot auto-enrollment of devices
|
||||
|
||||
Investigate the log file if you have issues even after performing all the mandatory verification steps. The first log file to investigate is the event log on the target Windows 10 device.
|
||||
|
||||
To collect Event Viewer logs:
|
||||
@ -232,5 +232,6 @@ To collect Event Viewer logs:
|
||||
|
||||
### Useful Links
|
||||
|
||||
- [Windows 10 Administrative Templates for Windows 10 May 2019 Update 1903](https://www.microsoft.com/download/details.aspx?id=58495)
|
||||
- [Windows 10 Administrative Templates for Windows 10 October 2018 Update 1809](https://www.microsoft.com/download/details.aspx?id=57576)
|
||||
- [Windows 10 Administrative Templates for Windows 10 April 2018 Update 1803](https://www.microsoft.com/download/details.aspx?id=56880)
|
||||
|
@ -106,3 +106,10 @@ The following diagram shows the NetworkQoSPolicy configuration service provider
|
||||
|
||||
<p style="margin-left: 20px">The supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
Read more about the XML DDF structure to create this policy by following the links below:
|
||||
|
||||
- [More Information about DDF and structure](networkqospolicy-ddf.md)
|
||||
- [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download)
|
||||
|
@ -52,8 +52,8 @@ threatFamilyName | string | Threat family.
|
||||
title | string | Alert title.
|
||||
description | String | Description of the threat, identified by the alert.
|
||||
alertCreationTime | DateTimeOffset | The date and time (in UTC) the alert was created.
|
||||
lastEventTime | DateTimeOffset | The last occurance of the event that triggered the alert on the same machine.
|
||||
firstEventTime | DateTimeOffset | The first occurance of the event that triggered the alert on that machine.
|
||||
lastEventTime | DateTimeOffset | The last occurrence of the event that triggered the alert on the same machine.
|
||||
firstEventTime | DateTimeOffset | The first occurrence of the event that triggered the alert on that machine.
|
||||
resolvedTime | DateTimeOffset | The date and time in which the status of the alert was changed to 'Resolved'.
|
||||
machineId | String | ID of a [machine](machine.md) entity that is associated with the alert.
|
||||
|
||||
|
@ -75,7 +75,7 @@ The **Graph** tells the story of the cybersecurity attack. For example, it shows
|
||||
|
||||
You can click the circles on the incident graph to view the details of the malicious files, associated file detections, how many instances has there been worldwide, whether it’s been observed in your organization, if so, how many instances.
|
||||
|
||||

|
||||

|
||||
|
||||
## Related topics
|
||||
- [Incidents queue](https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/view-incidents-queue)
|
||||
|
@ -4,6 +4,8 @@ ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.prod: w10
|
||||
title: Note
|
||||
---
|
||||
>[!Note]
|
||||
> This page focuses on performing a machine action via API. See [take response actions on a machine](respond-machine-alerts.md) for more information about response actions functionality via Microsoft Defender ATP.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Manage automation file uploads
|
||||
description: Enable content analysis and configure the file extension and email attachment extensions that will be sumitted for analysis
|
||||
description: Enable content analysis and configure the file extension and email attachment extensions that will be submitted for analysis
|
||||
keywords: automation, file, uploads, content, analysis, file, extension, email, attachment
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -45,5 +45,4 @@ For example, if you add *exe* and *bat* as file or attachment extension names, t
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Manage automation allowed/blocked lists](manage-automation-allowed-blocked-list.md)
|
||||
- [Manage automation folder exclusions](manage-automation-folder-exclusions.md)
|
||||
- [Manage automation folder exclusions](manage-automation-folder-exclusions.md)
|
||||
|
@ -9,7 +9,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: mjcaparas
|
||||
ms.author: macaparas
|
||||
ms.author: macapara
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
@ -172,7 +172,7 @@ After completing the steps in the Before you begin section, you can proceed with
|
||||
|
||||
|
||||
## Mashup Microsoft Defender ATP data with other data sources
|
||||
You can use Power BI Desktop to analyse data from Microsoft Defender ATP and mash that data up with other data sources to gain better security perspective in your organization.
|
||||
You can use Power BI Desktop to analyze data from Microsoft Defender ATP and mash that data up with other data sources to gain better security perspective in your organization.
|
||||
|
||||
1. In Power BI Desktop, in the Home ribbon, click **Get data** and search for **Microsoft Defender Advanced Threat Protection**.
|
||||
|
||||
|
@ -4,6 +4,8 @@ ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.prod: w10
|
||||
title: "Prerelease"
|
||||
---
|
||||
|
||||
>[!IMPORTANT]
|
||||
|
@ -20,6 +20,11 @@ ms.topic: conceptual
|
||||
|
||||
# What's new in Microsoft Defender Advanced Threat Protection for Mac
|
||||
|
||||
## 100.68.99
|
||||
|
||||
- Added the ability to configure the antivirus functionality to run in [passive mode](microsoft-defender-atp-mac-preferences.md#enable--disable-passive-mode)
|
||||
- Performance improvements & bug fixes
|
||||
|
||||
## 100.65.28
|
||||
|
||||
- Added support for macOS Catalina
|
||||
@ -32,4 +37,4 @@ ms.topic: conceptual
|
||||
> - For manual deployments, see the updated instructions in the [Manual deployment](microsoft-defender-atp-mac-install-manually.md#how-to-allow-full-disk-access) topic.
|
||||
> - For managed deployments, see the updated instructions in the [JAMF-based deployment](microsoft-defender-atp-mac-install-with-jamf.md#privacy-preferences-policy-control) and [Microsoft Intune-based deployment](microsoft-defender-atp-mac-install-with-intune.md#create-system-configuration-profiles) topics.
|
||||
|
||||
- Performance improvements
|
||||
- Performance improvements & bug fixes
|
||||
|
@ -14,7 +14,6 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 09/21/2017
|
||||
---
|
||||
|
||||
# Maintain AppLocker policies
|
||||
@ -41,7 +40,9 @@ There are three methods you can use to maintain AppLocker policies:
|
||||
- [Maintaining AppLocker policies on the local computer](#bkmk-applkr-use-locsnapin)
|
||||
|
||||
## <a href="" id="bkmk-applkr-use-mdm"></a>Maintaining AppLocker policies by using Mobile Device Management (MDM)
|
||||
Using the AppLocker configuration service provider, you can select which apps are allowed or blocked from running. Using the CSP, you can configure app restrictions based on grouping (such as EXE, MSI, DLL, Store apps and more) and then chose how to enforce different policies for different apps.
|
||||
|
||||
For more information, see the [AppLocker CSP](https://docs.microsoft.com/windows/client-management/mdm/applocker-csp).
|
||||
|
||||
|
||||
## <a href="" id="bkmk-applkr-use-gp"></a>Maintaining AppLocker policies by using Group Policy
|
||||
|
Loading…
x
Reference in New Issue
Block a user