diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index a815d35fe0..78c7959ac0 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -6,6 +6,21 @@ "redirect_document_id": true }, { +"source_path": "devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md", +"redirect_url": "/itpro/surface-hub/finishing-your-surface-hub-meeting", +"redirect_document_id": true +}, +{ +"source_path": "devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md", +"redirect_url": "/itpro/surface-hub/provisioning-packages-for-surface-hub", +"redirect_document_id": true +}, +{ +"source_path": "devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md", +"redirect_url": "/itpro/surface-hub/admin-group-management-for-surface-hub", +"redirect_document_id": true +}, +{ "source_path": "devices/surface-hub/surface-hub-administrators-guide.md", "redirect_url": "/itpro/surface-hub/index", "redirect_document_id": true diff --git a/browsers/edge/available-policies.md b/browsers/edge/available-policies.md index b22ded8a4f..207acd7b9a 100644 --- a/browsers/edge/available-policies.md +++ b/browsers/edge/available-policies.md @@ -60,7 +60,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable or don't configure this policy setting (default), it can be turned on and configured by the employee in the Clear browsing data options area, under Settings. ### Allow Developer Tools -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you decide whether F12 Developer Tools are available on Microsoft Edge. - If you enable or don’t configure this setting (default), the F12 Developer Tools are available in Microsoft Edge. @@ -68,7 +68,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable this setting, the F12 Developer Tools aren’t available in Microsoft Edge. ### Allow Extensions -- **Supported versions:** Windows 10, Version 1607 or later +- **Supported versions:** Windows 10, version 1607 or later - **Description:** This policy setting lets you decide whether employees can use Edge Extensions. @@ -77,7 +77,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable this setting, employees can’t use Edge Extensions. ### Allow InPrivate browsing -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you decide whether employees can browse using InPrivate website browsing. @@ -86,7 +86,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable this setting, employees can’t use InPrivate website browsing. ### Allow Microsoft Compatibility List -- **Supported versions:** Windows 10, Version 1607 or later +- **Supported versions:** Windows 10, version 1607 or later - **Description:** This policy setting lets you decide whether to use the Microsoft Compatibility List (a Microsoft-provided list that helps sites with known compatibility issues to display properly) in Microsoft Edge. By default, the Microsoft Compatibility List is enabled and can be viewed by visiting about:compat. @@ -172,7 +172,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you don’t configure this setting (default), employees can choose whether to send Do Not Track requests to websites asking for tracking info. ### Configure Favorites -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you configure the default list of Favorites that appear for your employees. Employees can change their Favorites by adding or removing items at any time. @@ -214,7 +214,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you don’t configure this setting (default), employees can choose whether search suggestions appear in the Address bar of Microsoft Edge. ### Configure Start pages -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you configure one or more Start pages, for domain-joined devices. Your employees won't be able to change this after you set it. @@ -282,7 +282,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable or don't configure this setting (default), employees can’t sync their favorites between Internet Explorer and Microsoft Edge. ### Prevent access to the about:flags page -- **Supported versions:** Windows 10, Version 1607 or later +- **Supported versions:** Windows 10, version 1607 or later - **Description:** This policy setting lets you decide whether employees can access the about:flags page, which is used to change developer settings and to enable experimental features. @@ -291,7 +291,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable or don’t configure this setting (default), employees can access the about:flags page. ### Prevent bypassing Windows Defender SmartScreen prompts for files -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you decide whether employees can override the Windows Defender SmartScreen warnings about downloading unverified files. @@ -300,7 +300,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable or don’t configure this setting (default), employees can ignore Windows Defender SmartScreen warnings and continue the download process. ### Prevent bypassing Windows Defender SmartScreen prompts for sites -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you decide whether employees can override the Windows Defender SmartScreen warnings about potentially malicious websites. @@ -327,7 +327,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you disable or don't configure this setting (default), employees will see the First Run page when opening Microsoft Edge for the first time. ### Prevent using Localhost IP address for WebRTC -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Description:** This policy setting lets you decide whether an employee’s Localhost IP address shows while making calls using the WebRTC protocol. By default, this setting is turned off. @@ -362,7 +362,7 @@ Microsoft Edge works with these Group Policy settings (`Computer Configuration\A - If you don't configure this setting (default), the default search engine is set to the one specified in App settings. ### Show message when opening sites in Internet Explorer -- **Supported versions:** Windows 10, Version 1607 and later +- **Supported versions:** Windows 10, version 1607 and later - **Description:** This policy setting lets you decide whether employees see an additional page in Microsoft Edge, stating that a site has been opened using Internet Explorer 11. @@ -452,7 +452,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **2.** Blocks all cookies from all sites. ### AllowDeveloperTools -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Desktop @@ -486,7 +486,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1.** Employees can send Do Not Track headers to websites requesting tracking info. ### AllowExtensions -- **Supported versions:** Windows 10, Version 1607 and later +- **Supported versions:** Windows 10, version 1607 and later - **Supported devices:** Desktop @@ -537,7 +537,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1 (default).** An employee must click the content, click a Click-to-Run button, or have the site appear on an auto-allow list before Microsoft Edge loads and runs Adobe Flash content. ### AllowInPrivate -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Both @@ -730,7 +730,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U >If there’s an .xml file in the cache container, IE waits 65 seconds and then checks the local cache for a newer version of the file from the server, based on standard caching rules. If the server file has a different version number than the version in the cache container, the server file is used and stored in the cache container.

If you’re already using a site list, enterprise mode continues to work during the 65 second wait; it just uses your existing site list instead of your new one. ### Favorites -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Both @@ -752,7 +752,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U URLs must be on separate lines and aren't shared between Microsoft Edge and Internet Explorer 11. ### FirstRunURL -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Mobile @@ -771,7 +771,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U ### HomePages -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Desktop @@ -790,7 +790,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U ### PreventAccessToAboutFlagsInMicrosoftEdge -- **Supported versions:** Windows 10, Version 1607 and later +- **Supported versions:** Windows 10, version 1607 and later - **Supported devices:** Desktop @@ -841,7 +841,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1.** Microsoft servers will not be contacted if a site is pinned to Start from Microsoft Edge. ### PreventSmartScreenPromptOverride -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Both @@ -858,7 +858,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1.** Turns on Windows Defender SmartScreen. ### PreventSmartScreenPromptOverrideForFiles -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Both @@ -875,7 +875,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1.** Stops employees from ignoring the Windows Defender SmartScreen warnings about unverified files. ### PreventUsingLocalHostIPAddressForWebRTC -- **Supported versions:** Windows 10, Version 1511 or later +- **Supported versions:** Windows 10, version 1511 or later - **Supported devices:** Desktop @@ -926,7 +926,7 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U - **1.** Allows you to configure the default search engine for your employees. ### ShowMessageWhenOpeningInteretExplorerSites -- **Supported versions:** Windows 10, Version 1607 and later +- **Supported versions:** Windows 10, version 1607 and later - **Supported devices:** Desktop diff --git a/devices/surface-hub/TOC.md b/devices/surface-hub/TOC.md index f701181fcb..5d807a4e97 100644 --- a/devices/surface-hub/TOC.md +++ b/devices/surface-hub/TOC.md @@ -1,4 +1,6 @@ # [Microsoft Surface Hub](index.md) +## [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md) +## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) ## [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md) ### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md) ### [Create and test a device account](create-and-test-a-device-account-surface-hub.md) @@ -10,7 +12,7 @@ #### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) #### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md) #### [Password management](password-management-for-surface-hub-device-accounts.md) -### [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) +### [Create provisioning packages](provisioning-packages-for-surface-hub.md) ### [Admin group management](admin-group-management-for-surface-hub.md) ## [Set up Microsoft Surface Hub](set-up-your-surface-hub.md) ### [Setup worksheet](setup-worksheet-surface-hub.md) @@ -28,13 +30,12 @@ #### [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md) #### [Wireless network management](wireless-network-management-for-surface-hub.md) ### [Install apps on your Surface Hub](install-apps-on-surface-hub.md) -### [End a Surface Hub meeting with I'm Done](i-am-done-finishing-your-surface-hub-meeting.md) +### [End a Surface Hub meeting with End session](i-am-done-finishing-your-surface-hub-meeting.md) ### [Save your BitLocker key](save-bitlocker-key-surface-hub.md) ### [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) ### [Using a room control system](use-room-control-system-with-surface-hub.md) -## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) -## [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md) -## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) -## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) +## [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) ## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) +## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) +## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) ## [Change history for Surface Hub](change-history-surface-hub.md) \ No newline at end of file diff --git a/devices/surface-hub/accessibility-surface-hub.md b/devices/surface-hub/accessibility-surface-hub.md index 46348c087d..7ea46504e4 100644 --- a/devices/surface-hub/accessibility-surface-hub.md +++ b/devices/surface-hub/accessibility-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.pagetype: surfacehub ms.sitesec: library -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -30,7 +30,7 @@ The full list of accessibility settings are available to IT admins in the **Sett | Mouse | Defaults selected for **Pointer size**, **Pointer color** and **Mouse keys**. | | Other options | Defaults selected for **Visual options** and **Touch feedback**. | -Additionally, these accessibility features and apps are returned to default settings when users press [I'm Done](i-am-done-finishing-your-surface-hub-meeting.md): +Additionally, these accessibility features and apps are returned to default settings when users press [End session](finishing-your-surface-hub-meeting.md): - Narrator - Magnifier - High contrast diff --git a/devices/surface-hub/admin-group-management-for-surface-hub.md b/devices/surface-hub/admin-group-management-for-surface-hub.md index 7607199209..2abc8df009 100644 --- a/devices/surface-hub/admin-group-management-for-surface-hub.md +++ b/devices/surface-hub/admin-group-management-for-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub, security -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md b/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md index 76275e3ec8..b04dd91222 100644 --- a/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md +++ b/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md @@ -1,5 +1,5 @@ --- -title: Appendix PowerShell (Surface Hub) +title: PowerShell for Surface Hub (Surface Hub) description: PowerShell scripts to help set up and manage your Microsoft Surface Hub . ms.assetid: 3EF48F63-8E4C-4D74-ACD5-461F1C653784 keywords: PowerShell, set up Surface Hub, manage Surface Hub @@ -7,14 +7,14 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- -# Appendix: PowerShell (Surface Hub) +# PowerShell for Surface Hub -PowerShell scripts to help set up and manage your Microsoft Surface Hub . +PowerShell scripts to help set up and manage your Microsoft Surface Hub. - [PowerShell scripts for Surface Hub admins](#scripts-for-admins) - [Create an on-premise account](#create-on-premise-ps-scripts) @@ -43,7 +43,8 @@ What do you need in order to run the scripts? - Remote PowerShell access to your organization's domain or tenant, Exchange servers, and Skype for Business servers. - Admin credentials for your organization's domain or tenant, Exchange servers, and Skype for Business servers. ->**Note**  Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub. +>[!NOTE] +>Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.   diff --git a/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md b/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md index f6cad56654..e49731d001 100644 --- a/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md +++ b/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/change-history-surface-hub.md b/devices/surface-hub/change-history-surface-hub.md index 74ee57c2f5..d8d69bb450 100644 --- a/devices/surface-hub/change-history-surface-hub.md +++ b/devices/surface-hub/change-history-surface-hub.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -14,6 +14,10 @@ localizationpriority: medium This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md). +## RELEASE: Windows 10, version 1703 + +The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). + ## February 2017 | New or changed topic | Description | diff --git a/devices/surface-hub/change-surface-hub-device-account.md b/devices/surface-hub/change-surface-hub-device-account.md index 6dc6bf7016..2ad7a30571 100644 --- a/devices/surface-hub/change-surface-hub-device-account.md +++ b/devices/surface-hub/change-surface-hub-device-account.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/create-a-device-account-using-office-365.md b/devices/surface-hub/create-a-device-account-using-office-365.md index 914b6136e6..b6719175f5 100644 --- a/devices/surface-hub/create-a-device-account-using-office-365.md +++ b/devices/surface-hub/create-a-device-account-using-office-365.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md index 9930a748e3..5c6ab373e5 100644 --- a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md +++ b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/device-reset-surface-hub.md b/devices/surface-hub/device-reset-surface-hub.md index f2cb38c5f2..0d070c1ae5 100644 --- a/devices/surface-hub/device-reset-surface-hub.md +++ b/devices/surface-hub/device-reset-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -49,21 +49,49 @@ If you see a blank screen for long periods of time during the **Reset device** p ![Image showing Update & Security group in Settings app for Surface Hub.](images/sh-settings-update-security.png) -3. Click **Recovery**, and then click **Get started**. +3. Click **Recovery**, and then, under **Reset device**, click **Get started**. ![Image showing Reset device option in Settings app for Surface Hub.](images/sh-settings-reset-device.png) -## Reset a Surface Hub from Windows Recovery Environment + +## Recover a Surface Hub from the cloud -On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset the device from [Windows Recovery Environment](https://technet.microsoft.com/library/cc765966.aspx) (Windows RE). +In the Windows Recovery Environment (Windows RE), you can recover your device by downloading a factory build from the cloud and installing it on the Surface Hub. This allows devices in an unusable state to recover without requiring assistance from Microsoft Support. -**To reset a Surface Hub from Windows Recovery Environment** +### Recover a Surface Hub in a bad state + +If the device account gets into an unstable state or the Admin account is running into issues, you can use cloud recovery in **Settings**. You should only use cloud recovery when [reset](#reset-a-surface-hub-from-settings) doesn't fix the problem. + +1. On your Surface Hub, go to **Settings** > **Update & security** > **Recovery**. + +2. Under **Recover from the cloud**, click **Restart now**. + + ![recover from the cloud](images/recover-from-the-cloud.png) + +### Recover a locked Surface Hub + +On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset or recover the device from [Windows RE](https://technet.microsoft.com/library/cc765966.aspx). 1. From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) for help with locating the power switch. -2. The device should automatically boot into Windows RE. Select **Advanced Repair**. -3. Select **Reset**. -4. If prompted, enter your device's BitLocker key. +2. The device should automatically boot into Windows RE. +3. After the Surface Hub enters Windows RE, select **Recover from the cloud**. (Optionally, you can choose **Reset**, however **Recover from the cloud** is the recommended approach.) + >[!NOTE] + >When using **Recover from the cloud**, an ethernet connection is recommended. + + ![Recover from the cloud](images/recover-from-cloud.png) + +4. Enter the Bitlocker key (if prompted). +5. When prompted, select **Reinstall**. + ![Reinstall](images/reinstall.png) + +6. Select **Yes** to repartition the disk. + + ![Repartition](images/repartition.png) + +Reset will begin after the image is downloaded from the cloud. You will see progress indicators. + +![downloading 97&](images/recover-progress.png) ## Related topics diff --git a/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md b/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md index 73557c1f2c..e6d812ea78 100644 --- a/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md +++ b/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md @@ -33,7 +33,7 @@ Surface Hub doesn't have a lock screen or a screen saver, but it has a similar f Surface Hub is designed to be used in communal spaces, such as meeting rooms. Unlike Windows PCs, anyone can walk up and use a Surface Hub without logging on. The system always runs as a local, auto logged-in, low-privilege user. It doesn't support logging in any additional users - including admin users. > [!NOTE] -> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **I'm done**. +> Surface Hub supports signing in to Microsoft Edge and other apps. However, these credentials are deleted when users press **End session**. *Organization policies that this may affect:*
Generally, Surface Hub uses lockdown features rather than user access control to enforce security. Policies related to password requirements, interactive logon, user accounts, and access control don't apply for Surface Hub. @@ -46,7 +46,7 @@ Users have access to a limited set of directories on the Surface Hub: - Pictures - Downloads -Files saved locally in these directories are deleted when users press **I'm done**. To save content created during a meeting, users should save files to a USB drive or to OneDrive. +Files saved locally in these directories are deleted when users press **End session**. To save content created during a meeting, users should save files to a USB drive or to OneDrive. *Organization policies that this may affect:*
Policies related to access permissions and ownership of files and folders don't apply for Surface Hub. Users can't browse and save files to system directories and network folders. diff --git a/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md b/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md index 3e9df023a1..527eaf6198 100644 --- a/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md +++ b/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/finishing-your-surface-hub-meeting.md b/devices/surface-hub/finishing-your-surface-hub-meeting.md new file mode 100644 index 0000000000..8733038060 --- /dev/null +++ b/devices/surface-hub/finishing-your-surface-hub-meeting.md @@ -0,0 +1,92 @@ +--- +title: End session - ending a Surface Hub meeting +description: To end a Surface Hub meeting, tap End session. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting. +keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: surfacehub +author: jdeckerMS +localizationpriority: medium +--- + +# End a Surface Hub meeting with End session +Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states: +- Applications +- Operating system +- User interface + +This topic explains what **End session** resets for each of these states. + +## Applications +When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **End session** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs. + +### Close applications +Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**. + +### Delete browser history +Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **End session** also ensures that application states are cleared and data is removed before the next session, or meeting, starts. + +### Reset applications +**End session** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub. + +### Remove Skype logs +Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **End session** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs. + +## Operating System +The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting. + +### File System +Meeting attendees have access to a limited set of directories on the Surface Hub. When **End session** is selected, Surface Hub clears these directories:
+- Music +- Videos +- Documents +- Pictures +- Downloads + +Surface Hub also clears these directories, since many applications often write to them: +- Desktop +- Favorites +- Recent +- Public Documents +- Public Music +- Public Videos +- Public Downloads + +### Credentials +User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **End session**. + +## User interface +User interface (UI) settings are returned to their default values when **End session** is selected. + +### UI items +- Reset Quick Actions to default state +- Clear Toast notifications +- Reset volume levels +- Reset sidebar width +- Reset tablet mode layout +- Sign user out of Office 365 meetings and files + +### Accessibility +Accessibility features and apps are returned to default settings when **End session** is selected. +- Filter keys +- High contrast +- Sticky keys +- Toggle keys +- Mouse keys +- Magnifier +- Narrator + +### Clipboard +The clipboard is cleared to remove data that was copied to the clipboard during the session. + +## Frequently asked questions +**What happens if I forget to tap End session at the end of a meeting, and someone else uses the Surface Hub later?**
+Surface Hub only cleans up meeting content when users tap **End session**. If you leave the meeting without tapping **End session**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one. You can also disable the ability to resume a session if **End session** is not pressed. + +**Are documents recoverable?**
+Removing files from the hard drive when **End session** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting. + +**Do the clean-up actions from End session comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**
+No. Currently, the clean-up actions from **End session** do not comply with this standard. + diff --git a/devices/surface-hub/first-run-program-surface-hub.md b/devices/surface-hub/first-run-program-surface-hub.md index 6ee36023cc..4e6ceac8b8 100644 --- a/devices/surface-hub/first-run-program-surface-hub.md +++ b/devices/surface-hub/first-run-program-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -43,9 +43,10 @@ Each of these sections also contains information about paths you might take when This is the first screen you'll see when you power up the Surface Hub for the first time. It's where you input localization information for your device. ->**Note**  This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing. +>[!NOTE] +>This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing. -  + Select a language and the initial setup options are displayed. ![Image showing ICD options checklist.](images/setuplocale.png) @@ -326,6 +327,9 @@ This is what happens when you choose an option. - **Use Microsoft Azure Active Directory** Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. After joining, admins from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization. + + >[!IMPORTANT] + >If you join Surface Hub to Azure AD during first-run setup, single sign-on (SSO) for Office apps will not work properly. Users will have to sign in to each Office app individually. - **Use Active Directory Domain Services** @@ -382,7 +386,7 @@ Once the device has been domain joined, you must specify a security group from t The following input is required: - **Domain:** This is the fully qualified domain name (FQDN) of the domain that you want to join. A security group from this domain can be used to manage the device. -- **User name:** The user name of an account that has sufficient permission to join the specified domain. +- **User name:** The user name of an account that has sufficient permission to join the specified domain. This account must be a computer object. - **Password:** The password for the account. After the credentials are verified, you will be asked to type a security group name. This input is required. diff --git a/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md b/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md deleted file mode 100644 index ccf99db112..0000000000 --- a/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: I am done - ending a Surface Hub meeting -description: To end a Surface Hub meeting, tap I am Done. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting. -keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -ms.pagetype: surfacehub -author: TrudyHa -localizationpriority: medium ---- - -# End a Surface Hub meeting with I'm Done -Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **I'm Done** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states: -- Applications -- Operating system -- User interface - -This topic explains what **I'm Done** resets for each of these states. - -## Applications -When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **I'm done** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs. - -### Close applications -Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**. - -### Delete browser history -Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **I'm Done** also ensures that application states are cleared and data is removed before the next session, or meeting, starts. - -### Reset applications -**I'm Done** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub. - -### Remove Skype logs -Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **I'm Done** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs. - -## Operating System -The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting. - -### File System -Meeting attendees have access to a limited set of directories on the Surface Hub. When **I'm Done** is selected, Surface Hub clears these directories:
-- Music -- Videos -- Documents -- Pictures -- Downloads - -Surface Hub also clears these directories, since many applications often write to them: -- Desktop -- Favorites -- Recent -- Public Documents -- Public Music -- Public Videos -- Public Downloads - -### Credentials -User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **I’m done**. - -## User interface -User interface (UI) settings are returned to their default values when **I'm Done** is selected. - -### UI items -- Reset Quick Actions to default state -- Clear Toast notifications -- Reset volume levels -- Reset sidebar width -- Reset tablet mode layout - -### Accessibility -Accessibility features and apps are returned to default settings when **I'm Done** is selected. -- Filter keys -- High contrast -- Sticky keys -- Toggle keys -- Mouse keys -- Magnifier -- Narrator - -### Clipboard -The clipboard is cleared to remove data that was copied to the clipboard during the session. - -## Frequently asked questions -**What happens if I forget to tap I'm Done at the end of a meeting, and someone else uses the Surface Hub later?**
-Surface Hub only cleans up meeting content when users tap **I'm Done**. If you leave the meeting without tapping **I'm Done**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one. - -**Are documents recoverable?**
-Removing files from the hard drive when **I'm Done** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting. - -**Do the clean-up actions from I'm Done comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**
-No. Currently, the clean-up actions from **I'm Done** do not comply with this standard. - diff --git a/devices/surface-hub/images/OOBE-2.jpg b/devices/surface-hub/images/OOBE-2.jpg new file mode 100644 index 0000000000..0c615a2ec4 Binary files /dev/null and b/devices/surface-hub/images/OOBE-2.jpg differ diff --git a/devices/surface-hub/images/account-management-details.PNG b/devices/surface-hub/images/account-management-details.PNG new file mode 100644 index 0000000000..66712394ec Binary files /dev/null and b/devices/surface-hub/images/account-management-details.PNG differ diff --git a/devices/surface-hub/images/account-management.PNG b/devices/surface-hub/images/account-management.PNG new file mode 100644 index 0000000000..34165dfcd6 Binary files /dev/null and b/devices/surface-hub/images/account-management.PNG differ diff --git a/devices/surface-hub/images/add-applications-details.PNG b/devices/surface-hub/images/add-applications-details.PNG new file mode 100644 index 0000000000..2efd3483ae Binary files /dev/null and b/devices/surface-hub/images/add-applications-details.PNG differ diff --git a/devices/surface-hub/images/add-applications.PNG b/devices/surface-hub/images/add-applications.PNG new file mode 100644 index 0000000000..2316deb2fd Binary files /dev/null and b/devices/surface-hub/images/add-applications.PNG differ diff --git a/devices/surface-hub/images/add-certificates-details.PNG b/devices/surface-hub/images/add-certificates-details.PNG new file mode 100644 index 0000000000..78cd783282 Binary files /dev/null and b/devices/surface-hub/images/add-certificates-details.PNG differ diff --git a/devices/surface-hub/images/add-certificates.PNG b/devices/surface-hub/images/add-certificates.PNG new file mode 100644 index 0000000000..24cb605d1c Binary files /dev/null and b/devices/surface-hub/images/add-certificates.PNG differ diff --git a/devices/surface-hub/images/add-config-file-details.PNG b/devices/surface-hub/images/add-config-file-details.PNG new file mode 100644 index 0000000000..c7b4db97e6 Binary files /dev/null and b/devices/surface-hub/images/add-config-file-details.PNG differ diff --git a/devices/surface-hub/images/add-config-file.PNG b/devices/surface-hub/images/add-config-file.PNG new file mode 100644 index 0000000000..5b779509d9 Binary files /dev/null and b/devices/surface-hub/images/add-config-file.PNG differ diff --git a/devices/surface-hub/images/apps.png b/devices/surface-hub/images/apps.png new file mode 100644 index 0000000000..5cb3b7ec8f Binary files /dev/null and b/devices/surface-hub/images/apps.png differ diff --git a/devices/surface-hub/images/developer-setup.PNG b/devices/surface-hub/images/developer-setup.PNG new file mode 100644 index 0000000000..8c93d5ed91 Binary files /dev/null and b/devices/surface-hub/images/developer-setup.PNG differ diff --git a/devices/surface-hub/images/enroll-mdm-details.PNG b/devices/surface-hub/images/enroll-mdm-details.PNG new file mode 100644 index 0000000000..f3a7fea8da Binary files /dev/null and b/devices/surface-hub/images/enroll-mdm-details.PNG differ diff --git a/devices/surface-hub/images/enroll-mdm.PNG b/devices/surface-hub/images/enroll-mdm.PNG new file mode 100644 index 0000000000..b7cfdbc767 Binary files /dev/null and b/devices/surface-hub/images/enroll-mdm.PNG differ diff --git a/devices/surface-hub/images/finish-details.png b/devices/surface-hub/images/finish-details.png new file mode 100644 index 0000000000..727efac696 Binary files /dev/null and b/devices/surface-hub/images/finish-details.png differ diff --git a/devices/surface-hub/images/finish.PNG b/devices/surface-hub/images/finish.PNG new file mode 100644 index 0000000000..7c65da1799 Binary files /dev/null and b/devices/surface-hub/images/finish.PNG differ diff --git a/devices/surface-hub/images/five.png b/devices/surface-hub/images/five.png new file mode 100644 index 0000000000..961f0e15b7 Binary files /dev/null and b/devices/surface-hub/images/five.png differ diff --git a/devices/surface-hub/images/four.png b/devices/surface-hub/images/four.png new file mode 100644 index 0000000000..0fef213b37 Binary files /dev/null and b/devices/surface-hub/images/four.png differ diff --git a/devices/surface-hub/images/icd-simple-edit.png b/devices/surface-hub/images/icd-simple-edit.png new file mode 100644 index 0000000000..aea2e24c8a Binary files /dev/null and b/devices/surface-hub/images/icd-simple-edit.png differ diff --git a/devices/surface-hub/images/one.png b/devices/surface-hub/images/one.png new file mode 100644 index 0000000000..42b4742c49 Binary files /dev/null and b/devices/surface-hub/images/one.png differ diff --git a/devices/surface-hub/images/ppkg-config.png b/devices/surface-hub/images/ppkg-config.png new file mode 100644 index 0000000000..10a2b7de58 Binary files /dev/null and b/devices/surface-hub/images/ppkg-config.png differ diff --git a/devices/surface-hub/images/ppkg-csv.png b/devices/surface-hub/images/ppkg-csv.png new file mode 100644 index 0000000000..0648f555e1 Binary files /dev/null and b/devices/surface-hub/images/ppkg-csv.png differ diff --git a/devices/surface-hub/images/proxy-details.PNG b/devices/surface-hub/images/proxy-details.PNG new file mode 100644 index 0000000000..fcc7b06a41 Binary files /dev/null and b/devices/surface-hub/images/proxy-details.PNG differ diff --git a/devices/surface-hub/images/proxy.PNG b/devices/surface-hub/images/proxy.PNG new file mode 100644 index 0000000000..cdfc02c454 Binary files /dev/null and b/devices/surface-hub/images/proxy.PNG differ diff --git a/devices/surface-hub/images/recover-from-cloud.png b/devices/surface-hub/images/recover-from-cloud.png new file mode 100644 index 0000000000..7d409edc5f Binary files /dev/null and b/devices/surface-hub/images/recover-from-cloud.png differ diff --git a/devices/surface-hub/images/recover-from-the-cloud.png b/devices/surface-hub/images/recover-from-the-cloud.png new file mode 100644 index 0000000000..07c1e22851 Binary files /dev/null and b/devices/surface-hub/images/recover-from-the-cloud.png differ diff --git a/devices/surface-hub/images/recover-progress.png b/devices/surface-hub/images/recover-progress.png new file mode 100644 index 0000000000..316d830a57 Binary files /dev/null and b/devices/surface-hub/images/recover-progress.png differ diff --git a/devices/surface-hub/images/reinstall.png b/devices/surface-hub/images/reinstall.png new file mode 100644 index 0000000000..2f307841aa Binary files /dev/null and b/devices/surface-hub/images/reinstall.png differ diff --git a/devices/surface-hub/images/repartition.png b/devices/surface-hub/images/repartition.png new file mode 100644 index 0000000000..26725a8c54 Binary files /dev/null and b/devices/surface-hub/images/repartition.png differ diff --git a/devices/surface-hub/images/set-up-device-admins-details.PNG b/devices/surface-hub/images/set-up-device-admins-details.PNG new file mode 100644 index 0000000000..42c04b4b3b Binary files /dev/null and b/devices/surface-hub/images/set-up-device-admins-details.PNG differ diff --git a/devices/surface-hub/images/set-up-device-admins.PNG b/devices/surface-hub/images/set-up-device-admins.PNG new file mode 100644 index 0000000000..e0e037903c Binary files /dev/null and b/devices/surface-hub/images/set-up-device-admins.PNG differ diff --git a/devices/surface-hub/images/set-up-device-details.PNG b/devices/surface-hub/images/set-up-device-details.PNG new file mode 100644 index 0000000000..be565ac8d9 Binary files /dev/null and b/devices/surface-hub/images/set-up-device-details.PNG differ diff --git a/devices/surface-hub/images/set-up-device.PNG b/devices/surface-hub/images/set-up-device.PNG new file mode 100644 index 0000000000..0c9eb0e3ff Binary files /dev/null and b/devices/surface-hub/images/set-up-device.PNG differ diff --git a/devices/surface-hub/images/set-up-network-details.PNG b/devices/surface-hub/images/set-up-network-details.PNG new file mode 100644 index 0000000000..7e1391326c Binary files /dev/null and b/devices/surface-hub/images/set-up-network-details.PNG differ diff --git a/devices/surface-hub/images/set-up-network.PNG b/devices/surface-hub/images/set-up-network.PNG new file mode 100644 index 0000000000..a0e856c103 Binary files /dev/null and b/devices/surface-hub/images/set-up-network.PNG differ diff --git a/devices/surface-hub/images/sh-quick-action.png b/devices/surface-hub/images/sh-quick-action.png index cb072a9793..3003e464b3 100644 Binary files a/devices/surface-hub/images/sh-quick-action.png and b/devices/surface-hub/images/sh-quick-action.png differ diff --git a/devices/surface-hub/images/sh-settings-reset-device.png b/devices/surface-hub/images/sh-settings-reset-device.png index b3e35bb385..f3a9a6dc5c 100644 Binary files a/devices/surface-hub/images/sh-settings-reset-device.png and b/devices/surface-hub/images/sh-settings-reset-device.png differ diff --git a/devices/surface-hub/images/sh-settings-update-security.png b/devices/surface-hub/images/sh-settings-update-security.png index a10d4ffb51..59212d1805 100644 Binary files a/devices/surface-hub/images/sh-settings-update-security.png and b/devices/surface-hub/images/sh-settings-update-security.png differ diff --git a/devices/surface-hub/images/sh-settings.png b/devices/surface-hub/images/sh-settings.png index 03125b3419..0134fda740 100644 Binary files a/devices/surface-hub/images/sh-settings.png and b/devices/surface-hub/images/sh-settings.png differ diff --git a/devices/surface-hub/images/six.png b/devices/surface-hub/images/six.png new file mode 100644 index 0000000000..2816328ec3 Binary files /dev/null and b/devices/surface-hub/images/six.png differ diff --git a/devices/surface-hub/images/surfacehub.png b/devices/surface-hub/images/surfacehub.png new file mode 100644 index 0000000000..1b9b484ab8 Binary files /dev/null and b/devices/surface-hub/images/surfacehub.png differ diff --git a/devices/surface-hub/images/three.png b/devices/surface-hub/images/three.png new file mode 100644 index 0000000000..887fa270d7 Binary files /dev/null and b/devices/surface-hub/images/three.png differ diff --git a/devices/surface-hub/images/two.png b/devices/surface-hub/images/two.png new file mode 100644 index 0000000000..b8c2d52eaf Binary files /dev/null and b/devices/surface-hub/images/two.png differ diff --git a/devices/surface-hub/index.md b/devices/surface-hub/index.md index 22e94d2746..dabf0f1f6e 100644 --- a/devices/surface-hub/index.md +++ b/devices/surface-hub/index.md @@ -12,19 +12,36 @@ localizationpriority: medium # Microsoft Surface Hub +>[Looking for the user's guide for Surface Hub?](http://download.microsoft.com/download/3/6/B/36B6331E-0C63-4E71-A05D-EE88D05081F8/surface-hub-user-guide-en-us.pdf) + +
Microsoft Surface Hub is an all-in-one productivity device that is intended for brainstorming, collaboration, and presentations. In order to get the maximum benefit from Surface Hub, your organization’s infrastructure and the Surface Hub itself must be properly set up and integrated. The documentation in this library describes what needs to be done both before and during setup in order to help you optimize your use of the device.![image of a Surface Hub](images/surfacehub.png)
+  + +## Surface Hub setup process + +In some ways, adding your new Surface Hub is just like adding any other Microsoft Windows-based device to your network. However, in order to get your Surface Hub up and running at its full capacity, there are some very specific requirements. Here are the next topics you'll need: + +1. [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) +2. [Gather the information listed in the Setup worksheet](setup-worksheet-surface-hub.md) +2. [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md) +3. [Run the Surface Hub first-run setup program (OOBE)](first-run-program-surface-hub.md) -Documents related to deploying and managing the Microsoft Surface Hub in your organization. ->[Looking for the user's guide for Surface Hub?](https://www.microsoft.com/surface/support/surface-hub) ## In this section | Topic | Description | | --- | --- | -| [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md) | This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.| +| [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md) | Discover the changes and improvements for Microsoft Surface Hub in the Windows 10, version 1703 release (also known as Creators Update). | | [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | This topic explains the differences between the operating system on Surface Hub and Windows 10 Enterprise. | -| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. | +| [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md) | This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Surface Hub. See [Intro to Surface Hub](intro-to-surface-hub.md) for a description of how the device and its features interact with your IT environment. | +| [Set up Microsoft Surface Hub](set-up-your-surface-hub.md) | Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program. | +| [Manage Microsoft Surface Hub](manage-surface-hub.md) | How to manage your Surface Hub after finishing the first-run program. | +| [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) | +| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. | PowerShell scripts to help set up and manage your Surface Hub. | +| [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) | Troubleshoot common problems, including setup issues, Exchange ActiveSync errors. | | [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide. | -| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation. | +| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation library. | + diff --git a/devices/surface-hub/install-apps-on-surface-hub.md b/devices/surface-hub/install-apps-on-surface-hub.md index d26712627a..dea976e29f 100644 --- a/devices/surface-hub/install-apps-on-surface-hub.md +++ b/devices/surface-hub/install-apps-on-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub, store -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/local-management-surface-hub-settings.md b/devices/surface-hub/local-management-surface-hub-settings.md index dea2a514bd..7d17d33c38 100644 --- a/devices/surface-hub/local-management-surface-hub-settings.md +++ b/devices/surface-hub/local-management-surface-hub-settings.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -16,29 +16,38 @@ After initial setup of Microsoft Surface Hub, the device’s settings can be loc ## Surface Hub settings -Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only cofigurable on Surface Hubs. +Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only configurable on Surface Hubs. | Setting | Location | Description | | ------- | -------- | ----------- | -| Device account | This device > Accounts | Set or change the Surface Hub's device account. | -| Device account sync status | This device > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. | -| Password rotation | This device > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. | -| Change admin account password | This device > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. | -| Configure Operations Management Suite (OMS) | This device > Device management | Set up monitoring for your Surface Hub using OMS. | -| Open the Windows Store app | This device > Apps & features | The Windows Store app is only available to admins through the Settings app. | -| Skype for Business domain name | This device > Calling | Configure a domain name for your Skype for Business server. | -| Default microphone and speaker settings | This device > Calling | Configure a default microphone and speaker for calls, and a default speaker for media playback. | -| Turn off wireless projection using Miracast | This device > Wireless projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. | -| Require a PIN for wireless projection | This device > Wireless projection | Choose whether people are required to enter a PIN before they use wireless projection. | -| Wireless projection (Miracast) channel | This device > Wireless projection | Set the channel for Miracast projection. | -| Meeting info shown on the welcome screen | This device > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. | -| Welcome screen background | This device > Welcome screen | Choose a background image for the welcome screen. | -| Turn on screen with motion sensors | This device > Session & clean up | Choose whether the screen turns on when motion is detected. | -| Session time out | This device > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. | -| Sleep time out | This device > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. | -| Friendly name | This device > About | Set the Surface Hub name that people will see when connecting wirelessly. | +| Device account | Surface Hub > Accounts | Set or change the Surface Hub's device account. | +| Device account sync status | Surface Hub > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. | +| Password rotation | Surface Hub > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password. | +| Change admin account password | Surface Hub > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. | +| Device Management | Surface Hub > Device management | Manage policies and business applications using mobile device management (MDM). | +| Provisioning packages | Surface Hub > Device management | Set or change provisioning packages installed on the Surface Hub. | +| Configure Operations Management Suite (OMS) | Surface Hub > Device management | Set up monitoring for your Surface Hub using OMS. | +| Open the Windows Store app | Surface Hub > Apps & features | The Windows Store app is only available to admins through the Settings app. | +| Skype for Business domain name | Surface Hub > Calling & Audio | Configure a domain name for your Skype for Business server. | +| Default Speaker volume | Surface Hub > Calling & Audio | Configure the default speaker volume for the Surface Hub when it starts a session. | +| Default microphone and speaker settings | Surface Hub > Calling & Audio | Configure a default microphone and speaker for calls, and a default speaker for media playback. | +| Enable Dolby Audio X2 | Surface Hub > Calling & Audio | Configure the Dolby Audio X2 speaker enhancements. | +| Open Connect App automatically | Surface Hub > Projection | Choose whether projection will automatically open the Connect app or wait for user input before opening. | +| Turn off wireless projection using Miracast | Surface Hub > Projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. | +| Require a PIN for wireless projection | Surface Hub > Projection | Choose whether people are required to enter a PIN before they use wireless projection. | +| Wireless projection (Miracast) channel | Surface Hub > Projection | Set the channel for Miracast projection. | +| Meeting info shown on the welcome screen | Surface Hub > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. | +| Welcome screen background | Surface Hub > Welcome screen | Choose a background image for the welcome screen. | +| Idle timeout to Welcome screen | Surface Hub > Session & Power | Choose how long until the Surface Hub returns to the welcome screen after no motion is detected. | +| Resume session | Surface Hub > Session & Power | Choose to allow users to resume a session after no motion is detected or to automatically clean up a session. | +| Access to Office 365 meetings and files | Surface Hub > Session & Power | Choose whether a user can sign in to Office 365 to get access to their meetings and files. | +| Turn on screen with motion sensors | Surface Hub > Session & clean up | Choose whether the screen turns on when motion is detected. | +| Session time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. | +| Sleep time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. | +| Friendly name | Surface Hub > About | Set the Surface Hub name that people will see when connecting wirelessly. | | Maintenance hours | Update & security > Windows Update > Advanced options | Configure when updates can be installed. | | Configure Windows Server Update Services (WSUS) server | Update & security > Windows Update > Advanced options | Change whether Surface Hub receives updates from a WSUS server instead of Windows Update. | +| Recover from the cloud | Update & security > Recovery | Reinstall the operating system on Surface Hub to a manufacturer build from the cloud. | | Save BitLocker key | Update & security > Recovery | Backup your Surface Hub's BitLocker key to a USB drive. | | Collect logs | Update & security > Recovery | Save logs to a USB drive to send to Microsoft later. | diff --git a/devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md b/devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md deleted file mode 100644 index db9230f9ad..0000000000 --- a/devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Manage settings with a local admin account (Surface Hub) -description: A local admin account will be set up on every Microsoft Surface Hub as part of the first run program. The only way to change the local admin options that you chose at that time is to reset the device. -ms.assetid: B4B3668B-985D-427E-8495-E30ABEECA679 -redirect_url: https://technet.microsoft.com/itpro/surface-hub/admin-group-management-for-surface-hub -keywords: local admin account, Surface Hub, change local admin options -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -ms.pagetype: surfacehub -author: TrudyHa -localizationpriority: medium ---- diff --git a/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md b/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md index 8cadcb7309..c1913c01cc 100644 --- a/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md +++ b/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md @@ -69,9 +69,19 @@ For more information, see [SurfaceHub configuration service provider](https://ms | Connect to your Operations Management Suite workspace | MOMAgent/WorkspaceID
MOMAgent/WorkspaceKey | Yes | Yes.
[Use a custom setting.](#example-sccm) | Yes | | Welcome screen background image | InBoxApps/Welcome/CurrentBackgroundPath | Yes | Yes.
[Use a custom setting.](#example-sccm) | Yes | | Meeting information displayed on the welcome screen | InBoxApps/Welcome/MeetingInfoOption | Yes | Yes.
[Use a custom setting.](#example-sccm) | Yes | -| Friendly name for wireless projection | Properties/FriendlyName | Yes.
[Use a custom policy.](#example-intune)) | Yes.
[Use a custom setting.](#example-sccm) | Yes | +| Friendly name for wireless projection | Properties/FriendlyName | Yes
[Use a custom policy.](#example-intune)) | Yes.
[Use a custom setting.](#example-sccm) | Yes | | Device account, including password rotation | DeviceAccount/*``*
See [SurfaceHub CSP](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). | No | No | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +| Specify Skype domain | InBoxApps/SkypeForBusiness/DomainName | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Auto launch Connect App when projection is initiated | InBoxApps/Connect/AutoLaunch | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Set default volume | Properties/DefaultVolume | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Set screen timeout | Properties/ScreenTimeout | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Set session timeout | Properties/SessionTimeout | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Set sleep timeout | Properties/SleepTimeout | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Allow session to resume after screen is idle | Properties/AllowSessionResume | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Allow device account to be used for proxy authentication | Properties/AllowAutoProxyAuth | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Disable auto-populating the sign-in dialog with invitees from scheduled meetings | Properties/DisableSignInSuggestions | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +| Disable "My meetings and files" feature in Start menu | Properties/DoNotShowMyMeetingsAndFiles | Yes
[Use a custom policy.](#example-intune)) | Yes
[Use a custom setting.] Yes | +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. ### Supported Windows 10 settings @@ -87,7 +97,7 @@ The following tables include info on Windows 10 settings that have been validate | Allow camera | Keep this enabled for Skype for Business. | [Camera/AllowCamera](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Camera_AllowCamera) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Allow location | Keep this enabled to support apps such as Maps. | [System/AllowLocation](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowLocation) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Allow telemetry | Keep this enabled to help Microsoft improve Surface Hub. | [System/AllowTelemetry](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowTelemetry) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Browser settings @@ -102,7 +112,7 @@ The following tables include info on Windows 10 settings that have been validate | Allow SmartScreen | Keep this enabled to turn on SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Prevent ignoring SmartScreen Filter warnings for websites | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Prevent ignoring SmartScreen Filter warnings for files | For extra security, use to stop users from ignoring SmartScreen Filter warnings and block them from downloading unverified files from Microsoft Edge. | [Browser/PreventSmartScreenPromptOverrideForFiles](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverrideForFiles) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Windows Update settings @@ -115,7 +125,7 @@ The following tables include info on Windows 10 settings that have been validate | Pause quality updates | See above. | [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes| | Configure device to use WSUS| Use to connect your Surface Hub to WSUS instead of Windows Update – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Delivery optimization | Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Configure Delivery Optimization for Windows 10](https://technet.microsoft.com/itpro/windows/manage/waas-delivery-optimization) for details. | DeliveryOptimization/*``*
See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Windows Defender settings @@ -123,7 +133,7 @@ The following tables include info on Windows 10 settings that have been validate | ----------- | ---------------- | ------------- |-------------------------- | ---------------------------------------- | ------------------------- | | Defender policies | Use to configure various Defender settings, including a scheduled scan time. | Defender/*``*
See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Defender status | Use to initiate a Defender scan, force a signature update, query any threats detected. | [Defender CSP](https://msdn.microsoft.com/library/windows/hardware/mt187856.aspx) | No. | No. | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Remote reboot @@ -132,7 +142,7 @@ The following tables include info on Windows 10 settings that have been validate | Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow
See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | No | No | Yes | | Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single
See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | | Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent
See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes.
Use a custom policy. | Yes.
Use a custom setting. | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Install certificates @@ -142,7 +152,7 @@ The following tables include info on Windows 10 settings that have been validate -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. #### Collect logs @@ -151,7 +161,7 @@ The following tables include info on Windows 10 settings that have been validate | Collect ETW logs | Use to remotely collect ETW logs from Surface Hub. | [DiagnosticLog CSP](https://msdn.microsoft.com/library/windows/hardware/mt219118.aspx) | No | No | Yes | -\*Settings supported with SyncML can also be configured in a Windows Imaging and Configuration Designer (Windows ICD) provisioning package. +\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package. ### Generate OMA URIs for settings You need to use a setting’s OMA URI to create a custom policy in Intune, or a custom setting in System Center Configuration Manager. @@ -252,7 +262,7 @@ For more information, see [Create configuration items for Windows 8.1 and Window [Manage Microsoft Surface Hub](manage-surface-hub.md) -[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md) +   diff --git a/devices/surface-hub/manage-surface-hub-settings.md b/devices/surface-hub/manage-surface-hub-settings.md index 5413d28a30..ecfbb7c584 100644 --- a/devices/surface-hub/manage-surface-hub-settings.md +++ b/devices/surface-hub/manage-surface-hub-settings.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/manage-surface-hub.md b/devices/surface-hub/manage-surface-hub.md index b464c430f2..95b3b394bd 100644 --- a/devices/surface-hub/manage-surface-hub.md +++ b/devices/surface-hub/manage-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -30,7 +30,7 @@ Learn about managing and updating Surface Hub. | [Remote Surface Hub management](remote-surface-hub-management.md) |Topics related to managing your Surface Hub remotely. Include install apps, managing settings with MDM and monitoring with Operations Management Suite. | | [Manage Surface Hub settings](manage-surface-hub-settings.md) |Topics related to managing Surface Hub settings: accessibility, device account, device reset, fully qualified domain name, Windows Update settings, and wireless network | | [Install apps on your Surface Hub]( https://technet.microsoft.com/itpro/surface-hub/install-apps-on-surface-hub) | Admins can install apps can from either the Windows Store or the Windows Store for Business.| -| [End a meeting with I’m done](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap I'm Done to clean up any sensitive data and prepare the device for the next meeting.| +| [End a meeting with End session](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting.| | [Save your BitLocker key](https://technet.microsoft.com/itpro/surface-hub/save-bitlocker-key-surface-hub) | Every Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.| | [Connect other devices and display with Surface Hub](https://technet.microsoft.com/itpro/surface-hub/connect-and-display-with-surface-hub) | You can connect other device to your Surface Hub to display content.| | [Using a room control system]( https://technet.microsoft.com/itpro/surface-hub/use-room-control-system-with-surface-hub) | Room control systems can be used with your Microsoft Surface Hub.| diff --git a/devices/surface-hub/manage-windows-updates-for-surface-hub.md b/devices/surface-hub/manage-windows-updates-for-surface-hub.md index 659e2a6ae5..f54bd79038 100644 --- a/devices/surface-hub/manage-windows-updates-for-surface-hub.md +++ b/devices/surface-hub/manage-windows-updates-for-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/monitor-surface-hub.md b/devices/surface-hub/monitor-surface-hub.md index 4b96956704..27f722e175 100644 --- a/devices/surface-hub/monitor-surface-hub.md +++ b/devices/surface-hub/monitor-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md b/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md index 8914899056..7a4a8ed551 100644 --- a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md +++ b/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/online-deployment-surface-hub-device-accounts.md b/devices/surface-hub/online-deployment-surface-hub-device-accounts.md index 6510d41971..0c25519753 100644 --- a/devices/surface-hub/online-deployment-surface-hub-device-accounts.md +++ b/devices/surface-hub/online-deployment-surface-hub-device-accounts.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/password-management-for-surface-hub-device-accounts.md b/devices/surface-hub/password-management-for-surface-hub-device-accounts.md index c6c3db5d36..851ae60a58 100644 --- a/devices/surface-hub/password-management-for-surface-hub-device-accounts.md +++ b/devices/surface-hub/password-management-for-surface-hub-device-accounts.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub, security -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/physically-install-your-surface-hub-device.md b/devices/surface-hub/physically-install-your-surface-hub-device.md index 489e6a03a3..3ea7a56b63 100644 --- a/devices/surface-hub/physically-install-your-surface-hub-device.md +++ b/devices/surface-hub/physically-install-your-surface-hub-device.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub, readiness -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/prepare-your-environment-for-surface-hub.md b/devices/surface-hub/prepare-your-environment-for-surface-hub.md index f5c342d43d..e11e0e6e42 100644 --- a/devices/surface-hub/prepare-your-environment-for-surface-hub.md +++ b/devices/surface-hub/prepare-your-environment-for-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: plan ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -27,11 +27,12 @@ Review these dependencies to make sure Surface Hub features will work in your IT | Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.

If screen sharing on a Surface Hub fails and the error message **An error occurred during the screen presentation** is displayed, see [Video Based Screen Sharing not working on Surface Hub](https://support.microsoft.com/help/3179272/video-based-screen-sharing-not-working-on-surface-hub) for help. | | Mobile device management (MDM) solution (Microsoft Intune, System Center Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. | | Microsoft Operations Managmement Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. | -| Network and Internet access |

In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred.

**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.

**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. | +| Network and Internet access |

In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1x Authentication is supported for both wired and wireless connections.

**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.

**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. | Additionally, note that Surface Hub requires the following open ports: - HTTPS: 443 - HTTP: 80 +- NTP: 123 Depending on your environment, access to additional ports may be needed: - For online environments, see [Office 365 IP URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US). @@ -49,7 +50,7 @@ Surface Hub interacts with a few different products and services. Depending on t ## Create and verify device account -A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, and send email. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details. +A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, send email, and (optionally) to authenticate to Exchange. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details. After you've created your device account, there are a couple of ways to verify that it's setup correctly. - Run Surface Hub device account validation PowerShell scripts. For more information, see [Surface Hub device account scripts](https://gallery.technet.microsoft.com/scriptcenter/Surface-Hub-device-account-6db77696) in Script Center, or [PowerShell scripts for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) later in this guide. diff --git a/devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md b/devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md deleted file mode 100644 index 73dd21ac2e..0000000000 --- a/devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -title: Create provisioning packages (Surface Hub) -description: For Windows 10, settings that use the registry or a content services platform (CSP) can be configured using provisioning packages. You can also add certificates during first run using provisioning. -ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345 -keywords: add certificate, provisioning package -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: surfacehub -author: TrudyHa -localizationpriority: medium ---- - -# Create provisioning packages (Surface Hub) - -This topic explains how to create a provisioning package using the Windows Imaging and Configuration Designer (ICD), and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings. - -You can apply a provisioning package using a USB during first run, or through the **Settings** app. - - -## Advantages -- Quickly configure devices without using a MDM provider. - -- No network connectivity required. - -- Simple to apply. - -[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/whats-new/new-provisioning-packages) - - -## Requirements - -To create and apply a provisioning package to a Surface Hub, you'll need the following: - -- Windows Imaging and Configuration Designer (ICD), which is installed as a part of the [Windows 10 Assessment and Deployment Kit (ADK)](http://go.microsoft.com/fwlink/p/?LinkId=526740). -- A PC running Windows 10. -- A USB flash drive. -- If you apply the package using the **Settings** app, you'll need device admin credentials. - -You'll create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub. - - -## Supported items for Surface Hub provisioning packages - -Currently, you can add these items to provisioning packages for Surface Hub: -- **Certificates** - You can add certificates, if needed, to authenticate to Microsoft Exchange. -- **Universal Windows Platform (UWP) apps** - You can install UWP apps. This can be an offline-licensed app from the Windows Store for Business, or an app created by an in-house dev. -- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD. -- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). - - -## Create the provisioning package - -Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a provisioning package. When you install the ADK, you can choose to install only the Imaging and Configuration Designer (ICD). [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740) - -1. Open Windows ICD (by default, `%windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe`). - -2. Click **Advanced provisioning**. - - ![ICD start options](images/ICDstart-option.PNG) - -3. Name your project and click **Next**. - -4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**. - - ![ICD new project](images/icd-new-project.png) - -5. In the project, under **Available customizations**, select **Common Team edition settings**. - - ![ICD common settings](images/icd-common-settings.png) - - -### Add a certificate to your package -You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange. - -> [!NOTE] -> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details. - -1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**. - -2. Enter a **CertificateName** and then click **Add**. - -2. Enter the **CertificatePassword**. - -3. For **CertificatePath**, browse and select the certificate. - -4. Set **ExportCertificate** to **False**. - -5. For **KeyLocation**, select **Software only**. - - -### Add a Universal Windows Platform (UWP) app to your package -Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business. - -1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**. - -2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \...\ tags. - -3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle). - -4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies. - -If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package. - -1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license". - -2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**. - -3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \ tag, use the value in the **LicenseID** attribute. - -4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1. - - -### Add a policy to your package -Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD. - -1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**. - -2. Select one of the available policy areas. - -3. Select and set the policy you want to add to your provisioning package. - - -### Add Surface Hub settings to your package - -You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package. - -1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**. - -2. Select one of the available setting areas. - -3. Select and set the setting you want to add to your provisioning package. - - -## Build your package - -1. When you are done configuring the provisioning package, on the **File** menu, click **Save**. - -2. Read the warning that project files may contain sensitive information, and click **OK**. - - > [!IMPORTANT] - > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed. - -3. On the **Export** menu, click **Provisioning package**. - -4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources. - -5. Set a value for **Package Version**, and then select **Next.** - - > [!TIP] - > You can make changes to existing packages and change the version number to update previously applied packages. - -6. Optional: You can choose to encrypt the package and enable package signing. - - - **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen. - - - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package. - - > [!IMPORTANT] - > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.  - -7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.

-Optionally, you can click **Browse** to change the default output location. - -8. Click **Next**. - -9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.

-If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**. - -10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.

-If your build is successful, the name of the provisioning package, output directory, and project directory will be shown. - - - If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build. - - - If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**. - -11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive. - - -## Apply a provisioning package to Surface Hub - -There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings). - - -### Apply a provisioning package during first run - -> [!IMPORTANT] -> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings. - -1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding. - -2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**. - - ![Set up device?](images/provisioningpackageoobe-01.png) - -3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**. - - ![Provision this device](images/provisioningpackageoobe-02.png) - -4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run. - - ![Choose a package](images/provisioningpackageoobe-03.png) - -5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**. The package will be applied, and you'll be taken to the next page in the first-run program. - - ![Do you trust this package?](images/provisioningpackageoobe-04.png) - - -### Apply a package using Settings - -1. Insert the USB flash drive containing the .ppkg file into the Surface Hub. - -2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted. - -3. Navigate to **This device** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**. - -4. Select **Add a package**. - -5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted. - -6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**. diff --git a/devices/surface-hub/provisioning-packages-for-surface-hub.md b/devices/surface-hub/provisioning-packages-for-surface-hub.md new file mode 100644 index 0000000000..0d3604f6ad --- /dev/null +++ b/devices/surface-hub/provisioning-packages-for-surface-hub.md @@ -0,0 +1,319 @@ +--- +title: Create provisioning packages (Surface Hub) +description: For Windows 10, settings that use the registry or a configuration service provider (CSP) can be configured using provisioning packages. +ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345 +keywords: add certificate, provisioning package +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: surfacehub +author: jdeckerMS +localizationpriority: medium +--- + +# Create provisioning packages (Surface Hub) + +This topic explains how to create a provisioning package using the Windows Configuration Designer, and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings. + +You can apply a provisioning package using a USB stick during first-run setup, or through the **Settings** app. + + +## Advantages +- Quickly configure devices without using a mobile device management (MDM) provider. + +- No network connectivity required. + +- Simple to apply. + +[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/configure/provisioning-packages) + + +## Requirements + +To create and apply a provisioning package to a Surface Hub, you'll need the following: + +- Windows Configuration Designer, which can be installed from Windows Store or from the Windows 10 Assessment and Deployment Kit (ADK). [Learn how to install Windows Configuration Designer.](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd) +- A USB stick. +- If you apply the package using the **Settings** app, you'll need device admin credentials. + +You create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub. + + +## Supported items for Surface Hub provisioning packages + +Using the **Provision Surface Hub devices** wizard, you can: + +- Enroll in Active Directory, Azure Active Directory, or MDM +- Create an device administrator account +- Add applications and certificates +- Configure proxy settings +- Add a Surface Hub configuration file + +>[!WARNING] +>You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using the wizard. + +Using the advanced provisioning editor, you can add these items to provisioning packages for Surface Hub: + +- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#surfacehubpolicies). +- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). + +>[!TIP] +> Use the wizard to create a package with the common settings, then switch to the advanced editor to add other settings. +> +>![open advanced editor](images/icd-simple-edit.png) + +## Use the Surface Hub provisioning wizard + +After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package. + +### Create the provisioning package + +1. Open Windows Configuration Designer: + - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut, + + or + + - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**. + +2. Click **Provision Surface Hub devices**. + +3. Name your project and click **Next**. + +### Configure settings + + + + + + + + + +
![step one](images/one.png) ![add certificates](images/add-certificates.png)

To provision the device with a certificate, click **Add a certificate**. Enter a name for the certificate, and then browse to and select the certificate to be used.		![add a certificate](images/add-certificates-details.png)
![step two](images/two.png) ![configure proxy settings](images/proxy.png)

Toggle **Yes** or **No** for proxy settings. The default configuration for Surface Hub is to automatically detect proxy settings, so you can select **No** if that is the setting that you want. However, if your infrastructure previously required using a proxy server and has changed to not require a proxy server, you can use a provisioning package to revert your Surface Hub devices to the default settings by selecting **Yes** and **Automatically detect settings**.

If you toggle **Yes**, you can select to automatically detect proxy settings, or you can manually configure the settings by entering a URL to a setup script, or a static proxy server address. You can also identify whether to use the proxy server for local addresses, and enter exceptions (addresses that Surface Hub should connect to directly without using the proxy server). 		![configure proxy settings](images/proxy-details.png)
![step three](images/three.png) ![device admins](images/set-up-device-admins.png)

You can enroll the device in Active Directory and specify a security group to use the Settings app, enroll in Azure Active Directory to allow global admins to use the Settings app, or create a local administrator account on the device.

To enroll the device in Active Directory, enter the credentials for a least-privileged user account to join the device to the domain, and specify the security group to have admin credentials on Surface Hub. If a provisioning package that enrolls a device in Active Directory is going to be applied to a Surface Hub that was reset, the same domain account can only be used if the account listed is a domain administrator or is the same account that set up the Surface Hub initially. Otherwise, a different domain account must be used in the provisioning package.

Before you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, [set up Azure AD join in your organization](https://docs.microsoft.com/azure/active-directory/active-directory-azureadjoin-setup). The **maximum number of devices per user** setting in your Azure AD tenant determines how many times the bulk token that you get in the wizard can be used. To enroll the device in Azure AD, select that option and enter a friendly name for the bulk token you will get using the wizard. Set an expiration date for the token (maximum is 30 days from the date you get the token). Click **Get bulk token**. In the **Let's get you signed in** window, enter an account that has permissions to join a device to Azure AD, and then the password. Click **Accept** to give Windows Configuration Designer the necessary permissions.

To create a local administrator account, select that option and enter a user name and password.

**Important:** If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. 		![join Active Directory, Azure AD, or create a local admin account](images/set-up-device-admins-details.png)
![step four](images/four.png) ![enroll in device management](images/enroll-mdm.png)

Toggle **Yes** or **No** for enrollment in MDM.

If you toggle **Yes**, you must provide a service account and password or certificate thumbprint that is authorized to enroll the device, and also specify the authentication type. If required by your MDM provider, also enter the URLs for the discovery service, enrollment service, and policy service. [Learn more about managing Surface Hub with MDM.](manage-settings-with-mdm-for-surface-hub.md)		![enroll in mobile device management](images/enroll-mdm-details.png)
![step five](images/five.png) ![add applications](images/add-applications.png)

You can install multiple Universal Windows Platform (UWP) apps in a provisioning package. For help with the settings, see [Provision PCs with apps](https://technet.microsoft.com/itpro/windows/configure/provision-pcs-with-apps).

**Important:** Although the wizard interface allows you to select a Classic Win32 app, only include UWP apps in a provisioning package that will be applied to Surface Hub. If you include a Classic Win32 app, provisioning will fail. 		![add an application](images/add-applications-details.png)
![step six](images/six.png) ![Add configuration file](images/add-config-file.png)

You don't configure any settings in this step. It provides instructions for including a configuration file that contains a list of device accounts. The configuration file must not contain column headers. When you apply the provisioning package to Surface Hub, if a Surface Hub configuration file is included on the USB drive, you can select the account and friendly name for the device from the file. See [Sample configuration file](#sample-configuration-file) for an example.

**Important:** The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703. 		![Add a Surface Hub configuration file](images/add-config-file-details.png)
![finish](images/finish.png)

You can set a password to protect your provisioning package. You must enter this password when you apply the provisioning package to a device.		![Protect your package](images/finish-details.png)
+ +After you're done, click **Create**. It only takes a few seconds. When the package is built, the location where the package is stored is displayed as a hyperlink at the bottom of the page. + +## Sample configuration file + +A Surface Hub configuration file contains a list of device accounts that your device can use to connect to Exchange and Skype for Business. When you apply a provisioning package to Surface Hub, you can include a configuration file in the root directory of the USB flash drive, and then select the desired account to apply to that device. The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703. + +Use Microsoft Excel or other CSV editor to create a CSV file named `SurfaceHubConfiguration.csv`. In the file, enter a list of device accounts and friendly names in this format: + +``` +,, +``` +>[!IMPORTANT] +>Because the configuration file stores the device account passwords in plaintext, we recommend that you update the passwords after you've applied the provisioning package to your devices. You can use the [DeviceAccount node](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp#deviceaccount) in the [Surface Hub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) to update the passwords via MDM. + + +The following is an example of `SurfaceHubConfiguration.csv`. + +``` +Rainier@contoso.com,password,Rainier Surface Hub +Adams@contoso.com,password,Adams Surface Hub +Baker@contoso.com,password,Baker Surface Hub +Glacier@constoso.com,password,Glacier Surface Hub +Stuart@contoso.com,password,Stuart Surface Hub +Fernow@contoso.com,password,Fernow Surface Hub +Goode@contoso.com,password,Goode Surface Hub +Shuksan@contoso.com,password,Shuksan Surface Hub +Buckner@contoso.com,password,Buckner Surface Hub +Logan@contoso.com,password,Logan Surface Hub +Maude@consoto.com,password,Maude Surface hub +Spickard@contoso.com,password,Spickard Surface Hub +Redoubt@contoso.com,password,Redoubt Surface Hub +Dome@contoso.com,password,Dome Surface Hub +Eldorado@contoso.com,password,Eldorado Surface Hub +Dragontail@contoso.com,password,Dragontail Surface Hub +Forbidden@contoso.com,password,Forbidden Surface Hub +Oval@contoso.com,password,Oval Surface Hub +StHelens@contoso.com,password,St Helens Surface Hub +Rushmore@contoso.com,password,Rushmore Surface Hub +``` + +## Use advanced provisioning + +After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package. + +### Create the provisioning package (advanced) + +1. Open Windows Configuration Designer: + - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut, + + or + + - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**. + +2. Click **Advanced provisioning**. + +3. Name your project and click **Next**. + +4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**. + + ![ICD new project](images/icd-new-project.png) + +5. In the project, under **Available customizations**, select **Common Team edition settings**. + + ![ICD common settings](images/icd-common-settings.png) + + +### Add a certificate to your package +You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange. + +> [!NOTE] +> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details. + +1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**. + +2. Enter a **CertificateName** and then click **Add**. + +2. Enter the **CertificatePassword**. + +3. For **CertificatePath**, browse and select the certificate. + +4. Set **ExportCertificate** to **False**. + +5. For **KeyLocation**, select **Software only**. + + +### Add a Universal Windows Platform (UWP) app to your package +Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Windows Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Windows Store for Business. + +1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**. + +2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Windows Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \...\ tags. + +3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle). + +4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies. + +If you acquired the app from the Windows Store for Business, you will also need to add the app license to your provisioning package. + +1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license". + +2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**. + +3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \ tag, use the value in the **LicenseID** attribute. + +4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1. + + +### Add a policy to your package +Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD. + +1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**. + +2. Select one of the available policy areas. + +3. Select and set the policy you want to add to your provisioning package. + + +### Add Surface Hub settings to your package + +You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package. + +1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**. + +2. Select one of the available setting areas. + +3. Select and set the setting you want to add to your provisioning package. + + +## Build your package + +1. When you are done configuring the provisioning package, on the **File** menu, click **Save**. + +2. Read the warning that project files may contain sensitive information, and click **OK**. + + > [!IMPORTANT] + > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed. + +3. On the **Export** menu, click **Provisioning package**. + +4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources. + +5. Set a value for **Package Version**, and then select **Next.** + + > [!TIP] + > You can make changes to existing packages and change the version number to update previously applied packages. + +6. Optional: You can choose to encrypt the package and enable package signing. + + - **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen. + + - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package. + + > [!IMPORTANT] + > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.  + +7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.

+Optionally, you can click **Browse** to change the default output location. + +8. Click **Next**. + +9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.

+If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**. + +10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.

+If your build is successful, the name of the provisioning package, output directory, and project directory will be shown. + + - If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build. + + - If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**. + +11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive. + + +## Apply a provisioning package to Surface Hub + +There are two options for deploying provisioning packages to a Surface Hub. You can apply a provisioning packing [during the first run wizard](#apply-a-provisioning-package-during-first-run), or using [Settings](#apply-a-package-using-settings). + + +### Apply a provisioning package during first run + +> [!IMPORTANT] +> Only use provisioning packages to install certificates during first run. Use the **Settings** app to install apps and apply other settings. + +1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding. + +2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**. + + ![Set up device?](images/provisioningpackageoobe-01.png) + +3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**. + + ![Provision this device](images/provisioningpackageoobe-02.png) + +4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run. + + ![Choose a package](images/provisioningpackageoobe-03.png) + +5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**. + + ![Do you trust this package?](images/provisioningpackageoobe-04.png) + +6. If a configuration file is included in the root directory of the USB flash drive, you will see **Select a configuration**. The first device account in the configuration file will be shown with a summary of the account information that will be applied to the Surface Hub. + + ![select a configuration](images/ppkg-config.png) + +7. In **Select a configuration**, select the device name to apply, and then click **Next**. + + ![select a friendly device name](images/ppkg-csv.png) + +The settings from the provisioning package will be applied to the device and OOBE will be complete. After the device restarts, you can remove the USB flash drive. + +### Apply a package using Settings + +1. Insert the USB flash drive containing the .ppkg file into the Surface Hub. + +2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted. + +3. Navigate to **Surface Hub** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**. + +4. Select **Add a package**. + +5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted. + +6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**. + + diff --git a/devices/surface-hub/remote-surface-hub-management.md b/devices/surface-hub/remote-surface-hub-management.md index 41588251fe..57bd619f8b 100644 --- a/devices/surface-hub/remote-surface-hub-management.md +++ b/devices/surface-hub/remote-surface-hub-management.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/save-bitlocker-key-surface-hub.md b/devices/surface-hub/save-bitlocker-key-surface-hub.md index 2354de0f40..6e6b8b5317 100644 --- a/devices/surface-hub/save-bitlocker-key-surface-hub.md +++ b/devices/surface-hub/save-bitlocker-key-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub, security -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/set-up-your-surface-hub.md b/devices/surface-hub/set-up-your-surface-hub.md index 95b7c2c92f..96310f473c 100644 --- a/devices/surface-hub/set-up-your-surface-hub.md +++ b/devices/surface-hub/set-up-your-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/setup-worksheet-surface-hub.md b/devices/surface-hub/setup-worksheet-surface-hub.md index a77cf5850f..d8e7f921c0 100644 --- a/devices/surface-hub/setup-worksheet-surface-hub.md +++ b/devices/surface-hub/setup-worksheet-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/surfacehub-whats-new-1703.md b/devices/surface-hub/surfacehub-whats-new-1703.md new file mode 100644 index 0000000000..537d6c55a9 --- /dev/null +++ b/devices/surface-hub/surfacehub-whats-new-1703.md @@ -0,0 +1,31 @@ +--- +title: What's new in Windows 10, version 1703 for Surface Hub +description: Windows 10, version 1703 (Creators Update) brings new features to Microsoft Surface Hub. +ms.prod: w10 +ms.mktglfcycl: manage +ms.pagetype: devices +ms.sitesec: library +author: jdeckerMS +localizationpriority: medium +--- + +# What's new in Windows 10, version 1703 for Microsoft Surface Hub? + +Windows 10, version 1703 (also called the Creators Update), introduces the following changes for Microsoft Surface Hub: + + +- Settings have been added to mobile device management (MDM) and configuration service providers (CSPs) to expand the Surface Hub management capabilities. [Learn more about the new settings.](manage-settings-with-mdm-for-surface-hub.md) + +- An easy-to-use wizard helps you quickly create provisioning packages that you can apply to multiple Surface Hub devices. [Learn how to create a provisioning package for Surface Hub.](provisioning-packages-for-certificates-surface-hub.md) + +- When you reset a Surface Hub device, you now have the ability to download and install a factory build of the operating system from the cloud. [Learn more about cloud recovery.](device-reset-surface-hub.md#cloud-recovery) + >[!NOTE] + >Cloud recovery doesn't work if you use proxy servers. + +- **I'm done** is now **End session**. [Learn how to use End session.](i-am-done-finishing-your-surface-hub-meeting.md) + + + + + + diff --git a/devices/surface-hub/troubleshoot-surface-hub.md b/devices/surface-hub/troubleshoot-surface-hub.md index cc3bd57b95..ff05c19f62 100644 --- a/devices/surface-hub/troubleshoot-surface-hub.md +++ b/devices/surface-hub/troubleshoot-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: support ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md b/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md index fbed027215..512cf6b4bf 100644 --- a/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md +++ b/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md @@ -3,7 +3,7 @@ title: Use fully qualified doman name with Surface Hub description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors. ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"] -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -16,7 +16,7 @@ There are a few scenarios where you need to specify the domain name of your Skyp **To configure the domain name for your Skype for Business server**
1. On Surface Hub, open **Settings**. -2. Click **This device**, and then click **Calling**. +2. Click **Surface Hub**, and then click **Calling & Audio**. 3. Under **Skype for Business configuration**, click **Configure domain name**. 4. Type the domain name for your Skype for Business server, and then click **Ok**. > [!TIP] diff --git a/devices/surface-hub/use-room-control-system-with-surface-hub.md b/devices/surface-hub/use-room-control-system-with-surface-hub.md index 16fd8c71d1..4ff4665c6a 100644 --- a/devices/surface-hub/use-room-control-system-with-surface-hub.md +++ b/devices/surface-hub/use-room-control-system-with-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- diff --git a/devices/surface-hub/wireless-network-management-for-surface-hub.md b/devices/surface-hub/wireless-network-management-for-surface-hub.md index 0ccd6ad70d..db080ce397 100644 --- a/devices/surface-hub/wireless-network-management-for-surface-hub.md +++ b/devices/surface-hub/wireless-network-management-for-surface-hub.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: surfacehub, networking -author: TrudyHa +author: jdeckerMS localizationpriority: medium --- @@ -24,7 +24,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele ### Choose a wireless access point 1. On the Surface Hub, open **Settings** and enter your admin credentials. -2. Click **System**, and then click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**. +2. Click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**. ![Image showing Wi-Fi settings, Network & Internet page.](images/networkmgtwireless-01.png) @@ -35,7 +35,7 @@ If a wired network connection is not available, the Surface Hub can use a wirele ### Review wireless settings 1. On the Surface Hub, open **Settings** and enter your admin credentials. -2. Click **System**, click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**. +2. Click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**. 3. Surface Hub shows you the properties for the wireless network connection. ![Image showing properties for connected Wi-Fi.](images/networkmgtwireless-04.png) diff --git a/windows/configure/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md b/windows/configure/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md index aded7204d4..8c7153b1ce 100644 --- a/windows/configure/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md +++ b/windows/configure/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md @@ -34,13 +34,28 @@ Three features enable Start and taskbar layout control: - The **Export-StartLayout** cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format. - **Note**   - To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](https://go.microsoft.com/fwlink/p/?LinkId=623707) cmdlet. + >[!NOTE]   + >To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](https://go.microsoft.com/fwlink/p/?LinkId=623707) cmdlet. - [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `` or create an .xml file just for the taskbar configuration. +- In Windows Configuration Designer, you use the **Policies/Start/StartLayout** setting to provide the contents of the .xml file that defines the Start and taskbar layout. -- In Windows Configuration Designer, you use the **Start/StartLayout** setting to set the path to the .xml file that defines the Start and taskbar layout. + +## Prepare the Start layout XML file + +Before you paste the contents of the .xml file in the **Policies/Start/StartLayout** setting, you must remove all line breaks and replace markup characters with escape characters. + +1. In PowerShell, run the following script: + + ``` + $path="layout.xml" + (Get-Content $path -Raw).Replace("'r'n","") | Set-Content $path -Force + ``` + +2. Copy the contents of layout.xml into an online tool that escapes characters. + +3. Copy the text with the escape characters and paste it in the **Polilcies/Start/StartLayout** setting in your provisioning package. ## Create a provisioning package that contains a customized Start layout @@ -60,12 +75,12 @@ Use the Windows Configuration Designer tool to create a provisioning package. [L 5. On **New project**, click **Finish**. The workspace for your package opens. -6. Expand **Runtime settings** > **Start**, and click **StartLayout**. +6. Expand **Runtime settings** > **Policies** > **Start**, and click **StartLayout**. >[!TIP] >If **Start** is not listed, check the type of settings you selected in step 4. You must create the project using settings for **All Windows desktop editions**. -7. Specify the path and file name of the Start layout .xml that you created with the [Export-StartLayout](https://go.microsoft.com/fwlink/p/?LinkId=620879) cmdlet. +7. Paste the text from the layout.xml file, [with line breaks removed and markup characters replaced with escape characters](#escape). 8. On the **File** menu, select **Save.** diff --git a/windows/configure/lockdown-xml.md b/windows/configure/lockdown-xml.md index 7525f64aa6..9398934ee7 100644 --- a/windows/configure/lockdown-xml.md +++ b/windows/configure/lockdown-xml.md @@ -479,7 +479,7 @@ After you build the provisioning package, follow the instructions for [applying After you deploy your devices, you can still configure lockdown settings through your MDM solution if it supports the [EnterpriseAssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=618601). -To push lockdown settings to enrolled devices, use the AssignedAccessXML setting and use the lockdown XML as the value. The lockdown XML will be in a HandheldLockdown section that becomes XML embedded in XML, so the XML that you enter must use escaped characters (such as < in place of <). After the MDM provider pushes your lockdown settings to the device, the CSP processes the file and updates the device. +To push lockdown settings to enrolled devices, use the AssignedAccessXML setting and use the lockdown XML as the value. The lockdown XML will be in a HandheldLockdown section that becomes XML embedded in XML, so the XML that you enter must use escaped characters (such as `<` in place of <). After the MDM provider pushes your lockdown settings to the device, the CSP processes the file and updates the device. ## Full Lockdown.xml example diff --git a/windows/configure/windows-10-start-layout-options-and-policies.md b/windows/configure/windows-10-start-layout-options-and-policies.md index d4669bfaed..258d6c4418 100644 --- a/windows/configure/windows-10-start-layout-options-and-policies.md +++ b/windows/configure/windows-10-start-layout-options-and-policies.md @@ -29,6 +29,7 @@ Organizations might want to deploy a customized Start and taskbar configuration >Using the layout modification XML to configure Start is not supported with roaming user profiles. For more information, see [Deploy Roaming User Profiles](https://technet.microsoft.com/library/jj649079.aspx). + ## Start options ![start layout sections](images/startannotated.png) @@ -79,6 +80,9 @@ Whether you apply the taskbar configuration to a clean install or an update, use * Change the order of pinned apps * Unpin any app +>[!NOTE] +>In Windows 10, version 1703, you can apply an MDM policy, `Start/NoPinningToTaskbar`, to prevents users from pinning and unpinning apps on the taskbar. + ### Taskbar configuration applied to clean install of Windows 10 In a clean install, if you apply a taskbar layout, only the apps that you specify and default apps that you do not remove will be pinned to the taskbar. Users can pin additional apps to the taskbar after the layout is applied. @@ -93,22 +97,16 @@ The new taskbar layout for upgrades to Windows 10, version 1607 or later, will a * If the user didn't pin the app and the app is in the updated layout file, the app will be pinned to the right. * New apps specified in updated layout file are pinned to right of user's pinned apps. - +[Learn how to onfigure Windows 10 taskbar](configure-windows-10-taskbar.md). ## Related topics -[Customize and export Start layout](customize-and-export-start-layout.md) - -[Configure Windows 10 taskbar](configure-windows-10-taskbar.md) - -[Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) - -[Customize Windows 10 Start with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) - -[Customize Windows 10 Start and taskbar with ICD and provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md) - -[Changes to Group Policy settings for Windows 10 Start](changes-to-start-policies-in-windows-10.md) +- [Customize and export Start layout](customize-and-export-start-layout.md) +- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) +- [Customize Windows 10 Start with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) +- [Customize Windows 10 Start and taskbar with ICD and provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md) +- [Changes to Group Policy settings for Windows 10 Start](changes-to-start-policies-in-windows-10.md)   diff --git a/windows/deploy/TOC.md b/windows/deploy/TOC.md index d31baa9297..a14e1d9f0d 100644 --- a/windows/deploy/TOC.md +++ b/windows/deploy/TOC.md @@ -1,4 +1,5 @@ # [Deploy Windows 10](index.md) +## [What's new in Windows 10 deployment](deploy-whats-new.md) ## [Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) ## [Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md) ### [Upgrade Readiness architecture](upgrade-readiness-architecture.md) @@ -26,6 +27,7 @@ ### [Build a distributed environment for Windows 10 deployment](build-a-distributed-environment-for-windows-10-deployment.md) ### [Refresh a Windows 7 computer with Windows 10](refresh-a-windows-7-computer-with-windows-10.md) ### [Replace a Windows 7 computer with a Windows 10 computer](replace-a-windows-7-computer-with-a-windows-10-computer.md) +### [Perform an in-place upgrade to Windows 10 with MDT](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) ### [Configure MDT settings](configure-mdt-settings.md) #### [Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md) #### [Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md) @@ -48,8 +50,7 @@ ### [Monitor the Windows 10 deployment with Configuration Manager](monitor-windows-10-deployment-with-configuration-manager.md) ### [Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md) ### [Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md) -## [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) -## [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) +### [Perform an in-place upgrade to Windows 10 using Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) ## [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) ## [Convert MBR partition to GPT](mbr-to-gpt.md) ## [Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) diff --git a/windows/deploy/change-history-for-deploy-windows-10.md b/windows/deploy/change-history-for-deploy-windows-10.md index a3c2c4364e..f0c32cf285 100644 --- a/windows/deploy/change-history-for-deploy-windows-10.md +++ b/windows/deploy/change-history-for-deploy-windows-10.md @@ -17,6 +17,9 @@ The topics in this library have been updated for Windows 10, version 1703 (also ## March 2017 | New or changed topic | Description | |----------------------|-------------| +| [What's new in Windows 10 deployment](deploy-whats-new.md) | New | +| [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) | Topic moved under [Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) in the table of contents and title adjusted to clarify in-place upgrade. | +| [Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) | Topic moved under [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md) in the table of contents and title adjusted to clarify in-place upgrade. | | [Convert MBR partition to GPT](mbr-to-gpt.md) | New | ## February 2017 diff --git a/windows/deploy/deploy-whats-new.md b/windows/deploy/deploy-whats-new.md new file mode 100644 index 0000000000..9d6a1b0d15 --- /dev/null +++ b/windows/deploy/deploy-whats-new.md @@ -0,0 +1,123 @@ +--- +title: What's new in Windows 10 deployment +description: Changes and new features related to Windows 10 deployment +keywords: deployment, automate, tools, configure, news +ms.mktglfcycl: deploy +localizationpriority: high +ms.prod: w10 +ms.sitesec: library +ms.pagetype: deploy +author: greg-lindsay +--- + +# What's new in Windows 10 deployment + +**Applies to** +- Windows 10 + + +## In this topic + +This topic provides an overview of new solutions and online content related to deploying Windows 10 in your organization. + +- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](https://technet.microsoft.com/itpro/windows/whats-new/index). +- For a detailed list of changes to Windows 10 ITPro TechNet library content, see [Online content change history](#online-content-change-history). + + +## Windows 10 Enterprise upgrade + +Windows 10 Enterprise E3 launched in the Cloud Solution Provider (CSP) channel on September 1, 2016. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Enterprise to their users. With Windows 10 Enterprise E3 in CSP, small and medium-sized organizations can more easily take advantage of Windows 10 Enterprise features. + +For more information, see [Windows 10 Enterprise E3 in CSP Overview](windows-10-enterprise-e3-overview.md) + + +## Deployment solutions and tools + +### Upgrade Readiness + +The Upgrade Readiness tool moved from public preview to general availability on March 2, 2017. + +Upgrade Readiness helps you ensure that applications and drivers are ready for a Windows 10 upgrade. The solution provides up-to-date application and driver inventory, information about known issues, troubleshooting guidance, and per-device readiness and tracking details. + +The development of Upgrade Readiness has been heavily influenced by input from the community the development of new features is ongoing. To begin using Upgrade Readiness, add it to an existing Operation Management Suite (OMS) workspace or sign up for a new OMS workspace with the Upgrade Readiness solution enabled. + +For more information about Upgrade Readiness, see the following topics: + +- [Windows Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics/) +- [Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md) + + +### Update Compliance + +Update Compliance helps you to keep Windows 10 devices in your organization secure and up-to-date. + +Update Compliance is a solution built using OMS Logs and Analytics that provides information about installation status of monthly quality and feature updates. Details are provided about the deployment progress of existing updates and the status of future updates. Information is also provided about devices that might need attention to resolve issues. + +For more information about Update Compliance, see [Monitor Windows Updates with Update Compliance](../manage/update-compliance-monitor.md). + + +### MBR2GPT + +MBR2GPT.EXE converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. Previously, it was necessary to image, then wipe and reload a disk to change from MBR format to GPT. + +There are many benefits to converting the partition style of a disk to GPT, including the use of larger disk partitions, added data reliability, and faster boot and shutdown speeds. The GPT format also enables you to use the Unified Extensible Firmware Interface (UEFI) which replaces the Basic Input/Output System (BIOS) firmware interface. Security features of Windows 10 that require UEFI mode include: Secure Boot, Early Launch Anti-malware (ELAM) driver, Windows Trusted Boot, Measured Boot, Device Guard, Credential Guard, and BitLocker Network Unlock. + +For more information, see [MBR2GPT.EXE](mbr-to-gpt.md). + + +### Microsoft Deployment Toolkit (MDT) + +MDT build 884 is available, including support for: +- Deployment and upgrade of Windows 10, version 1607 (including Enterprise LTSB and Education editions) and Windows Server 2016. +- The Windows ADK for Windows 10, version 1607. +- Integration with Configuration Manager version 1606. + +For more information about MDT, see the [MDT resource page](https://technet.microsoft.com/en-US/windows/dn475741). + + +### Windows Assessment and Deployment Kit (ADK) + +The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. See the following topics: + +- [What's new in ADK kits and tools](https://msdn.microsoft.com/windows/hardware/commercialize/what-s-new-in-kits-and-tools) +- [Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) + + +## Testing and validation guidance + +### Windows 10 deployment proof of concept (PoC) + +The Windows 10 PoC guide enables you to test Windows 10 deployment in a virtual environment and become familiar with deployment tools such as MDT and Configuration Manager. The PoC guide provides step-by-step instructions for installing and using Hyper-V to create a virtual lab environment. The guide makes extensive use of Windows PowerShell to streamline each phase of the installation and setup. + +For more information, see the following guides: + +- [Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md) +- [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md) +- [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md) + + +## Troubleshooting guidance + +[Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) was published in October of 2016 and will continue to be updated with new fixes. The topic provides a detailed explanation of the Windows 10 upgrade process and instructions on how to locate, interpret, and resolve specific errors that can be encountered during the upgrade process. + + +## Online content change history + +The following topics provide a change history for Windows 10 ITPro TechNet library content related to deploying and using Windows 10. + +[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) +
[Change history for Plan for Windows 10 deployment](../plan/change-history-for-plan-for-windows-10-deployment.md) +
[Change history for Manage and update Windows 10](../manage/change-history-for-manage-and-update-windows-10.md) +
[Change history for Keep Windows 10 secure](../keep-secure/change-history-for-keep-windows-10-secure.md) + + +## Related topics + +[Overview of Windows as a service](../manage/waas-overview.md) +
[Windows 10 deployment considerations](../plan/windows-10-deployment-considerations.md) +
[Windows 10 release information](https://technet.microsoft.com/en-us/windows/release-info.aspx) +
[Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/en-us/windows/windows-10-specifications) +
[Windows 10 upgrade paths](windows-10-upgrade-paths.md) +
[Windows 10 deployment tools](windows-deployment-scenarios-and-tools.md) + + \ No newline at end of file diff --git a/windows/deploy/index.md b/windows/deploy/index.md index 8b1846f60e..8058cf8890 100644 --- a/windows/deploy/index.md +++ b/windows/deploy/index.md @@ -16,13 +16,12 @@ Learn about deploying Windows 10 for IT professionals. |Topic |Description | |------|------------| +|[What's new in Windows 10 deployment](deploy-whats-new.md) |See this topic for a summary of new features and some recent changes related to deploying Windows 10 in your organization. | |[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md) |To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the key capabilities and limitations of each, is a key task. | |[Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md) |With Upgrade Readiness, enterprises now have the tools to plan and manage the upgrade process end to end, allowing them to adopt new Windows releases more quickly. With Windows telemetry enabled, Upgrade Readiness collects system, application, and driver data for analysis. We then identify compatibility issues that can block an upgrade and suggest fixes when they are known to Microsoft. The Upgrade Readiness workflow steps you through the discovery and rationalization process until you have a list of computers that are ready to be upgraded. | |[Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md) |This guide contains instructions to configure a proof of concept (PoC) environment requiring a minimum amount of resources. The guide makes extensive use of Windows PowerShell and Hyper-V. Subsequent companion guides contain steps to deploy Windows 10 using the PoC environment. After completing this guide, see the following Windows 10 PoC deployment guides: [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md), [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md). | |[Deploy Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-10-with-the-microsoft-deployment-toolkit.md) |This guide will walk you through the process of deploying Windows 10 in an enterprise environment using the Microsoft Deployment Toolkit (MDT). | |[Deploy Windows 10 with System Center 2012 R2 Configuration Manager](deploy-windows-10-with-system-center-2012-r2-configuration-manager.md) |If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT) or. | -|[Upgrade to Windows 10 with the Microsoft Deployment Toolkit](upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) |The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a Microsoft Deployment Toolkit (MDT) task sequence to completely automate the process. | -|[Upgrade to Windows 10 with System Center Configuration Manager](upgrade-to-windows-10-with-system-center-configuraton-manager.md) |The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. | |[Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) |This topic provides a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade. | |[Convert MBR partition to GPT](mbr-to-gpt.md) |This topic provides detailed instructions for using the MBR2GPT partition conversion tool. | |[Configure a PXE server to load Windows PE](configure-a-pxe-server-to-load-windows-pe.md) |This guide describes how to configure a PXE server to load Windows PE by booting a client computer from the network. | diff --git a/windows/deploy/upgrade-readiness-get-started.md b/windows/deploy/upgrade-readiness-get-started.md index 9f9abda9b2..4829baa632 100644 --- a/windows/deploy/upgrade-readiness-get-started.md +++ b/windows/deploy/upgrade-readiness-get-started.md @@ -44,7 +44,7 @@ If you are already using OMS, you’ll find Upgrade Readiness in the Solutions G If you are not using OMS: -1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **Sign up** to kick off the onboarding process. +1. Go to the [Upgrade Readiness page on Microsoft.com](https://go.microsoft.com/fwlink/?LinkID=799190&clcid=0x409) and click **New Customers >** to kick off the onboarding process. 2. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS. 3. Create a new OMS workspace. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select **Create**. 4. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. @@ -130,4 +130,4 @@ To ensure that user computers are receiving the most up to date data from Micros ### Distribute the deployment script at scale -Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Readiness deployment script at scale. For more information, see the [Upgrade Readiness blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/). \ No newline at end of file +Use a software distribution system such as System Center Configuration Manager to distribute the Upgrade Readiness deployment script at scale. For more information, see the [Upgrade Readiness blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/). diff --git a/windows/deploy/upgrade-to-windows-10-with-system-center-configuraton-manager.md b/windows/deploy/upgrade-to-windows-10-with-system-center-configuraton-manager.md index 1739910931..4df01c9022 100644 --- a/windows/deploy/upgrade-to-windows-10-with-system-center-configuraton-manager.md +++ b/windows/deploy/upgrade-to-windows-10-with-system-center-configuraton-manager.md @@ -1,6 +1,6 @@ --- -title: Upgrade to Windows 10 with System Center Configuration Manager (Windows 10) -description: The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. +title: Perform an in-place upgrade to Windows 10 using Configuration Manager (Windows 10) +description: The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. Use a System Center Configuration Manager task sequence to completely automate the process. ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878 keywords: upgrade, update, task sequence, deploy ms.prod: w10 @@ -9,7 +9,7 @@ ms.mktglfcycl: deploy author: mtniehaus --- -# Upgrade to Windows 10 with System Center Configuration Manager +# Perform an in-place upgrade to Windows 10 using Configuration Manager **Applies to** diff --git a/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md b/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md index c3f69f25b9..4deadb668f 100644 --- a/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md +++ b/windows/deploy/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md @@ -1,5 +1,5 @@ --- -title: Upgrade to Windows 10 with the Microsoft Deployment Toolkit (Windows 10) +title: Perform an in-place upgrade to Windows 10 with MDT (Windows 10) description: The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. ms.assetid: B8993151-3C1E-4F22-93F4-2C5F2771A460 keywords: upgrade, update, task sequence, deploy @@ -11,7 +11,7 @@ ms.pagetype: mdt author: mtniehaus --- -# Upgrade to Windows 10 with the Microsoft Deployment Toolkit +# Perform an in-place upgrade to Windows 10 with MDT **Applies to** - Windows 10 diff --git a/windows/deploy/use-upgrade-readiness-to-manage-windows-upgrades.md b/windows/deploy/use-upgrade-readiness-to-manage-windows-upgrades.md index ee298dc448..21ff12135a 100644 --- a/windows/deploy/use-upgrade-readiness-to-manage-windows-upgrades.md +++ b/windows/deploy/use-upgrade-readiness-to-manage-windows-upgrades.md @@ -41,7 +41,7 @@ As mentioned previously, the default target version in Upgrade Readiness is set The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version. -You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, and Windows version 1610. +You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, and Windows version 1607. To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution: diff --git a/windows/deploy/windows-10-poc-mdt.md b/windows/deploy/windows-10-poc-mdt.md index 78b5aa1d76..e42cec7206 100644 --- a/windows/deploy/windows-10-poc-mdt.md +++ b/windows/deploy/windows-10-poc-mdt.md @@ -5,6 +5,8 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy +keywords: deployment, automate, tools, configure, mdt +localizationpriority: high author: greg-lindsay --- diff --git a/windows/deploy/windows-10-poc-sc-config-mgr.md b/windows/deploy/windows-10-poc-sc-config-mgr.md index ff0b497b45..b7c115e44a 100644 --- a/windows/deploy/windows-10-poc-sc-config-mgr.md +++ b/windows/deploy/windows-10-poc-sc-config-mgr.md @@ -5,6 +5,8 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy +keywords: deployment, automate, tools, configure, sccm, configuration manager +localizationpriority: high author: greg-lindsay --- diff --git a/windows/deploy/windows-10-poc.md b/windows/deploy/windows-10-poc.md index 74b8d0f352..3db31d59c4 100644 --- a/windows/deploy/windows-10-poc.md +++ b/windows/deploy/windows-10-poc.md @@ -5,6 +5,8 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy +keywords: deployment, automate, tools, configure, mdt, sccm +localizationpriority: high author: greg-lindsay --- diff --git a/windows/images/W10-WaaS-poster.PNG b/windows/images/W10-WaaS-poster.PNG new file mode 100644 index 0000000000..76f843c1b8 Binary files /dev/null and b/windows/images/W10-WaaS-poster.PNG differ diff --git a/windows/images/front-page-video.PNG b/windows/images/front-page-video.PNG new file mode 100644 index 0000000000..afe78e3564 Binary files /dev/null and b/windows/images/front-page-video.PNG differ diff --git a/windows/images/w10-configure.png b/windows/images/w10-configure.png new file mode 100644 index 0000000000..ebfef8d97b Binary files /dev/null and b/windows/images/w10-configure.png differ diff --git a/windows/images/w10-deploy.png b/windows/images/w10-deploy.png new file mode 100644 index 0000000000..d567f44f1d Binary files /dev/null and b/windows/images/w10-deploy.png differ diff --git a/windows/images/w10-manage.png b/windows/images/w10-manage.png new file mode 100644 index 0000000000..9ace55b79b Binary files /dev/null and b/windows/images/w10-manage.png differ diff --git a/windows/images/w10-plan.png b/windows/images/w10-plan.png new file mode 100644 index 0000000000..045f85e914 Binary files /dev/null and b/windows/images/w10-plan.png differ diff --git a/windows/images/w10-secure.png b/windows/images/w10-secure.png new file mode 100644 index 0000000000..7799e94849 Binary files /dev/null and b/windows/images/w10-secure.png differ diff --git a/windows/images/w10-update.png b/windows/images/w10-update.png new file mode 100644 index 0000000000..876374904b Binary files /dev/null and b/windows/images/w10-update.png differ diff --git a/windows/images/w10-whatsnew.png b/windows/images/w10-whatsnew.png new file mode 100644 index 0000000000..cc040c45aa Binary files /dev/null and b/windows/images/w10-whatsnew.png differ diff --git a/windows/index.md b/windows/index.md index 08a4bee465..8d86b31add 100644 --- a/windows/index.md +++ b/windows/index.md @@ -8,37 +8,94 @@ author: brianlic-msft --- # Windows 10 and Windows 10 Mobile + +This library provides the core content that IT pros need to evaluate, plan, deploy, secure and manage devices running Windows 10 or Windows 10 Mobile. +

-This library provides the core content that IT pros need to evaluate, plan, deploy, and manage devices running Windows 10 or Windows 10 Mobile. +
+ + + + + + + + + + + + + + +
+ + Read what's new in Windows 10 + +
What's New? + 		+ + Plan your Windows 10 enterprise deployment + +
Plan + 		+ + Deploy Windows 10 in your enterprise + +
Deploy + 		+ + Manage Windows 10 in your enterprise + +
Manage +
+
+ + Keep Windows 10 secure + +
Keep Secure + 		+
+ + Configure Windows 10 in your enterprise + +
Configure + 		+
+ + Update Windows 10 in your enterprise + +
Update + 		+
+ + Get your + +
Try it +
-## In this library +
+# Get to know Windows as a Service (WaaS) + + + + + +
The Windows 10 operating system introduces a new way to build, deploy, and service Windows: Windows as a service. Microsoft has reimagined each part of the process, to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers. + + These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers, and leveling out the resources needed to deploy and maintain Windows over time. + -[What's new in Windows 10](whats-new/index.md) + * [Read more about Windows as a Service]() + * [Download the WaaS infographic]() -[Plan for Windows 10 deployment](plan/index.md) +
Get to know Windows as a Service (WaaS)
-[Deploy Windows 10](deploy/index.md) - -[Configure Windows 10](configure/index.md) - -[Update Windows 10](update/index.md) - -[Keep Windows 10 secure](keep-secure/index.md) - -[Manage Windows 10](manage/index.md) ## Related topics - - [Windows 10 TechCenter](https://go.microsoft.com/fwlink/?LinkId=620009)     - - - - - diff --git a/windows/keep-secure/TOC.md b/windows/keep-secure/TOC.md index b3dc0db5dd..f2339f5940 100644 --- a/windows/keep-secure/TOC.md +++ b/windows/keep-secure/TOC.md @@ -41,6 +41,9 @@ #### [Unenlightened and enlightened app behavior while using Windows Information Protection (WIP)](app-behavior-with-wip.md) #### [Recommended Enterprise Cloud Resources and Neutral Resources network settings with Windows Information Protection (WIP)](recommended-network-definitions-for-wip.md) #### [Using Outlook Web Access with Windows Information Protection (WIP)](using-owa-with-wip.md) +## [Windows Defender SmartScreen](windows-defender-smartscreen-overview.md) +### [Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](windows-defender-smartscreen-available-settings.md) +### [Set up and use Windows Defender SmartScreen on individual devices](windows-defender-smartscreen-set-individual-device.md) ## [Use Windows Event Forwarding to help with intrusion detection](use-windows-event-forwarding-to-assist-in-instrusion-detection.md) ## [Override Process Mitigation Options to help enforce app-related security policies](override-mitigation-options-for-app-related-security-policies.md) ## [VPN technical guide](vpn-guide.md) @@ -782,6 +785,7 @@ ##### [Create custom threat intelligence alerts](custom-ti-api-windows-defender-advanced-threat-protection.md) ##### [PowerShell code examples](powershell-example-code-windows-defender-advanced-threat-protection.md) ##### [Python code examples](python-example-code-windows-defender-advanced-threat-protection.md) +##### [Experiment with custom threat intelligence alerts](experiment-custom-ti-windows-defender-advanced-threat-protection.md) ##### [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti-windows-defender-advanced-threat-protection.md) #### [Check sensor state](check-sensor-status-windows-defender-advanced-threat-protection.md) ##### [Fix unhealthy sensors](fix-unhealhty-sensors-windows-defender-advanced-threat-protection.md) @@ -797,16 +801,48 @@ #### [Troubleshoot Windows Defender ATP](troubleshoot-windows-defender-advanced-threat-protection.md) #### [Review events and errors on endpoints with Event Viewer](event-error-codes-windows-defender-advanced-threat-protection.md) #### [Windows Defender compatibility](defender-compatibility-windows-defender-advanced-threat-protection.md) -### [Windows Defender in Windows 10](windows-defender-in-windows-10.md) -#### [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) -#### [Configure Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md) -#### [Windows Defender Offline in Windows 10](windows-defender-offline.md) -#### [Use PowerShell cmdlets for Windows Defender](use-powershell-cmdlets-windows-defender-for-windows-10.md) -#### [Enable the Block at First Sight feature in Windows 10](windows-defender-block-at-first-sight.md) -#### [Configure enhanced notifications for Windows Defender in Windows 10](windows-defender-enhanced-notifications.md) -#### [Run a Windows Defender scan from the command line](run-cmd-scan-windows-defender-for-windows-10.md) -#### [Detect and block Potentially Unwanted Applications with Windows Defender](enable-pua-windows-defender-for-windows-10.md) -#### [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) +### [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) +#### [Windows Defender AV in the Windows Defender Security Center app](windows-defender-security-center-antivirus.md) +#### [Evaluate Windows Defender Antivirus protection](evaluate-windows-defender-antivirus.md) +#### [Deploy, manage updates, and report on Windows Defender Antivirus](deploy-manage-report-windows-defender-antivirus.md) +##### [Deploy and enable Windows Defender Antivirus](deploy-windows-defender-antivirus.md) +###### [Deployment guide for VDI environments](deployment-vdi-windows-defender-antivirus.md) +##### [Report on Windows Defender Antivirus protection](report-monitor-windows-defender-antivirus.md) +##### [Manage updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +###### [Manage protection and definition updates](manage-protection-updates-windows-defender-antivirus.md) +###### [Manage when protection updates should be downloaded and applied](manage-protection-update-schedule-windows-defender-antivirus.md) +###### [Manage updates for endpoints that are out of date](manage-outdated-endpoints-windows-defender-antivirus.md) +###### [Manage event-based forced updates](manage-event-based-updates-windows-defender-antivirus.md) +###### [Manage updates for mobile devices and VMs](manage-updates-mobile-devices-vms-windows-defender-antivirus.md) +#### [Configure Windows Defender Antivirus features](configure-windows-defender-antivirus-features.md) +##### [Utilize Microsoft cloud-provided protection](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) +###### [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) +###### [Specify the cloud-delivered protection level](specify-cloud-protection-level-windows-defender-antivirus.md) +###### [Configure and validate network connections](configure-network-connections-windows-defender-antivirus.md) +###### [Enable the Block at First Sight feature](configure-block-at-first-sight-windows-defender-antivirus.md) +###### [Configure the cloud block timeout period](configure-cloud-block-timeout-period-windows-defender-antivirus.md) +##### [Configure behavioral, heuristic, and real-time protection](configure-protection-features-windows-defender-antivirus.md) +###### [Detect and block Potentially Unwanted Applications](detect-block-potentially-unwanted-apps-windows-defender-antivirus.md) +###### [Enable and configure always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +##### [Configure end-user interaction with Windows Defender AV](configure-end-user-interaction-windows-defender-antivirus.md) +###### [Configure the notifications that appear on endpoints](configure-notifications-windows-defender-antivirus.md) +###### [Prevent users from seeing or interacting with the user interface](prevent-end-user-interaction-windows-defender-antivirus.md) +###### [Prevent or allow users to locally modify policy settings](configure-local-policy-overrides-windows-defender-antivirus.md) +#### [Customize, initiate, and review the results of scans and remediation](customize-run-review-remediate-scans-windows-defender-antivirus.md) +##### [Exclude files and processes from scans](configure-exclusions-windows-defender-antivirus.md) +##### [Configure email, removable storage, network, reparse point, and archive scanning](configure-advanced-scan-types-windows-defender-antivirus.md) +##### [Configure remediation for scans](configure-remediation-windows-defender-antivirus.md) +##### [Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) +##### [Configure and run scans](run-scan-windows-defender-antivirus.md) +##### [Review scan results](review-scan-results-windows-defender-antivirus.md) +##### [Run and review the results of a Windows Defender Offline scan](windows-defender-offline.md) +#### [Review event logs and error codes to troubleshoot issues](troubleshoot-windows-defender-antivirus.md) +#### [Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md) +##### [Use Group Policy settings to configure and manage Windows Defender AV](use-group-policy-windows-defender-antivirus.md) +##### [Use System Center Configuration Manager and Microsoft Intune to configure and manage Windows Defender AV](use-intune-config-manager-windows-defender-antivirus.md) +##### [Use PowerShell cmdlets to configure and manage Windows Defender AV](use-powershell-cmdlets-windows-defender-antivirus.md) +##### [Use Windows Management Instrumentation (WMI) to configure and manage Windows Defender AV](use-wmi-windows-defender-antivirus.md) +##### [Use the mpcmdrun.exe commandline tool to configure and manage Windows Defender AV](command-line-arguments-windows-defender-antivirus.md) ### [Windows Firewall with Advanced Security](windows-firewall-with-advanced-security.md) #### [Isolating Windows Store Apps on Your Network](isolating-apps-on-your-network.md) #### [Securing End-to-End IPsec Connections by Using IKEv2 in Windows Server 2012](securing-end-to-end-ipsec-connections-by-using-ikev2.md) diff --git a/windows/keep-secure/change-history-for-keep-windows-10-secure.md b/windows/keep-secure/change-history-for-keep-windows-10-secure.md index ef564941db..6cd59dffcb 100644 --- a/windows/keep-secure/change-history-for-keep-windows-10-secure.md +++ b/windows/keep-secure/change-history-for-keep-windows-10-secure.md @@ -18,6 +18,9 @@ This topic lists new and updated topics in the [Keep Windows 10 secure](index.md |---------------------|------------| |[Protect derived domain credentials with Credential Guard](credential-guard.md) |Updated to include additional security qualifications starting with Window 10, version 1703.| |[Requirements and deployment planning guidelines for Device Guard](requirements-and-deployment-planning-guidelines-for-device-guard.md) |Updated to include additional security qualifications starting with Window 10, version 1703.| +|[Windows Defender SmartScreen overview](windows-defender-smartscreen-overview.md)|New | +|[Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](windows-defender-smartscreen-available-settings.md)|New | +|[Use Windows Defender Security Center to set Windows Defender SmartScreen for individual devices](windows-defender-smartscreen-set-individual-device.md)|New | ## February 2017 diff --git a/windows/keep-secure/code/example-script.ps1 b/windows/keep-secure/code/example-script.ps1 new file mode 100644 index 0000000000..e6563c2378 --- /dev/null +++ b/windows/keep-secure/code/example-script.ps1 @@ -0,0 +1,60 @@ +$authUrl = 'Your Authorization URL' +$clientId = 'Your Client ID' +$clientSecret = 'Your Client Secret' + + +Try +{ + $tokenPayload = @{ + "resource" = 'https://graph.windows.net' + "client_id" = $clientId + "client_secret" = $clientSecret + "grant_type"='client_credentials'} + + "Fetching an access token" + $response = Invoke-RestMethod $authUrl -Method Post -Body $tokenPayload + $token = $response.access_token + "Token fetched successfully" + + $headers = @{ + "Content-Type" = "application/json" + "Accept" = "application/json" + "Authorization" = "Bearer {0}" -f $token } + + $apiBaseUrl = "https://ti.securitycenter.windows.com/V1.0/" + + $alertDefinitionPayload = @{ + "Name" = "Test Alert" + "Severity" = "Medium" + "InternalDescription" = "A test alert used to demonstrate the Windows Defender ATP TI API feature" + "Title" = "Test alert." + "UxDescription" = "This is a test alert based on a sample custom alert definition. This alert was triggered manually using a provided test command. It indicates that the Threat Intelligence API has been properly enabled." + "RecommendedAction" = "No recommended action for this test alert." + "Category" = "SuspiciousNetworkTraffic" + "Enabled" = "true"} + "Creating an Alert Definition" + $alertDefinition = + Invoke-RestMethod ("{0}AlertDefinitions" -f $apiBaseUrl) ` + -Method Post -Headers $headers -Body ($alertDefinitionPayload | ConvertTo-Json) + "Alert Definition created successfully" + $alertDefinitionId = $alertDefinition.Id + + $iocPayload = @{ + "Type"="IpAddress" + "Value"="52.184.197.12" + "DetectionFunction"="Equals" + "Enabled"="true" + "AlertDefinition@odata.bind"="AlertDefinitions({0})" -f $alertDefinitionId } + + "Creating an Indicator of Compromise" + $ioc = + Invoke-RestMethod ("{0}IndicatorsOfCompromise" -f $apiBaseUrl) ` + -Method Post -Headers $headers -Body ($iocPayload | ConvertTo-Json) + "Indicator of Compromise created successfully" + + "All done!" +} +Catch +{ + 'Something went wrong! Got the following exception message: {0}' -f $_.Exception.Message +} diff --git a/windows/keep-secure/code/example.ps1 b/windows/keep-secure/code/example.ps1 index 278824d13a..6941c80627 100644 --- a/windows/keep-secure/code/example.ps1 +++ b/windows/keep-secure/code/example.ps1 @@ -1,8 +1,6 @@ -$tenantId = '{Your Tenant ID}' -$clientId = '{Your Client ID}' -$clientSecret = '{Your Client Secret}' - -$authUrl = "https://login.windows.net/{0}/oauth2/token" -f $tenantId +$authUrl = 'Your Authorization URL' +$clientId = 'Your Client ID' +$clientSecret = 'Your Client Secret' $tokenPayload = @{ "resource"='https://graph.windows.net' diff --git a/windows/keep-secure/code/example.py b/windows/keep-secure/code/example.py index 7bf906738c..6203b5230b 100644 --- a/windows/keep-secure/code/example.py +++ b/windows/keep-secure/code/example.py @@ -2,11 +2,9 @@ import json import requests from pprint import pprint -tenant_id="{your tenant ID}" -client_id="{your client ID}" -client_secret="{your client secret}" - -auth_url = "https://login.windows.net/{0}/oauth2/token".format(tenant_id) +auth_url="Your Authorization URL" +client_id="Your Client ID" +client_secret="Your Client Secret" payload = {"resource": "https://graph.windows.net", "client_id": client_id, diff --git a/windows/keep-secure/command-line-arguments-windows-defender-antivirus.md b/windows/keep-secure/command-line-arguments-windows-defender-antivirus.md new file mode 100644 index 0000000000..ea9f0e7d05 --- /dev/null +++ b/windows/keep-secure/command-line-arguments-windows-defender-antivirus.md @@ -0,0 +1,59 @@ +--- +title: Use the command line to manage Windows Defender AV +description: Windows Defender AV has a dedicated command-line utility that can run scans and configure protection. +keywords: run windows defender scan, run antivirus scan from command line, run windows defender scan from command line, mpcmdrun, defender +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + +# Use the mpcmdrun.exe command-line tool to configure and manage Windows Defender Antivirus + +**Applies to:** + +- Windows 10 + + +You can use a dedicated command-line tool to perform various functions in Windows Defender Antivirus. + +This utility can be handy when you want to automate the use of Windows Defender Antivirus. + +The utility is available in _%Program Files%\Windows Defender\MpCmdRun.exe_ and must be run from a command prompt. + +> [!NOTE] +> You may need to open an administrator-level version of the command prompt. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt. + + +The utility has the following commands: + +```DOS +MpCmdRun.exe [command] [-options] +``` + +Command | Description +:---|:--- +\- ? **or** -h | Displays all available options for the tool +\-Scan [-ScanType #] [-File [-DisableRemediation] [-BootSectorScan]][-Timeout ] | Scans for malicious software +\-Trace [-Grouping #] [-Level #]| Starts diagnostic tracing +\-GetFiles | Collects support information +\-RemoveDefinitions [-All] | Restores the installed signature definitions to a previous backup copy or to the original default set of signatures +\-AddDynamicSignature [-Path] | Loads a dynamic signature +\-ListAllDynamicSignature [-Path] | Lists the loaded dynamic signatures +\-RemoveDynamicSignature [-SignatureSetID] | Removes a dynamic signature +\-ValidateMapsConnection | Used to validate connection to the [cloud-delivered protection service](configure-network-connections-windows-defender-antivirus.md) + + + + +## Related topics + +- [Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) + + diff --git a/windows/keep-secure/configuration-management-reference-windows-defender-antivirus.md b/windows/keep-secure/configuration-management-reference-windows-defender-antivirus.md new file mode 100644 index 0000000000..edf44cdddc --- /dev/null +++ b/windows/keep-secure/configuration-management-reference-windows-defender-antivirus.md @@ -0,0 +1,44 @@ +--- +title: Windows Defender AV reference for management tools +description: Learn how Group Policy, Configuration Manager, PowerShell, WMI, Intune, and the comman line can be used to manage Windows Defender AV +keywords: group policy, gpo, config manager, sccm, scep, powershell, wmi, intune, defender, antivirus, antimalware, security, protection +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Reference topics for management and configuration tools + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +Windows Defender Antivirus can be managed and configured with the following tools: + +- Group Policy +- System Center Configuration Manager and Microsoft Intune +- PowerShell cmdlets +- Windows Management Instruction (WMI) +- The mpcmdrun.exe utility + +The topics in this section provide further information, links, and resources for using these tools in conjunction with Windows Defender AV. + +## In this section + +Topic | Description +---|--- +[Use Group Policy settings to configure and manage Windows Defender AV](use-group-policy-windows-defender-antivirus.md)|List of all Group Policy settings located in the Windows 10, version 1703 ADMX templates +[Use System Center Configuration Manager and Microsoft Intune to configure and manage Windows Defender AV](use-intune-config-manager-windows-defender-antivirus.md)|Information on using System Center Configuration Manager and Microsoft Intune to deploy, manage, report, and configure Windows Defender AV +[Use PowerShell cmdlets to configure and manage Windows Defender AV](use-powershell-cmdlets-windows-defender-antivirus.md)|Instructions on using PowerShell cmdlets in the Defender Module and links to documentation for all cmdlets and allowed parameters +[Use Windows Management Instrumentation (WMI) to configure and manage Windows Defender AV](use-wmi-windows-defender-antivirus.md)| Instructions on using WMI to manage Windows Defender AV and links to documentation for the Windows Defender WMIv2 APIs (including all classes, methods, and properties) +[Use the mpcmdrun.exe command-line tool to configure and manage Windows Defender Antivirus](command-line-arguments-windows-defender-antivirus.md)|Instructions on using the dedicated command-line tool to manage and use Windows Defender AV + diff --git a/windows/keep-secure/configure-advanced-scan-types-windows-defender-antivirus.md b/windows/keep-secure/configure-advanced-scan-types-windows-defender-antivirus.md new file mode 100644 index 0000000000..cd5a3e9874 --- /dev/null +++ b/windows/keep-secure/configure-advanced-scan-types-windows-defender-antivirus.md @@ -0,0 +1,158 @@ +--- +title: Configure advanced scanning types for Windows Defender AV +description: You can configure Windows Defender AV to scan email storage files, back-up or reparse points, network files, and archived files (such as .zip files). +keywords: advanced scans, scanning, email, archive, zip, rar, archive, reparse scanning +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure email, removable storage, network, reparse point, and archive scanning in Windows Defender AV + + +**Applies to** +- Windows 10 + + + + + + + +## Manage email scans in Windows Defender + +You can use Windows Defender to scan email files. Malware can install itself and hide in email files, and although real-time protection offers you the best protection from email malware, you can also scan emails stored on your PC or server with Windows Defender. +> **Important:** Mail scanning only applies to on-demand and scheduled scans, not on-access scans. + +Windows Defender scans Microsoft Office Outlook 2003 and older email files. We identify the file type at run-time based on the content of the file, not on location or extension. +> **Note: ** Scanning email files might increase the time required to complete a scan. + +Windows Defender can extract embedded objects within a file (attachments and archived files, for example) and scan internally. +> **Note:** While Windows Defender can be configured to scan email files, it can only remediate threats detected inside certain files, for example: +- DBX +- MBX +- MIME + +You can configure Windows Defender to scan PST files used by Outlook 2003 or older versions (where the archive type is set to non-uni-code), but Windows Defender cannot remediate threats detected inside PST files. We recommend using real-time protection to protect against email malware. + +If Windows Defender detects a threat inside an email, it will show you the following information to assist you in identifying the compromised email, so you can remediate the threat: +- Email subject +- Attachment name +Email scanning in Windows Defender is turned off by default. There are three ways you can manage scans through Windows Defender: +- *Group Policy* settings +- WMI +- PowerShell +> **Important:** There are some risks associated with scanning some Microsoft Outlook files and email messages. You can read about tips and risks associated with scanning Outlook files and email messages in the following articles: +- [Scanning Outlook files in Outlook 2013](https://technet.microsoft.com/library/dn769141.aspx#bkmk-1) +- [Scanning email messages in Outlook 2013](https://technet.microsoft.com/library/dn769141.aspx#bkmk-2) + +## Use *Group Policy* settings to enable email scans + +This policy setting allows you to turn on email scanning. When email scanning is enabled, the engine will parse the mailbox and mail files to analyze the mail bodies and attachments. + +Turn on email scanning with the following *Group Policy* settings: +1. Open the **Group Policy Editor**. +2. In the **Local Computer Policy** tree, expand **Computer Configuration**, then **Administrative Templates**, then **Windows Components**, then **Windows Defender**. +3. Click **Scan**. +4. Double-click **Turn on e-mail scanning**. + + This will open the **Turn on e-mail scanning** window: + + ![turn on e-mail scanning window](images/defender-scanemailfiles.png) + +5. Select **Enabled**. +6. Click **OK** to apply changes. + +## Use WMI to disable email scans + +You can write a WMI script or application to disable email scanning. Read more about [WMI in this article](https://msdn.microsoft.com/library/windows/desktop/dn439477.aspx), and read about [Windows Preference classes in this article](https://msdn.microsoft.com/library/windows/desktop/dn455323.aspx). + +Use the **DisableEmailScanning** property of the **MSFT\_MpPreference** class (part of the Windows DefenderWMI provider) to enable or disable this setting: +**DisableEmailScanning** +Data type: **boolean** +Access type: Read-only +Disable email scanning. + +## Use PowerShell to enable email scans + +You can also enable email scanning using the following PowerShell parameter: +1. Open PowerShell or PowerShellIntegrated Scripting Environment (ISE). +2. Type **Set-MpPreference -DisableEmailScanning $false**. + +Read more about this in: +- [Scripting with Windows PowerShell](https://technet.microsoft.com/library/bb978526.aspx) +- [Defender Cmdlets](https://technet.microsoft.com/library/dn433280.aspx) + +## Manage archive scans in Windows Defender + +You can use Windows Defender to scan archive files. Malware can install itself and hide in archive files, and although real-time protection offers you the best protection from malware, you can also scan archives stored on your PC or server with Windows Defender. +> **Important:** Archive scanning only applies to on-demand and scheduled scans, not on-access scans. + +Archive scanning in Windows Defender is turned on by default. There are four ways you can manage scans through Windows Defender: +- *Group Policy* settings +- WMI +- PowerShell +- Endpoint Protection +> **Note:** Scanning archive files might increase the time required to complete a scan. + +If you exclude an archive file type by using the **Extensions** box, Windows Defender will not scan files with that extension (no matter what the content is), even when you have selected the **Scan archive files** check box. For example, if you exclude .rar files but theres a .r00 file thats actually .rar content, it will still be scanned if archive scanning is enabled. + +## Use *Group Policy* settings to enable archive scans + +This policy setting allows you to turn on archive scanning. + +Turn on email scanning with the following *Group Policy* settings: +1. Open the **Group Policy Editor**. +2. In the **Local Computer Policy** tree, expand **Computer Configuration**, then **Administrative Templates**, then **Windows Components**, then **Windows Defender**. +3. Click **Scan**. +4. Double-click **Scan archive files**. + + This will open the **Scan archive files** window: + + ![scan archive files window](images/defender-scanarchivefiles.png) + +5. Select **Enabled**. +6. Click **OK** to apply changes. + +There are a number of archive scan settings in the **Scan** repository you can configure through *Group Policy*, for example: +- Maximum directory depth level into which archive files are unpacked during scanning + + ![specify the maximum depth to scan archive files window](images/defender-scanarchivedepth.png) + +- Maximum size of archive files that will be scanned + + ![specify the maximum size of archive files to be scanned window](images/defender-scanarchivesize.png) + +- Maximum percentage CPU utilization permitted during a scan + + ![specify the maximum percentage od cpu utilization during a scan window](images/defender-scanarchivecpu.png) + +## Use WMI to disable archive scans + +You can write a WMI script or application to disable archive scanning. Read more about [WMI in this article](https://msdn.microsoft.com/library/windows/desktop/dn439477.aspx), and read about [Windows Preference classes in this article](https://msdn.microsoft.com/library/windows/desktop/dn455323.aspx). + +Use the **DisableArchiveScanning** property of the **MSFT\_MpPreference** class (part of the Windows DefenderWMI provider) to enable or disable this setting: +**DisableArchiveScanning** +Data type: **boolean** +Access type: Read-only +Disable archive scanning. + +## Use PowerShell to enable archive scans + +You can also enable archive scanning using the following PowerShell parameter: +1. Open PowerShell or PowerShellISE. +2. Type **Set-MpPreference -DisableArchiveScanning $false**. + +Read more about this in: +- [Scripting with Windows PowerShell](https://technet.microsoft.com/library/bb978526.aspx) +- [Defender Cmdlets](https://technet.microsoft.com/library/dn433280.aspx) + +## Use Endpoint Protection to configure archive scans + +In Endpoint Protection, you can use the advanced scanning options to configure archive scanning. For more information, see [What are advanced scanning options?](https://technet.microsoft.com/library/ff823807.aspx) + diff --git a/windows/keep-secure/configure-block-at-first-sight-windows-defender-antivirus.md b/windows/keep-secure/configure-block-at-first-sight-windows-defender-antivirus.md new file mode 100644 index 0000000000..7bd0777196 --- /dev/null +++ b/windows/keep-secure/configure-block-at-first-sight-windows-defender-antivirus.md @@ -0,0 +1,149 @@ +--- +title: Enable Block at First Sight to detect malware in seconds +description: Enable the Block at First sight feature to detect and block malware within seconds, and validate that it is configured correctly. +keywords: scan, BAFS, malware, first seen, first sight, cloud, defender +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + + + + +# Enable the Block at First Sight feature + +**Applies to** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy +- Windows Defender Security Center app + + +Block at First Sight is a feature of Windows Defender Antivirus cloud-delivered protection that provides a way to detect and block new malware within seconds. + +It is enabled by default when certain pre-requisite settings are also enabled. In most cases, these pre-requisite settings are also enabled by default, so the feature is running without any intervention. You can use group policy settings to confirm the feature is enabled. + +You can also [specify how long the file should be prevented from running](configure-cloud-block-timeout-period-windows-defender-antivirus.md) while the cloud-based protection service analyzes the file. + +> [!IMPORTANT] +> There is no specific individual setting in System Center Configuration Manager to enable or disable Block at First Sight. It is enabled by default when the pre-requisite settings are configured correctly. You must use Group Policy settings to enable or disable the feature. + +## How it works + +When a Windows Defender Antivirus client encounters a suspicious but undetected file, it queries our cloud protection backend. The cloud backend will apply heuristics, machine learning, and automated analysis of the file to determine the files as malicious or clean. The following video describes how this feature works. + +The Block at first sight feature only uses the cloud protection backend for executable files that are downloaded from the Internet, or originating from the Internet zone. A hash value of the EXE file is checked via the cloud backend to determine if this is a previously undetected file. + + + +If the cloud backend is unable to make a determination, the file will be locked by Windows Defender AV while a copy is uploaded to the cloud. The cloud will perform additional analysis to reach a determination before it allows the file to run or blocks it in all future encounters, depending on whether the file is determined to be malicious or safe. + +In many cases this process can reduce the response time for new malware from hours to seconds. + + +## Confirm and validate Block at First Sight is enabled + +Block at First Sight requires a number of Group Policy settings to be configured correctly or it will not work. Usually, these settings are already enabled in most default Windows Defender AV deployments in enterprise networks. + + + +### Confirm Block at First Sight is enabled with Group Policy + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > MAPS** and configure the following Group Policies: + + 1. Double-click the **Join Microsoft MAPS** setting and ensure the option is set to **Enabled**. Click **OK**. + + 1. Double-click the **Send file samples when further analysis is required** setting and ensure the option is set to **Enabled** and the additional options are either of the following: + + 1. Send safe samples (1) + + 1. Send all samples (3) + + > [!WARNING] + > Setting to 0 (Always Prompt) will lower the protection state of the device. Setting to 2 (Never send) means the "Block at First Sight" feature will not function. + + 1. Click **OK**. + +1. In the **Group Policy Management Editor**, expand the tree to **Windows components > Windows Defender Antivirus > Real-time Protection**: + + 1. Double-click the **Scan all downloaded files and attachments** setting and ensure the option is set to **Enabled**. Click **OK**. + + 1. Double-click the **Turn off real-time protection** setting and ensure the option is set to **Disabled**. Click **OK**. + +If you had to change any of the settings, you should re-deploy the Group Policy Object across your network to ensure all endpoints are covered. + + +### Confirm Block at First Sight is enabled with the Windows Defender Security Center app + +You can confirm that Block at First Sight is enabled in Windows Settings. + +The feature is automatically enabled as long as **Cloud-based protection** and **Automatic sample submission** are both turned on. + +**Confirm Block at First Sight is enabled on individual clients** + +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then the **Virus & threat protection settings** label: + +![Screenshot of the Virus & threat protection settings label in the Windows Defender Security Center app](images/defender/wdav-protection-settings-wdsc.png) + +3. Confirm that **Cloud-based Protection** and **Automatic sample submission** are switched to **On**. + +> [!NOTE] +> If the pre-requisite settings are configured and deployed using Group Policy, the settings described in this section will be greyed-out and unavailable for use on individual endpoints. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings. + + +### Validate Block at First Sight is working + +You can validate that the feature is working by following the steps outlined in the [Validate connections between your network and the cloud](configure-network-connections-windows-defender-antivirus.md#validate) topic. + + +## Disable Block at First Sight + +> [!WARNING] +> Disabling the Block at First Sight feature will lower the protection state of the endpoint and your network. + +You may choose to disable the Block at First Sight feature if you want to retain the pre-requisite settings without using Block at First Sight protection. You might wish to do this if you are experiencing latency issues or you want to test the feature's impact on your network. + +**Disable Block at First Sight with Group Policy** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree through **Windows components > Windows Defender Antivirus > MAPS**. + +1. Double-click the **Configure the Block at First Sight feature** setting and set the option to **Disabled**. + + > [!NOTE] + > Disabling the Block at First Sight feature will not disable or alter the pre-requisite group policies. + + +## Related topics + +- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) +- [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) + + diff --git a/windows/keep-secure/configure-cloud-block-timeout-period-windows-defender-antivirus.md b/windows/keep-secure/configure-cloud-block-timeout-period-windows-defender-antivirus.md new file mode 100644 index 0000000000..8846515965 --- /dev/null +++ b/windows/keep-secure/configure-cloud-block-timeout-period-windows-defender-antivirus.md @@ -0,0 +1,74 @@ +--- +title: Configure the Windows Defender AV cloud block timeout period +description: You can configure how long Windows Defender Antivirus will block a file from running while waiting for a cloud determination. +keywords: windows defender antivirus, antimalware, security, defender, cloud, timeout, block, period, seconds +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure the cloud block timeout period + + + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy + + + + + + +When Windows Defender Antivirus is suspicious of a file, it can prevent the file from running while it queries the [Windows Defender Antivirus cloud-protection service](utilize-microsoft-cloud-protection-windows-defender-antivirus.md). + +The default period that the file will be [blocked](configure-block-at-first-sight-windows-defender-antivirus.md) for is 10 seconds. You can specify an additional period of time to wait before the file is allowed to run. This can help ensure there is enough time to receive a proper determination from the Windows Defender Antivirus cloud. + + + +## Prerequisites to use the extended cloud block timeout + +The [Block at First Sight](configure-block-at-first-sight-windows-defender-antivirus.md) feature and its prerequisites must be enabled before you can specifiy an extended timeout period. + +## Specify the extended timeout period + +You can use Group Policy to specify an extended timeout for cloud checks. + +**Use Group Policy to specify an extended timeout period:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +2. In the **Group Policy Management Editor** go to **Computer configuration**. + +3. Click **Policies** then **Administrative templates**. + +4. Expand the tree to **Windows components > Windows Defender Antivirus > MpEngine** + +5. Double-click the **Configure extended cloud check** setting and ensure the option is enabled. Specify the additional amount of time to prevent the file from running while waiting for a cloud determination. You can specify the additional time, in seconds, from 1 second to 50 seconds. This time will be added to the default 10 seconds. + +6. Click **OK**. + + +## Related topics + +- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) +- [Utilize Microsoft cloud-delivered protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) +- [Configure the Block at First Sight feature](configure-block-at-first-sight-windows-defender-antivirus.md) +- [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) + + + + diff --git a/windows/keep-secure/configure-end-user-interaction-windows-defender-antivirus.md b/windows/keep-secure/configure-end-user-interaction-windows-defender-antivirus.md new file mode 100644 index 0000000000..47b2f3f968 --- /dev/null +++ b/windows/keep-secure/configure-end-user-interaction-windows-defender-antivirus.md @@ -0,0 +1,39 @@ +--- +title: Configure how users can interact with Windows Defender AV +description: Configure how end-users interact with Windows Defender AV, what notifications they see, and if they can override settings. +keywords: endpoint, user, interaction, notifications, ui lockdown mode, headless mode, hide interface +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure end-user interaction with Windows Defender Antivirus + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy + +You can configure how users of the endpoints on your network can interact with Windows Defender Antivirus. + +This includes whether they see the Windows Defender AV interface, what notifications they see, and if they can locally override globally deployed Group Policy settings. + +## In this section + +Topic | Description +---|--- +[Configure the notifications that appear on endpoints](configure-notifications-windows-defender-antivirus.md) | Configure and customize additional notifications, customized text for notifications, and notifications about reboots for remediation +[Prevent users from seeing or interacting with the Windows Defender AV user interface](prevent-end-user-interaction-windows-defender-antivirus.md) | Hide the user interface from users +[Prevent users from locally modifying policy settings](configure-local-policy-overrides-windows-defender-antivirus.md) | Prevent (or allow) users from overriding policy settings on their individual endpoints diff --git a/windows/keep-secure/configure-exclusions-windows-defender-antivirus.md b/windows/keep-secure/configure-exclusions-windows-defender-antivirus.md new file mode 100644 index 0000000000..11e86abb86 --- /dev/null +++ b/windows/keep-secure/configure-exclusions-windows-defender-antivirus.md @@ -0,0 +1,141 @@ +--- +title: Set up exclusions for Windows Defender AV scans +description: You can exclude files (including files modified by specified processes) and folders from being scanned by Windows Defender AV +keywords: +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Exclude files and processes from Windows Defender AV scans + + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell +- Windows Management Instrumentation (WMI) +- Microsoft Intune +- Windows Defender Security Center + +You can exclude certain files, folders, and process-modified files from being scanned by Windows Defender AV. The exclusions apply to both [scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) and [always-on real-time protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md). + +Changes made via Group Policy to the exclusion lists will show in the lists in the [Windows Defender Security Center app](windows-defender-security-center-antivirus.md#exclusions). + +However, changes made in the Windows Defender Security Center app will not show in the lists in the Group Policy settings. + + +## Exclude file extensions from Windows Defender AV scans + +You can exclude certain file extenstions from being scanned by Windows Defender AV. + +**Use Group Policy to exclude specified file extensions from scans:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Exclusions**. + + +6. Double-click the **Extension Exclusions** setting and add the exclusions: + + 1. Set the option to **Enabled**. + 2. Under the **Options** section, click **Show...** + 3. Enter each file extension on its own line under the **Value name** column. Enter **0** in the **Value** column for all processes. + +7. Click **OK**. + +![The Group Policy setting for file exclusions](images/defender/wdav-extension-exclusions.png) + + + + +## Exclude paths and files from Windows Defender AV scans + +**Use Group Policy to exclude specified paths or folders from scans:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Exclusions**. + + +6. Double-click the **Path Exclusions** setting and add the exclusions: + + 1. Set the option to **Enabled**. + 2. Under the **Options** section, click **Show...** + 3. Enter each path or file on its own line under the **Value name** column. If you are entering a file, ensure you enter a fully qualified path to the file, including the drive letter, folder path, filename, and extesnsion. Enter **0** in the **Value** column for all processes. + +7. Click **OK**. + +![The Group Policy setting for folder exclusions](images/defender/wdav-path-exclusions.png) + + +## Exclude files opened by processes from Windows Defender AV scns + +You can exclude files that are opened by specified processes from being scanned. The specified process won't be excluded - but any files that are opened by that process will be. + +You can only exclude executable files. + +**Use Group Policy to exclude files that have been used or modified by specified processes from scans:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Exclusions**. + + +6. Double-click the **Process Exclusions** setting and add the exclusions: + + 1. Set the option to **Enabled**. + 2. Under the **Options** section, click **Show...** + 3. Enter each process on its own line under the **Value name** column. Ensure you enter a fully qualified path to the process, including the drive letter, folder path, filename, and extesnsion. Enter **0** in the **Value** column for all processes. + +7. Click **OK**. + +![The Group Policy setting for specifying process exclusions](images/defender/wdav-process-exclusions.png) + + + ## Configure auto exclusions lists for Windows Server deployments + +If you are using Windows Defender AV to protect Windows Server endpoints or machines, you are [automatically enrolled in certain exclusions](https://technet.microsoft.com/en-us/windows-server-docs/security/windows-defender/automatic-exclusions-for-windows-defender), as defined by your specified Server role. + +These exclusions will not appear in the standard exclusion lists shown in the [Windows Defender Security Center app](windows-defender-security-center-antivirus.md#exclusions). + +You can also [add custom exclusions to the auto exclusions with PowerShell](https://technet.microsoft.com/en-us/windows-server-docs/security/windows-defender/windows-defender-overview-windows-server#BKMK_DefExclusions). +Exclusions | Turn off Auto Exclusions | + + + + + + + +## Related topics + +- [Customize, initiate, and review the results of Windows Defender AV scans and remediation](customize-run-review-remediate-scans-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) \ No newline at end of file diff --git a/windows/keep-secure/configure-local-policy-overrides-windows-defender-antivirus.md b/windows/keep-secure/configure-local-policy-overrides-windows-defender-antivirus.md new file mode 100644 index 0000000000..fb1993e2a1 --- /dev/null +++ b/windows/keep-secure/configure-local-policy-overrides-windows-defender-antivirus.md @@ -0,0 +1,103 @@ +--- +title: Configure local overrides for Windows Defender AV settings +description: Enable or disable users from locally changing settings in Windows Defender AV. +keywords: local override, local policy, group policy, gpo, lockdown,merge, lists +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Prevent or allow users to locally modify Windows Defender AV policy settings + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy + + +By default, Windows Defender AV settings that are deployed via a Group Policy Object to the endpoints in your network will prevent users from locally changing the settings. You can change this in some instances. + +For example, it may be necessary to allow certain user groups (such as security researchers and threat investigators) further control over individual settings on the endpoints they use. + +## Configure local overrides for Windows Defender AV settings + +The default setting for these policies is **Disabled**. + +If they are set to **Enabled**, users on endpoints can make changes to the associated setting with the [Windows Defender Security Center](windows-defender-security-center-antivirus.md) app, local Group Policy settings, and PowerShell cmdlets (where appropriate). + +The following table lists each of the override policy setting and the configuration instructions for the associated feature or setting. + +To configure these settings: + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus** and then the **Location** specified in the table below. + +6. Double-click the policy **Setting** as specified in the table below, and set the option to your desired configuration. Click **OK**, and repeat for any other settings. + +7. Deploy the Group Policy Object as usual. + +Location | Setting | Impact if **Enabled** | Configuration topic +---|---|---|--- +MAPS | Configure local setting override for reporting to Microsoft MAPS | User can disable cloud protection | [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) +Quarantine | Configure local setting override for the removal of items from Quarantine folder | User can change the number of days threats are kept in the quarantine folder before being removed |[Configure remediation for scans](configure-remediation-windows-defender-antivirus.md) +Real-time protection | Configure local setting override for monitoring file and program activity on your computer | User can disable real-time protection | [Enable and configure Windows Defender AV always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +Real-time protection | Configure local setting override for monitoring for incoming and outgoing file activity | User can change direction for file activity monitoring | [Enable and configure Windows Defender AV always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +Real-time protection | Configure local setting override for scanning all downloaded files and attachments | Allow user to disable scans of downloaded files and attachments | [Enable and configure Windows Defender AV always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +Real-time protection | Configure local setting override for turn on behavior monitoring | User | [Enable and configure Windows Defender AV always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +Real-time protection | Configure local setting override to turn on real-time protection | xxx | [Enable and configure Windows Defender AV always-on protection and monitoring](configure-real-time-protection-windows-defender-antivirus.md) +Remediation | Configure local setting override for the time of day to run a scheduled full scan to complete remediation | xxx | [Configure remediation for scans](configure-remediation-windows-defender-antivirus.md) +Scan | Configure local setting override for maximum percentage of CPU utilization | xxx | [Configure and run scans](run-scan-windows-defender-antivirus.md) +Scan | Configure local setting override for schedule scan day | xxx | [Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) +Scan | Configure local setting override for scheduled quick scan time | xxx | [Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) +Scan | Configure local setting override for scheduled scan time | xxx | [Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) +Scan | Configure local setting override for the scan type to use for a scheduled scan | xxx | [Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) + + + + + + +## Configure how locally and globally defined threat remediation and exclusions lists are merged + +You can also configure how locally defined lists are combined or merged with globally defined lists. This setting applies to [exclusion lists](configure-exclusions-windows-defender-antivirus.md) and [specified remediation lists](configure-remediation-windows-defender-antivirus.md). + +By default, lists that have been configured in local group policy and the Windows Defender Security Center app are merged with lists that are defined by the appropriate GPO that you have deployed on your network. Where there are conflicts, the globally defined list takes precendence. + +You can disable this setting to ensure that only globally defined lists (such as those from any deployed GPOs) are used. + + +**Use Group Policy to disable local list merging:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus**. + +6. Double-click the **Configure local administrator merge behavior for lists** setting and set the option to **Enabled**. Click **OK**. + + + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) +- [Configure end-user interaction with Windows Defender AV](configure-end-user-interaction-windows-defender-antivirus.md) \ No newline at end of file diff --git a/windows/keep-secure/configure-network-connections-windows-defender-antivirus.md b/windows/keep-secure/configure-network-connections-windows-defender-antivirus.md new file mode 100644 index 0000000000..4bba9f4ec2 --- /dev/null +++ b/windows/keep-secure/configure-network-connections-windows-defender-antivirus.md @@ -0,0 +1,199 @@ +--- +title: Configure and test Windows Defender Antivirus network connections +description: Configure and test your connection to the Windows Defender Antivirus cloud-delivered protection service. +keywords: windows defender antivirus, antimalware, security, defender, cloud, aggressiveness, protection level +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure and validate network connections for Windows Defender Antivirus + + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + + +To ensure Windows Defender Antivirus cloud-delivered protection works properly, you need to configure your network to allow connections between your endpoints and certain Microsoft servers. + +This topic lists the connections that must be allowed, including firewall rules, and provides instructions for validating your connection. This will help ensure you receive the best protection from our cloud-delivered protection services. + +See the Enterprise Mobility and Security blog post [Important changes to Microsoft Active Protection Services endpoint](https://blogs.technet.microsoft.com/enterprisemobility/2016/05/31/important-changes-to-microsoft-active-protection-service-maps-endpoint/) for some details about network connectivity. + +## Allow connections to the Windows Defender Antivirus cloud + +The Windows Defender Antivirus cloud provides fast, strong protection for your endpoints. Enabling the cloud-delivered protection service is optional, however it is highly recommend as it provides very important protection against malware on your endpoints and across your network. + +>[!NOTE] +>The Windows Defender Antivirus cloud service is a mechanism for delivering updated protection to your network and endpoints. Although it is called a cloud service, it is not simply protection for files stored in the cloud, rather it uses distributed resources and machine learning to deliver protection to your endpoints at a rate that is far faster than traditional signature updates. + +See the [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) topic for details on enabling the service with Group Policy, System Center Configuration Manager, PowerShell cmdlets, Microsoft Intune, or on individual clients in the Windows Defender Security Center app. + +After you've enabled the service, you may need to configure your network or firewall to allow connections between it and your endpoints. + +The following table lists the services and their associated URLs that your network must be able to connect to. You should ensure there are no firewall or network filtering rules that would deny access to these URLs, or you may need to create an **allow** rule specifically for them: + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ServiceDescriptionURL
+ Windows Defender Antivirus cloud-based protection service, also referred to as Microsoft Active Protection Service (MAPS) + + Used by Windows Defender Antivirus to provide cloud-based protection + +*.wdcp.microsoft.com*
+*.wdcpalt.microsoft.com* +
+Microsoft Update Service (MU) + +Signature and product updates + +*.updates.microsoft.com +
+ Definition updates alternate download location (ADL) + + Alternate location for Windows Defender Antivirus definition updates if the installed definitions fall out of date (7 or more days behind) + +*.download.microsoft.com +
+ Malware submission storage + + Upload location for files submitted to Microsoft via the Submission form or automatic sample submission + +*.blob.core.windows.net +
+Certificate Revocation List (CRL) + +Used by Windows when creating the SSL connection to MAPS for updating the CRL + +http://www.microsoft.com/pkiops/crl/
+http://www.microsoft.com/pkiops/certs
+http://crl.microsoft.com/pki/crl/products
+http://www.microsoft.com/pki/certs + +
+Symbol Store + +Used by Windows Defender Antivirus to restore certain critical files during remediation flows + +https://msdl.microsoft.com/download/symbols +
+Universal Telemetry Client + +Used by Windows to send client telemetry, Windows Defender Antivirus uses this for product quality monitoring purposes + +This update uses SSL (TCP Port 443) to download manifests and upload telemetry to Microsoft that uses the following DNS endpoints:
  • vortex-win.data.microsoft.com
  • settings-win.data.microsoft.com
+ + + + +## Validate connections between your network and the cloud + +After whitelisting the URLs listed above, you can test if you are connected to the Windows Defender AV cloud and are correctly reporting and receiving information to ensure you are fully protected. + +**Use the cmdline tool to validate cloud-delivered protection:** + +Use the following argument with the Windows Defender AV command line utility (*mpcmdrun.exe*) to verify that your network can communicate with the Windows Defender AV cloud: + +```DOS +MpCmdRun - ValidateMapsConnection +``` + +See [Use the mpcmdrun.exe commandline tool to configure and manage Windows Defender Antivirus](command-line-arguments-windows-defender-antivirus.md) for more information on how to use the *mpcmdrun.exe* utility. + +**Attempt to download a fake malware file from Microsoft:** + +You can download a sample file that Windows Defender AV will detect and block if you are properly connected to the cloud. + +Download the file by visiting the following link: +- http://aka.ms/ioavtest + +>[!NOTE] +>This file is not an actual piece of malware. It is a fake file that is designed to test if you are properly connected to the cloud. + +If you are properly connected, you will see a warning notification from Windows Defender Antivirus: + +![Windows Defender Antivirus notification informing the user that malware was found](images/defender/wdav-malware-detected.png) + +If you are using Microsoft Edge, you'll also see a notification message: + +![Microsoft Edge informing the user that malware was found](images/defender/wdav-bafs-edge.png) + +A similar message occurs if you are uding Internet Explorer: + +![Windows Defender Antivirus notification informing the user that malware was found](images/defender/wdav-bafs-ie.png) + +You will also see a detection under **Quarantined threats** in the **Scan history** section in the Windows Defender Security Center app: + +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then the **Scan history** label: + + ![Screenshot of the Scan history label in the Windows Defender Security Center app](images/defender/wdav-history-wdsc.png) + +3. Under the **Quarantined threats** section, click the **See full history** label to see the detected fake malware: + + ![Screenshot of quarantined items in the Windows Defender Security Center app](images/defender/wdav-quarantined-history-wdsc.png) + +The Windows event log will also show [Windows Defender client event ID 2050](troubleshoot-windows-defender-antivirus.md). + +>[!IMPORTANT] +>You will not be able to use a proxy auto-config (.pac) file to test network connections to these URLs. You will need to verify your proxy servers and any network filtering tools manually to ensure connectivity. + + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-in-windows-10.md) +- [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) +- [Run a Windows Defender scan from the command line](command-line-arguments-windows-defender-antivirus.md) and [Command line arguments](command-line-arguments-windows-defender-antivirus.md) +- [Important changes to Microsoft Active Protection Services endpoint](https://blogs.technet.microsoft.com/enterprisemobility/2016/05/31/important-changes-to-microsoft-active-protection-service-maps-endpoint/) + + diff --git a/windows/keep-secure/configure-notifications-windows-defender-antivirus.md b/windows/keep-secure/configure-notifications-windows-defender-antivirus.md new file mode 100644 index 0000000000..2244318943 --- /dev/null +++ b/windows/keep-secure/configure-notifications-windows-defender-antivirus.md @@ -0,0 +1,129 @@ +--- +title: Configure notifications for Windows Defender Antivirus +description: Configure and customize notifications from Windows Defender AV. +keywords: notifications, defender, endpoint, management, admin +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure the notifications that appear on endpoints + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy +- Windows Defender Security Center app + +In Windows 10, application notifications about malware detection and remediation by Windows Defender are more robust, consistent, and concise. + +Notifications will appear on endpoints when manually triggered and scheduled scans are completed and threats are detected. These notifications will also be seen in the **Notification Center**, and a summary of scans and threat detections will also appear at regular time intervals. + +You can also configure how standard notifications appear on endpoints, such as notfications for reboot or when a threat has been detected and remediated. + +## Configure the additional notifications that appear on endpoints + +You can configure the display of additional notifications, such as recent threat detection summaries, in the [Windows Defender Security Center app](windows-defender-security-center-antivirus.md) and with Group Policy. + +> [!NOTE] +> In Windows 10, version 1607 the feature was called **Enhanced notifications** and could be configured under **Windows Settings** > **Update & security** > **Windows Defender**. In Group Policy settings in all versions of Windows 10 it is called **Enhanced notifications**. + +> [!IMPORTANT] +> Disabling additional notifications will not disable critical notifications, such as threat detection and remediation alerts. + +**Use the Windows Defender Security Center app to disable additional notifications:** + +1. Open the Windows Defender Security Center by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then the **Virus & threat protection settings** label: + +![Screenshot of the Virus & threat protection settings label in the Windows Defender Security Center](images/defender/wdav-protection-settings-wdsc.png) + +3. Scroll to the **Notifications** section and click **Change notification settings**. + +4. Slide the switch to **Off** or **On** to disable or enable additional notifications. + +**Use Group Policy to disable additional notifications:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Reporting**. + +6. Double-click the **Turn off enhanced notifications** setting and set the option to **Enabled**. Click **OK**. This will prevent additional notifications from appearing. + + +## Configure standard notifications on endpoints + +You can use Group Policy to: +- Display additional, customized text on endpoints when the user needs to perform an action +- Hide all notifications on endpoints +- Hide reboot notifications on endpoints + +Hiding notifications can be useful in situations where you cannot hide the entire Windows Defender AV interface. See [Prevent users from seeing or interacting with the Windows Defender AV user interface](prevent-end-user-interaction-windows-defender-antivirus.md) for more information. + +> [!NOTE] +> Hiding notifications will only occur on endpoints to which the policy has been deployed. Notifications related to actions that must be taken (such as a reboot) will still appear on the [System Center Configuration Manager Endpoint Protection monitoring dashboard and reports](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/monitor-endpoint-protection). + +**Use Group Policy to display additional, custom text in notifications:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Client interface**. + +6. Double-click the **Display additional text to clients when they need to perform an action** setting and set the option to **Enabled**. + +7. Enter the additional text you want to be shown to users. Click **OK**. + +**Use Group Policy to hide notifications:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Client interface**. + +6. Double-click the **Suppress all notifications** setting and set the option to **Enabled**. Click **OK**. This will prevent additional notifications from appearing. + +**Use Group Policy to hide reboot notifications:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Client interface**. + +6. Double-click the **Suppresses reboot notifications** setting and set the option to **Enabled**. Click **OK**. This will prevent additional notifications from appearing. + + + + + + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) +- [Configure end-user interaction with Windows Defender AV](configure-end-user-interaction-windows-defender-antivirus.md) diff --git a/windows/keep-secure/configure-protection-features-windows-defender-antivirus.md b/windows/keep-secure/configure-protection-features-windows-defender-antivirus.md new file mode 100644 index 0000000000..bf1f2f595e --- /dev/null +++ b/windows/keep-secure/configure-protection-features-windows-defender-antivirus.md @@ -0,0 +1,43 @@ +--- +title: Enable and configure protection features in Windows Defender AV +description: Enable behavior-based, heuristic, and real-time protection in Windows Defender AV. +keywords: heuristic, machine-learning, behavior monitor, real-time protection, always-on, windows defender antivirus, antimalware, security, defender +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure behavioral, heuristic, and real-time protection + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +Windows Defender Antivirus uses several methods to provide threat protection: + +- Cloud-delivered protection for near-instant detection and blocking of new and emerging threats +- Always-on scanning, using file and process behavior monitoring and other heuristics (also known as "real-time protection") +- Dedicated protection updates based on machine-learning, human and automated big-data analysis, and in-depth threat resistance research + +You can configure how Windows Defender AV uses these methods with Group Policy, System Center Configuration Manage, PowerShell cmdlets, and Windows Management Instrumentation (WMI). + +This section covers configuration for always-on scanning, including how to detect and block apps that are deemed unsafe, but may not be detected as malware. + +See the [Utilize Microsoft cloud-delivered protection](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) section for how to enable and configure Windows Defender AV cloud-delivered protection. + + +## In this section + + Topic | Description +---|--- +[Detect and block potentially unwanted applications](detect-block-potentially-unwanted-apps-windows-defender-antivirus.md) | Detect and block apps that may be unwanted in your network, such as adware, browser modifiers and toolbars, and rogue or fake antivirus apps +[Enable and configure Windows Defender AV protection capabilities](configure-real-time-protection-windows-defender-antivirus.md) | Enable and configure real-time protection, heuristics, and other always-on antivirus monitoring features \ No newline at end of file diff --git a/windows/keep-secure/configure-real-time-protection-windows-defender-antivirus.md b/windows/keep-secure/configure-real-time-protection-windows-defender-antivirus.md new file mode 100644 index 0000000000..ad4ca873ec --- /dev/null +++ b/windows/keep-secure/configure-real-time-protection-windows-defender-antivirus.md @@ -0,0 +1,99 @@ +--- +title: Configure always-on real-time protection in Windows Defender AV +description: Enable and configure real-time protectoin features such as behavior monitoring, heuristics, and machine-learning in Windows Defender AV +keywords: real-time protection, rtp, machine-learning, behavior monitoring, heuristics +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + + +# Enable and configure Windows Defender AV always-on protection and monitoring + + + +**Applies to:** + +- Windows 10 + + +**Audience** + +- Enterprise security administrators + + +**Manageability available with** + +- Group Policy + + + + +Always-on protection consists of real-time protection, behavior monitoring, and heuristics to identify malware based on known suspicious and malicious activities. + +These activities include events such as processes making unusual changes to existing files, modifiying or creating automatic startup registry keys and startup locations (also known as auto-start extensibilty points, or ASEPs), and other changes to the file system or file structure. + + +## Configure and enable always-on protection + +You can configure how always-on protection works with the following Group Policy settings described in this section. + +To configure these settings: + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus** and then the **Location** specified in the table below. + +6. Double-click the policy **Setting** as specified in the table below, and set the option to your desired configuration. Click **OK**, and repeat for any other settings. + + + + +Location | Setting | Description | Default setting (if not configured) +---|---|---|--- +Real-time protection | Monitor file and program activity on your computer | The AV engine makes note of any file changes (file writes, such as moves, copies, or modifications) and general program activity (programs that are opened or running and that cause other programs to run) | Enabled +Real-time protection | Scan all downloaded files and attachments | Downloaded files and attachments are automatically scanned. This operates in addition to Windows Defender SmartScreen filter, which scans files before and during downloading | Enabled +Real-time protection | Turn on process scanning whenever real-time protection is enabled | You can independently enable the AV engine to scan running processes for suspicious modifications or behaviors. This is useful if you have disabled real-time protection | Enabled +Real-time protection | Turn on behavior monitoring | The AV engine will monitor file processes, file and registry changes, and other events on your endpoints for suspicious and known malicious activity | Enabled +Real-time protection | Turn on raw volume write notifications | Information about raw volume writes will be analysed by behavior monitoring | Enabled +Real-time protection | Define the maximum size of downloaded files and attachments to be scanned | You can define the size in kilobytes | Enabled +Real-time protection | Configure monitoring for incoming and outgoing file and program activity | Specify whether monitoring should occur on incoming, outgoing, both, or neither direction. This is relevant for Windows Server installations where you have defined specific servers or server roles that see large amounts of file changes in only one direction and you want to improve network performance. Note that fully updated endpoints (and servers) on a network will see little performance impact irrespective of the number or direction of file changes. +Scan | Turn on heuristics | Heuristic protection will disable or block suspicious activity immediately before the AV engine is asked to detect the activity | Enabled (both directions) + + + + +## Disable real-time protection +> [!WARNING] +> Disabling real-time protection will drastically reduce the protection on your endpoints and is not recommended. + +The main real-time protection capability is enabled by default, but you can disable it with Group Policy: + +**Use Group Policy to diasble real-time protection:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Real-time protection**. + +6. Double-click the **Turn off real-time protection** setting and set the option to **Enabled**. Click **OK**. + + + +## Related topics + +- [Configure behavioral, heuristic, and real-time protection](configure-protection-features-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) \ No newline at end of file diff --git a/windows/keep-secure/configure-remediation-windows-defender-antivirus.md b/windows/keep-secure/configure-remediation-windows-defender-antivirus.md new file mode 100644 index 0000000000..bfc941c20c --- /dev/null +++ b/windows/keep-secure/configure-remediation-windows-defender-antivirus.md @@ -0,0 +1,17 @@ +--- +title: Remediate and resolve infections detected by Windows Defender AV +description: Configure what Windows Defender AV should do when it detects a threat, and how long quarantined files should be retained in the quarantine folder +keywords: +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + + +# Configure remediation for Windows Defender AV scans \ No newline at end of file diff --git a/windows/keep-secure/configure-windows-defender-antivirus-features.md b/windows/keep-secure/configure-windows-defender-antivirus-features.md new file mode 100644 index 0000000000..d1da91abab --- /dev/null +++ b/windows/keep-secure/configure-windows-defender-antivirus-features.md @@ -0,0 +1,54 @@ +--- +title: Configure Windows Defender Antivirus features (Windows 10) +description: You can configure features for Windows Defender Antivirus using Configuration Manager, MDM software (such as Intune), PowerShell, and with Group Policy settings. +keywords: windows defender antivirus, antimalware, security, defender, configure, configuration, Config Manager, System Center Configuration Manager, SCCM, Intune, MDM, mobile device management, GP, group policy, PowerShell +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Configure Windows Defender Antivirus features + + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +Windows Defender Antivirus can be configured with a number of tools, including: + +- Group Policy settings +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instrumentation (WMI) +- Microsoft Intune + + +The following broad categories of features can be configured: + +- Cloud-delivered protection +- Always-on real-time protection, including behavioral, heuristic, and machine-learning-based protection +- How end-users interact with the client on individual endpoints + +The topics in this section describe how to perform key tasks when configuring Windows Defender AV. Each topic includes instructions for the applicable configuration tool (or tools). + +You can also review the [Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md) topic for an overview of each tool and links to further help. + + +## In this section +Topic | Description +:---|:--- +[Utilize Microsoft cloud-provided protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) | Cloud-delivered protection provides an advanced level of fast, robust antivirus detection +[Configure behavioral, heuristic, and real-time protection](configure-protection-features-windows-defender-antivirus.md)|Enable behavior-based, heuristic, and real-time protection in Windows Defender AV +[Configure end-user interaction with WDAM](configure-end-user-interaction-windows-defender-antivirus.md)|Configure how end-users interact with Windows Defender AV, what notifications they see, and if they can override settings + + + diff --git a/windows/keep-secure/configure-windows-defender-in-windows-10.md b/windows/keep-secure/configure-windows-defender-in-windows-10.md index 93469dafa2..32dc5bdf7d 100644 --- a/windows/keep-secure/configure-windows-defender-in-windows-10.md +++ b/windows/keep-secure/configure-windows-defender-in-windows-10.md @@ -1,6 +1,6 @@ --- title: Configure and use Windows Defender in Windows 10 -description: IT professionals can configure definition updates and cloud-based protection in Windows Defender in Windows 10 through Microsoft Active Directory and Windows Server Update Services (WSUS). +description: IT professionals can configure definition updates and cloud-based protection in Windows Defender in Windows 10 through Microsoft Active Directory and Windows Server Update Services (WSUS). ms.assetid: 22649663-AC7A-40D8-B1F7-5CAD9E49653D ms.prod: w10 ms.mktglfcycl: manage @@ -8,197 +8,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: jasesso +redirect_url: /itpro/windows/keep-secure/deploy-manage-report-windows-defender-antivirus/ --- # Configure Windows Defender in Windows 10 -**Applies to** -- Windows 10 - -You can configure definition updates and cloud-based protection in Windows Defender in Windows 10 through Microsoft Active Directory and Windows Server Update Services (WSUS). - -You can also enable and configure the Microsoft Active Protection Service to ensure endpoints are protected by cloud-based protection technologies. - -## Configure definition updates - -It is important to update definitions regularly to ensure that your endpoints are protected. Definition updates can be configured to suit the requirements of your organization. - -Windows Defender supports the same updating options (such as using multiple definition sources) as other Microsoft endpoint protection products; for more information, see [Configuring Definition Updates](https://technet.microsoft.com/library/gg412502.aspx). - -When you configure multiple definition sources in Windows Defender, you can configure the fallback order using the following values through *Group Policy* settings: - -- InternalDefinitionUpdateServer - WSUS -- MicrosoftUpdateServer - Microsoft Update -- MMPC - [Microsoft Malware Protection Center definitions page](http://www.microsoft.com/security/portal/definitions/adl.aspx) -- FileShares - file share - -Read about deploying administrative template files for Windows Defender in the article [Description of the Windows Defender Group Policy administrative template settings](https://support.microsoft.com/kb/927367). - -You can also manage your Windows Defender update configuration settings through System Center Configuration Manager. See [How to Configure Definition Updates for Endpoint Protection in Configuration Manager](https://technet.microsoft.com/library/jj822983.aspx) for details. - -## Definition update logic - -You can update Windows Defender definitions in four ways depending on your business requirements: - -- WSUS, the managed server. You can manage the distribution of updates that are released through Microsoft Update to computers in your enterprise environment; read more on the [Windows Server Update Services](https://technet.microsoft.com/windowsserver/bb332157.aspx) website. -- Microsoft Update, the unmanaged server. You can use this method to get regular updates from Microsoft Update. -- The [Microsoft Malware Protection Center definitions page](http://www.microsoft.com/security/portal/definitions/adl.aspx), as an alternate download location. You can use this method if you want to download the latest definitions. -- File share, where the definition package is downloaded. You can retrieve definition updates from a file share. The file share must be provisioned on a regular basis with the update files. - -## Update Windows Defender definitions through Active Directory and WSUS - -This section details how to update Windows Defender definitions for Windows 10 endpoints through Active Directory and WSUS. - ---- - - - - - - - - - - - - - - - - - - - - - - - - -
MethodInstructions

WSUS

See [Software Updates and Windows Server Update Services Definition Updates](https://technet.microsoft.com/library/gg398036.aspx) in the [Configuring Definition Updates](https://technet.microsoft.com/library/gg412502.aspx) topic that also applies to Windows Defender.

Microsoft Update

Set the following fallback order Group Policy to enable Microsoft Update:

-
    -
  1. Open the Group Policy Editor.
    2. -
  2. In the Local Computer Policy tree, expand Computer Configuration, then Administrative Templates, then Windows Components, then Windows Defender.
    3. -
  3. Click on Signature Updates.
    4. -

  4. Double-click on Define the order of sources for downloading definition updates.

    -

    This will open the Define the order of sources for downloading definition updates window.

    5. -
  5. Click Enable.
    6. -

  6. In the Options pane, define the following Group Policy to enable Microsoft Update:

    -

    {MicrosoftUpdateServer}

    -

    "Define the order of sources for downloading definition updates" field

    7. -

  7. Click OK.

    -

    The window will close automatically.

    8. -

[Microsoft Malware Protection Center definitions page](http://www.microsoft.com/security/portal/definitions/adl.aspx)

Set the following fallback order Group Policy to enable Windows Defender to download updated signatures:

-
    -
  1. Open the Group Policy Editor.
    2. -
  2. In the Local Computer Policy tree, expand Computer Configuration, then Administrative Templates, then Windows Components, then Windows Defender.
    3. -
  3. Click on Signature Updates.
    4. -

  4. Double-click on Define the order of sources for downloading definition updates.

    -

    This will open the Define the order of sources for downloading definition updates window.

    5. -
  5. Click Enable.
    6. -

  6. In the Options pane, define the following Group Policy to enable Windows Defender to download updated signatures:

    -

    {MMPC}

    -

    "Define the order of sources for downloading definition updates" field

    7. -

  7. Click OK.

    -

    The window will close automatically.

    8. -

File share

-
    -
  1. Open the Group Policy Editor.
    2. -
  2. In the Local Computer Policy tree, expand Computer Configuration, then Administrative Templates, then Windows Components, then Windows Defender.
    3. -
  3. Click on Signature Updates.
    4. -

  4. Double-click on Define the order of sources for downloading definition updates.

    -

    This will open the Define the order of sources for downloading definition updates window:

    5. -
  5. Click Enable.
    6. -

  6. In the Options pane, define the following Group Policy to enable Windows Defender to download updated signatures:

    -

    {FileShares}

    -

    "Define the order of sources for downloading definition updates" field

    7. -

  7. Click OK.

    -

    The window will close automatically.

    8. -

  8. Double-click on Define file shares for downloading definition updates.

    -

    This will open the Define file shares for downloading definition updates window.

    9. -
  9. Click Enable.
    10. -

  10. In the Options pane, define the following Group Policy to specify the Universal Naming Convention (UNC) share source:

    -

    {\\unc1\\unc2} - where you define [unc] as the UNC shares.

    -

    "Define the file shares for downloading definition updates" field

    11. -

  11. Click OK.

    -

    The window will close automatically.

    12. -
-  -## Manage cloud-based protection - -Windows Defender offers improved cloud-based protection and threat intelligence for endpoint protection clients using the Microsoft Active Protection Service. Read more about the Microsoft Active Protection Service community in [Join the Microsoft Active Protection Service community](http://windows.microsoft.com/windows-8/join-maps-community). - -You can enable or disable the Microsoft Active Protection Service using *Group Policy* settings and administrative template files. - -More information on deploying administrative template files for Windows Defender is available in the article [Description of the Windows Defender Group Policy administrative template settings](https://support.microsoft.com/kb/927367). - -The Microsoft Active Protection Service can be configured with the following *Group Policy* settings: - -1. Open the **Group Policy Editor**. -2. In the **Local Computer Policy** tree, expand **Computer Configuration**, then **Administrative Templates**, then **Windows Components**, then **Windows Defender**. -3. Click on **MAPS**. -4. Double-click on **Join Microsoft MAPS**. -5. Select your configuration option from the **Join Microsoft MAPS** list. - - >**Note:**  Any settings modified on an endpoint will be overridden by the administrator's policy setting. -   -Use the Windowsdefender.adm *Group Policy* template file to control the policy settings for Windows Defender in Windows 10: - -Policy setting: **Configure Microsoft SpyNet Reporting** - -Registry key name: **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\SpyNet\\SpyNetReporting** - -Policy description: **Adjusts membership in Microsoft Active Protection Service** - -You can also configure preferences using the following PowerShell parameters: - -- Turn Microsoft Active Protection Service off: *Set-MpPreference -MAPSReporting 0* -- Turn Microsoft Active Protection Service on: *Set-MpPreference -MAPSReporting 2* - -Read more about this in: - -- [Scripting with Windows PowerShell](https://technet.microsoft.com/library/bb978526.aspx) -- [Defender Cmdlets](https://technet.microsoft.com/library/dn433280.aspx) - ->**Note:**  Any information that Windows Defender collects is encrypted in transit to our servers, and then stored in secure facilities. Microsoft takes several steps to avoid collecting any information that directly identifies you, such as your name, email address, or account ID. -  -Read more about how to manage your privacy settings in [Setting your preferences for Windows 10 services](http://windows.microsoft.com/windows-10/services-setting-preferences). - -## Opt-in to Microsoft Update - -You can use Microsoft Update to keep definitions on mobile computers running Windows Defender in Windows 10 up to date when they are not connected to the corporate network. If the mobile computer doesn't have a [Windows Server Update Service](https://technet.microsoft.com/windowsserver/bb332157.aspx) (WSUS) connection, the signatures will still come from Microsoft Update. This means that signatures can be pushed down (via Microsoft Update) even if WSUS overrides Windows Update. - -You need to opt-in to Microsoft Update on the mobile computer before it can retrieve the definition updates from Microsoft Update. - -There are two ways you can opt-in to Microsoft Update in Windows Defender for Windows 10: - -1. Use a VBScript to create a script, then run it on each computer in your network. -2. Manually opt-in every computer on your network through the **Settings** menu. - -You can create a VBScript and run it on each computer on your network; this is an efficient way to opt-in to Microsoft Update. - -**Use a VBScript to opt in to Microsoft Update** - -1. Use the instructions in the MSDN article [Opt-In to Microsoft Update](https://msdn.microsoft.com/library/windows/desktop/aa826676.aspx) to create the VBScript. -2. Run the VBScript you created on each computer in your network. - -You can manually opt-in each individual computer on your network to receive Microsoft Update. - -**Manually opt-in to Microsoft Update** - -1. Open **Windows Update** in **Update & security** settings on the computer you want to opt-in. -2. Click **Advanced** options. -3. Select the checkbox for **Give me updates for other Microsoft products when I update Windows**. - -## Schedule updates for Microsoft Update - -Opting-in to Microsoft Update means that your system administrator can schedule updates to your mobile computer, so that it keeps up-to-date with the latest software versions and security definitions, even when you’re on the road. - -For more information on scheduling updates, see [Configure definition updates](https://technet.microsoft.com/library/mt622088.aspx#configure-definition-updates). - -## Related topics - -- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) -- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) +This page has been redirected to *Windows Defender Antivirus in Windows 10*. diff --git a/windows/keep-secure/customize-run-review-remediate-scans-windows-defender-antivirus.md b/windows/keep-secure/customize-run-review-remediate-scans-windows-defender-antivirus.md new file mode 100644 index 0000000000..ac57f3e615 --- /dev/null +++ b/windows/keep-secure/customize-run-review-remediate-scans-windows-defender-antivirus.md @@ -0,0 +1,40 @@ +--- +title: Run and customize scheduled and on-demand scans +description: Customize and initiate scans using Windows Defender AV on endpoints across your network. +keywords: scan, schedule, customize, exclusions, exclude files, remediation, scan results, quarantine, remove threat, quick scan, full scan +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Customize, initiate, and review the results of Windows Defender AV scans and remediation + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + + +You can use Group Policy, PowerShell, and Windows Management Instrumentation (WMI) to configure scans run by Windows Defender Antivirus. + + + +## In this section + +Topic | Description +---|--- +[Exclude files and processes from scans](configure-exclusions-windows-defender-antivirus.md) | You can exclude files (including files modified by specified processes) and folders from on-demand scans, scheduled scans, and always-on real-time protection monitoring and scanning +[Configure email, removable storage, network, reparse point, and archive scanning](configure-advanced-scan-types-windows-defender-antivirus.md) | You can configure Windows Defender AV to include certain types of email storage files, back-up or reparse points, and archived files (such as .zip files) in scans. You can also enable network file scanning +[Configure remediation for scans](configure-remediation-windows-defender-antivirus.md) | Configure what Windows Defender AV should do when it detects a threat, and how long quarantined files should be retained in the quaratine folder +[Configure scheduled scans](scheduled-catch-up-scans-windows-defender-antivirus.md) | Set up recurring (scheduled) scans, including when they should run and whether they run as full or quick scans +[Configure and run scans](run-scan-windows-defender-antivirus.md) | Run and configure on-demand scans using PowerShell, Windows Management Instrumentation, or individually on endpoints with the Windows Defender Security Center app +[Review scan results](review-scan-results-windows-defender-antivirus.md) | Review the results of scans using System Center Configuration Manager, Microsoft Intune, or the Windows Defender Security Center app + diff --git a/windows/keep-secure/deploy-manage-report-windows-defender-antivirus.md b/windows/keep-secure/deploy-manage-report-windows-defender-antivirus.md new file mode 100644 index 0000000000..18cfd5e134 --- /dev/null +++ b/windows/keep-secure/deploy-manage-report-windows-defender-antivirus.md @@ -0,0 +1,94 @@ +--- +title: Deploy, manage, and report on Windows Defender Antivirus +description: You can deploy and manage Windows Defender Antivirus with Group Policy, Configuration Manager, WMI, PowerShell, or Intune +keywords: deploy, manage, update, protection, windows defender antivirus +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Deploy, manage, and report on Windows Defender Antivirus + +**Applies to:** + +- Windows 10 + +**Audience** + +- IT administrators + +You can deploy, manage, and report on Windows Defender Antivirus in a number of ways. + +As the Windows Defender AV client is installed as a core part of Windows 10, traditional deployment of a client to your endpoints does not apply. + +However, in most cases you will still need to enable the protection service on your endpoints with System Center Configuration Manager, Microsoft Intune, Azure Secrutiy Center, or Group Policy Objects, which is described in the following table. + +You'll also see additional links for: +- Managing Windows Defender Antivirus protection, including managing product and protection updates +- Reporting on Windows Defender Antivirus protection + +> [!IMPORTANT] +> In most cases, Windows 10 will disable Windows Defender Antivirus if it finds another antivirus product running and up-to-date. You must disable or uninstall third-party antivirus products before Windows Defender Antivirus will be functioning. If you re-enable or install third-part antivirus products, then Windows 10 will automatically disable Windows Defender Antivirus. + + +Tool|Deployment options (1)|Management options (network-wide configuration and policy or baseline deployment) ([2](#fn2))|Reporting options +---|---|---|--- +System Center Configuration Manager ([3](#fn3))|Use the [Endpoint Protection point site system role][] and [enable Endpoint Protection with custom client settings][]|With [default and customized antimalware policies][] and [client management][]|With the default [Configuration Manager Monitoring workspace][] and [email alerts][] +Microsoft Intune|[Deploy the Microsoft Intune client to endpoints][]|Use and deploy a [custom Intune policy][] and use the Intune console to [manage tasks][]|[Monitor endpoint protection in the Microsoft Intune administration console][] +Windows Management Instrumentation|Deploy with Group Policy, System Center Configuration Manager, or manually on individual endpoints.|Use the [Set method of the MSFT_MpPreference class][] and the [Update method of the MSFT_MpSignature class][]|Use the [MSFT_MpComputerStatus][] class and the get method of associated classes in the [Windows Defender WMIv2 Provider][] +PowerShell|Deploy with Group Policy, System Center Configuration Manager, or manually on individual endpoints.|Use the [Set-MpPreference][] and [Update-MpSignature] [] cmdlets available in the Defender module|Use the appropriate [Get- cmdlets available in the Defender module][] +Group Policy and Active Directory (domain-joined)|Use a Group Policy Object to deploy configuration changes and ensure Windows Defender Antivirus is enabled.|Use Group Policy Objects (GPOs) to [Configure update options for Windows Defender Antivirus][] and [Configure Windows Defender features][]|Endpoint reporting is not available with Group Policy. You can generate a list of [Group Policies to determine if any settings or policies are not applied][] +Microsoft Azure|Deploy Microsoft Antimalware for Azure in the [Azure portal, by using Visual Studio virtual machine configuration, or using Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/azure/security/azure-security-antimalware#antimalware-deployment-scenarios). You can also [Install Endpoint protection in Azure Security Center](https://docs.microsoft.com/en-us/azure/security-center/security-center-install-endpoint-protection)|Configure [Microsoft Antimalware for Virtual Machines and Cloud Services with Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/servicemanagement/azure.antimalware/v3.4.0/azure.antimalware) or [use code samples](https://gallery.technet.microsoft.com/Antimalware-For-Azure-5ce70efe)|Use [Microsoft Antimalware for Virtual Machines and Cloud Services with Azure PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/servicemanagement/azure.antimalware/v3.4.0/azure.antimalware) to enable monitoring. You can also review usage reports in Azure Active Directory to determine suspicious activity, including the [Possibly infected devices][] report and configure an SIEM tool to report on [Windows Defender Antivirus events][] and add that tool as an app in AAD. + +1. The availability of some functions and features, especially related to cloud-delivered protection, differ between System Center Configuration Manager, current branch (for example, System Center Configuration Manager 2016) and System Center Configuration Manager 2012. In this library, we've focused on Windows 10, Windows Server 2016, and System Center Configuration Manager, current branch (2016). See the [Utilize Microsoft cloud-provided protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) topic for a table that describes the major differences. [(Return to table)](#ref1) + +1. Configuration of features and protection, including configuring product and protection updates, are further described in the [Configure Windows Defender Antivirus features](configure-notifications-windows-defender-antivirus.md) section in this library. [(Return to table)](#ref2) + +1. In Windows 10, Windows Defender Antivirus is a component available without installation or deployment of an additional client or service. It will automatically be enabled when third-party antivirus products are either uninstalled or out of date. Traditional deployment therefore is not required. Deployment here refers to ensuring the Windows Defender Antivirus component is available and enabled on endpoints or servers. [(Return to table)](#ref3) + + + + + +[Endpoint Protection point site system role]: https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-protection-site-role +[default and customized antimalware policies]: https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies +[client management]: https://docs.microsoft.com/en-us/sccm/core/clients/manage/manage-clients +[enable Endpoint Protection with custom client settings]: https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-protection-configure-client +[Configuration Manager Monitoring workspace]: https://docs.microsoft.com/en-us/sccm/protect/deploy-use/monitor-endpoint-protection +[email alerts]: https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-configure-alerts +[Deploy the Microsoft Intune client to endpoints]: https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune +[custom Intune policy]: https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune#configure-microsoft-intune-endpoint-protection + [custom Intune policy]: https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune#configure-microsoft-intune-endpoint-protection +[manage tasks]: https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune#choose-management-tasks-for-endpoint-protection +[Monitor endpoint protection in the Microsoft Intune administration console]: https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune#monitor-endpoint-protection +[Set method of the MSFT_MpPreference class]: https://msdn.microsoft.com/en-us/library/dn439474 +[Update method of the MSFT_MpSignature class]: https://msdn.microsoft.com/en-us/library/dn439474 +[MSFT_MpComputerStatus]: https://msdn.microsoft.com/en-us/library/dn455321 +[Windows Defender WMIv2 Provider]: https://msdn.microsoft.com/en-us/library/dn439477 +[Set-MpPreference]: https://technet.microsoft.com/itpro/powershell/windows/defender/set-mppreference.md +[Update-MpSignature]: https://technet.microsoft.com/itpro/powershell/windows/defender/update-mpsignature +[Get- cmdlets available in the Defender module]: https://technet.microsoft.com/itpro/powershell/windows/defender/index +[Configure update options for Windows Defender Antivirus]: manage-updates-baselines-windows-defender-antivirus.md +[Configure Windows Defender features]: configure-windows-defender-antivirus-features.md +[Group Policies to determine if any settings or policies are not applied]: https://technet.microsoft.com/en-us/library/cc771389.aspx +[Possibly infected devices]: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-reporting-sign-ins-from-possibly-infected-devices +[Windows Defender Antivirus events]: troubleshoot-windows-defender-antivirus.md + + +## In this section + +Topic | Description +---|--- +[Deploy and enable Windows Defender Antivirus protection](deploy-windows-defender-antivirus.md) | While the client is installed as a core part of Windows 10, and traditional deployment does not apply, you will still need to enable the client on your endpoints with System Center Configuration Manager, Microsoft Intune, or Group Policy Objects. +[Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) | There are two parts to updating Windows Defender Antivirus: updating the client on endpoints (product updates), and updating definitions (protection updates). You can update definitions in a number of ways, using System Center Configuration Manager, Group Policy, PowerShell, and WMI. +[Monitor and report on Windows Defender Antivirus protection](report-monitor-windows-defender-antivirus.md) | You can use System Center Configuration Manager, a third-party SIEM product (by consuming Windows event logs), or Microsoft Intune to monitor protection status and create reports about endpoint protection + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-in-windows-10.md) +- [Configure Windows Defender Antivirus features](configure-windows-defender-antivirus-features.md) diff --git a/windows/keep-secure/deploy-windows-defender-antivirus.md b/windows/keep-secure/deploy-windows-defender-antivirus.md new file mode 100644 index 0000000000..6f98f62d52 --- /dev/null +++ b/windows/keep-secure/deploy-windows-defender-antivirus.md @@ -0,0 +1,40 @@ +--- +title: Deploy and enable Windows Defender Antivirus +description: Deploy Windows Defender AV for protection of your endpoints with Configuration Manager, Microsoft Intune, Group Policy, PowerShell cmdlets, or WMI. +keywords: deploy, enable, windows defender av +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Deploy and enable Windows Defender Antivirus + + +**Applies to:** + +- Windows 10 + +**Audience** + +- Network administrators +- IT administrators + + +Depending on the management tool you are using, you may need to specifically enable or configure Windows Defender AV protection. + +See the [(Deployment, managament, and reporting options table)](deploy-manage-report-windows-defender-antivirus.md#ref1) for instructions on how to enable protection with System Center Configuration Manager, Group Policy, Active Directory, Microsoft Azure, Microsoft Intune, PowerShell cmdlets, and Windows Management Instruction (WMI). + +Some scenarios require additional guidance on how to successfully deploy or configure Windows Defender AV protection, such as Virtual Desktop Infrastructure (VDI) environments. + +The remaining topic in this section provides end-to-end advice and best practices for [setting up Windows Defender AV ion virtual machines (VMs) in a VDI or Remote Desktop Services (RDS) environment](deployment-vdi-windows-defender-antivirus.md). + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-in-windows-10.md) +- [Deploy, manage updates, and report on Windows Defender Antivirus](deploy-manage-report-windows-defender-antivirus.md) +- [Deployment guide for Windows Defender Antivirus in a virtual desktop infrasructure (VDI) environment](deployment-vdi-windows-defender-antivirus.md) \ No newline at end of file diff --git a/windows/keep-secure/deployment-vdi-windows-defender-antivirus.md b/windows/keep-secure/deployment-vdi-windows-defender-antivirus.md new file mode 100644 index 0000000000..50d37bfe9d --- /dev/null +++ b/windows/keep-secure/deployment-vdi-windows-defender-antivirus.md @@ -0,0 +1,309 @@ +--- +title: Windows Defender Antivirus VDI deployment guide +description: Learn how to deploy Windows Defender Antivirus in a VDI environment for the best balance between protection and performance. +keywords: vdi, hyper-v, vm, virtual machine, windows defender, antivirus, av, virtual desktop, rds, remote desktop +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Deployment guide for Windows Defender Antivirus in a virtual desktop infrastructure (VDI) environment + +**Applies to:** + +- Windows 10 + +**Audience** + +- IT professionals + +**Manageability available with** + +- System Center Configuration Manager (current branch) +- Group Policy + + + +In addition to standard on-premises or hardware configurations, you can also use Windows Defender Antivirus (Windows Defender AV) in a remote desktop (RDS) or virtual desktop infrastructure (VDI) environment. + +Boot storms can be a problem in large-scale VDIs; this guide will help reduce the overall network bandwidth and performance impact on your hardware. For more details on the best configuration options to ensure a good balance between performance and protection, see the [Configure endpoints for optimal performance](#configure-endpoints-for-optimal-performance) section. + +See the [Microsoft Desktop virtualization site](https://www.microsoft.com/en-us/server-cloud/products/virtual-desktop-infrastructure/) for more details on Microsoft Remote Desktop Services and VDI support. + +For Azure-based virtual machines, you can also review the [Install Endpoint Protection in Azure Security Center](https://docs.microsoft.com/en-us/azure/security-center/security-center-install-endpoint-protection) topic. + +There are three main steps in this guide to help roll out Windows Defender AV protection across your VDI: + +1. [Create and deploy the base image (for example, as a virtual hard disk (VHD)) that your virtual machines (VMs) will use](#create-and-deploy-the-base-image) +2. [Manage the base image and updates for your VMs](#manage-vms-and-base-image) +3. [Configure the VMs for optimal protection and performance](#configure-endpoints-for-optimal-performance), including: + - [Randomize scheduled scans](#randomize-scheduled-scans) + - [Use quick scans](#use-quick-scans) + - [Prevent notifications](#prevent-notifications) + - [Disable scans from occuring after every update](#disable-scans-after-an-update) + - [Scan out-of-date machines or machines that have been offline for a while](#scan-vms-that-have-been-offline) + +>[!IMPORTANT] +> While the VDI can be hosted on Windows Server 2012 or Windows Server 2016, the virtual machines (VMs) should be running Windows 10, 1607 at a minimum, due to increased protection technologies and features that are unavailable in earlier versions of Windows. + +>[!NOTE] +>When you manage Windows with System Center Configuration Manager, Windows Defender AV protection will be referred to as Endpoint Protection or System Center Endpoint Protection. See the [Endpoint Protection section at the Configuration Manager library]( https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-protection) for more information. + +The following table lists the configuration settings that we recommend when deploying Windows Defender AV in a VDI environment: + + + +## Create and deploy the base image + +The main steps in this section include: +1. Create your standard base image according to your requirements +2. Apply Windows Defender AV protection updates to your base image +3. Seal or “lock” the image to create a “known-good” image +4. Deploy your image to your VMs + +### Create the base image +First, you should create your base image according to your business needs, applying or installing the relevant line of business (LOB) apps and settings as you normally would. Typically, this would involve creating a VHD or customized .iso, depending on how you will deploy the image to your VMs. + +### Apply protection updates to the base image +After creating the image, you should ensure it is fully updated. See [Configure Windows Defender in Windows 10]( https://technet.microsoft.com/en-us/itpro/windows/keep-secure/configure-windows-defender-in-windows-10) for instructions on how to update Windows Defender AV protection via WSUS, Microsoft Update, the MMPC site, or UNC file shares. You should ensure that your initial base image is also fully patched with Microsoft and Windows updates and patches. + +### Seal the base image +When the base image is fully updated, you should run a quick scan on the image. This “sealing” or “locking” of the image helps Windows Defender AV build a cache of known-good files and avoid scanning them again on your VMs. In turn, this can help ensure performance on the VM is not impacted. + +You can run a quick scan [from the command line](command-line-arguments-windows-defender-antivirus.md) or via [System Center Configuration Manager](run-scan-windows-defender-antivirus.md). + +>[!NOTE] +>Quick scan versus full scan +>Quick scan looks at all the locations where there could be malware registered to start with the system, such as registry keys and known Windows startup folders. Combined with our always on real-time protection capability - which reviews files when they are opened and closed, and whenever a user navigates to a folder – quick scan helps provide strong coverage both for malware that starts with the system and kernel-level malware. +>Therefore, when considering performance – especially for creating a new or updated image in preparation for deployment – it makes sense to use a quick scan only. +>A full scan, however, can be useful on a VM that has encountered a malware threat to identify if there are any inactive components lying around and help perform a thorough clean-up. + + +### Deploy the base image +You’ll then need to deploy the base image across your VDI. For example, you can create or clone a VHD from your base image, and then use that VHD when you create or start your VMs. + +The following references provide ways you can create and deploy the base image across your VDI: + +- [Single image management for Virtual Desktop Collections](https://blogs.technet.microsoft.com/enterprisemobility/2012/10/29/single-image-management-for-virtual-desktop-collections-in-windows-server-2012/) +- [Using Hyper-V to create a Base OS image that can be used for VMs and VHDs](https://blogs.technet.microsoft.com/haroldwong/2011/06/12/using-hyper-v-to-create-a-base-os-image-that-can-be-used-for-vms-and-boot-to-vhd/) +- [Plan for Hyper-V security in Windows Server 2016]( https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/plan/plan-for-hyper-v-security-in-windows-server-2016) +- [Create a virtual machine in Hyper-V (with a VHD)](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/get-started/create-a-virtual-machine-in-hyper-v) +- [Build Virtual Desktop templates]( https://technet.microsoft.com/en-us/library/dn645526(v=ws.11).aspx) + + + + + +## Manage your VMs and base image +How you manage your VDI will affect the performance impact of Windows Defender AV on your VMs and infrastructure. + +Because Windows Defender AV downloads protection updates every day, [or based on your protection update settings](manage-protection-updates-windows-defender-antivirus.md), network bandwidth can be a problem if multiple VMs attempt to download updates at the same time. + +Following the guidelines in this means the VMs will only need to download “delta” updates, which are the differences between an existing definition set and the next one. Delta updates are typically much smaller (a few kilobytes) than a full definition download (which can average around 150 mb). + + +### Manage updates for persistent VDIs + +If you are using a persistent VDI, you should update the base image monthly, and set up protection updates to be delivered daily via a file share, as follows: +1. Create a dedicated file share location on your network that can be accessed by your VMs and your VM host (or other, persistent machine, such as a dedicated admin console that you use to manage your VMs). +2. Set up a scheduled task on your VM host to automatically download updates from the MMPC website or Microsoft Update and save them to the file share (the [SignatureDownloadCustomTask PowerShell script](https://www.powershellgallery.com/packages/SignatureDownloadCustomTask/1.4/DisplayScript) can help with this). +3. [Configure the VMs to pull protection updates from the file share](manage-protection-updates-windows-defender-antivirus.md). +4. Disable or delay automatic Microsoft updates on your VMs. See [Update Windows 10 in the enterprise](https://technet.microsoft.com/en-us/itpro/windows/manage/waas-update-windows-10) for information on managing operating system updates with WSUS, SCCM, and others. +5. On or just after each Patch Tuesday (the second Tuesday of each month), update your base image with [the latest protection updates from the MMPC website, WSUS, or Microsoft Update](manage-protection-updates-windows-defender-antivirus.md). Also apply all other Windows patches and fixes that were delivered on the Patch Tuesday. You can automate this by following the instructions in [Orchestrated offline VM Patching using Service Management Automation](https://blogs.technet.microsoft.com/privatecloud/2013/12/06/orchestrated-offline-vm-patching-using-service-management-automation/). +5. [Run a quick scan](run-scan-windows-defender-antivirus.md) on your base image before deploying it to your VMs. + +A benefit to aligning your image update to the monthly Microsoft Update is that you ensure your VMs will have the latest Windows security patches and other important Microsoft updates without each VM needing to individually download them. + + +### Manage updates for non-persistent VDIs + +If you are using a non-persistent VDI, you can update the base image daily (or nightly) and directly apply the latest updates to the image. + +An example: +1. Every night or other time when you can safely take your VMs offline, update your base image with t[the latest protection updates from the MMPC website, WSUS, or Microsoft Update](manage-protection-updates-windows-defender-antivirus.md). +2. [Run a quick scan](run-scan-windows-defender-antivirus.md) on your base image before deploying it to your VMs. + + + + +## Configure endpoints for optimal performance +There are a number of settings that can help ensure optimal performance on your VMs and VDI without affecting the level of protection, including: + - [Randomize scheduled scans](#randomize-scheduled-scans) + - [Use quick scans](#use-quick-scans) + - [Prevent notifications](#prevent-notifications) + - [Disable scans from occuring after every update](#disable-scans-after-an-update) + - [Scan out-of-date machines or machines that have been offline for a while](#scan-vms-that-have-been-offline) + +These settings can be configured as part of creating your base image, or as a day-to-day management function of your VDI infrastructure or network. + + + + +### Randomize scheduled scans + +Windows Defender AV supports the randomization of scheduled scans and signature updates. This can be extremely helpful in reducing boot storms (especially when used in conjuction with [Disable scans from occuring after every update](#disable-scans-after-an-update) and [Scan out-of-date machines or machines that have been offline for a while](#scan-vms-that-have-been-offline). + +Scheduled scans run in addition to [real-time protection and scanning](configure-real-time-protection-windows-defender-antivirus.md). + +The start time of the scan itself is still based on the scheduled scan policy – ScheduleDay, ScheduleTime, ScheduleQuickScanTime. + + + +**Use Group Policy to randomize scheduled scan start times:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender** and configure the following setting: + + 1. Double-click the **Randomize scheduled task times** setting and set the option to **Enabled**. Click **OK**. This adds a true randomization (it is still random if the disk image is replicated) of plus or minus 30 minutes (using all of the intervals) to the start of the scheduled scan and the signature update. For example, if the sechedule start time was set at 2.30pm, then enabling this setting could cause one machine to scan and update at 2.33pm and another machine to scan and update at 2.14pm. + +**Use Configuration Manager to randomize schedule scans:** + +See [How to create and deploy antimalware policies: Advanced settings]( https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#advanced-settings) for details on configuring System Center Configuration Manager (current branch). + +See [Schedule scans](scheduled-catch-up-scans-windows-defender-antivirus.md) for other configuration options available for scheduled scans. + +### Use quick scans + +You can specify the type of scan that should be performed during a scheduled scan. +Quick scans are the preferred approach as they are designed to look in all places where malware needs to reside to be active. + +**Use Group Policy to specify the type of scheduled scan:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +2. In the **Group Policy Management Editor** go to **Computer configuration**. + +3. Click **Policies** then **Administrative templates**. + +4. Expand the tree to **Windows components > Windows Defender > Scan** and configure the following setting: + 1. Double-click the **Specify the scan type to use for a scheduled scan** setting and set the option to **Enabled** and **Quick scan**. Click **OK**. + +**Use Configuration Manager to specify the type of scheduled scan:** + +See [How to create and deploy antimalware policies: Scheduled scans settings]( https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#scheduled-scans-settings) for details on configuring System Center Configuration Manager (current branch). + + + +### Prevent notifications + +Sometimes, Windows Defender AV notifications may be sent to or persist across multiple sessions. In order to minimize this problem, you can use the lock down the user interface for Windows Defender AV. + +**Use Group Policy to hide notifications:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender > Client Interface** and configure the following settings: + +1. Double-click the **Suppress all notifications** setting and set the option to **Enabled**. Click **OK**. This prevents notifications from Windows Defender AV appearing in the action center on Windows 10 when scans or remediation is performed. +2. Double-click the **Enable headless UI mode** setting and set the option to **Enabled**. Click **OK**. This hides the entire Windows Defender AV user interface from users. + + +**Use Configuration Manager to hide notifications:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Advanced** section and configure the following settings: + +1. Set **Disable the client user interface** to **Yes**. This hides the entire Windows Defender AV user interface. +2. Set **Show notifications messages on the client computer...** to **Yes**. This hides notifications from appearing. + +3. Click **OK**. + +3. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + +### Disable scans after an update + +This setting will prevent a scan from occurring after receiving an update. You can apply this when creating the base image if you have also run a quick scan. This prevents the newly updated VM from performing a scan again (as you’ve already scanned it when you created the base image). + +>[!IMPORTANT] +>Running scans after an update will help ensure your VMs are protected with the latest definition updates. Disabling this option will reduce the protection level of your VMs and should only be used when first creating or deploying the base image. + +**Use Group Policy to disable scans after an update:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender > Signature Updates** and configure the following setting: + +1. Double-click the **Turn on scan after signature update** setting and set the option to **Disabled**. Click **OK**. This prevents a scan from running immediately after an update. + + +**Use Configuration Manager to disable scans after an update:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Scheduled scans** section and configure the following setting: + +1. Set **Check for the latest definition updates before running a scan** to **No**. This prevents a scan after an update. + +3. Click **OK**. + +2. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + + + + + +### Scan VMs that have been offline + +This setting will help ensure protection for a VM that has been offline for some time or has otherwise missed a scheduled scan. + +DisableCatchupQuickScan, is the setting that I use (set to OFF) to ensure that a quick scan is performed on a VM which has been offline and has missed a schedule scan. + + +**Use Group Policy to enable a catch-up scan:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender > Scan** and configure the following setting: + +1. Double-click the **Turn on catch-up quick scan** setting and set the option to **Enabled**. Click **OK**. This forces a scan if the VM has missed two or more consecutive scheduled scans. + + +**Use Configuration Manager to disable scans after an update:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Scheduled scans** section and configure the following setting: + +1. Set **Force a scan of the selected scan type if client computer is offline during...** to **Yes**. This forces a scan if the VM has missed two or more consecutive scheduled scans. + +3. Click **OK**. + +2. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + + + +### Exclusions +Windows Server 2016 contains Windows Defender Antivirus and will automatically deliver the right exclusions for servers running a VDI environment. However, if you are running an older Windows server version, you can refer to the exclusions that are applied on this page: +- [Automatic exclusions for Windows Server Antimalware](https://technet.microsoft.com/en-us/windows-server-docs/security/windows-defender/automatic-exclusions-for-windows-defender) + +## Additional resources + +- [Video: Microsoft Senior Program Manager Bryan Keller on how System Center Configuration Manger 2012 manages VDI and integrates with App-V]( http://channel9.msdn.com/Shows/Edge/Edge-Show-5-Manage-VDI-using-SCCM-2012#time=03m02s) +- [Project VRC: Antivirus impact and best practices on VDI](https://blogs.technet.microsoft.com/privatecloud/2013/12/06/orchestrated-offline-vm-patching-using-service-management-automation/) +- [TechNet forums on Remote Desktop Services and VDI](https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverTS) +- [SignatureDownloadCustomTask PowerShell script](https://www.powershellgallery.com/packages/SignatureDownloadCustomTask/1.4/DisplayScript) diff --git a/windows/keep-secure/detect-block-potentially-unwanted-apps-windows-defender-antivirus.md b/windows/keep-secure/detect-block-potentially-unwanted-apps-windows-defender-antivirus.md new file mode 100644 index 0000000000..30d7011a23 --- /dev/null +++ b/windows/keep-secure/detect-block-potentially-unwanted-apps-windows-defender-antivirus.md @@ -0,0 +1,110 @@ +--- +title: Block Potentially Unwanted Applications with Windows Defender AV +description: Enable the Potentially Unwanted Application (PUA) feature in Windows Defender Antivirus to block unwanted software such as adware. +keywords: pua, enable, unwanted software, unwanted apps, adware, browser toolbar, detect, block, windows defender +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: detect +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Detect and block Potentially Unwanted Applications + +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- System Center Configuration Manager +- PowerShell cmdlets +- Microsoft Intune + +The Potentially Unwanted Application (PUA) protection feature in Windows Defender Antivirus can identify and block PUAs from downloading and installing on endpoints in your network. + +These applications are not considered viruses, malware, or other types of threats, but might perform actions on endpoints that adversely affect their performance or use. PUA can also refer to applications that are considered to have a poor reputation. + +Typical PUA behavior includes: +- Various types of software bundling +- Ad-injection into web browsers +- Driver and registry optimizers that detect issues, request payment to fix the errors, but remain on the endpoint and make no changes or optimizations (also known as "rogue antivirus" programs) + +These applications can increase the risk of your network being infected with malware, cause malware infections to be harder to identify, and can waste IT resources in cleaning up the applications. + +## How it works + +PUAs are blocked when a user attempts to download or install the detected file, and if the file meets one of the following conditions: +- The file is being scanned from the browser +- The file is in the %downloads% folder +- The file is in the %temp% folder + +The file is placed in the quarantine section so it won’t run. + +When a PUA is detected on an endpoint, the endpoint will present a notification to the user ([unless notifications have been disabled](configure-notifications-windows-defender-antivirus.md)) in the same format as normal threat detections (prefaced with "PUA:"). + +They will also appear in the usual [quarantine list in the Windows Defender Security Center app](windows-defender-security-center-antivirus.md#detection-history). + + +## View PUA events + +PUA events are reported in the Windows Event Viewer and not in System Center Configuration Manager or Intune. + +See [Troubleshoot event IDs](troubleshoot-windows-defender-antivirus.md) for details on viewing Windows Defender Antivirus events. PUA events are recorded under event ID 1160. + + +## Configure the PUA protection feature + +You can enable the PUA protection feature with System Center Configuration Manager, PowerShell cmdlets, or Microsoft Intune. + +You can also use the PUA audit mode to detect PUA without blocking them. The detections will be captured in the Windows event log. + +This feature is useful if your company is conducting an internal software security compliance check and you’d like to avoid any false positives. + + +**Use Configuration Manager to configure the PUA protection feature:** + +PUA protection is enabled by default in System Center Configuration Manager (current branch), including version 1606 and later. + +See [How to create and deploy antimalware policies: Scheduled scans settings](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#real-time-protection-settings) for details on configuring System Center Configuration Manager (current branch). + +For Configuration Manager 2012, see [How to Deploy Potentially Unwanted Application Protection Policy for Endpoint Protection in Configuration Manager](https://technet.microsoft.com/library/hh508770.aspx#BKMK_PUA). + +> [!NOTE] +> PUA events are reported in the Windows Event Viewer and not in System Center Configuration Manager. + +**Use PowerShell cmdlets to configure the PUA protection feature:** + +Use the following cmdlet: + +```PowerShell +Set-MpPreference -PUAProtection +``` + +Setting the value for this cmdlet to `Enabled` will turn the feature on if it has been disabled. + +Setting `AuditMode` will detect PUAs but will not block them. + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + + + +**Use Intune to configure the PUA protection feature** + +See [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune) and [Windows Defender policy settings in Windows 10](https://docs.microsoft.com/en-us/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune#windows-defender-1) for more details. + + + +## Related topics + +- [Windows Defender Antivirus](windows-defender-antivirus-in-windows-10.md) +- [Configure behavioral, heuristic, and real-time protection](configure-protection-features-windows-defender-antivirus.md) + + diff --git a/windows/keep-secure/enable-cloud-protection-windows-defender-antivirus.md b/windows/keep-secure/enable-cloud-protection-windows-defender-antivirus.md new file mode 100644 index 0000000000..ddb0ce57ac --- /dev/null +++ b/windows/keep-secure/enable-cloud-protection-windows-defender-antivirus.md @@ -0,0 +1,153 @@ +--- +title: Enable cloud-delivered protection in Windows Defender Antivirus +description: Enable cloud-delivered protection to benefit from fast and advanced protection features. +keywords: windows defender antivirus, antimalware, security, cloud, block at first sight +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Enable cloud-delivered protection in Windows Defender AV + + + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) +- Microsoft Intune +- Windows Defender Security Center app + + +>[!NOTE] +>The Windows Defender Antivirus cloud service is a mechanism for delivering updated protection to your network and endpoints. Although it is called a cloud service, it is not simply protection for files stored in the cloud, rather it uses distributed resources and machine learning to deliver protection to your endpoints at a rate that is far faster than traditional signature updates. + + + +You can enable or disable Windows Defender Antivirus cloud-delivered protection with Group Policy, System Center Configuration Manager, PowerShell cmdlets, Microsoft Intune, or on individual clients in the Windows Defender Security Center app. + +See [Utilize Microsoft cloud-delivered protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) for an overview of Windows Defender Antivirus cloud-based protection. + +There are specific network-connectivity requirements to ensure your endpoints can connect to the cloud-delivered protection service. See [Configure and validate network connections for Windows Defender AV](configure-network-connections-windows-defender-antivirus.md) for more details. + +>[!NOTE] +>In Windows 10, there is no difference between the **Basic** and **Advanced** options described in this topic. This is a legacy distinction and choosing either setting will result in the same level of cloud-delivered protection. There is no difference in the type or amount of information that is shared. See the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?linkid=521839) for more information on what we collect. + + +**Use Group Policy to enable cloud-delivered protection:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > MAPS** + +1. Double-click the **Join Microsoft MAPS** setting and ensure the option is enabled and set to **Basic MAPS** or **Advanced MAPS**. Click **OK**. + +1. Double-click the **Send file samples when further analysis is required** setting and ensure the option is set to **Enabled** and the additional options are either of the following: + + 1. **Send safe samples** (1) + 1. **Send all samples** (3) + + > [!WARNING] + > Setting to 0 (Always Prompt) will lower the protection state of the device. Setting to 2 (Never send) means the [Block at First Sight](configure-block-at-first-sight-windows-defender-antivirus.md) feature will not function. + +1. Click **OK**. + + + +**Use Configuration Manager to enable cloud-delivered protection:** + +See [How to create and deploy antimalware policies: Cloud-protection service](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#cloud-protection-service) for details on configuring System Center Configuration Manager (current branch). + + +**Use PowerShell cmdlets to enable cloud-delivered protection:** + +Use the following cmdlets to enable cloud-delivered protection: + +```PowerShell +Set-MpPreference -MAPSReporting Advanced +Set-MpPreference -SubmitSamplesConsent 3 +``` +>[!NOTE] +>You can also set -SubmitSamplesConsent to 1. Setting it to 0 will lower the protection state of the device, and setting it to 2 means the [Block at First Sight](configure-block-at-first-sight-windows-defender-antivirus.md) feature will not function. + + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + +**Use Windows Management Instruction (WMI) to enable cloud-delivered protection:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn439474(v=vs.85).aspx) class for the following properties: + +```WMI +MAPSReporting +SubmitSamplesConsent +``` + +See the following for more information and allowed parameters: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + +**Use Intune to enable cloud-delivered protection** + +1. Open the [Microsoft Intune administration console](https://manage.microsoft.com/), and navigate to the associated policy you want to configure. +2. Under the **Endpoint Protection** setting, scroll down to the **Endpoint Protection Service** section set the **Submit files automatically when further analysis is required** setting to either of the following: + 1. **Send samples automatically** + 1. **Send all samples automatically** + + > [!WARNING] + > Setting to **Always Prompt** will lower the protection state of the device. Setting to **Never send** means the [Block at First Sight](configure-block-at-first-sight-windows-defender-antivirus.md) feature will not function. +5. Scoll down to the **Microsoft Active Protection Service** section and set the following settings: + + Setting | Set to + --|-- + Join Microsoft Active Protection Service | Yes + Membership level | Advanced + Receive dynamic definitions based on Microsoft Active Protection Service reports | Yes + +3. Save and [deploy the policy as usual](https://docs.microsoft.com/en-us/intune/deploy-use/common-windows-pc-management-tasks-with-the-microsoft-intune-computer-client). + +See [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune) for more details. + +**Enable cloud-delivered protection on individual clients with the Windows Defender Security Center app** +> [!NOTE] +> If the **Configure local setting override for reporting Microsoft MAPS** GP setting is set to **Disabled**, then the **Cloud-based protection** setting in Windows Settings will be greyed-out and unavailable. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings. + + +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then the **Virus & threat protection settings** label: + +![Screenshot of the Virus & threat protection settings label in the Windows Defender Security Center app](images/defender/wdav-protection-settings-wdsc.png) + +3. Confirm that **Cloud-based Protection** and **Automatic sample submission** are switched to **On**. + +>[!NOTE] +>If automatic sample submission has been configured with GP then the setting will be greyed-out and unavailble. + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-in-windows-10.md) +- [Configure the cloud block timeout period](configure-cloud-block-timeout-period-windows-defender-antivirus.md) +- [Configure the block at first sight feature](configure-block-at-first-sight-windows-defender-antivirus.md) +- [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) +- [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune)] +- [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) +- [Utilize Microsoft cloud-delivered protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) +- [How to create and deploy antimalware policies: Cloud-protection service](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#cloud-protection-service) \ No newline at end of file diff --git a/windows/keep-secure/enable-custom-ti-windows-defender-advanced-threat-protection.md b/windows/keep-secure/enable-custom-ti-windows-defender-advanced-threat-protection.md index e83fa5ae63..e717a28f79 100644 --- a/windows/keep-secure/enable-custom-ti-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/enable-custom-ti-windows-defender-advanced-threat-protection.md @@ -27,6 +27,8 @@ Before you can create custom threat intelligence (TI) using REST API, you'll nee 1. In the navigation pane, select **Preference Setup** > **Threat intel API**. + ![Image of threat intel API menu](images/atp-threat-intel-api.png) + 2. Select **Enable threat intel API**. This activates the **Azure Active Directory application** setup sections with pre-populated values. 3. Copy the individual values or select **Save details to file** to download a file that contains all the values. diff --git a/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md b/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md index 82a3908d87..0feb3a91f8 100644 --- a/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md +++ b/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md @@ -10,111 +10,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: dulcemv +redirect_url: /detect-block-potentially-unwanted-apps-windows-defender-antivirus/ --- # Detect and block Potentially Unwanted Application in Windows 10 -**Applies to:** - -- Windows 10 - -You can enable the Potentially Unwanted Application (PUA) feature in Managed Windows Defender to identify and block unwanted software during download and install time. - -Potentially Unwanted Application (PUA) refers to applications that are not considered viruses, malware, or other types of threats, but might perform actions on your computer that adversely affect your computing experience. It also refers to applications considered to have a poor reputation. - -Typical examples of PUA behavior include: -* Various types of software bundling -* Ad-injection into your browsers -* Driver and registry optimizers that detect issues, request payment to fix them, and persist - -These applications can increase the risk of your network being infected with malware, cause malware infections to be harder to identify among the noise, and can waste helpdesk, IT, and user time in cleaning up the applications. - -Since the stakes are higher in an enterprise environment, the potential disaster and potential productivity and performance disruptions that PUA brings can be a cause of concern. Hence, it is important to deliver trusted protection in this field. - -##Enable PUA protection in System Center Configuration Manager and Intune - -The PUA feature is available for enterprise users who are running System Center Configuration Manager or Intune in their infrastructure. - -###Configure PUA in System Center Configuration Manager - -For System Center Configuration Manager users, PUA is enabled by default. See the following topics for configuration details: - -If you are using these versions | See these topics -:---|:--- -System Center Configuration Manager (current branch) version 1606 | [Create a new antimalware policy](https://technet.microsoft.com/en-US/library/mt613199.aspx#To-create-a-new-antimalware-policy)
[Real-time Protection Settings](https://technet.microsoft.com/en-US/library/mt613199.aspx#Real-time-Protection-Settings) -System Center 2012 R2 Endpoint Protection
System Center 2012 Configuration Manager
System Center 2012 Configuration Manager SP1
System Center 2012 Configuration Manager SP2
System Center 2012 R2 Configuration Manager
System Center 2012 Endpoint Protection SP1
System Center 2012 Endpoint Protection
System Center 2012 R2 Configuration Manager SP1| [How to Deploy Potentially Unwanted Application Protection Policy for Endpoint Protection in Configuration Manager](https://technet.microsoft.com/library/hh508770.aspx#BKMK_PUA) - -
-###Use PUA audit mode in System Center Configuration Manager - -You can use PowerShell to detect PUA without blocking them. In fact, you can run audit mode on individual machines. This feature is useful if your company is conducting an internal software security compliance check and you’d like to avoid any false positives. - -1. Open PowerShell as Administrator:
- - a. Click **Start**, type **powershell**, and press **Enter**. - - b. Click **Windows PowerShell** to open the interface. - >[!NOTE] - >You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt. -2. Enter the PowerShell command: - - ```text - set-mpPreference -puaprotection 2 - ``` -> [!NOTE] -> PUA events are reported in the Windows Event Viewer and not in System Center Configuration Manager. - - -###Configure PUA in Intune - - PUA is not enabled by default. You need to [Create and deploy a PUA configuration policy to use it](https://docs.microsoft.com/en-us/intune/deploy-use/manage-settings-and-features-on-your-devices-with-microsoft-intune-policies). See the [Potentially Unwanted Application Detection policy setting](https://docs.microsoft.com/en-us/intune/deploy-use/windows-10-policy-settings-in-microsoft-intune) for details. - - -###Use PUA audit mode in Intune - - You can detect PUA without blocking them from your client so you can gain insights into what can be blocked. - -1. Open PowerShell as Administrator:
- - a. Click **Start**, type **powershell**, and press **Enter**. - - b. Click **Windows PowerShell** to open the interface. - - >[!NOTE] - >You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt. - -2. Enter the PowerShell command: - - ```text - set-mpPreference -puaprotection 1 - ``` - -##View PUA events - -PUA events are reported in the Windows Event Viewer and not in System Center Configuration Manager or Intune. To view PUA events: - -1. Open **Event Viewer**. -2. In the console tree, expand **Applications and Services Logs**, then **Microsoft**, then **Windows**, then **Windows Defender**. -3. Double-click on **Operational**. -4. In the details pane, view the list of individual events to find your event. PUA events are under Event ID 1160 along with detection details. - -You can find a complete list of the Microsoft antimalware event IDs, the symbol, and the description of each ID in [Windows Server Antimalware Events TechNet](https://technet.microsoft.com/library/dn913615.aspx). - - -##What PUA notifications look like - -When a detection occurs, end users who enabled the PUA detection feature will see the following notification: - - -To see historical PUA detections that occurred on a PC, users can go to History, then **Quarantined items** or **All detected items**. - -##PUA threat naming convention - -When enabled, potentially unwanted applications are identified with threat names that start with “PUA:”, such as, PUA:Win32/Creprote. - -##PUA blocking conditions - -PUA protection quarantines the file so they won’t run. PUA will be blocked only at download or install-time. A file will be included for blocking if it has been identified as PUA and meets one of the following conditions: -* The file is being scanned from the browser -* The file is in the %downloads% folder -* Or if the file in the %temp% folder +This page has been redirected to *Detect and block unwanted applications*. \ No newline at end of file diff --git a/windows/keep-secure/evaluate-windows-defender-antivirus.md b/windows/keep-secure/evaluate-windows-defender-antivirus.md new file mode 100644 index 0000000000..af84e29eb5 --- /dev/null +++ b/windows/keep-secure/evaluate-windows-defender-antivirus.md @@ -0,0 +1,51 @@ +--- +title: Evaluate Windows Defender Antivirus +description: Businesses of all sizes can use this guide to evaluate and test the protection offered by Windows Defender Antivirus in Windows 10. +keywords: windows defender antivirus, cloud protection, cloud, antimalware, security, defender, evaluate, test, protection, compare, real-time protection +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Evaluate Windows Defender Antivirus protection + + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + + +If youre an enterprise security administrator, and you want to determine how well Windows Defender Antivirus protects you from viruses, malware, and potentially unwanted applications, then you can use this guide to help you evaluate Microsoft protection. + +It explains the important features available for both small and large enterprises in Windows Defender, and how they will increase malware detection and protection across your network. + +You can choose to configure and evaluate each setting independently, or all at once. We have grouped similar settings based upon typical evaluation scenarios, and include instructions for using PowerShell to enable the settings. + +The guide is available in PDF format for offline viewing: +- [Download the guide in PDF format](https://www.microsoft.com/download/details.aspx?id=54795) + +You can also download a PowerShell that will enable all the settings described in the guide automatically. You can obtain the script alongside the PDF download above, or individually from PowerShell Gallery: +- [Download the PowerShell script to automatically configure the settings](https://www.powershellgallery.com/packages/WindowsDefender_InternalEvaluationSettings/1.0/DisplayScript) + +> [!IMPORTANT] +> The guide is currently intended for single-machine evaluation of Windows Defender Antivirus protection. Enabling all of the settings in this guide may not be suitable for real-world deployment. +> +> For the latest recommendations for real-world deployment and monitoring of Windows Defender Antivirus across a network, see the [Deploy, manage, and report](deploy-manage-report-windows-defender-antivirus.md) topic in this library. + + +## Related topics + +- [Windows Defender Antivirus](windows-defender-in-windows-10.md) +- [Deploy, manage, and report](deploy-manage-report-windows-defender-antivirus.md) + + + diff --git a/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md b/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md new file mode 100644 index 0000000000..e840000672 --- /dev/null +++ b/windows/keep-secure/experiment-custom-ti-windows-defender-advanced-threat-protection.md @@ -0,0 +1,85 @@ +--- +title: Experiment with custom threat intelligence alerts +description: Use this end-to-end guide to start using the Windows Defender ATP threat intelligence API. +keywords: alert definitions, indicators of compromise, threat intelligence, custom threat intelligence, rest api, api +search.product: eADQiWindows 10XVcnh +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: security +author: mjcaparas +localizationpriority: high +--- + +# Experiment with custom threat intelligence (TI) alerts + +**Applies to:** + +- Windows 10 Enterprise +- Windows 10 Education +- Windows 10 Pro +- Windows 10 Pro Education +- Windows Defender Advanced Threat Protection (Windows Defender ATP) + +[Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.] + +With the Windows Defender ATP threat intelligence API, you can create custom threat intelligence alerts that can help you keep track of possible attack activities in your organization. + +For more information about threat intelligence concepts, see [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md). + +This article demonstrates an end-to-end usage of the threat intelligence API to get you started in using the threat intelligence API. + +You'll be guided through sample steps so you can experience how the threat intelligence API feature works. Sample steps include creating alerts definitions and indicators of compromise (IOCs), and examples of how triggered custom TI alerts look like. + +## Step 1: Enable the threat intelligence API and obtain authentication details +To use the threat intelligence API feature, you'll need to enable the feature. For more information, see [Enable the custom threat intelligence application](enable-custom-ti-windows-defender-advanced-threat-protection.md). + +This step is required to generate security credentials that you need to use while working with the API. + +## Step 2: Create a sample alert definition and IOCs +This step will guide you in creating an alert definition and an IOC for a malicious IP. + +1. Open a Windows PowerShell ISE. + +2. Copy and paste the following PowerShell script. This script will upload a sample alert definition and IOC to Windows Defender ATP which you can use to generate an alert. + + NOTE:
+ Make sure you replace the `authUrl`, `clientId`, and `clientSecret` values with your details which you saved in when you enabled the threat intelligence application. + + [!code[ExampleScript](./code/example-script.ps1#L1-L60)] + +3. Run the script and verify that the operation succeeded in the results the window. Wait up to 20 minutes until the new or updated alert definition propagates to the detection engines. + + ![Image of the script running](images/atp-running-script.png) + + NOTE:
+ If you get the exception “The remote server returned an error: (407) Proxy Authentication Required", you need to add the proxy configuration by adding the following code to the PowerShell script: + + ```syntax + $webclient=New-Object System.Net.WebClient + $creds=Get-Credential + $webclient.Proxy.Credentials=$creds + ``` + +## Step 3: Simulate a custom TI alert +This step will guide you in simulating an event in connection to a malicious IP that will trigger the Windows Defender ATP custom TI alert. + +1. Open a Windows PowerShell ISE in the machine you onboarded to Windows Defender ATP. + +2. Type `Invoke-WebRequest 52.184.197.12` in the editor and click **Run**. This call will generate a network communication event to a Microsoft's dedicated demo server that will raise an alert based on the custom alert definition. + + ![Image of editor with command to Invoke-WebRequest](images/atp-simulate-custom-ti.png) + +## Step 4: Explore the custom alert in the portal +This step will guide you in exploring the custom alert in the portal. + +1. Open the [Windows Defender ATP portal](http: /securitycenter.windows.com/) on a browser. + +2. Log in with your Windows Defender ATP credentials. + +3. The dashboard should display the custom TI alert for the victim machine resulting from the simulated attack. + + ![Image of sample custom ti alert in the portal](images/atp-sample-custom-ti-alert.png) + +> [!NOTE] +> It can take up to 15 minutes for the alert to appear in the portal. diff --git a/windows/keep-secure/get-started-with-windows-defender-for-windows-10.md b/windows/keep-secure/get-started-with-windows-defender-for-windows-10.md index f7c920bb4f..e9c2b82470 100644 --- a/windows/keep-secure/get-started-with-windows-defender-for-windows-10.md +++ b/windows/keep-secure/get-started-with-windows-defender-for-windows-10.md @@ -8,183 +8,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: jasesso +redirect_url: /deploy-manage-report-windows-defender-antivirus/ --- # Update and manage Windows Defender in Windows 10 -**Applies to** -- Windows 10 - -IT professionals can manage Windows Defender on Windows 10 endpoints in their organization using Microsoft Active Directory or Windows Server Update Services (WSUS), apply updates to endpoints, and manage scans using: - -- Group Policy Settings -- Windows Management Instrumentation (WMI) -- PowerShell - -## Manage Windows Defender endpoints through Active Directory and WSUS - -All Windows 10 endpoints are installed with Windows Defender and include support for management through: -- Active Directory -- WSUS - -You can use the Active Directory to configure the settings; Group policies can be used for centralized configuration and enforcement of many Windows Defender settings including client user interface, scan settings, and exclusions. -WSUS can be used to view basic update compliance and deploy updates manually or through automatic rules. - -Note that System Center 2012 R2 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, and Microsoft Intune can provide centralized management of Windows Defender, including: - -- Settings management -- Definition update management -- Alerts and alert management -- Reports and reporting - -When you enable *Endpoint Protection* on your clients, it will install an additional management layer on Windows Defender to manage the in-box Windows Defender agent. While the client user interface will still appear as Windows Defender, the management layer for System Center Endpoint Protection or Intune will be listed in the **Add/Remove Programs** control panel, though it will appear as if the full product is installed. Learn more about managing *Endpoint Protection*: - -- [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](https://technet.microsoft.com/library/dn646970.aspx) -- [Endpoint Protection in Configuration Manager](https://technet.microsoft.com/library/hh508760.aspx) - -Read more about System Center Configuration Manager in [Introduction to Endpoint Protection in Configuration Manager](https://technet.microsoft.com/library/hh508781.aspx). -> **Important:**  You must be licensed to use *Endpoint Protection* to manage clients in your Configuration Manager hierarchy. -  -## Apply updates to Windows Defender endpoints - -It is important to keep Windows Defender endpoints updated to ensure they are protected. All Windows Defender updates, including General Distribution Release (GDR) updates, are now applied as operating system updates. -You can manage the distribution of updates through the [Windows Server Update Services (WSUS)](https://technet.microsoft.com/windowsserver/bb332157). - -## Manage email scans in Windows Defender - -You can use Windows Defender to scan email files. Malware can install itself and hide in email files, and although real-time protection offers you the best protection from email malware, you can also scan emails stored on your PC or server with Windows Defender. -> **Important:**  Mail scanning only applies to on-demand and scheduled scans, not on-access scans. -  -Windows Defender scans Microsoft Office Outlook 2003 and older email files. We identify the file type at run-time based on the content of the file, not on location or extension. -> **Note: **  Scanning email files might increase the time required to complete a scan. -  -Windows Defender can extract embedded objects within a file (attachments and archived files, for example) and scan internally. -> **Note:**  While Windows Defender can be configured to scan email files, it can only remediate threats detected inside certain files, for example: -- DBX -- MBX -- MIME -  -You can configure Windows Defender to scan PST files used by Outlook 2003 or older versions (where the archive type is set to non-uni-code), but Windows Defender cannot remediate threats detected inside PST files. We recommend using real-time protection to protect against email malware. - -If Windows Defender detects a threat inside an email, it will show you the following information to assist you in identifying the compromised email, so you can remediate the threat: -- Email subject -- Attachment name -Email scanning in Windows Defender is turned off by default. There are three ways you can manage scans through Windows Defender: -- *Group Policy* settings -- WMI -- PowerShell -> **Important:**  There are some risks associated with scanning some Microsoft Outlook files and email messages. You can read about tips and risks associated with scanning Outlook files and email messages in the following articles: -- [Scanning Outlook files in Outlook 2013](https://technet.microsoft.com/library/dn769141.aspx#bkmk-1) -- [Scanning email messages in Outlook 2013](https://technet.microsoft.com/library/dn769141.aspx#bkmk-2) -  -## Use *Group Policy* settings to enable email scans - -This policy setting allows you to turn on email scanning. When email scanning is enabled, the engine will parse the mailbox and mail files to analyze the mail bodies and attachments. - -Turn on email scanning with the following *Group Policy* settings: -1. Open the **Group Policy Editor**. -2. In the **Local Computer Policy** tree, expand **Computer Configuration**, then **Administrative Templates**, then **Windows Components**, then **Windows Defender**. -3. Click **Scan**. -4. Double-click **Turn on e-mail scanning**. - - This will open the **Turn on e-mail scanning** window: - - ![turn on e-mail scanning window](images/defender-scanemailfiles.png) - -5. Select **Enabled**. -6. Click **OK** to apply changes. - -## Use WMI to disable email scans - -You can write a WMI script or application to disable email scanning. Read more about [WMI in this article](https://msdn.microsoft.com/library/windows/desktop/dn439477.aspx), and read about [Windows Preference classes in this article](https://msdn.microsoft.com/library/windows/desktop/dn455323.aspx). - -Use the **DisableEmailScanning** property of the **MSFT\_MpPreference** class (part of the Windows DefenderWMI provider) to enable or disable this setting: -**DisableEmailScanning** -Data type: **boolean** -Access type: Read-only -Disable email scanning. - -## Use PowerShell to enable email scans - -You can also enable email scanning using the following PowerShell parameter: -1. Open PowerShell or PowerShellIntegrated Scripting Environment (ISE). -2. Type **Set-MpPreference -DisableEmailScanning $false**. - -Read more about this in: -- [Scripting with Windows PowerShell](https://technet.microsoft.com/library/bb978526.aspx) -- [Defender Cmdlets](https://technet.microsoft.com/library/dn433280.aspx) - -## Manage archive scans in Windows Defender - -You can use Windows Defender to scan archive files. Malware can install itself and hide in archive files, and although real-time protection offers you the best protection from malware, you can also scan archives stored on your PC or server with Windows Defender. -> **Important:**  Archive scanning only applies to on-demand and scheduled scans, not on-access scans. -  -Archive scanning in Windows Defender is turned on by default. There are four ways you can manage scans through Windows Defender: -- *Group Policy* settings -- WMI -- PowerShell -- Endpoint Protection -> **Note:**  Scanning archive files might increase the time required to complete a scan. -  -If you exclude an archive file type by using the **Extensions** box, Windows Defender will not scan files with that extension (no matter what the content is), even when you have selected the **Scan archive files** check box. For example, if you exclude .rar files but there’s a .r00 file that’s actually .rar content, it will still be scanned if archive scanning is enabled. - -## Use *Group Policy* settings to enable archive scans - -This policy setting allows you to turn on archive scanning. - -Turn on email scanning with the following *Group Policy* settings: -1. Open the **Group Policy Editor**. -2. In the **Local Computer Policy** tree, expand **Computer Configuration**, then **Administrative Templates**, then **Windows Components**, then **Windows Defender**. -3. Click **Scan**. -4. Double-click **Scan archive files**. - - This will open the **Scan archive files** window: - - ![scan archive files window](images/defender-scanarchivefiles.png) - -5. Select **Enabled**. -6. Click **OK** to apply changes. - -There are a number of archive scan settings in the **Scan** repository you can configure through *Group Policy*, for example: -- Maximum directory depth level into which archive files are unpacked during scanning - - ![specify the maximum depth to scan archive files window](images/defender-scanarchivedepth.png) - -- Maximum size of archive files that will be scanned - - ![specify the maximum size of archive files to be scanned window](images/defender-scanarchivesize.png) - -- Maximum percentage CPU utilization permitted during a scan - - ![specify the maximum percentage od cpu utilization during a scan window](images/defender-scanarchivecpu.png) - -## Use WMI to disable archive scans - -You can write a WMI script or application to disable archive scanning. Read more about [WMI in this article](https://msdn.microsoft.com/library/windows/desktop/dn439477.aspx), and read about [Windows Preference classes in this article](https://msdn.microsoft.com/library/windows/desktop/dn455323.aspx). - -Use the **DisableArchiveScanning** property of the **MSFT\_MpPreference** class (part of the Windows DefenderWMI provider) to enable or disable this setting: -**DisableArchiveScanning** -Data type: **boolean** -Access type: Read-only -Disable archive scanning. - -## Use PowerShell to enable archive scans - -You can also enable archive scanning using the following PowerShell parameter: -1. Open PowerShell or PowerShellISE. -2. Type **Set-MpPreference -DisableArchiveScanning $false**. - -Read more about this in: -- [Scripting with Windows PowerShell](https://technet.microsoft.com/library/bb978526.aspx) -- [Defender Cmdlets](https://technet.microsoft.com/library/dn433280.aspx) - -## Use Endpoint Protection to configure archive scans - -In Endpoint Protection, you can use the advanced scanning options to configure archive scanning. For more information, see [What are advanced scanning options?](https://technet.microsoft.com/library/ff823807.aspx) - -## Related topics - -- [Configure Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md) -- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) -  -  +This page has been redirected to *Windows Defender Antivirus in Windows 10*. diff --git a/windows/keep-secure/images/atp-running-script.png b/windows/keep-secure/images/atp-running-script.png new file mode 100644 index 0000000000..ebfdebadc5 Binary files /dev/null and b/windows/keep-secure/images/atp-running-script.png differ diff --git a/windows/keep-secure/images/atp-sample-custom-ti-alert.png b/windows/keep-secure/images/atp-sample-custom-ti-alert.png new file mode 100644 index 0000000000..e536f6f4cc Binary files /dev/null and b/windows/keep-secure/images/atp-sample-custom-ti-alert.png differ diff --git a/windows/keep-secure/images/atp-simulate-custom-ti.png b/windows/keep-secure/images/atp-simulate-custom-ti.png new file mode 100644 index 0000000000..2828654c79 Binary files /dev/null and b/windows/keep-secure/images/atp-simulate-custom-ti.png differ diff --git a/windows/keep-secure/images/atp-threat-intel-api.png b/windows/keep-secure/images/atp-threat-intel-api.png new file mode 100644 index 0000000000..ef6720b29e Binary files /dev/null and b/windows/keep-secure/images/atp-threat-intel-api.png differ diff --git a/windows/keep-secure/images/defender/malware-detected.png b/windows/keep-secure/images/defender/malware-detected.png new file mode 100644 index 0000000000..91fce5a44b Binary files /dev/null and b/windows/keep-secure/images/defender/malware-detected.png differ diff --git a/windows/keep-secure/images/defender/order-update-sources-wdav.png b/windows/keep-secure/images/defender/order-update-sources-wdav.png new file mode 100644 index 0000000000..904f314699 Binary files /dev/null and b/windows/keep-secure/images/defender/order-update-sources-wdav.png differ diff --git a/windows/keep-secure/images/defender/quarantine.png b/windows/keep-secure/images/defender/quarantine.png new file mode 100644 index 0000000000..6a908aedec Binary files /dev/null and b/windows/keep-secure/images/defender/quarantine.png differ diff --git a/windows/keep-secure/images/defender/wdav-bafs-edge.png b/windows/keep-secure/images/defender/wdav-bafs-edge.png new file mode 100644 index 0000000000..d7376570b6 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-bafs-edge.png differ diff --git a/windows/keep-secure/images/defender/wdav-bafs-ie.png b/windows/keep-secure/images/defender/wdav-bafs-ie.png new file mode 100644 index 0000000000..94cb3a30fb Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-bafs-ie.png differ diff --git a/windows/keep-secure/images/defender/wdav-extension-exclusions.png b/windows/keep-secure/images/defender/wdav-extension-exclusions.png new file mode 100644 index 0000000000..e1a86e09e0 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-extension-exclusions.png differ diff --git a/windows/keep-secure/images/defender/wdav-headless-mode-1607.png b/windows/keep-secure/images/defender/wdav-headless-mode-1607.png new file mode 100644 index 0000000000..7ccaf5d0ff Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-headless-mode-1607.png differ diff --git a/windows/keep-secure/images/defender/wdav-headless-mode-1703.png b/windows/keep-secure/images/defender/wdav-headless-mode-1703.png new file mode 100644 index 0000000000..d4288ca82c Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-headless-mode-1703.png differ diff --git a/windows/keep-secure/images/defender/wdav-headless-mode-off-1703.png b/windows/keep-secure/images/defender/wdav-headless-mode-off-1703.png new file mode 100644 index 0000000000..d5599ce99b Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-headless-mode-off-1703.png differ diff --git a/windows/keep-secure/images/defender/wdav-history-wdsc.png b/windows/keep-secure/images/defender/wdav-history-wdsc.png new file mode 100644 index 0000000000..cdc75b8852 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-history-wdsc.png differ diff --git a/windows/keep-secure/images/defender/wdav-malware-detected.png b/windows/keep-secure/images/defender/wdav-malware-detected.png new file mode 100644 index 0000000000..b0add084db Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-malware-detected.png differ diff --git a/windows/keep-secure/images/defender/wdav-order-update-sources.png b/windows/keep-secure/images/defender/wdav-order-update-sources.png new file mode 100644 index 0000000000..fb6fefee98 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-order-update-sources.png differ diff --git a/windows/keep-secure/images/defender/wdav-path-exclusions.png b/windows/keep-secure/images/defender/wdav-path-exclusions.png new file mode 100644 index 0000000000..2fb0f6e107 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-path-exclusions.png differ diff --git a/windows/keep-secure/images/defender/wdav-process-exclusions.png b/windows/keep-secure/images/defender/wdav-process-exclusions.png new file mode 100644 index 0000000000..559d65ac2f Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-process-exclusions.png differ diff --git a/windows/keep-secure/images/defender/wdav-protection-settings-wdsc.png b/windows/keep-secure/images/defender/wdav-protection-settings-wdsc.png new file mode 100644 index 0000000000..854e2b209d Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-protection-settings-wdsc.png differ diff --git a/windows/keep-secure/images/defender/wdav-quarantined-history-wdsc.png b/windows/keep-secure/images/defender/wdav-quarantined-history-wdsc.png new file mode 100644 index 0000000000..e8e2eec956 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-quarantined-history-wdsc.png differ diff --git a/windows/keep-secure/images/defender/wdav-settings-old.png b/windows/keep-secure/images/defender/wdav-settings-old.png new file mode 100644 index 0000000000..05c23e510a Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-settings-old.png differ diff --git a/windows/keep-secure/images/defender/wdav-wdsc.png b/windows/keep-secure/images/defender/wdav-wdsc.png new file mode 100644 index 0000000000..81c50c1635 Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-wdsc.png differ diff --git a/windows/keep-secure/images/defender/wdav-windows-defender-app-old.png b/windows/keep-secure/images/defender/wdav-windows-defender-app-old.png new file mode 100644 index 0000000000..09cea8052c Binary files /dev/null and b/windows/keep-secure/images/defender/wdav-windows-defender-app-old.png differ diff --git a/windows/keep-secure/images/windows-defender-security-center.png b/windows/keep-secure/images/windows-defender-security-center.png new file mode 100644 index 0000000000..a3286fb528 Binary files /dev/null and b/windows/keep-secure/images/windows-defender-security-center.png differ diff --git a/windows/keep-secure/images/windows-defender-smartscreen-control.png b/windows/keep-secure/images/windows-defender-smartscreen-control.png new file mode 100644 index 0000000000..b2700addba Binary files /dev/null and b/windows/keep-secure/images/windows-defender-smartscreen-control.png differ diff --git a/windows/keep-secure/interactive-logon-prompt-user-to-change-password-before-expiration.md b/windows/keep-secure/interactive-logon-prompt-user-to-change-password-before-expiration.md index 3b6173cf5c..e188c2bed0 100644 --- a/windows/keep-secure/interactive-logon-prompt-user-to-change-password-before-expiration.md +++ b/windows/keep-secure/interactive-logon-prompt-user-to-change-password-before-expiration.md @@ -43,10 +43,10 @@ The following table lists the actual and effective default values for this polic | - | - | | Default Domain Policy| Not defined| | Default Domain Controller Policy | Not defined| -| Stand-Alone Server Default Settings | 14 days| -| DC Effective Default Settings | 14 days | -| Member Server Effective Default Settings| 14 days | -| Client Computer Effective Default Settings | 14 days| +| Stand-Alone Server Default Settings | 5 days| +| DC Effective Default Settings | 5 days | +| Member Server Effective Default Settings| 5 days | +| Client Computer Effective Default Settings | 5 days|   ## Policy management @@ -74,11 +74,11 @@ If user passwords are configured to expire periodically in your organization, us ### Countermeasure -Configure the **Interactive logon: Prompt user to change password before expiration** setting to 14 days. +Configure the **Interactive logon: Prompt user to change password before expiration** setting to 5 days. ### Potential impact -Users see a dialog-box prompt to change their password each time that they log on to the domain when their password is configured to expire in 14 or fewer days. +Users see a dialog-box prompt to change their password each time that they log on to the domain when their password is configured to expire in 5 or fewer days. ## Related topics diff --git a/windows/keep-secure/manage-event-based-updates-windows-defender-antivirus.md b/windows/keep-secure/manage-event-based-updates-windows-defender-antivirus.md new file mode 100644 index 0000000000..39ecd14409 --- /dev/null +++ b/windows/keep-secure/manage-event-based-updates-windows-defender-antivirus.md @@ -0,0 +1,179 @@ +--- +title: Apply Windows Defender AV updates after certain events +description: Manage how Windows Defender Antivirus applies proteciton updates after startup or receiving cloud-delivered detection reports. +keywords: updates, protection, force updates, events, startup, check for latest, notifications +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage event-based forced updates + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) + + +Windows Defender AV allows you to determine if updates should (or should not) occur after certain events, such as at startup or after receiving specific reports from the cloud-delivered protection service. + + +## Check for protection updates before running a scan + +You can use Group Policy, Configuration Manager, PowerShell cmdlets, and WMI to force Windows Defender AV to check and download protection updates before running a scheduled scan. + + +**Use Group Policy to check for protection updates before running a scan:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Scan**. + +6. Double-click the **Check for the latest virus and spyware definitions before running a scheduled scan** setting and set the option to **Enabled**. + +7. Click **OK**. + +**Use Configuration Manager to check for protection updates before running a scan:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Scheduled scans** section and set **Check for the latest definition updates before running a scan** to **Yes**. + +3. Click **OK**. + +4. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + +**Use PowerShell cmdlets to to check for protection updates before running a scan:** + +Use the following cmdlets: + +```PowerShell +Set-MpPreference -CheckForSignaturesBeforeRunningScan +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + + +**Use Windows Management Instruction (WMI) to to check for protection updates before running a scan** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +CheckForSignaturesBeforeRunningScan +``` + +See the following for more information: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + + + + + +## Check for protection updates on startup + +You can use Group Policy to force Windows Defender AV to check and download protection updates when the machine is started. + +**Use Group Policy to download protection updates at startup:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates**. + +5. Double-click the **Check for the latest virus and spyware definitions on startup** setting and set the option to **Enabled**. + +6. Click **OK**. + +You can also use Group Policy, PowerShell, or WMI to configure Windows Defender AV to check for updates at startup even when it is not running. + +**Use Group Policy to download updates when Windows Defender AV is not present:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates**. + +6. Double-click the **Initiate definition update on startup** setting and set the option to **Enabled**. + +7. Click **OK**. + +**Use PowerShell cmdlets to download updates when Windows Defender AV is not present:** + +Use the following cmdlets to enable cloud-delivered protection: + +```PowerShell +Set-MpPreference -SignatureDisableUpdateOnStartupWithoutEngine +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + + +**Use Windows Management Instruction (WMI) to download updates when Windows Defender AV is not present:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +SignatureDisableUpdateOnStartupWithoutEngine +``` + +See the following for more information: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + + + + + +## Allow ad hoc changes to protection based on cloud-delivered protection + +Windows Defender AV can make changes to its protection based on cloud-delivered protection. This can occur outside of normal or scheduled protection updates. + +If you have enabled cloud-delivered protection, Windows Defender AV will send files it is suspicious about to the Windows Defender cloud. If the cloud service reports that the file is malicious, and the file is detected in a recent protection update, you can use Group Policy to configure Windows Defender AV to automatically receive that protection update. Other important protection updates can also be applied. + +**Use Group Policy to automatically download recent updates based on cloud-delivered protection:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates** and configure the following: + 1. Double-click the **Allow real-time definition updates based on reports to Microsoft MAPS** setting and set the option to **Enabled**. Click **OK**. + 2. Double-click the **Allow notifications to disable definitions based reports to Microsoft MAPS** setting and set the option to **Enabled**. Click **OK**. + + + +## Related topics + +- [Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) + + + diff --git a/windows/keep-secure/manage-outdated-endpoints-windows-defender-antivirus.md b/windows/keep-secure/manage-outdated-endpoints-windows-defender-antivirus.md new file mode 100644 index 0000000000..87b9ad4cbd --- /dev/null +++ b/windows/keep-secure/manage-outdated-endpoints-windows-defender-antivirus.md @@ -0,0 +1,190 @@ +--- +title: Apply Windows Defender AV protection updates to out of date endpoints +description: Define when and how updates should be applied for endpoints that have not updated in a while. +keywords: updates, protection, out-of-date, outdated, old, catch-up +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage updates and scans for endpoints that are out of date + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) + + + +Windows Defender AV lets you define how long an endpoint can avoid an update or how many scans it can miss before it is required to update and scan itself. This is especially useful in environments where devices are not often connected to a corporate or external network, or devices that are not used on a daily basis. + +For example, an employee that uses a particular PC is on break for three days and does not log on to their PC during that time. + +When the user returns to work and logs on to their PC, Windows Defender AV will immediately check and download the latest protection updates, and run a scan. + +## Set up catch-up protection updates for endpoints that haven't updated for a while + +If Windows Defender AV did not download protection updates for a specified period, you can set it up to automatically check and download the latest update at the next log on. This is useful if you have [globally disabled automatic update downloads on startup](manage-event-based-updates-windows-defender-antivirus.md). + +**Use Group Policy to enable and configure the catch-up update feature:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates**. + +6. Double-click the **Define the number of days after which a catch-up definition update is required** setting and set the option to **Enabled**. Enter the number of days after which you want Windows Defender AV to check for and download the latest protection update. + +7. Click **OK**. + +**Use PowerShell cmdlets to configure catch-up protection updates:** + +Use the following cmdlets to enable cloud-delivered protection: + +```PowerShell +Set-MpPreference -SignatureUpdateCatchupInterval +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + +**Use Windows Management Instruction (WMI) to configure catch-up protection updates:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +SignatureUpdateCatchupInterval +``` + +See the following for more information and allowed parameters: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + +**Use Configuration Manager to configure catch-up protection updates:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Definition updates** section and configure the following settings: + + 1. Set **Force a definition update if the client computer is offline for more than two consecutive scheduled updates** to **Yes**. + 2. For the **If Configuration Manager is used as a source for definition updates...**, specify the hours before which the protection updates delivered by Configuration Manager should be considered out-of-date. This will cause the next update location to be used, based on the defined [fallback source order](manage-protection-updates-windows-defender-antivirus.md#fallback-order). + +3. Click **OK**. + +4. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + + +## Set the number of days before protection is reported as out-of-date + +You can also specify the number of days after which Windows Defender AV protection is considered old or out-of-date. After the specified number of days, the client will report itself as out-of-date, and show an error to the user of the PC. It may also cause Windows Defender AV to attempt to download an update from other sources (based on the defined [fallback source order](manage-protection-updates-windows-defender-antivirus.md#fallback-order). + +**Use Group Policy to specify the number of days before protection is considered out-of-date:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates** and configure the following settings: + + 1. Double-click the **Define the number of days before spyware definitions are considered out of date** setting and set the option to **Enabled**. Enter the number of days after which you want Windows Defender AV to consider spyware definitions as out-of-date. + + 2. Click **OK**. + + 3. Double-click the **Define the number of days before virus definitions are considered out of date** setting and set the option to **Enabled**. Enter the number of days after which you want Windows Defender AV to consider virus and other threat definitions as out-of-date. + + 4. Click **OK**. + + + + +## Set up catch-up scans for endpoints that have not been scanned for a while + +You can set the number of consecutive scheduled scans that can be missed before Windows Defender AV will force a scan. + +The process for enabling this feature is: + +1. Set up at least one scheduled scan (see the [Schedule scans](scheduled-catch-up-scans-windows-defender-antivirus.md) topic). +2. Enable the catch-up scan feature. +3. Define the number of scans that can be skipped before a catch-up scan occurs. + +This feature can be enabled for both full and quick scans. + +**Use Group Policy to enable and configure the catch-up scan feature:** + +1. Ensure you have set up at least one scheduled scan. + +2. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Scan** and configure the following settings: + + 1. If you have set up scheduled quick scans, double-click the **Turn on catch-up quick scan** setting and set the option to **Enabled**. + 2. If you have set up scheduled full scans, double-click the **Turn on catch-up full scan** setting and set the option to **Enabled**. Click **OK**. + 3. Double-click the **Define the number of days after which a catch-up scan is forced** setting and set the option to **Enabled**. + 4. Enter the number of scans that can be missed before a scan will be automatically run when the user next logs on to the PC. The type of scan that is run is determined by the **Specify the scan type to use for a scheduled scan** (see the [Schedule scans](scheduled-catch-up-scans-windows-defender-antivirus.md) topic). Click **OK**. + +> [!NOTE] +> The GP setting title refers to the number of days. The setting, however, is applied to the number of scans (not days) before the catch-up scan will be run. + +**Use PowerShell cmdlets to XX:** + +Use the following cmdlets to enable cloud-delivered protection: + +```PowerShell +Set-MpPreference -DisableCatchupFullScan +Set-MpPreference -DisableCatchupQuickScan + +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + +**Use Windows Management Instruction (WMI) to configure catch-up scans:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +DisableCatchupFullScan +DisableCatchupQuickScan +``` + +See the following for more information and allowed parameters: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + +**Use Configuration Manager to configure catch-up scans:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Scheduled scans** section and **Force a scan of the selected scan type if client computer is offline...** to **Yes**. + +3. Click **OK**. + +4. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + + +## Related topics + +- [Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) diff --git a/windows/keep-secure/manage-protection-update-schedule-windows-defender-antivirus.md b/windows/keep-secure/manage-protection-update-schedule-windows-defender-antivirus.md new file mode 100644 index 0000000000..8112758cdd --- /dev/null +++ b/windows/keep-secure/manage-protection-update-schedule-windows-defender-antivirus.md @@ -0,0 +1,111 @@ +--- +title: Schedule Windows Defender Antivirus protection updates +description: Schedule the day, time, and interval for when protection updates should be downloaded +keywords: updates, security baselines, schedule updates +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage the schedule for when protection updates should be downloaded and applied + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) + + +Windows Defender AV lets you determine when it should look for and download updates. + +You can schedule updates for your endpoints by: + +- Specifying the day of the week to check for protection updates +- Specifying the interval to check for protection updates +- Specifying the time to check for protection updates + +You can also randomize the times when each endpoint checks and downloads protection updates. See the [Schedule scans](scheduled-catch-up-scans-windows-defender-antivirus.md) topic for more information. + +**Use Group Policy to schedule protection updates:** + +> [!IMPORTANT] +> By default, Windows Defender AV will check for an update 15 minutes before the time of any scheduled scans. Enabling these settings will override that default. + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates** and configure the following settings: + + 1. Double-click the **Specify the interval to check for definition updates** setting and set the option to **Enabled**. Enter the nuber of hours between updates. Click **OK**. + 2. Double-click the **Specify the day of the week to check for definition updates** setting and set the option to **Enabled**. Enter the day of the week to check for updates. Click **OK**. + 3. Double-click the **Specify the time to check for definition updates** setting and set the option to **Enabled**. Enter the time when updates should be checked. The time is based on the local time of the endpoint. Click **OK**. + + +**Use Configuration Manager to schedule protection updates:** + +1. On your System Center Configuration Manager console, open the antimalware policy you want to change (click **Assets and Compliance** in the navigation pane on the left, then expand the tree to **Overview** > **Endpoint Protection** > **Antimalware Policies**) + +2. Go to the **Definition updates** section. + +3. To check and download updates at a certain time: + 1. Set **Check for Endpoint Protection definitions at a specific interval...** to **0**. + 2. Set **Check for Endpoint Protection definitions daily at...** to the time when updates should be checked. + 3 +4. To check and download updates on a continual interval, Set **Check for Endpoint Protection definitions at a specific interval...** to the number of hours that should occur between updates. + +5. [Deploy the updated policy as usual](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#deploy-an-antimalware-policy-to-client-computers). + + +**Use PowerShell cmdlets to schedule protection updates:** + +Use the following cmdlets to enable cloud-delivered protection: + +```PowerShell +Set-MpPreference -SignatureScheduleDay +Set-MpPreference -SignatureScheduleTime +Set-MpPreference -SignatureUpdateInterval +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + +**Use Windows Management Instruction (WMI) to schedule protection updates:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +SignatureScheduleDay +SignatureScheduleTime +SignatureUpdateInterval +``` + +See the following for more information and allowed parameters: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + +## Related topics + +- [Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) + + + + + + diff --git a/windows/keep-secure/manage-protection-updates-windows-defender-antivirus.md b/windows/keep-secure/manage-protection-updates-windows-defender-antivirus.md new file mode 100644 index 0000000000..00e332bca1 --- /dev/null +++ b/windows/keep-secure/manage-protection-updates-windows-defender-antivirus.md @@ -0,0 +1,136 @@ +--- +title: Manage how and where Windows Defender AV receives updates +description: Manage how Windows Defender Antivirus receives protection updates. +keywords: updates, security baselines, protection, fallback order, ADL, MMPC, UNC, file path, share, wsus +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage Windows Defender Antivirus protection and definition updates + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) + + + + +Windows Defender AV uses both [cloud-delivered protection](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) (also called the Microsoft Advanced Protection Service or MAPS) and periodically downloaded protection updates to provide protection. These protection updates are also known as "definitions" or "signature updates". + +The cloud-based protection is “always-on” and requires an active connection to the Internet to function, while the protection updates generally occur once a day (although this can be configured). + +There are two components to managing protection updates - where the updates are downloaded from, and when updates are downloaded and applied. + +This topic describes the locations + + +## Manage the fallback order for downloading protection updates +There are five locations where you can specify where an endpoint should obtain updates. Typically, you would configure each endpoint to individually download the updates from a primary source and specify fallback sources in case the primary source is unavailable. + +- [Windows Server Update Service (WSUS)](https://technet.microsoft.com/windowsserver/bb332157.aspx) +- Microsoft Update. +- The [Microsoft Malware Protection Center definitions page (MMPC)](http://www.microsoft.com/security/portal/definitions/adl.aspx) +- A network file share +- Configuration manager + +Each location has typical scenarios (in addition to acting as fallback locations) for when you would use that source, as described in the following table: + +Location | Sample scenario +---|--- +WSUS | You are using WSUS to manage updates for your network +Microsoft Update | You want your endpoints to connect directly to Microsoft Update. This can be useful for endpoints that irregularly connect to your enterprise network. +MMPC | You need to download the latest protection updates because of a recent infection or to help provision a strong, base image for [VDI deployment](deployment-vdi-windows-defender-antivirus.md). +File share | You have non-Internet-connected devices (such as VMs). You can use your Internet-connected VM host download the updates to a network share, from which the VMs can obtain the updates. See the [VDI deployment guide](deployment-vdi-windows-defender-antivirus.md) for how file shares can be used in virtual desktop infrastructure (VDI) environments. +Configuration Manager | You are using System Center Configuration Manager to update your endpoints. + +You can manage the order in which update sources are used with Group Policy, System Center Configuration Manager, PowerShell cmdlets, and WMI. + +> [!IMPORTANT] +> If you set WSUS as a download location, you must approve the updates - regardless of what management tool you use to specify the location. You can set up an automatic approval rule with WSUS, which may be useful as updates arrive at least once a day. See [To synchronize endpoint protection updates in standalone WSUS](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus) for more details. + + +**Use Group Policy to manage the update location:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender > Signature updates** and configure the following settings: + + 1. Double-click the **Define the order of sources for downloading definition updates** setting and set the option to **Enabled**. + + 2. Enter the order of sources, separated by a single pipe, for example: `InternalDefinitionUpdateServer|MicrosoftUpdateServer|MMPC`, shown in the following screenshot. + + ![Screenshot of group policy setting listing the order of sources](images/defender/wdav-order-update-sources.png) + + 3. Click **OK**. This will set the order of protection update sources. + + 1. Double-click the **Define file shares for downloading definition updates** setting and set the option to **Enabled**. + + 2. Enter the file share source. If you have multiple sources, enter each source in the order they should be used, separated by a single pipe. Use [standard UNC notation](https://msdn.microsoft.com/en-us/library/gg465305.aspx) for denoting the path, for example: `\\host-name1\share-name\object-name|\\host-name2\share-name\object-name`. If you do not enter any paths then this source will be skipped when the VM downloads updates. + + 3. Click **OK**. This will set the order of file shares when that source is referenced in the **Define the order of sources...** group policy setting. + + +**Use Configuration Manager to manage the update location:** + +See [Configure Definition Updates for Endpoint Protection](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-definition-updates) for details on configuring System Center Configuration Manager (current branch). + + +**Use PowerShell cmdlets to manage the update location:** + +Use the following PowerShell cmdlets to set the update order. + +```PowerShell +Set-MpPreference -SignatureFallbackOrder {LOCATION|LOCATION|LOCATION|LOCATION} +Set-MpPreference -SignatureDefinitionUpdateFileSharesSouce {\\UNC SHARE PATH|\\UNC SHARE PATH} +``` +See the following for more information: +- [Set-MpPreference -SignatureFallbackOrder](https://technet.microsoft.com/en-us/itpro/powershell/windows/defender/set-mppreference#-signaturefallbackorder) +- [Set-MpPreference -SignatureDefinitionUpdateFileSharesSouce](https://technet.microsoft.com/en-us/itpro/powershell/windows/defender/set-mppreference#-signaturedefinitionupdatefilesharessources) +- [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) +- [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) + +**Use Windows Management Instruction (WMI) to manage the update location:** + +Use the [**Set** method of the **MSFT_MpPreference**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class for the following properties: + +```WMI +SignatureFallbackOrder +SignatureDefinitionUpdateFileSharesSouce +``` + +See the following for more information: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) + + + + + + + + + + +## Related topics + +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) diff --git a/windows/keep-secure/manage-updates-baselines-windows-defender-antivirus.md b/windows/keep-secure/manage-updates-baselines-windows-defender-antivirus.md new file mode 100644 index 0000000000..f2036b77ff --- /dev/null +++ b/windows/keep-secure/manage-updates-baselines-windows-defender-antivirus.md @@ -0,0 +1,53 @@ +--- +title: Manage Windows Defender Antivirus updates and apply baselines +description: Manage how Windows Defender Antivirus receives protection and product updates. +keywords: updates, security baselines, protection, schedule updates, force updates, mobile updates, wsus +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage Windows Defender Antivirus updates and apply baselines + + +**Applies to:** + +- Windows 10 + +**Audience** + +- Network administrators + +There are two types of updates related to keeping Windows Defender Antivirus: +1. Protection updates +2. Product updates + +You can also apply [Windows security baselines](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/windows-security-baselines) to quickly bring your endpoints up to a uniform level of protection. + +## Protection updates + +Windows Defender AV uses both [cloud-delivered protection](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) (also called the Microsoft Advanced Protection Service or MAPS) and periodically downloaded protection updates to provide protection. These protection updates are also known as "definitions" or "signature updates". + +The cloud-based protection is always-on and requires an active connection to the Internet to function, while the protection updates generally occur once a day (although this can be configured). See the [Utilize Microsoft cloud-provided protection in Windows Defender Antivirus](utilize-microsoft-cloud-protection-windows-defender-antivirus.md) topic for more details about enabling and configuring cloud-provided protection. + + +## Product updates + +Windows Defender AV requires monthly updates (known as "engine updates"), and will receive major feature updates alongside Windows 10 releases. + +You can manage the distribution of updates through Windows Server Update Service (WSUS), with [System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/sum/understand/software-updates-introduction), or in the normal manner that you deploy Microsoft and Windows updates to endpoints in your network. + +## In this section + +Topic | Description +---|--- +[Manage how protection updates are downloaded and applied](manage-protection-updates-windows-defender-antivirus.md) | Protection updates can be delivered through a number of sources. +[Manage when protection updates should be downloaded and applied](manage-protection-update-schedule-windows-defender-antivirus.md) | You can schedule when protection updates should be downloaded. +[Manage updates for endpoints that are out of date](manage-outdated-endpoints-windows-defender-antivirus.md) | If an endpoint misses an update or scheduled scan, you can force an update or scan at the next log on. +[Manage event-based forced updates](manage-event-based-updates-windows-defender-antivirus.md) | You can set protection updates to be downloaded at startup or after certain cloud-based protection events. +[Manage updates for mobile devices and virtual machines (VMs)](manage-updates-mobile-devices-vms-windows-defender-antivirus.md)| You can specify settings, such as whether updates should occur on battery power, that are especially useful for mobile devices and virtual machines. diff --git a/windows/keep-secure/manage-updates-mobile-devices-vms-windows-defender-antivirus.md b/windows/keep-secure/manage-updates-mobile-devices-vms-windows-defender-antivirus.md new file mode 100644 index 0000000000..660d4049a7 --- /dev/null +++ b/windows/keep-secure/manage-updates-mobile-devices-vms-windows-defender-antivirus.md @@ -0,0 +1,104 @@ +--- +title: Define how mobile devices are updated by Windows Defender AV +description: Manage how mobile devices, such as laptops, should be updated with Windows Defender AV protection updates. +keywords: updates, protection, schedule updates, battery, mobile device, laptop, notebook, opt-in, microsoft update, wsus, override +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Manage updates for mobile devices and virtual machines (VMs) + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy + + + + +Mobile devices and VMs may require additional configuration to ensure performance is not impacted by updates. + +There are two settings that are particularly useful for these devices: + +- Opt-in to Microsoft Update on mobile computers without a WSUS connection +- Prevent definition updates when running on battery power + +The following topics may also be useful in this situations: +- [Configuring scheduled and catch-up scans](scheduled-catch-up-scans-windows-defender-antivirus.md) +- [Manage updates for endpoints that are out of date](manage-outdated-endpoints-windows-defender-antivirus.md) +- [Deployment guide for Windows Defender Antivirus in a virtual desktop infrastructure (VDI) environment](deployment-vdi-windows-defender-antivirus.md) + +## Opt-in to Microsoft Update on mobile computers without a WSUS connection + +You can use Microsoft Update to keep definitions on mobile devices running Windows Defender AV up to date when they are not connected to the corporate network or don't otherwise have a WSUS connection. + +This means that protection updates can be delivered to devices (via Microsoft Update) even if you have set WSUS to override Microsoft Update. + +You can opt-in to Microsoft Update on the mobile device in one of the following ways: + +1. Change the setting with Group Policy +2. Use a VBScript to create a script, then run it on each computer in your network. +3. Manually opt-in every computer on your network through the **Settings** menu. + +**Use Group Policy to opt-in to Microsoft Update:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates**. + +6. Double-click the **Allow definition updates from Microsoft Update** setting and set the option to **Enabled**. Click **OK**. + + +**Use a VBScript to opt-in to Microsoft Update** + +1. Use the instructions in the MSDN article [Opt-In to Microsoft Update](https://msdn.microsoft.com/library/windows/desktop/aa826676.aspx) to create the VBScript. +2. Run the VBScript you created on each computer in your network. + + +**Manually opt-in to Microsoft Update** + +1. Open **Windows Update** in **Update & security** settings on the computer you want to opt-in. +2. Click **Advanced** options. +3. Select the checkbox for **Give me updates for other Microsoft products when I update Windows**. + +## Prevent definition updates when running on battery power + +You can configure Windows Defender AV to only download protection updates when the PC is connected to a wired power source. + +**Use Group Policy to prevent definition updates on battery power:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Signature Updates** and configure the following setting: + + 1. Double-click the **Allow definition updates when running on battery power** setting and set the option to **Disabled**. + 2. Click **OK**. This will prevent protection updates from downloading when the PC is on battery power. + + + + + +## Related topics + +- [Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) diff --git a/windows/keep-secure/powershell-example-code-windows-defender-advanced-threat-protection.md b/windows/keep-secure/powershell-example-code-windows-defender-advanced-threat-protection.md index 5574319409..c30415b0fd 100644 --- a/windows/keep-secure/powershell-example-code-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/powershell-example-code-windows-defender-advanced-threat-protection.md @@ -36,7 +36,7 @@ These code examples demonstrate the following tasks: ## Step 1: Obtain an Azure AD access token The following example demonstrates how to obtain an Azure AD access token that you can use to call methods in the custom threat intelligence API. After you obtain a token, you have 60 minutes to use this token in calls to the custom threat intelligence API before the token expires. After the token expires, you can generate a new token. -Replace the *tenantid*, *clientid*, and *clientSecret* values with the ones you got from **Preferences settings** page in the portal: +Replace the *authUrl*, *clientid*, and *clientSecret* values with the ones you got from **Preferences settings** page in the portal: [!code[CustomTIAPI](./code/example.ps1#L1-L14)] diff --git a/windows/keep-secure/prevent-end-user-interaction-windows-defender-antivirus.md b/windows/keep-secure/prevent-end-user-interaction-windows-defender-antivirus.md new file mode 100644 index 0000000000..ce95481ff2 --- /dev/null +++ b/windows/keep-secure/prevent-end-user-interaction-windows-defender-antivirus.md @@ -0,0 +1,89 @@ +--- +title: Hide the Windows Defender Antivirus interface +description: You can hide virus and threat protection tile in the Windows Defender Security Center app. +keywords: ui lockdown, headless mode, hide app, hide settings, hide interface +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Prevent users from seeing or interacting with the Windows Defender AV user interface +**Applies to:** + +- Windows 10 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy + + +You can use Group Policy to prevent users on endpoints from seeing the Windows Defender Antivirus interface. You can also prevent them from pausing scans. + +## Hide the Windows Defender Antivirus interface + +In Windows 10, versions 1703, hiding the interface will hide Windows Defender AV notifications and prevent the Virus & threat protection tile from appearing in the Windows Defender Security Center app. + +With the setting set to **Enabled**: + +![Screenshot of Windows Defender Security Center without the shield icon and virus and threat protection section](images/defender/wdav-headless-mode-1703.png) + +With the setting set to **Disabled** or not configured: + +![Scheenshot of Windows Defender Security Center showing the shield icon and virus and threat protection section](images/defender/wdav-headless-mode-off-1703.png) + +>[!NOTE] +>Hiding the interface will also prevent Windows Defender AV notifications from appearing on the endpoint. Windows Defender Advanced Threat Protection notifications will still appear. You can also individually [Configure the notifications that appear on endpoints](configure-notifications-windows-defender-antivirus.md) + + +In earlier versions of Windows 10, the setting will hide the Windows Defender client interface. If the user attempts to open it, they will receive a warning "Your system administrator has restricted access to this app.": + +![Warning message when headless mode is enabled in Windows 10, versions earlier than 1703 that says Your system administrator has restricted access to this app](images/defender/wdav-headless-mode-1607.png) + +**Use Group Policy to hide the Windows Defender AV interface from users:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Client interface**. + +6. Double-click the **Enable headless UI mode** setting and set the option to **Enabled**. Click **OK**. + + +Also see the [Prevent users from locally modifying policy settings](configure-local-policy-overrides-windows-defender-antivirus.md) topic for more options on preventing users form modifying protection on their PCs. + +## Prevent users from pausing a scan + +You can prevent users from pausing scans. This can be helpful to ensure scheduled or on-demand scans are not interrupted by users. + + +**Use Group Policy to prevent users from pausing a scan:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > Scan**. + +6. Double-click the **Allow users to pause scan** setting and set the option to **Disabled**. Click **OK**. + + +## Related topics + + +- [Configure the notifications that appear on endpoints](configure-notifications-windows-defender-antivirus.md) +- [Configure end-user interaction with Windows Defender AV](configure-end-user-interaction-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) \ No newline at end of file diff --git a/windows/keep-secure/python-example-code-windows-defender-advanced-threat-protection.md b/windows/keep-secure/python-example-code-windows-defender-advanced-threat-protection.md index 6e63d9f1b5..d162c44a38 100644 --- a/windows/keep-secure/python-example-code-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/python-example-code-windows-defender-advanced-threat-protection.md @@ -37,7 +37,7 @@ These code examples demonstrate the following tasks: ## Step 1: Obtain an Azure AD access token The following example demonstrates how to obtain an Azure AD access token that you can use to call methods in the custom threat intelligence API. After you obtain a token, you have 60 minutes to use this token in calls to the custom threat intelligence API before the token expires. After the token expires, you can generate a new token. -Replace the *tenant\_id*, *client_id*, and *client_secret* values with the ones you got from **Preferences settings** page in the portal: +Replace the *auth_url*, *client_id*, and *client_secret* values with the ones you got from **Preferences settings** page in the portal: [!code[CustomTIAPI](./code/example.py#L1-L17)] diff --git a/windows/keep-secure/report-monitor-windows-defender-antivirus.md b/windows/keep-secure/report-monitor-windows-defender-antivirus.md new file mode 100644 index 0000000000..c2a5ab14a1 --- /dev/null +++ b/windows/keep-secure/report-monitor-windows-defender-antivirus.md @@ -0,0 +1,38 @@ +--- +title: Monitor and report on Windows Defender Antivirus protection +description: Use Configuration Manager or SIEM tools to consume reports, and monitor Windows Defender AV with PowerShell and WMI. +keywords: siem, monitor, report, windows defender av +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Report on Windows Defender Antivirus protection + +**Applies to:** + +- Windows 10 + +**Audience** + +- IT administrators + +There are a number of ways you can review protection status and alerts, depending on the management tool you are using for Windows Defender AV. + + + +You can use System Center Configuration Manager to [monitor Windows Defender AV protection](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/monitor-endpoint-protection) or [create email alerts](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-configure-alerts), or you can also monitor protection using the [Microsoft Intune console](ttps://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune#monitor-endpoint-protection). + +If you have a third-party security information and event management (SIEM) tool, you can also consume [Windows Defender client event IDs](troubleshoot-windows-defender-antivirus.md#windows-defender-av-ids) to review specific events and errors from your endpoints. + +For monitoring or determining status with PowerShell, WMI, or Microsoft Azure, see the [(Deployment, managament, and reporting options table)](deploy-manage-report-windows-defender-antivirus.md#ref1). + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) +- [Deploy, manage updates, and report on Windows Defender Antivirus](deploy-manage-report-windows-defender-antivirus.md) diff --git a/windows/keep-secure/review-scan-results-windows-defender-antivirus.md b/windows/keep-secure/review-scan-results-windows-defender-antivirus.md new file mode 100644 index 0000000000..7147c968b9 --- /dev/null +++ b/windows/keep-secure/review-scan-results-windows-defender-antivirus.md @@ -0,0 +1,15 @@ +--- +title: Review the results of Windows Defender AV scans +description: Review the results of scans using System Center Configuration Manager, Microsoft Intune, or the Windows Defender Security Center app +keywords: +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Review Windows Defender AV scan results diff --git a/windows/keep-secure/run-cmd-scan-windows-defender-for-windows-10.md b/windows/keep-secure/run-cmd-scan-windows-defender-for-windows-10.md index 2234eebd86..f8f3682a5d 100644 --- a/windows/keep-secure/run-cmd-scan-windows-defender-for-windows-10.md +++ b/windows/keep-secure/run-cmd-scan-windows-defender-for-windows-10.md @@ -10,46 +10,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: mjcaparas +redirect_url: /command-line-arguments-windows-defender-antivirus/ --- # Run a Windows Defender scan from the command line -**Applies to:** - -- Windows 10 - -IT professionals can use a command-line utility to run a Windows Defender scan. - -The utility is available in _%Program Files%\Windows Defender\MpCmdRun.exe_. - -This utility can be handy when you want to automate the use of Windows Defender. - -**To run a quick scan from the command line** - -1. Click **Start**, type **cmd**, and press **Enter**. -2. Navigate to _%ProgramFiles%\Windows Defender_ and enter the following command, and press **Enter**: - -``` -C:\Program Files\Windows Defender\mpcmdrun.exe -scan -scantype 1 -``` -The quick scan will start. When the scan completes, you'll see a message indicating that the scan is finished. - - -The utility also provides other commands that you can run: - -``` -MpCmdRun.exe [command] [-options] -``` - -Command | Description -:---|:--- -\- ? / -h | Displays all available options for the tool -\-Scan [-ScanType #] [-File [-DisableRemediation] [-BootSectorScan]][-Timeout ] | Scans for malicious software -\-Trace [-Grouping #] [-Level #]| Starts diagnostic tracing -\-GetFiles | Collects support information -\-RemoveDefinitions [-All] | Restores the installed signature definitions to a previous backup copy or to the original default set of signatures -\-AddDynamicSignature [-Path] | Loads a dynamic signature -\-ListAllDynamicSignature [-Path] | Lists the loaded dynamic signatures -\-RemoveDynamicSignature [-SignatureSetID] | Removes a dynamic signature -
-The command-line utility provides detailed information on the other commands supported by the tool. +This page has been redirected to *Usethempcmdrun.execommandlinetooltoconfigureandmanageWindowsDefenderAntivirus*. \ No newline at end of file diff --git a/windows/keep-secure/run-scan-windows-defender-antivirus.md b/windows/keep-secure/run-scan-windows-defender-antivirus.md new file mode 100644 index 0000000000..2c09909c04 --- /dev/null +++ b/windows/keep-secure/run-scan-windows-defender-antivirus.md @@ -0,0 +1,59 @@ +--- +title: Run and customize on-demand scans in Windows Defender AV +description: Run and configure on-demand scans using PowerShell, Windows Management Instrumentation, or individually on endpoints with the Windows Defender Security Center app +keywords: +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + + + + +# Configure and run Windows Defender AV scans + +**Applies to:** + +- Windows 10 + +IT professionals can use a command-line utility to run a Windows Defender scan. + +The utility is available in _%Program Files%\Windows Defender\MpCmdRun.exe_. + +This utility can be handy when you want to automate the use of Windows Defender. + +**To run a quick scan from the command line** + +1. Click **Start**, type **cmd**, and press **Enter**. +2. Navigate to _%ProgramFiles%\Windows Defender_ and enter the following command, and press **Enter**: + +``` +C:\Program Files\Windows Defender\mpcmdrun.exe -scan -scantype 1 +``` +The quick scan will start. When the scan completes, you'll see a message indicating that the scan is finished. + + +The utility also provides other commands that you can run: + +``` +MpCmdRun.exe [command] [-options] +``` + +Command | Description +:---|:--- +\- ? / -h | Displays all available options for the tool +\-Scan [-ScanType #] [-File [-DisableRemediation] [-BootSectorScan]][-Timeout ] | Scans for malicious software +\-Trace [-Grouping #] [-Level #]| Starts diagnostic tracing +\-GetFiles | Collects support information +\-RemoveDefinitions [-All] | Restores the installed signature definitions to a previous backup copy or to the original default set of signatures +\-AddDynamicSignature [-Path] | Loads a dynamic signature +\-ListAllDynamicSignature [-Path] | Lists the loaded dynamic signatures +\-RemoveDynamicSignature [-SignatureSetID] | Removes a dynamic signature +
+The command-line utility provides detailed information on the other commands supported by the tool. diff --git a/windows/keep-secure/scheduled-catch-up-scans-windows-defender-antivirus.md b/windows/keep-secure/scheduled-catch-up-scans-windows-defender-antivirus.md new file mode 100644 index 0000000000..0c16327c23 --- /dev/null +++ b/windows/keep-secure/scheduled-catch-up-scans-windows-defender-antivirus.md @@ -0,0 +1,50 @@ +--- +title: Schedule regular scans with Windows Defender AV +description: Set up recurring (scheduled) scans, including when they should run and whether they run as full or quick scans +keywords: +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + +# Configure scheduled scans for Windows Defender AV + + + +**Applies to** +- Windows 10 + +**Audience** + +- Network administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager +- PowerShell cmdlets +- Windows Management Instruction (WMI) + + + +> [!IMPORTANT] +> By default, Windows Defender AV will check for an update 15 minutes before the time of any scheduled scans. You can [Manage the schedule for when protection updates should be downloaded and applied](manage-protection-update-schedule-windows-defender-antivirus.md) to override this default. + + +RANDOMIZE + + + + + +## Related topics + +- [Manage Windows Defender Antivirus updates and apply baselines](manage-updates-baselines-windows-defender-antivirus.md) +- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +- [Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md) diff --git a/windows/keep-secure/specify-cloud-protection-level-windows-defender-antivirus.md b/windows/keep-secure/specify-cloud-protection-level-windows-defender-antivirus.md new file mode 100644 index 0000000000..923b49d30a --- /dev/null +++ b/windows/keep-secure/specify-cloud-protection-level-windows-defender-antivirus.md @@ -0,0 +1,69 @@ +--- +title: Specify cloud-delivered protection level in Windows Defender Antivirus +description: Set the aggressiveness of cloud-delivered protection in Windows Defender Antivirus. +keywords: windows defender antivirus, antimalware, security, defender, cloud, aggressiveness, protection level +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Specify the cloud-delivered protection level + + + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy +- System Center Configuration Manager (current branch) + +You can specify the level of cloud-protection offered by Windows Defender Antivirus with Group Policy and System Center Configuration Manager. + +>[!NOTE] +>The Windows Defender Antivirus cloud service is a mechanism for delivering updated protection to your network and endpoints. Although it is called a cloud service, it is not simply protection for files stored in the cloud, rather it uses distributed resources and machine learning to deliver protection to your endpoints at a rate that is far faster than traditional signature updates. + + + +**Use Group Policy to specify the level of cloud-delivered protection:** + +1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. + +3. In the **Group Policy Management Editor** go to **Computer configuration**. + +4. Click **Policies** then **Administrative templates**. + +5. Expand the tree to **Windows components > Windows Defender Antivirus > MpEngine**. + +1. Double-click the **Select cloud protection level** setting and set it to **Enabled**. Select the level of protection: + 1. Setting to **Default Windows Defender Antivirus blocking level** will provide strong detection without increasing the risk of detecting legitimate files. + 2. Setting to **High blocking level** will apply a strong level of detection. While unlikely, some legitimate files may be detected (although you will have the option to unblock or dispute that detection). + +1. Click **OK**. + + +**Use Configuration Manager to specify the level of cloud-delivered protection:** + +1. See [How to create and deploy antimalware policies: Cloud-protection service](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#cloud-protection-service) for details on configuring System Center Configuration Manager (current branch). + + + + +## Related topics + +- [Windows Defender Antivirus in Windows 10](windows-defender-in-windows-10.md) +- [Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) +- [How to create and deploy antimalware policies: Cloud-protection service](https://docs.microsoft.com/en-us/sccm/protect/deploy-use/endpoint-antimalware-policies#cloud-protection-service) + + diff --git a/windows/keep-secure/troubleshoot-windows-defender-antivirus.md b/windows/keep-secure/troubleshoot-windows-defender-antivirus.md new file mode 100644 index 0000000000..0006cde7b3 --- /dev/null +++ b/windows/keep-secure/troubleshoot-windows-defender-antivirus.md @@ -0,0 +1,3325 @@ +--- +title: Windows Defender AV event IDs and error codes +description: Look up the causes and solutions for Windows Defender Antivirus event IDs and errors +keywords: event, error code, siem, logging, troubleshooting, wef, windows event forwarding +ms.assetid: EE488CC1-E340-4D47-B50B-35BD23CB4D70 +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Review event logs and error codes to troubleshoot issues with Windows Defender AV + + +**Applies to** +- Windows 10 + +**Audience** + +- Enterprise security administrators + + +If you encounter a problem with Windows Defender Antivirus, you can search the tables in this topic to find a matching issue and potential solution. + +The tables list: + +- [Windows Defender AV client event IDs](#windows-defender-av-ids) +- [Windows Defender AV client error codes](#error-codes) +- [Internal Windows Defender AV client error codes (used by Microsoft during development and testing)](#internal-error-codes) + + + +## Windows Defender AV client event IDs + +Windows Defender AV records event IDs in the Windows event log. + +You can directly view the event log, or if you have a third-party security information and event management (SIEM) tool, you can also consume [Windows Defender client event IDs](troubleshoot-windows-defender-antivirus.md#windows-defender-av-ids) to review specific events and errors from your endpoints. + +The table in this section lists the main Windows Defender Antivirus client event IDs and, where possible, provides suggested solutions to fix or resolve the error. + +**To view a Windows Defender client event** + +1. Open **Event Viewer**. +2. In the console tree, expand **Applications and Services Logs**, then **Microsoft**, then **Windows**, then **Windows Defender**. +3. Double-click on **Operational**. +4. In the details pane, view the list of individual events to find your event. +5. Click the event to see specific details about an event in the lower pane, under the **General** and **Details** tabs. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Event ID: 1000 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_STARTED

+
+

Message:

+		 +

An antimalware scan started. +

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
Scan Resources: <Resources (such as files/directories/BHO) that were scanned.>
+
User: <Domain>\<User>
+
+

+
Event ID: 1001 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_COMPLETED

+
+

Message:

+		 +

An antimalware scan finished.

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
User: <Domain>\<User>
+
Scan Time: <The duration of a scan.>
+
+

+
Event ID: 1002 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_CANCELLED +

+
+

Message:

+		 +

An antimalware scan was stopped before it finished. +

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
User: <Domain>\<User>
+
Scan Time: <The duration of a scan.>
+
+

+
Event ID: 1003 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_PAUSED +

+
+

Message:

+		 +

An antimalware scan was paused. +

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
User: <Domain>\<User>
+
+

+
Event ID: 1004 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_RESUMED +

+
+

Message:

+		 +

An antimalware scan was resumed. +

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
User: <Domain>\<User>
+
+

+
Event ID: 1005 +

Symbolic name:

+		 +

MALWAREPROTECTION_SCAN_FAILED +

+
+

Message:

+		 +

An antimalware scan failed. +

+
+

Description:

+		 +

+

+
Scan ID: <ID number of the relevant scan.>
+
Scan Type: <Scan type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
+
+
Scan Parameters: <Scan parameters>, for example:
    +
  • Full scan
    • +
  • Quick scan
    • +
  • Customer scan
    • +
+
+
User: <Domain>\<User>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
+

User action:

+		 +

The Windows Defender client encountered an error, and the current scan has stopped. The scan might fail due to a client-side issue. This event record includes the scan ID, type of scan (antivirus, antispyware, antimalware), scan parameters, the user that started the scan, the error code, and a description of the error. +

+

To troubleshoot this event: +

    +
  1. Run the scan again.
    2. +
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. +
  3. Contact Microsoft Technical Support. +
    4. +
+

+
Event ID: 1006 +

Symbolic name:

+		 +

MALWAREPROTECTION_MALWARE_DETECTED +

+
+

Message:

+		 +

The antimalware engine found malware or other potentially unwanted software. +

+
+

Description:

+		 +

+

For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example:
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
Status: <Status>
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1007 +

Symbolic name:

+		 +

MALWAREPROTECTION_MALWARE_ACTION_TAKEN +

+
+

Message:

+		 +

The antimalware platform performed an action to protect your system from malware or other potentially unwanted software. +

+
+

Description:

+		 +

+

Windows Defender has taken action to protect this machine from malware or other potentially unwanted software. For more information please see the following:

+
+
User: <Domain>\<User>
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Action: <Action>, for example:
    +
  • Clean: The resource was cleaned
    • +
  • Quarantine: The resource was quarantined
    • +
  • Remove: The resource was deleted
    • +
  • Allow: The resource was allowed to execute/exist
    • +
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • +
  • No action: No action
    • +
  • Block: The resource was blocked from executing
    • +
+
+
Status: <Status>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1008 +

Symbolic name:

+		 +

MALWAREPROTECTION_MALWARE_ACTION_FAILED

+
+

Message:

+		 +

The antimalware platform attempted to perform an action to protect your system from malware or other potentially unwanted software, but the action failed.

+
+

Description:

+		 +

+

Windows Defender has encountered an error when taking action on malware or other potentially unwanted software. For more information please see the following:

+
+
User: <Domain>\<User>
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Action: <Action>, for example:
    +
  • Clean: The resource was cleaned
    • +
  • Quarantine: The resource was quarantined
    • +
  • Remove: The resource was deleted
    • +
  • Allow: The resource was allowed to execute/exist
    • +
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • +
  • No action: No action
    • +
  • Block: The resource was blocked from executing
    • +
+
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Status: <Status>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1009 +

Symbolic name:

+		 +

MALWAREPROTECTION_QUARANTINE_RESTORE +

+
+

Message:

+		 +

The antimalware platform restored an item from quarantine. +

+
+

Description:

+		 +

+

Windows Defender has restored an item from quarantine. For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
User: <Domain>\<User>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1010 +

Symbolic name:

+		 +

MALWAREPROTECTION_QUARANTINE_RESTORE_FAILED +

+
+

Message:

+		 +

The antimalware platform could not restore an item from quarantine. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to restore an item from quarantine. For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
User: <Domain>\<User>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1011 +

Symbolic name:

+		 +

MALWAREPROTECTION_QUARANTINE_DELETE

+
+

Message:

+		 +

The antimalware platform deleted an item from quarantine. +

+
+

Description:

+		 +

+

Windows Defender has deleted an item from quarantine. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
User: <Domain>\<User>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1012 +

Symbolic name:

+		 +

MALWAREPROTECTION_QUARANTINE_DELETE_FAILED +

+
+

Message:

+		 +

The antimalware platform could not delete an item from quarantine.

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to delete an item from quarantine. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
User: <Domain>\<User>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
Event ID: 1013 +

Symbolic name:

+		 +

MALWAREPROTECTION_MALWARE_HISTORY_DELETE +

+
+

Message:

+		 +

The antimalware platform deleted history of malware and other potentially unwanted software.

+
+

Description:

+		 +

+

Windows Defender has removed history of malware and other potentially unwanted software.

+
+
Time: The time when the event occurred, for example when the history is purged. Note that this parameter is not used in threat events so that there is no confusion regarding whether it is remediation time or infection time. For those, we specifically call them as Action Time or Detection Time.
+
User: <Domain>\<User>
+
+

+
Event ID: 1014 +

Symbolic name:

+		 +

MALWAREPROTECTION_MALWARE_HISTORY_DELETE_FAILED +

+
+

Message:

+		 +

The antimalware platform could not delete history of malware and other potentially unwanted software.

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to remove history of malware and other potentially unwanted software.

+
+
Time: The time when the event occurred, for example when the history is purged. Note that this parameter is not used in threat events so that there is no confusion regarding whether it is remediation time or infection time. For those, we specifically call them as Action Time or Detection Time.
+
User: <Domain>\<User>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
Event ID: 1015 +

Symbolic name:

+		 +

MALWAREPROTECTION_BEHAVIOR_DETECTED +

+
+

Message:

+		 +

The antimalware platform detected suspicious behavior.

+
+

Description:

+		 +

+

Windows Defender has detected a suspicious behavior. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example: +
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
Status: <Status>
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Signature ID: Enumeration matching severity.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
Fidelity Label:
+
Target File Name: <File name> +Name of the file.
+
+

+
Event ID: 1116 +

Symbolic name:

+		 +

MALWAREPROTECTION_STATE_MALWARE_DETECTED

+
+

Message:

+		 +

The antimalware platform detected malware or other potentially unwanted software. +

+
+

Description:

+		 +

+

Windows Defender has detected malware or other potentially unwanted software. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example: +
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
+

User action:

+		 +

No action is required. Windows Defender can suspend and take routine action on this threat. If you want to remove the threat manually, in the Windows Defender interface, click Clean Computer.

+
Event ID: 1117 +

Symbolic name:

+		 +

MALWAREPROTECTION_STATE_MALWARE_ACTION_TAKEN +

+
+

Message:

+		 +

The antimalware platform performed an action to protect your system from malware or other potentially unwanted software. +

+
+

Description:

+		 +

+

Windows Defender has taken action to protect this machine from malware or other potentially unwanted software. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example: +
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Action: <Action>, for example:
    +
  • Clean: The resource was cleaned
    • +
  • Quarantine: The resource was quarantined
    • +
  • Remove: The resource was deleted
    • +
  • Allow: The resource was allowed to execute/exist
    • +
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • +
  • No action: No action
    • +
  • Block: The resource was blocked from executing
    • +
+
+
Action Status: <Description of additional actions>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+

NOTE: +

Whenever Windows Defender, Microsoft Security Essentials, Malicious Software Removal Tool, or System Center Endpoint Protection detects a malware, it will restore the following system settings and services which the malware might have changed:

    +
  • Default Internet Explorer or Edge setting
    • +
  • User Access Control settings
    • +
  • Chrome settings
    • +
  • Boot Control Data
    • +
  • Regedit and Task Manager registry settings
    • +
  • Windows Update, Background Intelligent Transfer Service, and Remote Procedure Call service
    • +
  • Windows Operating System files
+The above context applies to the following client and server versions: + + + + + + + + + + + + + +
Operating systemOperating system version
+

Client Operating System

+		 +

Windows Vista (Service Pack 1, or Service Pack 2), Windows 7 and later

+
+

Server Operating System

+		 +

Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2016

+
+

+
+
+

User action:

+		 +

No action is necessary. Windows Defender removed or quarantined a threat.

+
Event ID: 1118 +

Symbolic name:

+		 +

MALWAREPROTECTION_STATE_MALWARE_ACTION_FAILED

+
+

Message:

+		 +

The antimalware platform attempted to perform an action to protect your system from malware or other potentially unwanted software, but the action failed. +

+
+

Description:

+		 +

+

Windows Defender has encountered a non-critical error when taking action on malware or other potentially unwanted software. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example: +
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Action: <Action>, for example:
    +
  • Clean: The resource was cleaned
    • +
  • Quarantine: The resource was quarantined
    • +
  • Remove: The resource was deleted
    • +
  • Allow: The resource was allowed to execute/exist
    • +
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • +
  • No action: No action
    • +
  • Block: The resource was blocked from executing
    • +
+
+
Action Status: <Description of additional actions>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
+

User action:

+		 +

No action is necessary. Windows Defender failed to complete a task related to the malware remediation. This is not a critical failure.

+
Event ID: 1119 +

Symbolic name:

+		 +

MALWAREPROTECTION_STATE_MALWARE_ACTION_CRITICALLY_FAILED +

+
+

Message:

+		 +

The antimalware platform encountered a critical error when trying to take action on malware or other potentially unwanted software. There are more details in the event message.

+
+

Description:

+		 +

+

Windows Defender has encountered a critical error when taking action on malware or other potentially unwanted software. +For more information please see the following:

+
+
Name: <Threat name>
+
ID: <Threat ID>
+
Severity: <Severity>, for example:
    +
  • Low
    • +
  • Moderate
    • +
  • High
    • +
  • Severe
    • +
+
+
Category: <Category description>, for example, any threat or malware type.
+
Path: <File path>
+
Detection Origin: <Detection origin>, for example: +
    +
  • Unknown
    • +
  • Local computer
    • +
  • Network share
    • +
  • Internet
    • +
  • Incoming traffic
    • +
  • Outgoing traffic
    • +
+
+
Detection Type: <Detection type>, for example:
    +
  • Heuristics
    • +
  • Generic
    • +
  • Concrete
    • +
  • Dynamic signature
    • +
+
+
Detection Source: <Detection source> for example:
    +
  • User: user initiated
    • +
  • System: system initiated
    • +
  • Real-time: real-time component initiated
    • +
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • +
  • NIS: Network inspection system
    • +
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • +
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • +
  • Remote attestation
    • +
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. +UAC
+
User: <Domain>\<User>
+
Process Name: <Process in the PID>
+
Action: <Action>, for example:
    +
  • Clean: The resource was cleaned
    • +
  • Quarantine: The resource was quarantined
    • +
  • Remove: The resource was deleted
    • +
  • Allow: The resource was allowed to execute/exist
    • +
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • +
  • No action: No action
    • +
  • Block: The resource was blocked from executing
    • +
+
+
Action Status: <Description of additional actions>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
+

User action:

+		 +

The Windows Defender client encountered this error due to critical issues. The endpoint might not be protected. Review the error description then follow the relevant User action steps below.

+ + + + + + + + + + + + + + + + + + + + + +
ActionUser action
+

Remove

+		 +

Update the definitions then verify that the removal was successful.

+
+

Clean

+		 +

Update the definitions then verify that the remediation was successful.

+
+

Quarantine

+		 +

Update the definitions and verify that the user has permission to access the necessary resources.

+
+

Allow

+		 +

Verify that the user has permission to access the necessary resources.

+
+

+

If this event persists:

    +
  1. Run the scan again.
    2. +
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. +
  3. Contact Microsoft Technical Support. +
    4. +
+

+
Event ID: 1120 +

Symbolic name:

+		 +

MALWAREPROTECTION_THREAT_HASH

+
+

Message:

+		 +

Windows Defender has deduced the hashes for a threat resource.

+
+

Description:

+		 +

+

Windows Defender client is up and running in a healthy state.

+
+
Current Platform Version: <Current platform version>
+
Threat Resource Path: <Path>
+
Hashes: <Hashes>
+
+

+
+
Note This event will only be logged if the following policy is set: ThreatFileHashLogging unsigned.
+
+
Event ID: 1150 +

Symbolic name:

+		 +

MALWAREPROTECTION_SERVICE_HEALTHY

+
+

Message:

+		 +

If your antimalware platform reports status to a monitoring platform, this event indicates that the antimalware platform is running and in a healthy state. +

+
+

Description:

+		 +

+

Windows Defender client is up and running in a healthy state.

+
+
Platform Version: <Current platform version>
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware Engine version>
+
+

+
+

User action:

+		 +

No action is necessary. The Windows Defenderclient is in a healthy state. This event is reported on an hourly basis.

+
Event ID: 2000 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_UPDATED +

+
+

Message:

+		 +

The antimalware definitions updated successfully. +

+
+

Description:

+		 +

+

Windows Defender signature version has been updated.

+
+
Current Signature Version: <Current signature version>
+
Previous Signature Version: <Previous signature version>
+
Signature Type: <Signature type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
  • Network Inspection System
    • +
+
+
Update Type: <Update type>, either Full or Delta.
+
User: <Domain>\<User>
+
Current Engine Version: <Current engine version>
+
Previous Engine Version: <Previous engine version>
+
+

+
+

User action:

+		 +

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when signatures are successfully updated.

+
Event ID: 2001 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_UPDATE_FAILED

+
+

Message:

+		 +

The antimalware definition update failed. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to update signatures.

+
+
New Signature Version: <New version number>
+
Previous Signature Version: <Previous signature version>
+
Update Source: <Update source>, for example: +
    +
  • Signature update folder
    • +
  • Internal definition update server
    • +
  • Microsoft Update Server
    • +
  • File share
    • +
  • Microsoft Malware Protection Center (MMPC)
    • +
+
+
Update Stage: <Update stage>, for example: +
    +
  • Search
    • +
  • Download
    • +
  • Install
    • +
+
+
Source Path: File share name for Universal Naming Convention (UNC), server name for Windows Server Update Services (WSUS)/Microsoft Update/ADL.
+
Signature Type: <Signature type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
  • Network Inspection System
    • +
+
+
Update Type: <Update type>, either Full or Delta.
+
User: <Domain>\<User>
+
Current Engine Version: <Current engine version>
+
Previous Engine Version: <Previous engine version>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
+

User action:

+		 +

This error occurs when there is a problem updating definitions.

+

To troubleshoot this event: +

    +
  1. Update the definitions. Either:
      +
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      +
      2. +
    2. Download the latest definitions from the Microsoft Malware Protection Center. +

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      +
      3. +
    +
    2. +
  2. Review the entries in the %Windir%\WindowsUpdate.log file for more information about this error.
    3. +
  3. Contact Microsoft Technical Support. +
    4. +
+

+
Event ID: 2002 +

Symbolic name:

+		 +

MALWAREPROTECTION_ENGINE_UPDATED

+
+

Message:

+		 +

The antimalware engine updated successfully. +

+
+

Description:

+		 +

+

Windows Defender engine version has been updated.

+
+
Current Engine Version: <Current engine version>
+
Previous Engine Version: <Previous engine version>
+
Engine Type: <Engine type>, either antimalware engine or Network Inspection System engine.
+
User: <Domain>\<User>
+
+

+
+

User action:

+		 +

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when the antimalware engine is successfully updated.

+
Event ID: 2003 +

Symbolic name:

+		 +

MALWAREPROTECTION_ENGINE_UPDATE_FAILED

+
+

Message:

+		 +

The antimalware engine update failed. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to update the engine.

+
+
New Engine Version:
+
Previous Engine Version: <Previous engine version>
+
Engine Type: <Engine type>, either antimalware engine or Network Inspection System engine.
+
User: <Domain>\<User>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
+

User action:

+		 +

The Windows Defender client update failed. This event occurs when the client fails to update itself. This event is usually due to an interruption in network connectivity during an update.

+

To troubleshoot this event: +

    +
  1. Update the definitions. Either:
      +
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      +
      2. +
    2. Download the latest definitions from the Microsoft Malware Protection Center. +

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      +
      3. +
    +
    2. +
  2. Contact Microsoft Technical Support. +
    3. +
+

+
Event ID: 2004 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_REVERSION

+
+

Message:

+		 +

There was a problem loading antimalware definitions. The antimalware engine will attempt to load the last-known good set of definitions.

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to load signatures and will attempt reverting back to a known-good set of signatures.

+
+
Signatures Attempted:
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Signature Version: <Definition version>
+
Engine Version: <Antimalware engine version>
+
+

+
+

User action:

+		 +

The Windows Defender client attempted to download and install the latest definitions file and failed. This error can occur when the client encounters an error while trying to load the definitions, or if the file is corrupt. Windows Defender will attempt to revert back to a known-good set of definitions.

+

To troubleshoot this event: +

    +
  1. Restart the computer and try again.
    2. +
  2. Download the latest definitions from the Microsoft Malware Protection Center. +

    Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

    +
    3. +
  3. Contact Microsoft Technical Support. +
    4. +
+

+
Event ID: 2005 +

Symbolic name:

+		 +

MALWAREPROTECTION_ENGINE_UPDATE_PLATFORMOUTOFDATE

+
+

Message:

+		 +

The antimalware engine failed to load because the antimalware platform is out of date. The antimalware platform will load the last-known good antimalware engine and attempt to update.

+
+

Description:

+		 +

+

Windows Defender could not load antimalware engine because current platform version is not supported. Windows Defender will revert back to the last known-good engine and a platform update will be attempted.

+
+
Current Platform Version: <Current platform version>
+
+

+
Event ID: 2006 +

Symbolic name:

+		 +

MALWAREPROTECTION_PLATFORM_UPDATE_FAILED +

+
+

Message:

+		 +

The platform update failed. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to update the platform.

+
+
Current Platform Version: <Current platform version>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
Event ID: 2007 +

Symbolic name:

+		 +

MALWAREPROTECTION_PLATFORM_ALMOSTOUTOFDATE

+
+

Message:

+		 +

The platform will soon be out of date. Download the latest platform to maintain up-to-date protection.

+
+

Description:

+		 +

+

Windows Defender will soon require a newer platform version to support future versions of the antimalware engine. Download the latest Windows Defender platform to maintain the best level of protection available.

+
+
Current Platform Version: <Current platform version>
+
+

+
Event ID: 2010 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_FASTPATH_UPDATED +

+
+

Message:

+		 +

The antimalware engine used the Dynamic Signature Service to get additional definitions. +

+
+

Description:

+		 +

+

Windows Defender used Dynamic Signature Service to retrieve additional signatures to help protect your machine.

+
+
Current Signature Version: <Current signature version>
+
Signature Type: <Signature type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
  • Network Inspection System
    • +
+
+
Current Engine Version: <Current engine version>
+
Dynamic Signature Type: <Dynamic signature type>, for example: +
    +
  • Version
    • +
  • Timestamp
    • +
  • No limit
    • +
  • Duration
    • +
+
+
Persistence Path: <Path>
+
Dynamic Signature Version: <Version number>
+
Dynamic Signature Compilation Timestamp: <Timestamp>
+
Persistence Limit Type: <Persistence limit type>, for example: +
    +
  • VDM version
    • +
  • Timestamp
    • +
  • No limit
    • +
+
+
Persistence Limit: Persistence limit of the fastpath signature.
+
+

+
Event ID: 2011 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_FASTPATH_DELETED +

+
+

Message:

+		 +

The Dynamic Signature Service deleted the out-of-date dynamic definitions. +

+
+

Description:

+		 +

+

Windows Defender used Dynamic Signature Service to discard obsolete signatures.

+
+
Current Signature Version: <Current signature version>
+
Signature Type: <Signature type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
  • Network Inspection System
    • +
+
+
Current Engine Version: <Current engine version>
+
Dynamic Signature Type: <Dynamic signature type>, for example: +
    +
  • Version
    • +
  • Timestamp
    • +
  • No limit
    • +
  • Duration
    • +
+
+
Persistence Path: <Path>
+
Dynamic Signature Version: <Version number>
+
Dynamic Signature Compilation Timestamp: <Timestamp>
+
Removal Reason:
+
Persistence Limit Type: <Persistence limit type>, for example: +
    +
  • VDM version
    • +
  • Timestamp
    • +
  • No limit
    • +
+
+
Persistence Limit: Persistence limit of the fastpath signature.
+
+

+
+

User action:

+		 +

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when the Dynamic Signature Service successfully deletes out-of-date dynamic definitions.

+
Event ID: 2012 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_FASTPATH_UPDATE_FAILED +

+
+

Message:

+		 +

The antimalware engine encountered an error when trying to use the Dynamic Signature Service. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to use Dynamic Signature Service.

+
+
Current Signature Version: <Current signature version>
+
Signature Type: <Signature type>, for example:
    +
  • Antivirus
    • +
  • Antispyware
    • +
  • Antimalware
    • +
  • Network Inspection System
    • +
+
+
Current Engine Version: <Current engine version>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Dynamic Signature Type: <Dynamic signature type>, for example: +
    +
  • Version
    • +
  • Timestamp
    • +
  • No limit
    • +
  • Duration
    • +
+
+
Persistence Path: <Path>
+
Dynamic Signature Version: <Version number>
+
Dynamic Signature Compilation Timestamp: <Timestamp>
+
Persistence Limit Type: <Persistence limit type>, for example: +
    +
  • VDM version
    • +
  • Timestamp
    • +
  • No limit
    • +
+
+
Persistence Limit: Persistence limit of the fastpath signature.
+
+

+
+

User action:

+		 +

Check your Internet connectivity settings.

+
Event ID: 2013 +

Symbolic name:

+		 +

MALWAREPROTECTION_SIGNATURE_FASTPATH_DELETED_ALL +

+
+

Message:

+		 +

The Dynamic Signature Service deleted all dynamic definitions. +

+
+

Description:

+		 +

+

Windows Defender discarded all Dynamic Signature Service signatures.

+
+
Current Signature Version: <Current signature version>
+
+

+
Event ID: 2020 +

Symbolic name:

+		 +

MALWAREPROTECTION_CLOUD_CLEAN_RESTORE_FILE_DOWNLOADED +

+
+

Message:

+		 +

The antimalware engine downloaded a clean file. +

+
+

Description:

+		 +

+

Windows Defender downloaded a clean file.

+
+
Filename: <File name> +Name of the file.
+
Current Signature Version: <Current signature version>
+
Current Engine Version: <Current engine version>
+
+

+
Event ID: 2021 +

Symbolic name:

+		 +

MALWAREPROTECTION_CLOUD_CLEAN_RESTORE_FILE_DOWNLOAD_FAILED

+
+

Message:

+		 +

The antimalware engine failed to download a clean file. +

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to download a clean file.

+
+
Filename: <File name> +Name of the file.
+
Current Signature Version: <Current signature version>
+
Current Engine Version: <Current engine version>
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
+

User action:

+		 +

Check your Internet connectivity settings. +

+

The Windows Defender client encountered an error when using the Dynamic Signature Service to download the latest definitions to a specific threat. This error is likely caused by a network connectivity issue. +

+
Event ID: 2030 +

Symbolic name:

+		 +

MALWAREPROTECTION_OFFLINE_SCAN_INSTALLED

+
+

Message:

+		 +

The antimalware engine was downloaded and is configured to run offline on the next system restart.

+
+

Description:

+		 +

Windows Defender downloaded and configured Windows Defender Offline to run on the next reboot.

+
Event ID: 2031 +

Symbolic name:

+		 +

MALWAREPROTECTION_OFFLINE_SCAN_INSTALL_FAILED +

+
+

Message:

+		 +

The antimalware engine was unable to download and configure an offline scan.

+
+

Description:

+		 +

+

Windows Defender has encountered an error trying to download and configure Windows Defender Offline.

+
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
Event ID: 2040 +

Symbolic name:

+		 +

MALWAREPROTECTION_OS_EXPIRING +

+
+

Message:

+		 +

Antimalware support for this operating system version will soon end. +

+
+

Description:

+		 +

The support for your operating system will expire shortly. Running Windows Defender on an out of support operating system is not an adequate solution to protect against threats.

+
Event ID: 2041 +

Symbolic name:

+		 +

MALWAREPROTECTION_OS_EOL +

+
+

Message:

+		 +

Antimalware support for this operating system has ended. You must upgrade the operating system for continued support. +

+
+

Description:

+		 +

The support for your operating system has expired. Running Windows Defender on an out of support operating system is not an adequate solution to protect against threats.

+
Event ID: 2042 +

Symbolic name:

+		 +

MALWAREPROTECTION_PROTECTION_EOL +

+
+

Message:

+		 +

The antimalware engine no longer supports this operating system, and is no longer protecting your system from malware. +

+
+

Description:

+		 +

The support for your operating system has expired. Windows Defender is no longer supported on your operating system, has stopped functioning, and is not protecting against malware threats.

+
Event ID: 3002 +

Symbolic name:

+		 +

MALWAREPROTECTION_RTP_FEATURE_FAILURE +

+
+

Message:

+		 +

Real-time protection encountered an error and failed.

+
+

Description:

+		 +

+

Windows Defender Real-Time Protection feature has encountered an error and failed.

+
+
Feature: <Feature>, for example: +
    +
  • On Access
    • +
  • Internet Explorer downloads and Microsoft Outlook Express attachments
    • +
  • Behavior monitoring
    • +
  • Network Inspection System
    • +
+
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
Reason: The reason Windows Defender real-time protection has restarted a feature.
+
+

+
+

User action:

+		 +

You should restart the system then run a full scan because it’s possible the system was not protected for some time. +

+

The Windows Defender client’s real-time protection feature encountered an error because one of the services failed to start. +

+

If it is followed by a 3007 event ID, the failure was temporary and the antimalware client recovered from the failure. +

+
Event ID: 3007 +

Symbolic name:

+		 +

MALWAREPROTECTION_RTP_FEATURE_RECOVERED

+
+

Message:

+		 +

Real-time protection recovered from a failure. We recommend running a full system scan when you see this error. +

+
+

Description:

+		 +

+

Windows Defender Real-time Protection has restarted a feature. It is recommended that you run a full system scan to detect any items that may have been missed while this agent was down.

+
+
Feature: <Feature>, for example: +
    +
  • On Access
    • +
  • IE downloads and Outlook Express attachments
    • +
  • Behavior monitoring
    • +
  • Network Inspection System
    • +
+
+
Reason: The reason Windows Defender real-time protection has restarted a feature.
+
+

+
+

User action:

+		 +

The real-time protection feature has restarted. If this event happens again, contact Microsoft Technical Support.

+
Event ID: 5000 +

Symbolic name:

+		 +

MALWAREPROTECTION_RTP_ENABLED +

+
+

Message:

+		 +

Real-time protection is enabled. +

+
+

Description:

+		 +

Windows Defender Real-time Protection scanning for malware and other potentially unwanted software was enabled.

+
Event ID: 5001 +

Symbolic name:

+		 +

MALWAREPROTECTION_RTP_DISABLED

+
+

Message:

+		 +

Real-time protection is disabled. +

+
+

Description:

+		 +

Windows Defender Real-time Protection scanning for malware and other potentially unwanted software was disabled.

+
Event ID: 5004 +

Symbolic name:

+		 +

MALWAREPROTECTION_RTP_FEATURE_CONFIGURED +

+
+

Message:

+		 +

The real-time protection configuration changed. +

+
+

Description:

+		 +

+

Windows Defender Real-time Protection feature configuration has changed.

+
+
Feature: <Feature>, for example: +
    +
  • On Access
    • +
  • IE downloads and Outlook Express attachments
    • +
  • Behavior monitoring
    • +
  • Network Inspection System
    • +
+
+
Configuration:
+
+

+
Event ID: 5007 +

Symbolic name:

+		 +

MALWAREPROTECTION_CONFIG_CHANGED +

+
+

Message:

+		 +

The antimalware platform configuration changed.

+
+

Description:

+		 +

+

Windows Defender Configuration has changed. If this is an unexpected event you should review the settings as this may be the result of malware.

+
+
Old value: <Old value number> +Old Windows Defender configuration value.
+
New value: <New value number> +New Windows Defender configuration value.
+
+

+
Event ID: 5008 +

Symbolic name:

+		 +

MALWAREPROTECTION_ENGINE_FAILURE

+
+

Message:

+		 +

The antimalware engine encountered an error and failed.

+
+

Description:

+		 +

+

Windows Defender engine has been terminated due to an unexpected error.

+
+
Failure Type: <Failure type>, for example: +Crash +or Hang
+
Exception Code: <Error code>
+
Resource: <Resource>
+
+

+
+

User action:

+		 +

To troubleshoot this event:

    +
  1. Try to restart the service.
      +
    • For antimalware, antivirus and spyware, at an elevated command prompt, type net stop msmpsvc, and then type net start msmpsvc to restart the antimalware engine.
      • +
    • For the Network Inspection System, at an elevated command prompt, type net start nissrv, and then type net start nissrv to restart the Network Inspection System engine by using the NiSSRV.exe file. +
      • +
    +
    2. +
  2. If it fails in the same way, look up the error code by accessing the Microsoft Support Site and entering the error number in the Search box, and contact Microsoft Technical Support.
    3. +
+

+
+

User action:

+		 +

The Windows Defender client engine stopped due to an unexpected error.

+

To troubleshoot this event: +

    +
  1. Run the scan again.
    2. +
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. +
  3. Contact Microsoft Technical Support. +
    4. +
+

+
Event ID: 5009 +

Symbolic name:

+		 +

MALWAREPROTECTION_ANTISPYWARE_ENABLED +

+
+

Message:

+		 +

Scanning for malware and other potentially unwanted software is enabled. +

+
+

Description:

+		 +

Windows Defender scanning for malware and other potentially unwanted software has been enabled.

+
Event ID: 5010 +

Symbolic name:

+		 +

MALWAREPROTECTION_ANTISPYWARE_DISABLED +

+
+

Message:

+		 +

Scanning for malware and other potentially unwanted software is disabled.

+
+

Description:

+		 +

Windows Defender scanning for malware and other potentially unwanted software is disabled.

+
Event ID: 5011 +

Symbolic name:

+		 +

MALWAREPROTECTION_ANTIVIRUS_ENABLED

+
+

Message:

+		 +

Scanning for viruses is enabled.

+
+

Description:

+		 +

Windows Defender scanning for viruses has been enabled.

+
Event ID: 5012 +

Symbolic name:

+		 +

MALWAREPROTECTION_ANTIVIRUS_DISABLED +

+
+

Message:

+		 +

Scanning for viruses is disabled. +

+
+

Description:

+		 +

Windows Defender scanning for viruses is disabled.

+
Event ID: 5100 +

Symbolic name:

+		 +

MALWAREPROTECTION_EXPIRATION_WARNING_STATE +

+
+

Message:

+		 +

The antimalware platform will expire soon. +

+
+

Description:

+		 +

+

Windows Defender has entered a grace period and will soon expire. After expiration, this program will disable protection against viruses, spyware, and other potentially unwanted software.

+
+
Expiration Reason: The reason Windows Defender will expire.
+
Expiration Date: The date Windows Defender will expire.
+
+

+
Event ID: 5101 +

Symbolic name:

+		 +

MALWAREPROTECTION_DISABLED_EXPIRED_STATE +

+
+

Message:

+		 +

The antimalware platform is expired. +

+
+

Description::

+		 +

+

Windows Defender grace period has expired. Protection against viruses, spyware, and other potentially unwanted software is disabled.

+
+
Expiration Reason:
+
Expiration Date:
+
Error Code: <Error code> +Result code associated with threat status. Standard HRESULT values.
+
Error Description: <Error description> +Description of the error.
+
+

+
+ + +## Windows Defender client error codes +If Windows Defender Antivirus experiences any issues it will usually give you an error code to help you troubleshoot the issue. Most often an error means there was a problem installing an update. +This section provides the following information about Windows Defender Antivirus client errors. +- The error code +- The possible reason for the error +- Advice on what to do now +Use the information in these tables to help troubleshoot Windows Defender Antivirus error codes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
External error codes
Error codeMessage displayedPossible reason for errorWhat to do now
+

0x80508007 +

+		 +

ERR_MP_NO_MEMORY +

+		 +

This error indicates that you might have run out of memory. +

+		 +

+

    +
  1. Check the available memory on your device.
    2. +
  2. Close any unused applications that are running to free up memory on your device.
    3. +
  3. Restart the device and run the scan again. +
    4. +
+

+
+

0x8050800C

+		 +

ERR_MP_BAD_INPUT_DATA

+		 +

This error indicates that there might be a problem with your security product.

+		 +

+

    +
  1. Update the definitions. Either:
      +
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      +
      2. +
    2. Download the latest definitions from the Microsoft Malware Protection Center. +

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      +
      3. +
    +
    2. +
  2. Run a full scan. +
    3. +
  3. Restart the device and try again.
    4. +
+

+
+

0x80508020

+		 +

ERR_MP_BAD_CONFIGURATION +

+		 +

This error indicates that there might be an engine configuration error; commonly, this is related to input +data that does not allow the engine to function properly. +

+
+

0x805080211 +

+		 +

ERR_MP_QUARANTINE_FAILED +

+		 +

This error indicates that Windows Defender failed to quarantine a threat. +

+
+

0x80508022 +

+		 +

ERR_MP_REBOOT_REQUIRED +

+		 +

This error indicates that a reboot is required to complete threat removal. +

+
+

0x80508023 +

+		 +

ERR_MP_THREAT_NOT_FOUND +

+		 +

This error indicates that the threat might no longer be present on the media, or malware might be stopping you from scanning your device. +

+		 +

Run the Microsoft Safety Scanner then update your security software and try again. +

+
+

ERR_MP_FULL_SCAN_REQUIRED +

+		 +

This error indicates that a full system scan might be required. +

+		 +

Run a full system scan. +

+
+

0x80508024 +

+
+

0x80508025 +

+		 +

ERR_MP_MANUAL_STEPS_REQUIRED +

+		 +

This error indicates that manual steps are required to complete threat removal. +

+		 +

Follow the manual remediation steps outlined in the Microsoft Malware Protection Encyclopedia. You can find a threat-specific link in the event history. +

+
+

0x80508026 +

+		 +

ERR_MP_REMOVE_NOT_SUPPORTED +

+		 +

This error indicates that removal inside the container type might not be not supported. +

+		 +

Windows Defender is not able to remediate threats detected inside the archive. Consider manually removing the detected resources. +

+
+

0x80508027 +

+		 +

ERR_MP_REMOVE_LOW_MEDIUM_DISABLED +

+		 +

This error indicates that removal of low and medium threats might be disabled. +

+		 +

Check the detected threats and resolve them as required. +

+
+

0x80508029 +

+		 +

ERROR_MP_RESCAN_REQUIRED +

+		 +

This error indicates a rescan of the threat is required. +

+		 +

Run a full system scan. +

+
+

0x80508030 +

+		 +

ERROR_MP_CALLISTO_REQUIRED +

+		 +

This error indicates that an offline scan is required. +

+		 +

Run Windows Defender Offline. You can read about how to do this in the Windows Defender Offline +article.

+
+

0x80508031 +

+		 +

ERROR_MP_PLATFORM_OUTDATED +

+		 +

This error indicates that Windows Defender does not support the current version of the platform and requires a new version of the platform. +

+		 +

You can only use Windows Defender in Windows 10. For Windows 8, Windows 7 and Windows Vista, you can use System Center Endpoint Protection. +

+
+ + +The following error codes are used during internal testing of Windows Defender AV. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Internal error codes
Error codeMessage displayedPossible reason for errorWhat to do now
+

0x80501004

+		 +

ERROR_MP_NO_INTERNET_CONN +

+		 +

Check your Internet connection, then run the scan again.

+		 +

Check your Internet connection, then run the scan again.

+
+

0x80501000

+		 +

ERROR_MP_UI_CONSOLIDATION_BASE

+		 +

This is an internal error. The cause is not clearly defined.

+		 +

+

    +
  1. Update the definitions. Either:
      +
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      +
      2. +
    2. Download the latest definitions from the Microsoft Malware Protection Center. +

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      +
      3. +
    +
    2. +
  2. Run a full scan. +
    3. +
  3. Restart the device and try again.
    4. +
+

+
+

0x80501001

+		 +

ERROR_MP_ACTIONS_FAILED

+
+

0x80501002

+		 +

ERROR_MP_NOENGINE

+
+

0x80501003

+		 +

ERROR_MP_ACTIVE_THREATS

+
+

0x805011011

+		 +

MP_ERROR_CODE_LUA_CANCELLED

+
+

0x80501101

+		 +

ERROR_LUA_CANCELLATION

+
+

0x80501102

+		 +

MP_ERROR_CODE_ALREADY_SHUTDOWN

+
+

0x80501103

+		 +

MP_ERROR_CODE_RDEVICE_S_ASYNC_CALL_PENDING

+
+

0x80501104

+		 +

MP_ERROR_CODE_CANCELLED

+
+

0x80501105

+		 +

MP_ERROR_CODE_NO_TARGETOS

+
+

0x80501106

+		 +

MP_ERROR_CODE_BAD_REGEXP

+
+

0x80501107

+		 +

MP_ERROR_TEST_INDUCED_ERROR

+
+

0x80501108

+		 +

MP_ERROR_SIG_BACKUP_DISABLED

+
+

0x80508001

+		 +

ERR_MP_BAD_INIT_MODULES

+
+

0x80508002

+		 +

ERR_MP_BAD_DATABASE

+
+

0x80508004

+		 +

ERR_MP_BAD_UFS

+
+

0x8050800C

+		 +

ERR_MP_BAD_INPUT_DATA

+
+

0x8050800D

+		 +

ERR_MP_BAD_GLOBAL_STORAGE

+
+

0x8050800E

+		 +

ERR_MP_OBSOLETE

+
+

0x8050800F

+		 +

ERR_MP_NOT_SUPPORTED

+
+

0x8050800F +0x80508010 +

+		 +

ERR_MP_NO_MORE_ITEMS

+
+

0x80508011

+		 +

ERR_MP_DUPLICATE_SCANID

+
+

0x80508012

+		 +

ERR_MP_BAD_SCANID

+
+

0x80508013

+		 +

ERR_MP_BAD_USERDB_VERSION

+
+

0x80508014

+		 +

ERR_MP_RESTORE_FAILED

+
+

0x80508016

+		 +

ERR_MP_BAD_ACTION

+
+

0x80508019

+		 +

ERR_MP_NOT_FOUND

+
+

0x80509001

+		 +

ERR_RELO_BAD_EHANDLE

+
+

0x80509003

+		 +

ERR_RELO_KERNEL_NOT_LOADED

+
+

0x8050A001

+		 +

ERR_MP_BADDB_OPEN

+
+

0x8050A002

+		 +

ERR_MP_BADDB_HEADER

+
+

0x8050A003

+		 +

ERR_MP_BADDB_OLDENGINE

+
+

0x8050A004

+		 +

ERR_MP_BADDB_CONTENT

+
+

0x8050A005

+		 +

ERR_MP_BADDB_NOTSIGNED

+
+

0x8050801

+		 +

ERR_MP_REMOVE_FAILED

+		 +

This is an internal error. It might be triggered when malware removal is not successful. +

+
+

0x80508018 +

+		 +

ERR_MP_SCAN_ABORTED +

+		 +

This is an internal error. It might have triggered when a scan fails to complete. +

+
+ +## Related topics + +- [Report on Windows Defender Antivirus protection](report-monitor-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) diff --git a/windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md b/windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md index 3730d58e83..2c5e7c8ce8 100644 --- a/windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md +++ b/windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md @@ -1,6 +1,6 @@ --- title: Troubleshoot Windows Defender in Windows 10 (Windows 10) -description: IT professionals can review information about event IDs in Windows Defender for Windows 10 and see any relevant action they can take. +description: IT professionals can review information about event IDs in Windows Defender for Windows 10 and see any relevant action they can take. ms.assetid: EE488CC1-E340-4D47-B50B-35BD23CB4D70 ms.prod: w10 ms.mktglfcycl: manage @@ -8,3315 +8,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: jasesso +redirect_url: /troubleshoot-windows-defender-antivirus/ --- # Troubleshoot Windows Defender in Windows 10 -**Applies to** -- Windows 10 - -IT professionals can review information about event IDs in Windows Defender for Windows 10 and see any relevant action they can take. - -## Windows Defender client event IDs - -This section provides the following information about Windows Defender client events: - -- The text of the message as it appears in the event -- The name of the source of the message -- The symbolic name that identifies each message in the programming source code -- Additional information about the message - -Use the information in this table to help troubleshoot Windows Defender client events; these are located in the **Windows Event Viewer**, under **Windows Logs**. - -**To view a Windows Defender client event** - -1. Open **Event Viewer**. -2. In the console tree, expand **Applications and Services Logs**, then **Microsoft**, then **Windows**, then **Windows Defender**. -3. Double-click on **Operational**. -4. In the details pane, view the list of individual events to find your event. -5. Click the event to see specific details about an event in the lower pane, under the **General** and **Details** tabs. - -You can find a complete list of the Microsoft antimalware event IDs, the symbol, and the description of each ID in [Windows Server Antimalware Events TechNet](https://technet.microsoft.com/library/dn913615.aspx). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Event ID: 1000 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_STARTED

-
-

Message:

-		 -

An antimalware scan started. -

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
Scan Resources: <Resources (such as files/directories/BHO) that were scanned.>
-
User: <Domain>\<User>
-
-

-
Event ID: 1001 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_COMPLETED

-
-

Message:

-		 -

An antimalware scan finished.

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
User: <Domain>\<User>
-
Scan Time: <The duration of a scan.>
-
-

-
Event ID: 1002 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_CANCELLED -

-
-

Message:

-		 -

An antimalware scan was stopped before it finished. -

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
User: <Domain>\<User>
-
Scan Time: <The duration of a scan.>
-
-

-
Event ID: 1003 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_PAUSED -

-
-

Message:

-		 -

An antimalware scan was paused. -

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
User: <Domain>\<User>
-
-

-
Event ID: 1004 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_RESUMED -

-
-

Message:

-		 -

An antimalware scan was resumed. -

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
User: <Domain>\<User>
-
-

-
Event ID: 1005 -

Symbolic name:

-		 -

MALWAREPROTECTION_SCAN_FAILED -

-
-

Message:

-		 -

An antimalware scan failed. -

-
-

Description:

-		 -

-

-
Scan ID: <ID number of the relevant scan.>
-
Scan Type: <Scan type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
-
-
Scan Parameters: <Scan parameters>, for example:
    -
  • Full scan
    • -
  • Quick scan
    • -
  • Customer scan
    • -
-
-
User: <Domain>\<User>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
-

User action:

-		 -

The Windows Defender client encountered an error, and the current scan has stopped. The scan might fail due to a client-side issue. This event record includes the scan ID, type of scan (antivirus, antispyware, antimalware), scan parameters, the user that started the scan, the error code, and a description of the error. -

-

To troubleshoot this event: -

    -
  1. Run the scan again.
    2. -
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. -
  3. Contact Microsoft Technical Support. -
    4. -
-

-
Event ID: 1006 -

Symbolic name:

-		 -

MALWAREPROTECTION_MALWARE_DETECTED -

-
-

Message:

-		 -

The antimalware engine found malware or other potentially unwanted software. -

-
-

Description:

-		 -

-

For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example:
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
Status: <Status>
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1007 -

Symbolic name:

-		 -

MALWAREPROTECTION_MALWARE_ACTION_TAKEN -

-
-

Message:

-		 -

The antimalware platform performed an action to protect your system from malware or other potentially unwanted software. -

-
-

Description:

-		 -

-

Windows Defender has taken action to protect this machine from malware or other potentially unwanted software. For more information please see the following:

-
-
User: <Domain>\<User>
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Action: <Action>, for example:
    -
  • Clean: The resource was cleaned
    • -
  • Quarantine: The resource was quarantined
    • -
  • Remove: The resource was deleted
    • -
  • Allow: The resource was allowed to execute/exist
    • -
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • -
  • No action: No action
    • -
  • Block: The resource was blocked from executing
    • -
-
-
Status: <Status>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1008 -

Symbolic name:

-		 -

MALWAREPROTECTION_MALWARE_ACTION_FAILED

-
-

Message:

-		 -

The antimalware platform attempted to perform an action to protect your system from malware or other potentially unwanted software, but the action failed.

-
-

Description:

-		 -

-

Windows Defender has encountered an error when taking action on malware or other potentially unwanted software. For more information please see the following:

-
-
User: <Domain>\<User>
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Action: <Action>, for example:
    -
  • Clean: The resource was cleaned
    • -
  • Quarantine: The resource was quarantined
    • -
  • Remove: The resource was deleted
    • -
  • Allow: The resource was allowed to execute/exist
    • -
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • -
  • No action: No action
    • -
  • Block: The resource was blocked from executing
    • -
-
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Status: <Status>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1009 -

Symbolic name:

-		 -

MALWAREPROTECTION_QUARANTINE_RESTORE -

-
-

Message:

-		 -

The antimalware platform restored an item from quarantine. -

-
-

Description:

-		 -

-

Windows Defender has restored an item from quarantine. For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
User: <Domain>\<User>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1010 -

Symbolic name:

-		 -

MALWAREPROTECTION_QUARANTINE_RESTORE_FAILED -

-
-

Message:

-		 -

The antimalware platform could not restore an item from quarantine. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to restore an item from quarantine. For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
User: <Domain>\<User>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1011 -

Symbolic name:

-		 -

MALWAREPROTECTION_QUARANTINE_DELETE

-
-

Message:

-		 -

The antimalware platform deleted an item from quarantine. -

-
-

Description:

-		 -

-

Windows Defender has deleted an item from quarantine. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
User: <Domain>\<User>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1012 -

Symbolic name:

-		 -

MALWAREPROTECTION_QUARANTINE_DELETE_FAILED -

-
-

Message:

-		 -

The antimalware platform could not delete an item from quarantine.

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to delete an item from quarantine. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
User: <Domain>\<User>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
Event ID: 1013 -

Symbolic name:

-		 -

MALWAREPROTECTION_MALWARE_HISTORY_DELETE -

-
-

Message:

-		 -

The antimalware platform deleted history of malware and other potentially unwanted software.

-
-

Description:

-		 -

-

Windows Defender has removed history of malware and other potentially unwanted software.

-
-
Time: The time when the event occurred, for example when the history is purged. Note that this parameter is not used in threat events so that there is no confusion regarding whether it is remediation time or infection time. For those, we specifically call them as Action Time or Detection Time.
-
User: <Domain>\<User>
-
-

-
Event ID: 1014 -

Symbolic name:

-		 -

MALWAREPROTECTION_MALWARE_HISTORY_DELETE_FAILED -

-
-

Message:

-		 -

The antimalware platform could not delete history of malware and other potentially unwanted software.

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to remove history of malware and other potentially unwanted software.

-
-
Time: The time when the event occurred, for example when the history is purged. Note that this parameter is not used in threat events so that there is no confusion regarding whether it is remediation time or infection time. For those, we specifically call them as Action Time or Detection Time.
-
User: <Domain>\<User>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
Event ID: 1015 -

Symbolic name:

-		 -

MALWAREPROTECTION_BEHAVIOR_DETECTED -

-
-

Message:

-		 -

The antimalware platform detected suspicious behavior.

-
-

Description:

-		 -

-

Windows Defender has detected a suspicious behavior. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example: -
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
Status: <Status>
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Signature ID: Enumeration matching severity.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
Fidelity Label:
-
Target File Name: <File name> -Name of the file.
-
-

-
Event ID: 1116 -

Symbolic name:

-		 -

MALWAREPROTECTION_STATE_MALWARE_DETECTED

-
-

Message:

-		 -

The antimalware platform detected malware or other potentially unwanted software. -

-
-

Description:

-		 -

-

Windows Defender has detected malware or other potentially unwanted software. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example: -
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
-

User action:

-		 -

No action is required. Windows Defender can suspend and take routine action on this threat. If you want to remove the threat manually, in the Windows Defender interface, click Clean Computer.

-
Event ID: 1117 -

Symbolic name:

-		 -

MALWAREPROTECTION_STATE_MALWARE_ACTION_TAKEN -

-
-

Message:

-		 -

The antimalware platform performed an action to protect your system from malware or other potentially unwanted software. -

-
-

Description:

-		 -

-

Windows Defender has taken action to protect this machine from malware or other potentially unwanted software. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example: -
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Action: <Action>, for example:
    -
  • Clean: The resource was cleaned
    • -
  • Quarantine: The resource was quarantined
    • -
  • Remove: The resource was deleted
    • -
  • Allow: The resource was allowed to execute/exist
    • -
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • -
  • No action: No action
    • -
  • Block: The resource was blocked from executing
    • -
-
-
Action Status: <Description of additional actions>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-

NOTE: -

Whenever Windows Defender, Microsoft Security Essentials, Malicious Software Removal Tool, or System Center Endpoint Protection detects a malware, it will restore the following system settings and services which the malware might have changed:

    -
  • Default Internet Explorer or Edge setting
    • -
  • User Access Control settings
    • -
  • Chrome settings
    • -
  • Boot Control Data
    • -
  • Regedit and Task Manager registry settings
    • -
  • Windows Update, Background Intelligent Transfer Service, and Remote Procedure Call service
    • -
  • Windows Operating System files
-The above context applies to the following client and server versions: - - - - - - - - - - - - - -
Operating systemOperating system version
-

Client Operating System

-		 -

Windows Vista (Service Pack 1, or Service Pack 2), Windows 7 and later

-
-

Server Operating System

-		 -

Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2016

-
-

-
-
-

User action:

-		 -

No action is necessary. Windows Defender removed or quarantined a threat.

-
Event ID: 1118 -

Symbolic name:

-		 -

MALWAREPROTECTION_STATE_MALWARE_ACTION_FAILED

-
-

Message:

-		 -

The antimalware platform attempted to perform an action to protect your system from malware or other potentially unwanted software, but the action failed. -

-
-

Description:

-		 -

-

Windows Defender has encountered a non-critical error when taking action on malware or other potentially unwanted software. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example: -
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Action: <Action>, for example:
    -
  • Clean: The resource was cleaned
    • -
  • Quarantine: The resource was quarantined
    • -
  • Remove: The resource was deleted
    • -
  • Allow: The resource was allowed to execute/exist
    • -
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • -
  • No action: No action
    • -
  • Block: The resource was blocked from executing
    • -
-
-
Action Status: <Description of additional actions>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
-

User action:

-		 -

No action is necessary. Windows Defender failed to complete a task related to the malware remediation. This is not a critical failure.

-
Event ID: 1119 -

Symbolic name:

-		 -

MALWAREPROTECTION_STATE_MALWARE_ACTION_CRITICALLY_FAILED -

-
-

Message:

-		 -

The antimalware platform encountered a critical error when trying to take action on malware or other potentially unwanted software. There are more details in the event message.

-
-

Description:

-		 -

-

Windows Defender has encountered a critical error when taking action on malware or other potentially unwanted software. -For more information please see the following:

-
-
Name: <Threat name>
-
ID: <Threat ID>
-
Severity: <Severity>, for example:
    -
  • Low
    • -
  • Moderate
    • -
  • High
    • -
  • Severe
    • -
-
-
Category: <Category description>, for example, any threat or malware type.
-
Path: <File path>
-
Detection Origin: <Detection origin>, for example: -
    -
  • Unknown
    • -
  • Local computer
    • -
  • Network share
    • -
  • Internet
    • -
  • Incoming traffic
    • -
  • Outgoing traffic
    • -
-
-
Detection Type: <Detection type>, for example:
    -
  • Heuristics
    • -
  • Generic
    • -
  • Concrete
    • -
  • Dynamic signature
    • -
-
-
Detection Source: <Detection source> for example:
    -
  • User: user initiated
    • -
  • System: system initiated
    • -
  • Real-time: real-time component initiated
    • -
  • IOAV: IE Downloads and Outlook Express Attachments initiated
    • -
  • NIS: Network inspection system
    • -
  • IEPROTECT: IE - IExtensionValidation; this protects against malicious webpage controls
    • -
  • Early Launch Antimalware (ELAM). This includes malware detected by the boot sequence
    • -
  • Remote attestation
    • -
Antimalware Scan Interface (AMSI). Primarily used to protect scripts (PS, VBS), though it can be invoked by third parties as well. -UAC
-
User: <Domain>\<User>
-
Process Name: <Process in the PID>
-
Action: <Action>, for example:
    -
  • Clean: The resource was cleaned
    • -
  • Quarantine: The resource was quarantined
    • -
  • Remove: The resource was deleted
    • -
  • Allow: The resource was allowed to execute/exist
    • -
  • User defined: User defined action which is normally one from this list of actions that the user has specified
    • -
  • No action: No action
    • -
  • Block: The resource was blocked from executing
    • -
-
-
Action Status: <Description of additional actions>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
-

User action:

-		 -

The Windows Defender client encountered this error due to critical issues. The endpoint might not be protected. Review the error description then follow the relevant User action steps below.

- - - - - - - - - - - - - - - - - - - - - -
ActionUser action
-

Remove

-		 -

Update the definitions then verify that the removal was successful.

-
-

Clean

-		 -

Update the definitions then verify that the remediation was successful.

-
-

Quarantine

-		 -

Update the definitions and verify that the user has permission to access the necessary resources.

-
-

Allow

-		 -

Verify that the user has permission to access the necessary resources.

-
-

 

-

If this event persists:

    -
  1. Run the scan again.
    2. -
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. -
  3. Contact Microsoft Technical Support. -
    4. -
-

-
Event ID: 1120 -

Symbolic name:

-		 -

MALWAREPROTECTION_THREAT_HASH

-
-

Message:

-		 -

Windows Defender has deduced the hashes for a threat resource.

-
-

Description:

-		 -

-

Windows Defender client is up and running in a healthy state.

-
-
Current Platform Version: <Current platform version>
-
Threat Resource Path: <Path>
-
Hashes: <Hashes>
-
-

-
-
Note  This event will only be logged if the following policy is set: ThreatFileHashLogging unsigned.
-
 
-
Event ID: 1150 -

Symbolic name:

-		 -

MALWAREPROTECTION_SERVICE_HEALTHY

-
-

Message:

-		 -

If your antimalware platform reports status to a monitoring platform, this event indicates that the antimalware platform is running and in a healthy state. -

-
-

Description:

-		 -

-

Windows Defender client is up and running in a healthy state.

-
-
Platform Version: <Current platform version>
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware Engine version>
-
-

-
-

User action:

-		 -

No action is necessary. The Windows Defenderclient is in a healthy state. This event is reported on an hourly basis.

-
Event ID: 2000 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_UPDATED -

-
-

Message:

-		 -

The antimalware definitions updated successfully. -

-
-

Description:

-		 -

-

Windows Defender signature version has been updated.

-
-
Current Signature Version: <Current signature version>
-
Previous Signature Version: <Previous signature version>
-
Signature Type: <Signature type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
  • Network Inspection System
    • -
-
-
Update Type: <Update type>, either Full or Delta.
-
User: <Domain>\<User>
-
Current Engine Version: <Current engine version>
-
Previous Engine Version: <Previous engine version>
-
-

-
-

User action:

-		 -

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when signatures are successfully updated.

-
Event ID: 2001 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_UPDATE_FAILED

-
-

Message:

-		 -

The antimalware definition update failed. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to update signatures.

-
-
New Signature Version: <New version number>
-
Previous Signature Version: <Previous signature version>
-
Update Source: <Update source>, for example: -
    -
  • Signature update folder
    • -
  • Internal definition update server
    • -
  • Microsoft Update Server
    • -
  • File share
    • -
  • Microsoft Malware Protection Center (MMPC)
    • -
-
-
Update Stage: <Update stage>, for example: -
    -
  • Search
    • -
  • Download
    • -
  • Install
    • -
-
-
Source Path: File share name for Universal Naming Convention (UNC), server name for Windows Server Update Services (WSUS)/Microsoft Update/ADL.
-
Signature Type: <Signature type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
  • Network Inspection System
    • -
-
-
Update Type: <Update type>, either Full or Delta.
-
User: <Domain>\<User>
-
Current Engine Version: <Current engine version>
-
Previous Engine Version: <Previous engine version>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
-

User action:

-		 -

This error occurs when there is a problem updating definitions.

-

To troubleshoot this event: -

    -
  1. Update the definitions. Either:
      -
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      -
      2. -
    2. Download the latest definitions from the Microsoft Malware Protection Center. -

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      -
      3. -
    -
    2. -
  2. Review the entries in the %Windir%\WindowsUpdate.log file for more information about this error.
    3. -
  3. Contact Microsoft Technical Support. -
    4. -
-

-
Event ID: 2002 -

Symbolic name:

-		 -

MALWAREPROTECTION_ENGINE_UPDATED

-
-

Message:

-		 -

The antimalware engine updated successfully. -

-
-

Description:

-		 -

-

Windows Defender engine version has been updated.

-
-
Current Engine Version: <Current engine version>
-
Previous Engine Version: <Previous engine version>
-
Engine Type: <Engine type>, either antimalware engine or Network Inspection System engine.
-
User: <Domain>\<User>
-
-

-
-

User action:

-		 -

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when the antimalware engine is successfully updated.

-
Event ID: 2003 -

Symbolic name:

-		 -

MALWAREPROTECTION_ENGINE_UPDATE_FAILED

-
-

Message:

-		 -

The antimalware engine update failed. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to update the engine.

-
-
New Engine Version:
-
Previous Engine Version: <Previous engine version>
-
Engine Type: <Engine type>, either antimalware engine or Network Inspection System engine.
-
User: <Domain>\<User>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
-

User action:

-		 -

The Windows Defender client update failed. This event occurs when the client fails to update itself. This event is usually due to an interruption in network connectivity during an update.

-

To troubleshoot this event: -

    -
  1. Update the definitions. Either:
      -
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      -
      2. -
    2. Download the latest definitions from the Microsoft Malware Protection Center. -

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      -
      3. -
    -
    2. -
  2. Contact Microsoft Technical Support. -
    3. -
-

-
Event ID: 2004 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_REVERSION

-
-

Message:

-		 -

There was a problem loading antimalware definitions. The antimalware engine will attempt to load the last-known good set of definitions.

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to load signatures and will attempt reverting back to a known-good set of signatures.

-
-
Signatures Attempted:
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Signature Version: <Definition version>
-
Engine Version: <Antimalware engine version>
-
-

-
-

User action:

-		 -

The Windows Defender client attempted to download and install the latest definitions file and failed. This error can occur when the client encounters an error while trying to load the definitions, or if the file is corrupt. Windows Defender will attempt to revert back to a known-good set of definitions.

-

To troubleshoot this event: -

    -
  1. Restart the computer and try again.
    2. -
  2. Download the latest definitions from the Microsoft Malware Protection Center. -

    Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

    -
    3. -
  3. Contact Microsoft Technical Support. -
    4. -
-

-
Event ID: 2005 -

Symbolic name:

-		 -

MALWAREPROTECTION_ENGINE_UPDATE_PLATFORMOUTOFDATE

-
-

Message:

-		 -

The antimalware engine failed to load because the antimalware platform is out of date. The antimalware platform will load the last-known good antimalware engine and attempt to update.

-
-

Description:

-		 -

-

Windows Defender could not load antimalware engine because current platform version is not supported. Windows Defender will revert back to the last known-good engine and a platform update will be attempted.

-
-
Current Platform Version: <Current platform version>
-
-

-
Event ID: 2006 -

Symbolic name:

-		 -

MALWAREPROTECTION_PLATFORM_UPDATE_FAILED -

-
-

Message:

-		 -

The platform update failed. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to update the platform.

-
-
Current Platform Version: <Current platform version>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
Event ID: 2007 -

Symbolic name:

-		 -

MALWAREPROTECTION_PLATFORM_ALMOSTOUTOFDATE

-
-

Message:

-		 -

The platform will soon be out of date. Download the latest platform to maintain up-to-date protection.

-
-

Description:

-		 -

-

Windows Defender will soon require a newer platform version to support future versions of the antimalware engine. Download the latest Windows Defender platform to maintain the best level of protection available.

-
-
Current Platform Version: <Current platform version>
-
-

-
Event ID: 2010 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_FASTPATH_UPDATED -

-
-

Message:

-		 -

The antimalware engine used the Dynamic Signature Service to get additional definitions. -

-
-

Description:

-		 -

-

Windows Defender used Dynamic Signature Service to retrieve additional signatures to help protect your machine.

-
-
Current Signature Version: <Current signature version>
-
Signature Type: <Signature type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
  • Network Inspection System
    • -
-
-
Current Engine Version: <Current engine version>
-
Dynamic Signature Type: <Dynamic signature type>, for example: -
    -
  • Version
    • -
  • Timestamp
    • -
  • No limit
    • -
  • Duration
    • -
-
-
Persistence Path: <Path>
-
Dynamic Signature Version: <Version number>
-
Dynamic Signature Compilation Timestamp: <Timestamp>
-
Persistence Limit Type: <Persistence limit type>, for example: -
    -
  • VDM version
    • -
  • Timestamp
    • -
  • No limit
    • -
-
-
Persistence Limit: Persistence limit of the fastpath signature.
-
-

-
Event ID: 2011 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_FASTPATH_DELETED -

-
-

Message:

-		 -

The Dynamic Signature Service deleted the out-of-date dynamic definitions. -

-
-

Description:

-		 -

-

Windows Defender used Dynamic Signature Service to discard obsolete signatures.

-
-
Current Signature Version: <Current signature version>
-
Signature Type: <Signature type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
  • Network Inspection System
    • -
-
-
Current Engine Version: <Current engine version>
-
Dynamic Signature Type: <Dynamic signature type>, for example: -
    -
  • Version
    • -
  • Timestamp
    • -
  • No limit
    • -
  • Duration
    • -
-
-
Persistence Path: <Path>
-
Dynamic Signature Version: <Version number>
-
Dynamic Signature Compilation Timestamp: <Timestamp>
-
Removal Reason:
-
Persistence Limit Type: <Persistence limit type>, for example: -
    -
  • VDM version
    • -
  • Timestamp
    • -
  • No limit
    • -
-
-
Persistence Limit: Persistence limit of the fastpath signature.
-
-

-
-

User action:

-		 -

No action is necessary. The Windows Defender client is in a healthy state. This event is reported when the Dynamic Signature Service successfully deletes out-of-date dynamic definitions.

-
Event ID: 2012 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_FASTPATH_UPDATE_FAILED -

-
-

Message:

-		 -

The antimalware engine encountered an error when trying to use the Dynamic Signature Service. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to use Dynamic Signature Service.

-
-
Current Signature Version: <Current signature version>
-
Signature Type: <Signature type>, for example:
    -
  • Antivirus
    • -
  • Antispyware
    • -
  • Antimalware
    • -
  • Network Inspection System
    • -
-
-
Current Engine Version: <Current engine version>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Dynamic Signature Type: <Dynamic signature type>, for example: -
    -
  • Version
    • -
  • Timestamp
    • -
  • No limit
    • -
  • Duration
    • -
-
-
Persistence Path: <Path>
-
Dynamic Signature Version: <Version number>
-
Dynamic Signature Compilation Timestamp: <Timestamp>
-
Persistence Limit Type: <Persistence limit type>, for example: -
    -
  • VDM version
    • -
  • Timestamp
    • -
  • No limit
    • -
-
-
Persistence Limit: Persistence limit of the fastpath signature.
-
-

-
-

User action:

-		 -

Check your Internet connectivity settings.

-
Event ID: 2013 -

Symbolic name:

-		 -

MALWAREPROTECTION_SIGNATURE_FASTPATH_DELETED_ALL -

-
-

Message:

-		 -

The Dynamic Signature Service deleted all dynamic definitions. -

-
-

Description:

-		 -

-

Windows Defender discarded all Dynamic Signature Service signatures.

-
-
Current Signature Version: <Current signature version>
-
-

-
Event ID: 2020 -

Symbolic name:

-		 -

MALWAREPROTECTION_CLOUD_CLEAN_RESTORE_FILE_DOWNLOADED -

-
-

Message:

-		 -

The antimalware engine downloaded a clean file. -

-
-

Description:

-		 -

-

Windows Defender downloaded a clean file.

-
-
Filename: <File name> -Name of the file.
-
Current Signature Version: <Current signature version>
-
Current Engine Version: <Current engine version>
-
-

-
Event ID: 2021 -

Symbolic name:

-		 -

MALWAREPROTECTION_CLOUD_CLEAN_RESTORE_FILE_DOWNLOAD_FAILED

-
-

Message:

-		 -

The antimalware engine failed to download a clean file. -

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to download a clean file.

-
-
Filename: <File name> -Name of the file.
-
Current Signature Version: <Current signature version>
-
Current Engine Version: <Current engine version>
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
-

User action:

-		 -

Check your Internet connectivity settings. -

-

The Windows Defender client encountered an error when using the Dynamic Signature Service to download the latest definitions to a specific threat. This error is likely caused by a network connectivity issue. -

-
Event ID: 2030 -

Symbolic name:

-		 -

MALWAREPROTECTION_OFFLINE_SCAN_INSTALLED

-
-

Message:

-		 -

The antimalware engine was downloaded and is configured to run offline on the next system restart.

-
-

Description:

-		 -

Windows Defender downloaded and configured Windows Defender Offline to run on the next reboot.

-
Event ID: 2031 -

Symbolic name:

-		 -

MALWAREPROTECTION_OFFLINE_SCAN_INSTALL_FAILED -

-
-

Message:

-		 -

The antimalware engine was unable to download and configure an offline scan.

-
-

Description:

-		 -

-

Windows Defender has encountered an error trying to download and configure Windows Defender Offline.

-
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
Event ID: 2040 -

Symbolic name:

-		 -

MALWAREPROTECTION_OS_EXPIRING -

-
-

Message:

-		 -

Antimalware support for this operating system version will soon end. -

-
-

Description:

-		 -

The support for your operating system will expire shortly. Running Windows Defender on an out of support operating system is not an adequate solution to protect against threats.

-
Event ID: 2041 -

Symbolic name:

-		 -

MALWAREPROTECTION_OS_EOL -

-
-

Message:

-		 -

Antimalware support for this operating system has ended. You must upgrade the operating system for continued support. -

-
-

Description:

-		 -

The support for your operating system has expired. Running Windows Defender on an out of support operating system is not an adequate solution to protect against threats.

-
Event ID: 2042 -

Symbolic name:

-		 -

MALWAREPROTECTION_PROTECTION_EOL -

-
-

Message:

-		 -

The antimalware engine no longer supports this operating system, and is no longer protecting your system from malware. -

-
-

Description:

-		 -

The support for your operating system has expired. Windows Defender is no longer supported on your operating system, has stopped functioning, and is not protecting against malware threats.

-
Event ID: 2050

Symbolic name:

MALWAREPROTECTION_SAMPLESUBMISSION_UPLOAD

Message:

The antimalware engine has uploaded a file for further analysis.
Filename <uploaded filename>
Sha256: <file SHA>

Description:

A file was uploaded to the Windows Defender Antimalware cloud for further analysis or processing.

Event ID: 2051

Symbolic name:

MALWAREPROTECTION_SAMPLESUBMISSION_UPLOADED_FAILED

Message:

The antimalware engine has encountered an error trying to upload a suspicious file for further analysis.
-Filename: <uploaded filename>
-Sha256: <file SHA>
-Current Signature Version: <signature version number>
-Current Engine Version: <engine version number>
-Error code: <error code>

Description:

A file could not be uploaded to the Windows Defender Antimalware cloud.

User action:

You can attempt to manually submit the file.

Event ID: 3002 -

Symbolic name:

-		 -

MALWAREPROTECTION_RTP_FEATURE_FAILURE -

-
-

Message:

-		 -

Real-time protection encountered an error and failed.

-
-

Description:

-		 -

-

Windows Defender Real-Time Protection feature has encountered an error and failed.

-
-
Feature: <Feature>, for example: -
    -
  • On Access
    • -
  • Internet Explorer downloads and Microsoft Outlook Express attachments
    • -
  • Behavior monitoring
    • -
  • Network Inspection System
    • -
-
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
Reason: The reason Windows Defender real-time protection has restarted a feature.
-
-

-
-

User action:

-		 -

You should restart the system then run a full scan because it’s possible the system was not protected for some time. -

-

The Windows Defender client’s real-time protection feature encountered an error because one of the services failed to start. -

-

If it is followed by a 3007 event ID, the failure was temporary and the antimalware client recovered from the failure. -

-
Event ID: 3007 -

Symbolic name:

-		 -

MALWAREPROTECTION_RTP_FEATURE_RECOVERED

-
-

Message:

-		 -

Real-time protection recovered from a failure. We recommend running a full system scan when you see this error. -

-
-

Description:

-		 -

-

Windows Defender Real-time Protection has restarted a feature. It is recommended that you run a full system scan to detect any items that may have been missed while this agent was down.

-
-
Feature: <Feature>, for example: -
    -
  • On Access
    • -
  • IE downloads and Outlook Express attachments
    • -
  • Behavior monitoring
    • -
  • Network Inspection System
    • -
-
-
Reason: The reason Windows Defender real-time protection has restarted a feature.
-
-

-
-

User action:

-		 -

The real-time protection feature has restarted. If this event happens again, contact Microsoft Technical Support.

-
Event ID: 5000 -

Symbolic name:

-		 -

MALWAREPROTECTION_RTP_ENABLED -

-
-

Message:

-		 -

Real-time protection is enabled. -

-
-

Description:

-		 -

Windows Defender Real-time Protection scanning for malware and other potentially unwanted software was enabled.

-
Event ID: 5001 -

Symbolic name:

-		 -

MALWAREPROTECTION_RTP_DISABLED

-
-

Message:

-		 -

Real-time protection is disabled. -

-
-

Description:

-		 -

Windows Defender Real-time Protection scanning for malware and other potentially unwanted software was disabled.

-
Event ID: 5004 -

Symbolic name:

-		 -

MALWAREPROTECTION_RTP_FEATURE_CONFIGURED -

-
-

Message:

-		 -

The real-time protection configuration changed. -

-
-

Description:

-		 -

-

Windows Defender Real-time Protection feature configuration has changed.

-
-
Feature: <Feature>, for example: -
    -
  • On Access
    • -
  • IE downloads and Outlook Express attachments
    • -
  • Behavior monitoring
    • -
  • Network Inspection System
    • -
-
-
Configuration:
-
-

-
Event ID: 5007 -

Symbolic name:

-		 -

MALWAREPROTECTION_CONFIG_CHANGED -

-
-

Message:

-		 -

The antimalware platform configuration changed.

-
-

Description:

-		 -

-

Windows Defender Configuration has changed. If this is an unexpected event you should review the settings as this may be the result of malware.

-
-
Old value: <Old value number> -Old Windows Defender configuration value.
-
New value: <New value number> -New Windows Defender configuration value.
-
-

-
Event ID: 5008 -

Symbolic name:

-		 -

MALWAREPROTECTION_ENGINE_FAILURE

-
-

Message:

-		 -

The antimalware engine encountered an error and failed.

-
-

Description:

-		 -

-

Windows Defender engine has been terminated due to an unexpected error.

-
-
Failure Type: <Failure type>, for example: -Crash -or Hang
-
Exception Code: <Error code>
-
Resource: <Resource>
-
-

-
-

User action:

-		 -

To troubleshoot this event:

    -
  1. Try to restart the service.
      -
    • For antimalware, antivirus and spyware, at an elevated command prompt, type net stop msmpsvc, and then type net start msmpsvc to restart the antimalware engine.
      • -
    • For the Network Inspection System, at an elevated command prompt, type net start nissrv, and then type net start nissrv to restart the Network Inspection System engine by using the NiSSRV.exe file. -
      • -
    -
    2. -
  2. If it fails in the same way, look up the error code by accessing the Microsoft Support Site and entering the error number in the Search box, and contact Microsoft Technical Support.
    3. -
-

-
-

User action:

-		 -

The Windows Defender client engine stopped due to an unexpected error.

-

To troubleshoot this event: -

    -
  1. Run the scan again.
    2. -
  2. If it fails in the same way, go to the Microsoft Support site, enter the error number in the Search box to look for the error code.
    3. -
  3. Contact Microsoft Technical Support. -
    4. -
-

-
Event ID: 5009 -

Symbolic name:

-		 -

MALWAREPROTECTION_ANTISPYWARE_ENABLED -

-
-

Message:

-		 -

Scanning for malware and other potentially unwanted software is enabled. -

-
-

Description:

-		 -

Windows Defender scanning for malware and other potentially unwanted software has been enabled.

-
Event ID: 5010 -

Symbolic name:

-		 -

MALWAREPROTECTION_ANTISPYWARE_DISABLED -

-
-

Message:

-		 -

Scanning for malware and other potentially unwanted software is disabled.

-
-

Description:

-		 -

Windows Defender scanning for malware and other potentially unwanted software is disabled.

-
Event ID: 5011 -

Symbolic name:

-		 -

MALWAREPROTECTION_ANTIVIRUS_ENABLED

-
-

Message:

-		 -

Scanning for viruses is enabled.

-
-

Description:

-		 -

Windows Defender scanning for viruses has been enabled.

-
Event ID: 5012 -

Symbolic name:

-		 -

MALWAREPROTECTION_ANTIVIRUS_DISABLED -

-
-

Message:

-		 -

Scanning for viruses is disabled. -

-
-

Description:

-		 -

Windows Defender scanning for viruses is disabled.

-
Event ID: 5100 -

Symbolic name:

-		 -

MALWAREPROTECTION_EXPIRATION_WARNING_STATE -

-
-

Message:

-		 -

The antimalware platform will expire soon. -

-
-

Description:

-		 -

-

Windows Defender has entered a grace period and will soon expire. After expiration, this program will disable protection against viruses, spyware, and other potentially unwanted software.

-
-
Expiration Reason: The reason Windows Defender will expire.
-
Expiration Date: The date Windows Defender will expire.
-
-

-
Event ID: 5101 -

Symbolic name:

-		 -

MALWAREPROTECTION_DISABLED_EXPIRED_STATE -

-
-

Message:

-		 -

The antimalware platform is expired. -

-
-

Description::

-		 -

-

Windows Defender grace period has expired. Protection against viruses, spyware, and other potentially unwanted software is disabled.

-
-
Expiration Reason:
-
Expiration Date:
-
Error Code: <Error code> -Result code associated with threat status. Standard HRESULT values.
-
Error Description: <Error description> -Description of the error.
-
-

-
- -## Windows Defender client error codes -If Windows Defender experiences any issues it will usually give you an error code to help you troubleshoot the issue. Most often an error means there was a problem installing an update. -This section provides the following information about Windows Defender client errors. -- The error code -- The possible reason for the error -- Advice on what to do now -Use the information in these tables to help troubleshoot Windows Defender error codes. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
External error codes
Error codeMessage displayedPossible reason for errorWhat to do now
-

0x80508007 -

-		 -

ERR_MP_NO_MEMORY -

-		 -

This error indicates that you might have run out of memory. -

-		 -

-

    -
  1. Check the available memory on your device.
    2. -
  2. Close any unused applications that are running to free up memory on your device.
    3. -
  3. Restart the device and run the scan again. -
    4. -
-

-
-

0x8050800C

-		 -

ERR_MP_BAD_INPUT_DATA

-		 -

This error indicates that there might be a problem with your security product.

-		 -

-

    -
  1. Update the definitions. Either:
      -
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      -
      2. -
    2. Download the latest definitions from the Microsoft Malware Protection Center. -

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      -
      3. -
    -
    2. -
  2. Run a full scan. -
    3. -
  3. Restart the device and try again.
    4. -
-

-
-

0x80508020

-		 -

ERR_MP_BAD_CONFIGURATION -

-		 -

This error indicates that there might be an engine configuration error; commonly, this is related to input -data that does not allow the engine to function properly. -

-
-

0x805080211 -

-		 -

ERR_MP_QUARANTINE_FAILED -

-		 -

This error indicates that Windows Defender failed to quarantine a threat. -

-
-

0x80508022 -

-		 -

ERR_MP_REBOOT_REQUIRED -

-		 -

This error indicates that a reboot is required to complete threat removal. -

-
-

0x80508023 -

-		 -

ERR_MP_THREAT_NOT_FOUND -

-		 -

This error indicates that the threat might no longer be present on the media, or malware might be stopping you from scanning your device. -

-		 -

Run the Microsoft Safety Scanner then update your security software and try again. -

-
-

ERR_MP_FULL_SCAN_REQUIRED -

-		 -

This error indicates that a full system scan might be required. -

-		 -

Run a full system scan. -

-
-

0x80508024 -

-
-

0x80508025 -

-		 -

ERR_MP_MANUAL_STEPS_REQUIRED -

-		 -

This error indicates that manual steps are required to complete threat removal. -

-		 -

Follow the manual remediation steps outlined in the Microsoft Malware Protection Encyclopedia. You can find a threat-specific link in the event history. -

-
-

0x80508026 -

-		 -

ERR_MP_REMOVE_NOT_SUPPORTED -

-		 -

This error indicates that removal inside the container type might not be not supported. -

-		 -

Windows Defender is not able to remediate threats detected inside the archive. Consider manually removing the detected resources. -

-
-

0x80508027 -

-		 -

ERR_MP_REMOVE_LOW_MEDIUM_DISABLED -

-		 -

This error indicates that removal of low and medium threats might be disabled. -

-		 -

Check the detected threats and resolve them as required. -

-
-

0x80508029 -

-		 -

ERROR_MP_RESCAN_REQUIRED -

-		 -

This error indicates a rescan of the threat is required. -

-		 -

Run a full system scan. -

-
-

0x80508030 -

-		 -

ERROR_MP_CALLISTO_REQUIRED -

-		 -

This error indicates that an offline scan is required. -

-		 -

Run Windows Defender Offline. You can read about how to do this in the Windows Defender Offline -article.

-
-

0x80508031 -

-		 -

ERROR_MP_PLATFORM_OUTDATED -

-		 -

This error indicates that Windows Defender does not support the current version of the platform and requires a new version of the platform. -

-		 -

You can only use Windows Defender in Windows 10. For Windows 8, Windows 7 and Windows Vista, you can use System Center Endpoint Protection. -

-
-

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Internal error codes
Error codeMessage displayedPossible reason for errorWhat to do now
-

0x80501004

-		 -

ERROR_MP_NO_INTERNET_CONN -

-		 -

Check your Internet connection, then run the scan again.

-		 -

Check your Internet connection, then run the scan again.

-
-

0x80501000

-		 -

ERROR_MP_UI_CONSOLIDATION_BASE

-		 -

This is an internal error. The cause is not clearly defined.

-		 -

-

    -
  1. Update the definitions. Either:
      -
    1. Click the Update definitions button on the Update tab in Windows Defender. Update definitions in Windows Defender

      Or,

      -
      2. -
    2. Download the latest definitions from the Microsoft Malware Protection Center. -

      Note: The size of the definitions file downloaded from the Microsoft Malware Protection Center can exceed 60 MB and should not be used as a long-term solution for updating definitions.

      -
      3. -
    -
    2. -
  2. Run a full scan. -
    3. -
  3. Restart the device and try again.
    4. -
-

-
-

0x80501001

-		 -

ERROR_MP_ACTIONS_FAILED

-
-

0x80501002

-		 -

ERROR_MP_NOENGINE

-
-

0x80501003

-		 -

ERROR_MP_ACTIVE_THREATS

-
-

0x805011011

-		 -

MP_ERROR_CODE_LUA_CANCELLED

-
-

0x80501101

-		 -

ERROR_LUA_CANCELLATION

-
-

0x80501102

-		 -

MP_ERROR_CODE_ALREADY_SHUTDOWN

-
-

0x80501103

-		 -

MP_ERROR_CODE_RDEVICE_S_ASYNC_CALL_PENDING

-
-

0x80501104

-		 -

MP_ERROR_CODE_CANCELLED

-
-

0x80501105

-		 -

MP_ERROR_CODE_NO_TARGETOS

-
-

0x80501106

-		 -

MP_ERROR_CODE_BAD_REGEXP

-
-

0x80501107

-		 -

MP_ERROR_TEST_INDUCED_ERROR

-
-

0x80501108

-		 -

MP_ERROR_SIG_BACKUP_DISABLED

-
-

0x80508001

-		 -

ERR_MP_BAD_INIT_MODULES

-
-

0x80508002

-		 -

ERR_MP_BAD_DATABASE

-
-

0x80508004

-		 -

ERR_MP_BAD_UFS

-
-

0x8050800C

-		 -

ERR_MP_BAD_INPUT_DATA

-
-

0x8050800D

-		 -

ERR_MP_BAD_GLOBAL_STORAGE

-
-

0x8050800E

-		 -

ERR_MP_OBSOLETE

-
-

0x8050800F

-		 -

ERR_MP_NOT_SUPPORTED

-
-

0x8050800F -0x80508010 -

-		 -

ERR_MP_NO_MORE_ITEMS

-
-

0x80508011

-		 -

ERR_MP_DUPLICATE_SCANID

-
-

0x80508012

-		 -

ERR_MP_BAD_SCANID

-
-

0x80508013

-		 -

ERR_MP_BAD_USERDB_VERSION

-
-

0x80508014

-		 -

ERR_MP_RESTORE_FAILED

-
-

0x80508016

-		 -

ERR_MP_BAD_ACTION

-
-

0x80508019

-		 -

ERR_MP_NOT_FOUND

-
-

0x80509001

-		 -

ERR_RELO_BAD_EHANDLE

-
-

0x80509003

-		 -

ERR_RELO_KERNEL_NOT_LOADED

-
-

0x8050A001

-		 -

ERR_MP_BADDB_OPEN

-
-

0x8050A002

-		 -

ERR_MP_BADDB_HEADER

-
-

0x8050A003

-		 -

ERR_MP_BADDB_OLDENGINE

-
-

0x8050A004

-		 -

ERR_MP_BADDB_CONTENT

-
-

0x8050A005

-		 -

ERR_MP_BADDB_NOTSIGNED

-
-

0x8050801

-		 -

ERR_MP_REMOVE_FAILED

-		 -

This is an internal error. It might be triggered when malware removal is not successful. -

-
-

0x80508018 -

-		 -

ERR_MP_SCAN_ABORTED -

-		 -

This is an internal error. It might have triggered when a scan fails to complete. -

-
- -## Related topics - -- [Configure Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md) -- [Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md) +This page has been redirected to *Troubleshoot Windows Defender Antivirus*. \ No newline at end of file diff --git a/windows/keep-secure/use-group-policy-windows-defender-antivirus.md b/windows/keep-secure/use-group-policy-windows-defender-antivirus.md new file mode 100644 index 0000000000..07133adfb1 --- /dev/null +++ b/windows/keep-secure/use-group-policy-windows-defender-antivirus.md @@ -0,0 +1,15 @@ +--- +title: Configure Windows Defender AV with Group Policy +description: Configure Windows Defender AV settings with Group Policy +keywords: group policy, GPO, configuration, settings +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Use Group Policy settings to configure and manage Windows Defender AV \ No newline at end of file diff --git a/windows/keep-secure/use-intune-config-manager-windows-defender-antivirus.md b/windows/keep-secure/use-intune-config-manager-windows-defender-antivirus.md new file mode 100644 index 0000000000..9f6c3a09b5 --- /dev/null +++ b/windows/keep-secure/use-intune-config-manager-windows-defender-antivirus.md @@ -0,0 +1,15 @@ +--- +title: Configure Windows Defender AV with Configuration Manager and Intune +description: Use System Center Configuration Manager and Microsoft Intune to configure Windows Defender AV and Endpoint Protection +keywords: scep, intune, endpoint protection, configuration +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Use System Center Configuration Manager and Microsoft Intune to configure and manage Windows Defender AV \ No newline at end of file diff --git a/windows/keep-secure/use-powershell-cmdlets-windows-defender-antivirus.md b/windows/keep-secure/use-powershell-cmdlets-windows-defender-antivirus.md new file mode 100644 index 0000000000..7d975adcd1 --- /dev/null +++ b/windows/keep-secure/use-powershell-cmdlets-windows-defender-antivirus.md @@ -0,0 +1,51 @@ +--- +title: Use PowerShell cmdlets to configure and run Windows Defender AV +description: In Windows 10, you can use PowerShell cmdlets to run scans, update definitions, and change settings in Windows Defender Antivirus. +keywords: scan, command line, mpcmdrun, defender +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Use PowerShell cmdlets to configure and manage Windows Defender AV + +**Applies to:** + +- Windows 10 + +You can use PowerShell to perform various functions in Windows Defender. Similar to the command prompt or command line, PowerShell is a task-based command-line shell and scripting language designed especially for system administration, and you can read more about it at the [PowerShell hub on MSDN](https://msdn.microsoft.com/en-us/powershell/mt173057.aspx). + +For a list of the cmdlets and their functions and available parameters, see the [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) topic. + +PowerShell cmdlets are most useful in Windows Server environments that don't rely on a graphical user interface (GUI) to configure software. + +> [!NOTE] +> PowerShell cmdlets should not be used as a replacement for a full network policy management infrastructure, such as [System Center Configuration Manager](https://technet.microsoft.com/en-us/library/gg682129.aspx), [Group Policy Management Console](https://technet.microsoft.com/en-us/library/cc731212.aspx), or [Windows Defender Group Policy ADMX templates](https://support.microsoft.com/en-us/kb/927367). + +PowerShell is typically installed under the folder _%SystemRoot%\system32\WindowsPowerShell_. + + +**Use Windows Defender PowerShell cmdlets** + +1. Click **Start**, type **powershell**, and press **Enter**. +2. Click **Windows PowerShell** to open the interface. + > [!NOTE] + > You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt. +3. Enter the command and parameters. + +To open online help for any of the cmdlets type the following: + +```PowerShell +Get-Help -Online +``` +Omit the `-online` parameter to get locally cached help. + +## Related topics + +- [Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md) +- [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) \ No newline at end of file diff --git a/windows/keep-secure/use-powershell-cmdlets-windows-defender-for-windows-10.md b/windows/keep-secure/use-powershell-cmdlets-windows-defender-for-windows-10.md index 0ab40df034..dec540347e 100644 --- a/windows/keep-secure/use-powershell-cmdlets-windows-defender-for-windows-10.md +++ b/windows/keep-secure/use-powershell-cmdlets-windows-defender-for-windows-10.md @@ -10,41 +10,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: iaanw +redirect_url: /use-powershell-cmdlets-windows-defender-antivirus/ --- # Use PowerShell cmdlets to configure and run Windows Defender -**Applies to:** - -- Windows 10 - -You can use PowerShell to perform various functions in Windows Defender. Similar to the command prompt or command line, PowerShell is a task-based command-line shell and scripting language designed especially for system administration, and you can read more about it at the [PowerShell hub on MSDN](https://msdn.microsoft.com/en-us/powershell/mt173057.aspx). - -For a list of the cmdlets and their functions and available parameters, see the [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) topic. - -PowerShell cmdlets are most useful in Windows Server environments that don't rely on a graphical user interface (GUI) to configure software. - -> [!NOTE] -> PowerShell cmdlets should not be used as a replacement for a full network policy management infrastructure, such as [System Center Configuration Manager](https://technet.microsoft.com/en-us/library/gg682129.aspx), [Group Policy Management Console](https://technet.microsoft.com/en-us/library/cc731212.aspx), or [Windows Defender Group Policy ADMX templates](https://support.microsoft.com/en-us/kb/927367). - -PowerShell is typically installed under the folder _%SystemRoot%\system32\WindowsPowerShell_. - - -**Use Windows Defender PowerShell cmdlets** - -1. Click **Start**, type **powershell**, and press **Enter**. -2. Click **Windows PowerShell** to open the interface. - > [!NOTE] - > You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt. -3. Enter the command and parameters. - -To open online help for any of the cmdlets type the following: - -```text -Get-Help -Online -``` -Omit the `-online` parameter to get locally cached help. - -## Related topics - -- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) \ No newline at end of file +This page has been redirected to *Use PowerShell cmdlets to configure and run Windows Defender Antivirus*. \ No newline at end of file diff --git a/windows/keep-secure/use-wmi-windows-defender-antivirus.md b/windows/keep-secure/use-wmi-windows-defender-antivirus.md new file mode 100644 index 0000000000..e369e90bd8 --- /dev/null +++ b/windows/keep-secure/use-wmi-windows-defender-antivirus.md @@ -0,0 +1,15 @@ +--- +title: Configure Windows Defender AV with WMI +description: Use WMI scripts to configure Windows Defender AV +keywords: wmi, scripts, windows management instrumentation, configuration +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Use System Center Configuration Manager and Microsoft Intune to configure and manage Windows Defender AV \ No newline at end of file diff --git a/windows/keep-secure/utilize-microsoft-cloud-protection-windows-defender-antivirus.md b/windows/keep-secure/utilize-microsoft-cloud-protection-windows-defender-antivirus.md new file mode 100644 index 0000000000..708740d908 --- /dev/null +++ b/windows/keep-secure/utilize-microsoft-cloud-protection-windows-defender-antivirus.md @@ -0,0 +1,57 @@ +--- +title: Utilize cloud-delivered protection in Windows Defender Antivirus +description: Cloud-delivered protection provides an advanced level of fast, robust antivirus detection. +keywords: windows defender antivirus, antimalware, security, defender, cloud, cloud-delivered protection +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Utilize Microsoft cloud-delivered protection in Windows Defender Antivirus + +**Applies to:** + +- Windows 10, version 1703 + +**Audience** + +- Enterprise security administrators + +Cloud-delivered protection for Windows Defender Antivirus, also referred to as Microsoft Advanced Protection Service (MAPS), provides you with strong, fast protection in addition to our standard real-time protection. + + + +>[!NOTE] +>The Windows Defender Antivirus cloud service is a mechanism for delivering updated protection to your network and endpoints. Although it is called a cloud service, it is not simply protection for files stored in the cloud, rather it uses distributed resources and machine learning to deliver protection to your endpoints at a rate that is far faster than traditional signature updates. + +Enabling cloud-delivered protection helps detect and block new malware - even if the malware has never been seen before - without needing to wait for a traditionally delivered definition update to block it. Definition updates can take hours to prepare and deliver, while our cloud service can deliver updated protection in seconds. + +Cloud-delivered protecton is enabled by default, however you may need to re-enable it if it has been disabled as part of previous organizational policies. + +The following table describes the differences in cloud-based protection between recent versions of Windows and System Center Configuration Manager. + + +Feature | Windows 8.1 (Group Policy) | Windows 10, version 1607 (Group Policy) | Windows 10, version 1703 (Group Policy) | Configuration manager 2012 | Configuration manager (current branch) | Microsoft Intune +---|---|---|---|---|---|--- +Cloud-protection service label | Microsoft Advanced Protection Service | Microsoft Advanced Protection Service | Cloud-based Protection | NA | Cloud protection service | Microsoft Advanced Protection Service +Reporting level (MAPS membership level) | Basic, Advanced | Advanced | Advanced | Dependent on Windows version | Dependent on Windows version | Dependent on Windows version +Block at first sight availability | No | Yes | Yes | Not configurable | Configurable | No +Cloud block timeout period | No | No | Configurable | Not configurable | Configurable | No + +You can also [configure Windows Defender AV to automatically receive new protection updates based on reports from our cloud service](manage-event-based-updates-windows-defender-antivirus.md#cloud-report-updates). + + +## In this section + + Topic | Description +---|--- +[Enable cloud-delivered protection](enable-cloud-protection-windows-defender-antivirus.md) | You can enable cloud-delivered protection with System Center Configuration Manager, Group Policy, Microsoft Intune, and PowerShell cmdlets. +[Specify the cloud-delivered protection level](specify-cloud-protection-level-windows-defender-antivirus.md) | You can specify the level of protection offered by the cloud with Group Policy and System Center Configuration Manager. The protection level will affect the amount of information shared with the cloud and how aggressively new files are blocked. +[Configure and validate network connections for Windows Defender Antivirus](configure-network-connections-windows-defender-antivirus.md) | There are certain Microsoft URLs that your network and endpoints must be able to connect to for cloud-delivered protection to work effectively. This topic lists the URLs that should be allowed via firewall or network filtering rules, and instructions for confirming your network is properly enrolled in cloud-delivered protection. +[Configure the Block at First Sight feature](configure-block-at-first-sight-windows-defender-antivirus.md) | The Block at First Sight feature can block new malware within seconds, without having to wait hours for a traditional signature. You can enable and configure it with System Center Configuration Manager and Group Policy. +[Configure the cloud block timeout period](configure-cloud-block-timeout-period-windows-defender-antivirus.md) | Windows Defender Antivirus can block suspicious files from running while it queries our cloud-based protection service. You can configure the amount of time the file will be prevented from running with System Center Configuration Manager and Group Policy. \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-antivirus-in-windows-10.md b/windows/keep-secure/windows-defender-antivirus-in-windows-10.md new file mode 100644 index 0000000000..350b93809e --- /dev/null +++ b/windows/keep-secure/windows-defender-antivirus-in-windows-10.md @@ -0,0 +1,74 @@ +--- +title: Windows Defender Antivirus +description: Learn how to manage, configure, and use Windows Defender AV, the built-in antimalware and antivirus product available in Windows 10. +keywords: windows defender antivirus, windows defender, antimalware, scep, system center endpoint protection, system center configuration manager, virus, malware, threat, detection, protection, security +ms.assetid: 6A9EB85E-1F3A-40AC-9A47-F44C4A2B55E2 +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + +# Windows Defender Antivirus in Windows 10 + +**Applies to** +- Windows 10 + +Windows Defender Antivirus is a built-in antimalware solution that provides security and antimalware management for desktops, portable computers, and servers. + +This library of documentation is aimed for enterprise security administrators who are either considering deployment, or have already deployed and are wanting to manage and configure Windows Defender AV on PC endpoints in their network. + +For more important information about running Windows Defender on a server platform, see [Windows Defender Overview for Windows Server](https://technet.microsoft.com/library/dn765478.aspx). + +## What's new in Windows 10, version 1703 + +New features for Windows Defender AV in Windows 10, version 1703 include: +- [Updates to how the Block at First Sight feature can be configured](configure-block-at-first-sight-windows-defender-antivirus.md) +- [The ability to specify the level of cloud-protection](specify-cloud-protection-level-windows-defender-antivirus.md) +- [Windows Defender Antivirus protection in the Windows Defender Security Center app](windows-defender-security-center-antivirus.md) + +We've expanded this documentation library to cover end-to-end deployment, management, and configuration for Windows Defender AV, and we've added some new guides that can help with evaluating and deploying Windows Defender AV in certain scenarios: +- [Evaluation guide for Windows Defender AV](evaluate-windows-defender-antivirus.md) +- [Deployment guide for Windows Defender AV in a virtual desktop infrastructure environment](deployment-vdi-windows-defender-antivirus.md) + +See the [In this library](#in-this-library) list at the end of this topic for links to each of the updated sections in this library. + + +## Minimum system requirements + +Windows Defender has the same hardware requirements as Windows 10. For more information, see: +- [Minimum hardware requirements](https://msdn.microsoft.com/library/windows/hardware/dn915086.aspx) +- [Hardware component guidelines](https://msdn.microsoft.com/library/windows/hardware/dn915049.aspx) + + +Some features require a certain version of Windows 10 - the minimum version required is specified at the top of each topic. + +## Compatibility with Windows Defender Advanced Threat Protection + +Windows Defender Advanced Threat Protection (ATP) is an additional service that helps enterprises to detect, investigate, and respond to advanced persistent threats on their network. + +See the [Windows Defender Advanced Threat Protection](windows-defender-advanced-threat-protection.md) topics for more information about the service. + +If you are enrolled in Windows Defender ATP, and you are not using Windows Defender as your real-time protection service on your endpoints, Windows Defender will automatically enter into a passive mode. + +In passive mode, Windows Defender will continue to run (using the *msmpeng.exe* process), and will continue to be updated, however there will be no Windows Defender user interface, scheduled scans won’t run, and Windows Defender will not provide real-time protection from malware. + +You can still [manage updates for Windows Defender](manage-updates-baselines-windows-defender-antivirus.md), however you can't move Windows Defender into the normal active mode if your endpoints have an up-to-date third-party product providing real-time protection from malware. + +If you uninstall the other product, and choose to use Windows Defender to provide protection to your endpoints, Windows Defender will automatically return to its normal active mode. + + + +## In this library + +Topic | Description +:---|:--- +[Evaluate Windows Defender Antivirus protection](evaluate-windows-defender-antivirus.md) | Evaluate the protection capabilities of Windows Defender Antivirus with a specialized evaluation guide and powershell script. +[Deploy, manage updates, and report on Windows Defender Antivirus](deploy-manage-report-windows-defender-antivirus.md) | While traditional client deployment is not required for Windows Defender AV, you will need to enable the service. You can also manage how protection and product updates are applies, and receive reports from Configuration Manager, Intune, and with some security information and event monitoring (SIEM) tools. +[Configure Windows Defender features](configure-windows-defender-antivirus-features.md) | Windows Defender AV has a large set of configurable features and options. You can use a number of management tools, including Group Policy, System Center Configuration Manager, Microsoft Intune, PowerShell cmdlets, and Windows Management Instrumentation (WMI). You can configure options such as cloud-delivered protection, always-on monitoring and scanning, and how end-users can interact or override global policy settings. +[Customize, initiate, and review the results of scans and remediation](customize-run-review-remediate-scans-windows-defender-antivirus.md) | You can set up scheduled scans, run on-demand scans, and configure how remediation works when threats are detected. +[Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-antivirus.md)|Review event IDs in Windows Defender Antivirus and take the appropriate actions. +[Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md)|The management and configuration tools that you can use with Windows Defender AV are listed and described here. + diff --git a/windows/keep-secure/windows-defender-block-at-first-sight.md b/windows/keep-secure/windows-defender-block-at-first-sight.md index 342b7ac541..4c9af5e903 100644 --- a/windows/keep-secure/windows-defender-block-at-first-sight.md +++ b/windows/keep-secure/windows-defender-block-at-first-sight.md @@ -10,121 +10,10 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: iaanw +redirect_url: /configure-block-at-first-sight-windows-defender-antivirus/ + --- # Block at First Sight -**Applies to** - -- Windows 10, version 1607 - -**Audience** - -- Network administrators - -Block at First Sight is a feature of Windows Defender cloud protection that provides a way to detect and block new malware within seconds. - -It is enabled by default when certain pre-requisite settings are also enabled. In most cases, these pre-requisite settings are also enabled by default, so the feature is running without any intervention. - -## How it works - -When a Windows Defender client encounters a suspicious but undetected file, it queries our cloud protection backend. The cloud backend will apply heuristics, machine learning, and automated analysis of the file to determine the files as malicious or clean. - -> [!NOTE] -> The Block at first sight feature only uses the cloud-protection backend for "portable executable" (PE) files that are downloaded from the Internet, or originating from the Internet zone. This includes file types such as .exe, .dll, .scr, and so on. A hash value of the file is checked via the cloud backend to determine if this is a previously undetected file. - -If the cloud backend is unable to make a determination, the file will be locked by Windows Defender while a copy is uploaded to the cloud. Only after the cloud has received the file will Windows Defender release the lock and let the file run. The cloud will perform additional analysis to reach a determination, blocking all future encounters of that file. - -In many cases this process can reduce the response time to new malware from hours to seconds. - -> [!NOTE] -> Suspicious file downloads requiring additional backend processing to reach a determination will be locked by Windows Defender on the first machine where the file is encountered, until it is finished uploading to the backend. Users will see a longer "Running security scan" message in the browser while the file is being uploaded. This might result in what appear to be slower download times for some files. - - -## Confirm Block at First Sight is enabled - -Block at First Sight requires a number of Group Policy settings to be configured correctly or it will not work. Usually, these settings are already enabled in most default Windows Defender deployments in enterprise networks. - -> [!IMPORTANT] -> There is no specific individual setting in System Center Configuration Manager to enable Block at First Sight. It is enabled by default when the pre-requisite settings are configured correctly. - -### Confirm Block at First Sight is enabled with Group Policy - -1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. - -3. In the **Group Policy Management Editor** go to **Computer configuration**. - -4. Click **Policies** then **Administrative templates**. - -5. Expand the tree to **Windows components > Windows Defender > MAPS** and configure the following Group Policies: - - 1. Double-click the **Join Microsoft MAPS** setting and ensure the option is set to **Enabled**. Click **OK**. - - 1. Double-click the **Send file samples when further analysis is required** setting and ensure the option is set to **Enabled** and the additional options are either of the following: - - 1. Send safe samples (1) - - 1. Send all samples (3) - - > [!WARNING] - > Setting to 0 (Always Prompt) will lower the protection state of the device. Setting to 2 (Never send) means the "Block at First Sight" feature will not function. - - 1. Click **OK**. - -1. In the **Group Policy Management Editor**, expand the tree to **Windows components > Windows Defender > Real-time Protection**: - - 1. Double-click the **Scan all downloaded files and attachments** setting and ensure the option is set to **Enabled**. Click **OK**. - - 1. Double-click the **Turn off real-time protection** setting and ensure the option is set to **Disabled**. Click **OK**. - -If you had to change any of the settings, you should re-deploy the Group Policy Object across your network to ensure all endpoints are covered. - - -### Confirm Block at First Sight is enabled with Windows Settings - -> [!NOTE] -> If the pre-requisite settings are configured and deployed using Group Policy, the settings described in this section will be greyed-out and unavailable for use on individual endpoints. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings. - -You can confirm that Block at First Sight is enabled in Windows Settings. The feature is automatically enabled, as long as **Cloud-based protection** and **Automatic sample submission** are both turned on. - -**Confirm Block at First Sight is enabled on individual clients** - -1. Open Windows Defender settings: - - a. Open the Windows Defender app and click **Settings**. - - b. On the main Windows Settings page, click **Update & Security** and then **Windows Defender**. - -2. Confirm that **Cloud-based Protection** and **Automatic sample submission** are switched to **On**. - -## Disable Block at First Sight - -> [!WARNING] -> Disabling the Block at First Sight feature will lower the protection state of the endpoint and your network. - -> [!NOTE] -> You cannot disable Block at First Sight with System Center Configuration Manager - -You may choose to disable the Block at First Sight feature if you want to retain the pre-requisite settings without using Block at First Sight protection. You might wish to do this if you are experiencing latency issues or you want to test the feature's impact on your network. - -**Disable Block at First Sight with Group Policy** - -1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. - -3. In the **Group Policy Management Editor** go to **Computer configuration**. - -4. Click **Policies** then **Administrative templates**. - -5. Expand the tree through **Windows components > Windows Defender > MAPS**. - -1. Double-click the **Configure the ‘Block at First Sight’ feature** setting and set the option to **Disabled**. - - > [!NOTE] - > Disabling the Block at First Sight feature will not disable or alter the pre-requisite group policies. - - -## Related topics - -- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) - - +This page has been redirected to *Configure the Block at First Sight feature*. \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-enhanced-notifications.md b/windows/keep-secure/windows-defender-enhanced-notifications.md index e70fede4fd..b63c67e65f 100644 --- a/windows/keep-secure/windows-defender-enhanced-notifications.md +++ b/windows/keep-secure/windows-defender-enhanced-notifications.md @@ -10,37 +10,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: iaanw +redirect_url: /configure-notifications-windows-defender-antivirus/ --- # Configure enhanced notifications for Windows Defender in Windows 10 -**Applies to:** - -- Windows 10, version 1607 - -In Windows 10, application notifications about malware detection and remediation by Windows Defender are more robust, consistent, and concise. - -Notifications will appear on endpoints when manually triggered and scheduled scans are completed and threats are detected. These notifications will also be seen in the **Notification Center**, and a summary of scans and threat detections will also appear at regular time intervals. - -You can enable and disable enhanced notifications in Windows Settings. - -## Disable notifications - -You can disable enhanced notifications on individual endpoints in Windows Settings. - -**Use Windows Settings to disable enhanced notifications on individual endpoints** - -1. Open the **Start** menu and click or type **Settings**. - -1. Click **Update & Security** and then **Windows Defender**. Scroll to the bottom of the settings page until you see the **Enhanced notifications** section. - -1. Toggle the setting between **On** and **Off**. - -![Windows Defender enhanced notifications](images/defender/enhanced-notifications.png) - - - - -## Related topics - -- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) +This page has been redirected to *Configure notifications*. \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-in-windows-10.md b/windows/keep-secure/windows-defender-in-windows-10.md index 58ecb02cde..4eb81e6c4e 100644 --- a/windows/keep-secure/windows-defender-in-windows-10.md +++ b/windows/keep-secure/windows-defender-in-windows-10.md @@ -8,72 +8,9 @@ ms.sitesec: library ms.pagetype: security localizationpriority: medium author: jasesso +redirect_url: /windows-defender-antivirus-in-windows-10/ --- # Windows Defender in Windows 10 -**Applies to** -- Windows 10 - -Windows Defender in Windows 10 is a built-in antimalware solution that provides security and antimalware management for desktops, portable computers, and servers. -This topic provides an overview of Windows Defender, including a list of system requirements and new features. - -For more important information about running Windows Defender on a server platform, see [Windows Defender Overview for Windows Server](https://technet.microsoft.com/windows-server-docs/security/windows-defender/windows-defender-overview-windows-server). - -Take advantage of Windows Defender by configuring settings and definitions using the following tools: -- Microsoft Active Directory *Group Policy* for settings -- Windows Server Update Services (WSUS) for definitions - -Windows Defender provides the most protection when cloud-based protection is enabled. Learn how to enable cloud-based protection in [Configure Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md). -> **Note:**  System Center 2012 R2 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, and Microsoft Intune can provide centralized management of Windows Defender, including: -- Settings management -- Definition update management -- Alerts and alert management -- Reports and report management - -When you enable endpoint protection for your clients, it will install an additional management layer on Windows Defender to manage the in-box Windows Defender agent. While the client user interface will still appear as Windows Defender, the management layer for Endpoint Protection will be listed in the **Add/Remove Programs** control panel, though it will appear as if the full product is installed. - - -### Compatibility with Windows Defender Advanced Threat Protection - -Windows Defender Advanced Threat Protection (ATP) is an additional service that helps enterprises to detect, investigate, and respond to advanced persistent threats on their network. - -See the [Windows Defender Advanced Threat Protection](windows-defender-advanced-threat-protection.md) topics for more information about the service. - -If you are enrolled in Windows Defender ATP, and you are not using Windows Defender as your real-time protection service on your endpoints, Windows Defender will automatically enter into a passive mode. - -In passive mode, Windows Defender will continue to run (using the *msmpeng.exe* process), and will continue to be updated, however there will be no Windows Defender user interface, scheduled scans won’t run, and Windows Defender will not provide real-time protection from malware. - -You can [configure updates for Windows Defender](configure-windows-defender-in-windows-10.md), however you can't move Windows Defender into the normal active mode if your endpoints have an up-to-date third-party product providing real-time protection from malware. - -If you uninstall the other product, and choose to use Windows Defender to provide protection to your endpoints, Windows Defender will automatically return to its normal active mode. - - -  -### Minimum system requirements - -Windows Defender has the same hardware requirements as Windows 10. For more information, see: -- [Minimum hardware requirements](https://msdn.microsoft.com/library/windows/hardware/dn915086.aspx) -- [Hardware component guidelines](https://msdn.microsoft.com/library/windows/hardware/dn915049.aspx) - -### New and changed functionality - -- **Improved detection for unwanted applications and emerging threats using cloud-based protection.** Use the Microsoft Active Protection Service to improve protection against unwanted applications and advanced persistent threats in your enterprise. -- **Windows 10 integration.** All Windows Defender in Windows 10 endpoints will show the Windows Defender user interface, even when the endpoint is managed. -- **Operating system, enterprise-level management, and bring your own device (BYOD) integration.** Windows 10 introduces a mobile device management (MDM) interface for devices running Windows 10. Administrators can use MDM-capable products, such as Intune, to manage Windows Defender on Windows 10 devices. - -For more information about what's new in Windows Defender in Windows 10, see [Windows Defender in Windows 10: System integration](https://www.microsoft.com/security/portal/enterprise/threatreports_august_2015.aspx) on the Microsoft Active Protection Service website. - -## In this section - -Topic | Description -:---|:--- -[Update and manage Windows Defender in Windows 10](get-started-with-windows-defender-for-windows-10.md)|Use Active Directory or Windows Server Update Services to manage and deploy updates to endpoints on your network. Configure and run special scans, including archive and email scans. -[Configure updates for Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md)|Configure definition updates and cloud-based protection with Active Directory and Windows Server Update Services. -[Windows Defender Offline in Windows 10](windows-defender-offline.md)|Manually run an offline scan directly from winthin Windows without having to download and create bootable media. -[Use PowerShell cmdlets for Windows Defender](use-powershell-cmdlets-windows-defender-for-windows-10.md)|Run scans and configure Windows Defender options with Windows PowerShell cmdlets in Windows 10. -[Enable the Block at First Sight feature in Windows 10](windows-defender-block-at-first-sight.md)|Use the Block at First Sight feature to leverage the Windows Defender cloud. -[Configure enhanced notifications for Windows Defender in Windows 10](windows-defender-enhanced-notifications.md)|Enable or disable enhanced notifications on endpoints running Windows Defender for greater details about threat detections and removal. -[Run a Windows Defender scan from the command line](run-cmd-scan-windows-defender-for-windows-10.md)|Use the command-line utility to run a Windows Defender scan. -[Detect and block Potentially Unwanted Applications with Windows Defender](enable-pua-windows-defender-for-windows-10.md)|Use the Potentially Unwanted Application (PUA) feature in Managed Windows Defender to identify and block unwanted software during download and install time. -[Troubleshoot Windows Defender in Windows 10](troubleshoot-windows-defender-in-windows-10.md)|Review event IDs in Windows Defender for Windows 10 and take the appropriate actions. +This page has been redirected to *Windows Defender Antivirus in Windows 10*. \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-offline.md b/windows/keep-secure/windows-defender-offline.md index a90a308ed7..c3e4825764 100644 --- a/windows/keep-secure/windows-defender-offline.md +++ b/windows/keep-secure/windows-defender-offline.md @@ -1,6 +1,6 @@ --- title: Windows Defender Offline in Windows 10 -description: You can use Windows Defender Offline straight from the Windows Defender client. You can also manage how it is deployed in your network. +description: You can use Windows Defender Offline straight from the Windows Defender Antivirus app. You can also manage how it is deployed in your network. keywords: scan, defender, offline search.product: eADQiWindows 10XVcnh ms.pagetype: security @@ -12,15 +12,26 @@ localizationpriority: medium author: iaanw --- -# Windows Defender Offline in Windows 10 +# Run and review the results of a Windows Defender Offline scan + **Applies to:** - Windows 10, version 1607 +**Audience** + +- Enterprise security administrators + +**Manageability available with** + +- Group Policy +- PowerShell cmdlets +- Windows Management Instruction (WMI) + Windows Defender Offline is an antimalware scanning tool that lets you boot and run a scan from a trusted environment. The scan runs from outside the normal Windows kernel so it can target malware that attempts to bypass the Windows shell, such as viruses and rootkits that infect or overwrite the master boot record (MBR). -In Windows 10, Windows Defender Offline can be run with one click directly from the Windows Defender client. In previous versions of Windows, a user had to install Windows Defender Offline to bootable media, restart the endpoint, and load the bootable media. +In Windows 10, Windows Defender Offline can be run with one click directly from the [Windows Defender Security Center app](windows-defender-security-center-antivirus.md). In previous versions of Windows, a user had to install Windows Defender Offline to bootable media, restart the endpoint, and load the bootable media. ## Pre-requisites and requirements @@ -39,16 +50,18 @@ To run Windows Defender Offline from the endpoint, the user must be logged in wi ## Windows Defender Offline updates -Windows Defender Offline uses the most up-to-date signature definitions available on the endpoint; it's updated whenever Windows Defender is updated with new signature definitions. Depending on your setup, this is usually though Microsoft Update or through the [Microsoft Malware Protection Center](https://www.microsoft.com/security/portal/definitions/adl.aspx). +Windows Defender Offline uses the most recent protection updates available on the endpoint; it's updated whenever Windows Defender Antivirus is updated. > [!NOTE] -> Before running an offline scan, you should attempt to update the definitions on the endpoint. You can either force an update via Group Policy or however you normally deploy updates to endpoints, or you can manually download and install the latest updates from the [Microsoft Malware Protection Center](https://www.microsoft.com/security/portal/definitions/adl.aspx). +> Before running an offline scan, you should attempt to update Windows Defender AV protection. You can either force an update with Group Policy or however you normally deploy updates to endpoints, or you can manually download and install the latest protection updates from the [Microsoft Malware Protection Center](https://www.microsoft.com/security/portal/definitions/adl.aspx). -For information on setting up Windows Defender updates, see the [Configure Windows Defender in Windows 10](configure-windows-defender-in-windows-10.md) topic. +See the [Manage Windows Defender Antivirus protection and definition updates](manage-protection-updates-windows-defender-antivirus.md) topic for more information. ## Usage scenarios -In Windows 10, version 1607, you can manually force an offline scan. Alternatively, if Windows Defender determines that Windows Defender Offline needs to run, it will prompt the user on the endpoint. The need to perform an offline scan will also be revealed in System Center Configuration Manager, if you're using it to manage your endpoints. +In Windows 10, version 1607, you can manually force an offline scan. Alternatively, if Windows Defender determines that Windows Defender Offline needs to run, it will prompt the user on the endpoint. + +The need to perform an offline scan will also be revealed in System Center Configuration Manager if you're using it to manage your endpoints. The prompt can occur via a notification, similar to the following: @@ -58,125 +71,76 @@ The user will also be notified within the Windows Defender client: ![Windows Defender showing the requirement to run Windows Defender Offline](images/defender/client.png) -In Configuration Manager, you can identify the status of endpoints by navigating to **Monitoring > Overview > Security > Endpoint Protection Status > System Center Endpoint Protection Status**. Windows Defender Offline scans are indicated under **Malware remediation status** as **Offline scan required**. +In Configuration Manager, you can identify the status of endpoints by navigating to **Monitoring > Overview > Security > Endpoint Protection Status > System Center Endpoint Protection Status**. + +Windows Defender Offline scans are indicated under **Malware remediation status** as **Offline scan required**. ![System Center Configuration Manager indicating a Windows Defender Offline scan is required](images/defender/sccm-wdo.png) -## Manage notifications +## Configure notifications -You can suppress Windows Defender Offline notifications with Group Policy. +Windows Defender Offline notifications are configured in the same policy setting as other Windows Defender AV notifications. -> [!NOTE] -> Changing these settings will affect *all* notifications from Windows Defender. Disabling notifications will mean the endpoint user will not see any messages about any threats detected, removed, or if additional steps are required. - -**Use Group Policy to suppress Windows Defender notifications:** - -1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**. - -3. In the **Group Policy Management Editor** go to **Computer configuration**. - -4. Click **Policies** then **Administrative templates**. - -5. Expand the tree to **Windows components > Windows Defender > Client Interface**. - -1. Double-click the **Suppress all notifications** setting and set the option to **Enabled**. Click **OK**. This will disable all notifications shown by the Windows Defender client. - -## Configure Windows Defender Offline settings - -You can use Windows Management Instrumentation to enable and disable certain features in Windows Defender Offline. For example, you can use `Set-MpPreference` to change the `UILockdown` setting to disable and enable notifications. - -For more information about using Windows Management Instrumentation to configure Windows Defender Offline, including configuration parameters and options, see the following topics: - -- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/windows/desktop/dn439477(v=vs.85).aspx) - -- [Windows Defender MSFT_MpPreference class](https://msdn.microsoft.com/en-us/library/windows/desktop/dn455323(v=vs.85).aspx) - -For more information about notifications in Windows Defender, see the [Configure enhanced notifications in Windows Defender](windows-defender-enhanced-notifications.md)] topic. +For more information about notifications in Windows Defender, see the [Configure the notifications that appear on endpoints](configure-notifications-windows-defender-antivirus.md) topic. ## Run a scan -Windows Defender Offline uses up-to-date threat definitions to scan the endpoint for malware that might be hidden. In Windows 10, version 1607, you can manually force an offline scan using Windows Update and Security settings. +> [!IMPORTANT] +> Before you use Windows Defender Offline, make sure you save any files and shut down running programs. The Windows Defender Offline scan takes about 15 minutes to run. It will restart the endpoint when the scan is complete. The scan is performed outside of the usual Windows operating environment. The user interface will appear different to a normal scan performed by Windows Defender. After the scan is completed, the endpoint will be restarted and Windows will load normally. -> [!NOTE] -> Before you use Windows Defender Offline, make sure you save any files and shut down running programs. The Windows Defender Offline scan takes about 15 minutes to run. It will restart the endpoint when the scan is complete. +You can run a Windows Defender Offline scan with the following: -You can set up a Windows Defender Offline scan with the following: - -- Windows Update and Security settings - -- Windows Defender - -- Windows Management Instrumentation - -- Windows PowerShell - -- Group Policy - -> [!NOTE] -> The scan is performed outside of the usual Windows operating environment. The user interface will appear different to a normal scan performed by Windows Defender. After the scan is completed, the endpoint will be restarted and Windows will load normally. - -**Run Windows Defender Offline from Windows Settings:** - -1. Open the **Start** menu and click or type **Settings**. - -1. Click **Update & Security** and then **Windows Defender**. Scroll to the bottom of the settings page until you see the **Windows Defender Offline** section. - -1. Click **Scan offline**. - - ![Windows Defender Offline setting](images/defender/settings-wdo.png) - -1. Follow the prompts to continue with the scan. You might be warned that you'll be signed out of Windows and that the endpoint will restart. - -**Run Windows Defender Offline from Windows Defender:** - -1. Open the **Start** menu, type **windows defender**, and press **Enter** to open the Windows Defender client. - -1. On the **Home** tab click **Download and Run**. - - ![Windows Defender home tab showing the Download and run button](images/defender/download-wdo.png) - -1. Follow the prompts to continue with the scan. You might be warned that you'll be signed out of Windows and that the endpoint will restart. +- PowerShell +- Windows Management Instrumentation (WMI) +- The Windows Defender Security Center app -**Use Windows Management Instrumentation to configure and run Windows Defender Offline:** -Use the `MSFT_MpWDOScan` class (part of the Windows Defender Windows Management Instrumentation provider) to run a Windows Defender Offline scan. - -The following Windows Management Instrumentation script snippet will immediately run a Windows Defender Offline scan, which will cause the endpoint to restart, run the offline scan, and then restart and boot into Windows. +**Use PowerShell cmdlets to run an offline scan:** + +Use the following cmdlets: + +```PowerShell +Start-MpWDOScan +``` + +See [Use PowerShell cmdlets to configure and run Windows Defender Antivirus](use-powershell-cmdlets-windows-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/en-us/library/dn433280.aspx) for more information on how to use PowerShell with Windows Defender Antivirus. + +**Use Windows Management Instruction (WMI) to run an offline scan:** + +Use the [**MSFT_MpWDOScan**](https://msdn.microsoft.com/en-us/library/dn455323(v=vs.85).aspx) class to run an offline scan. + +The following WMI script snippet will immediately run a Windows Defender Offline scan, which will cause the endpoint to restart, run the offline scan, and then restart and boot into Windows. ```WMI wmic /namespace:\\root\Microsoft\Windows\Defender path MSFT_MpWDOScan call Start ``` -For more information about using Windows Management Instrumentation to run a scan in Windows Defender, including configuration parameters and options, see the following topics: +See the following for more information: +- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx) -- [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/windows/desktop/dn439477(v=vs.85).aspx) -- [MSFT_MpWDOScan class article](https://msdn.microsoft.com/library/windows/desktop/mt622458(v=vs.85).aspx) +**Use the Windows Defender Security app to run an offline scan:** -**Run Windows Defender Offline using PowerShell:** +1. Open the Windows Defender Security Center by clicking the shield icon in the task bar or searching the start menu for **Defender**. -Use the PowerShell parameter `Start-MpWDOScan` to run a Windows Defender Offline scan. +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then the **Advanced scan** label: + + +3. Select **Windows Defender Offline scan** and click **Scan now**. + + +> [!NOTE] +> In Windows 10, version 1607, the offline scan could be run from under **Windows Settings** > **Update & security** > **Windows Defender** or from the Windows Defender client. -For more information on available cmdlets and optios, see the [Use PowerShell cmdlets to configure and run Windows Defender](use-powershell-cmdlets-windows-defender-for-windows-10.md) topic. ## Review scan results -Windows Defender Offline scan results will be listed in the main Windows Defender user interface after performing the scan. +Windows Defender Offline scan results will be listed in the [Scan history section of the Windows Defender Security Center app](windows-defender-security-center-antivirus.md#detection-history). -1. Open the **Start** menu, type **windows defender**, and press **Enter** to open the Windows Defender client. - -1. Go to the **History** tab. - -1. Select **All detected items**. - -1. Click **View details**. - -Any detected items will display. Items that are detected by Windows Defender Offline will be listed as **Offline** in the **Detection source**: - -![Windows Defender detection source showing as Offline](images/defender/detection-source.png) ## Related topics -- [Windows Defender in Windows 10](windows-defender-in-windows-10.md) \ No newline at end of file +- [Customize, initiate, and review the results of scans and remediation](customize-run-review-remediate-scans-windows-defender-antivirus.md) +- [Windows Defender Antivirus](windows-defender-antivirus-in-windows-10.md) \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-security-center-antivirus.md b/windows/keep-secure/windows-defender-security-center-antivirus.md new file mode 100644 index 0000000000..3eba103bd0 --- /dev/null +++ b/windows/keep-secure/windows-defender-security-center-antivirus.md @@ -0,0 +1,145 @@ +--- +title: Windows Defender Antivirus in the Windows Defender Security Center app +description: Windows Defender AV is now included in the Windows Defender Security Center app. +keywords: wdav, antivirus, firewall, security, windows +search.product: eADQiWindows 10XVcnh +ms.pagetype: security +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: security +localizationpriority: medium +author: iaanw +--- + + + + + +# Windows Defender Antivirus in the Windows Defender Security Center app + +**Applies to** + +- Windows 10, version 1703 + +**Audience** + +- End-users + +**Manageability available with** + +- Windows Defender Security Center app + + +In Windows 10, version 1703 (also known as the Creators Update), the Windows Defender app is now part of the Windows Defender Security Center. + +Settings that were previously part of the Windows Defender client and main Windows Settings have been combined and moved to the new app, which is installed by default as part of Windows 10, version 1703. + +The app also includes the settings and status of: + +- The PC (as "device health") +- Windows Firewall +- Windows Defender SmartScreen Filter +- Parental and Family Controls + +**Review virus and threat protection settings in the Windows Defender Security Center app:** + +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +![Screenshot of the Virus & threat protection settings label in the Windows Defender Security Center](images/defender/wdav-protection-settings-wdsc.png) + +## Comparison of settings and functions of the old app and the new app + +All of the previous functions and settings from the Windows Defender app (in versions of Windows 10 before version 1703) are now found in the new Windows Defender Security app. Settings that were previously located in Windows Settings under **Update & security** > **Windows Defender** are also now in the new app. + +The following diagrams compare the location of settings and functions between the old and new apps: + +![Version of Windows Defender in Windows 10 before version 1703](images/defender/wdav-windows-defender-app-old.png) + +![Windows Defender Antivirus in Windows 10, version 1703 and later](images/defender/wdav-wdsc.png) + +Item | Windows 10, before version 1703 | Windows 10, version 1703 | Description +---|---|---|--- +1 | **Update** tab | **Protection updates** | Update the protection ("definition updates") +2 | **History** tab | **Scan history** | Review threats that were quarantined, removed, or allowed +3 | **Settings** (links to **Windows Settings**) | **Virus & threat protection settings** | Enable various features, including Real-time protection, Cloud-delivered protection, Advanced notifications, and Automatic ample submission +4 | **Scan options** | **Advanced scan** | Run a full scan, custom scan, or a Windows Defender Offline scan +5 | Run a scan (based on the option chosen under **Scan options** | **Quick scan** | In Windows 10, version 1703 you can run custom and full scans under the **Advanced scan** option + + +## Common tasks + +This section describes how to perform some of the most common tasks when reviewing or interacting with the threat protection provided by Windows Defender Antivirus in the new Windows Defender Security app. + +> [!NOTE] +> If these settings are configured and deployed using Group Policy, the settings described in this section will be greyed-out and unavailable for use on individual endpoints. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings. The [Configure end-user interaction with Windows Defender Antivirus](configure-end-user-interaction-windows-defender-antivirus.md) topic describes how local policy override settings can be configured. + +**Run a scan with the Windows Defender Security Center app** +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +3. Click **Quick scan**. + +4. Click **Advanced scan** to specify different types of scans, such as a full scan. + + +**Download protection updates in the Windows Defender Security Center app** +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +3. Click **Protection updates**. + +4. Click **Check for updates** to download new protection updates (if there are any). + + + +**Ensure Windows Defender Antivirus is enabled in the Windows Defender Security Center app** + +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +3. Click **Virus & threat protection settings**. + +4. Toggle the switches to **On** for the following settings: + 1. **Real-time protection** + 2. **Cloud-based protection** + 3. **Automatic sample submission** + + + + + +**Add exclusions for Windows Defender Antivirus in the Windows Defender Security Center app** +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +3. Click **Virus & threat protection settings**. + +4. Under the **Exclusions** setting, click **Add or remove exclusions**. + +5. Click the plus icon to choose the type and set the options for each exclusion. + + +**Review threat detection history in the Windows Defender Security Center app** +1. Open the Windows Defender Security Center app by clicking the shield icon in the task bar or searching the start menu for **Defender**. + +2. Click the **Virus & threat protection** tile (or the shield icon on the left menu bar). + +3. Click **Scan history**. + +4. Click **See full history** under each of the categories (**Current threats**, **Quarantined threats**, **Allowed threats**). + + + + +## Related topics + +- [Windows Defender Antivirus](windows-defender-antivirus-in-windows-10.md) + + diff --git a/windows/keep-secure/windows-defender-smartscreen-available-settings.md b/windows/keep-secure/windows-defender-smartscreen-available-settings.md new file mode 100644 index 0000000000..936751e349 --- /dev/null +++ b/windows/keep-secure/windows-defender-smartscreen-available-settings.md @@ -0,0 +1,215 @@ +--- +title: Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings (Windows 10) +description: A list of all available setttings for Windows Defender SmartScreen using Group Policy and mobile device management (MDM) settings. +keywords: SmartScreen Filter, Windows SmartScreen +ms.prod: w10 +ms.mktglfcycl: explore +ms.sitesec: library +ms.pagetype: security +author: eross-msft +localizationpriority: high +--- + +# Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings +**Applies to:** + +- Windows 10 +- Windows 10 Mobile + +Windows Defender SmartScreen works with Group Policy and mobile device management (MDM) settings to help you manage your organization's computer settings. Based on how you set up Windows Defender SmartScreen, you can show employees a warning page and let them continue to the site, or you can block the site entirely. + +## Group Policy settings +SmartScreen uses registry-based Administrative Template policy settings. For more info about Group Policy, see the [Group Policy TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=214514). This site provides links to the latest technical documentation, videos, and downloads for Group Policy. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingSupported onDescription
Windows 10, version 1703:
Administrative Templates\Windows Components\Windows Defender SmartScreen\Explorer\Configure Windows Defender SmartScreen

Windows 10, Version 1607 and earlier:
Administrative Templates\Windows Components\File Explorer\Configure Windows SmartScreen

At least Windows Server 2012, Windows 8 or Windows RTThis policy setting turns on Windows Defender SmartScreen.

If you enable this setting, it turns on Windows Defender SmartScreen and your employees are unable to turn it off. Additionally, when enabling this feature, you must also pick whether SmartScreen should Warn your employees or Warn and prevent bypassing the message (effectively blocking the employee from the site).

If you disable this setting, it turns off Windows Defender SmartScreen and your employees are unable to turn it on.

If you don't configure this setting, your employees can decide whether to use Windows Defender SmartScreen.

Administrative Templates\Windows Components\Windows Defender SmartScreen\Explorer\Configure App Install ControlWindows 10, version 1703This setting helps protect PCs by allowing users to install apps only from the Windows Store. SmartScreen must be enabled for this feature to work properly.

If you enable this setting, your employees can only install apps from the Windows Store.

If you disable this setting, your employees can install apps from anywhere, including as a download from the Internet.

If you don't configure this setting, your employees can choose whether they can install from anywhere or only from Windows Store.

Windows 10, version 1703:
Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Configure Windows Defender SmartScreen

Windows 10, Version 1607 and earlier:
Administrative Templates\Windows Components\Microsoft Edge\Configure Windows SmartScreen

Microsoft Edge on Windows 10 or laterThis policy setting turns on Windows Defender SmartScreen.

If you enable this setting, it turns on Windows Defender SmartScreen and your employees are unable to turn it off.

If you disable this setting, it turns off Windows Defender SmartScreen and your employees are unable to turn it on.

If you don't configure this setting, your employees can decide whether to use Windows Defender SmartScreen.

Windows 10, version 1703:
Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for files

Windows 10, Version 1511 and 1607:
Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows SmartScreen prompts for files

Microsoft Edge on Windows 10, version 1511 or laterThis policy setting stops employees from bypassing the Windows Defender SmartScreen warnings about potentially malicious files.

If you enable this setting, it stops employees from bypassing the warning, stopping the file download.

If you disable or don't configure this setting, your employees can bypass the warnings and continue to download potentially malicious files.

Windows 10, version 1703:
Administrative Templates\Windows Components\Windows Defender SmartScreen\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for sites

Windows 10, Version 1511 and 1607:
Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows SmartScreen prompts for sites

Microsoft Edge on Windows 10, version 1511 or laterThis policy setting stops employees from bypassing the Windows Defender SmartScreen warnings about potentially malicious sites.

If you enable this setting, it stops employees from bypassing the warning, stopping them from going to the site.

If you disable or don't configure this setting, your employees can bypass the warnings and continue to visit a potentially malicious site.

Administrative Templates\Windows Components\Internet Explorer\Prevent managing SmartScreen FilterInternet Explorer 9 or laterThis policy setting prevents the employee from managing SmartScreen Filter.

If you enable this policy setting, the employee isn't prompted to turn on SmartScreen Filter. All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the employee.

If you disable or don't configure this policy setting, the employee is prompted to decide whether to turn on SmartScreen Filter during the first-run experience.

Administrative Templates\Windows Components\Internet Explorer\Prevent bypassing SmartScreen Filter warningsInternet Explorer 8 or laterThis policy setting determines whether an employee can bypass warnings from SmartScreen Filter.

If you enable this policy setting, SmartScreen Filter warnings block the employee.

If you disable or don't configure this policy setting, the employee can bypass SmartScreen Filter warnings.

Administrative Templates\Windows Components\Internet Explorer\Prevent bypassing SmartScreen Filter warnings about files that are not commonly downloaded from the InternetInternet Explorer 9 or laterThis policy setting determines whether the employee can bypass warnings from SmartScreen Filter. SmartScreen Filter warns the employee about executable files that Internet Explorer users do not commonly download from the Internet.

If you enable this policy setting, SmartScreen Filter warnings block the employee.

If you disable or don't configure this policy setting, the employee can bypass SmartScreen Filter warnings.

+ +## MDM settings +If you manage your policies using Microsoft Intune, you'll want to use these MDM policy settings. All settings support both desktop computers (running Windows 10 Pro or Windows 10 Enterprise, enrolled with Microsoft Intune) and Windows 10 Mobile devices. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingSupported versionsDetails
AllowSmartScreenWindows 10 +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/Browser/AllowSmartScreen
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Turns off Windows Defender SmartScreen.
      • +
    • 1. Turns on Windows Defender SmartScreen.
+
EnableAppInstallControlWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/SmartScreen/EnableAppInstallControl
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Turns off Application Installation Control, allowing users to download and install files from anywhere on the web.
      • +
    • 1. Turns on Application Installation Control, allowing users to install apps from the Windows Store only.
+
EnableSmartScreenInShellWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/SmartScreen/EnableSmartScreenInShell
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Turns off SmartScreen in Windows.
      • +
    • 1. Turns on SmartScreen in Windows.
+
PreventOverrideForFilesInShellWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/SmartScreen/PreventOverrideForFilesInShell
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Employees can ignore SmartScreen warnings and run malicious files.
      • +
    • 1. Employees can't ignore SmartScreen warnings and run malicious files.
+
PreventSmartScreenPromptOverrideWindows 10, Version 1511 and later +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/Browser/PreventSmartscreenPromptOverride
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Employees can ignore SmartScreen warnings.
      • +
    • 1. Employees can't ignore SmartScreen warnings.
+
PreventSmartScreenPromptOverrideForFilesWindows 10, Version 1511 and later +
    +
  • URI full path. ./Vendor/MSFT/Policy/Config/Browser/PreventSmartScreenPromptOverrideForFiles
    • +
  • Data type. Integer
    • +
  • Allowed values:
      +
    • 0 . Employees can ignore SmartScreen warnings for files.
      • +
    • 1. Employees can't ignore SmartScreen warnings for files.
+
+ +## Recommended Group Policy and MDM settings for your organization +By default, Windows Defender SmartScreen lets employees bypass warnings. Unfortunately, this can let employees continue to an unsafe site or to continue to download an unsafe file, even after being warned. Because of this possibility, we strongly recommend that you set up Windows Defender SmartScreen to block high-risk interactions instead of providing just a warning. + +To better help you protect your organization, we recommend turning on and using these specific Windows Defender SmartScreen Group Policy and MDM settings. + + + + + + + + + + + + + + + + + + + + + +
Group Policy settingRecommendation
Administrative Templates\Windows Components\Microsoft Edge\Configure Windows Defender SmartScreenEnable. Turns on Windows Defender SmartScreen.
Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for sitesEnable. Stops employees from ignoring warning messages and continuing to a potentially malicious website.
Administrative Templates\Windows Components\Microsoft Edge\Prevent bypassing Windows Defender SmartScreen prompts for filesEnable. Stops employees from ingnoring warning messages and continuing to download potentially malicious files.
Administrative Templates\Windows Components\File Explorer\Configure Windows Defender SmartScreenEnable with the Warn and prevent bypass option. Stops employees from ignoring warning messages about malicious files downloaded from the Internet.
+

+ + + + + + + + + + + + + + + + + + + + + + + + + +
MDM settingRecommendation
Browser/AllowSmartScreen1. Turns on Windows Defender SmartScreen.
Browser/PreventSmartScreenPromptOverride1. Stops employees from ignoring warning messages and continuing to a potentially malicious website.
Browser/PreventSmartScreenPromptOverrideForFiles1. Stops employees from ingnoring warning messages and continuing to download potentially malicious files.
SmartScreen/EnableSmartScreenInShell1. Turns on Windows Defender SmartScreen in Windows.

Requires at least Windows 10, version 1703.

SmartScreen/PreventOverrideForFilesInShell1. Stops employees from ignoring warning messages about malicious files downloaded from the Internet.

Requires at least Windows 10, version 1703.

+ +## Related topics +- [Keep Windows 10 secure](https://technet.microsoft.com/itpro/windows/keep-secure/index) + +- [Security technologies in Windows 10](https://technet.microsoft.com/itpro/windows/keep-secure/security-technologies) + +- [Available Group Policy and Mobile Data Management (MDM) settings for Microsoft Edge](https://technet.microsoft.com/itpro/microsoft-edge/available-policies) + +>[!NOTE] +>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md). \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-smartscreen-overview.md b/windows/keep-secure/windows-defender-smartscreen-overview.md new file mode 100644 index 0000000000..4df34ae566 --- /dev/null +++ b/windows/keep-secure/windows-defender-smartscreen-overview.md @@ -0,0 +1,66 @@ +--- +title: Windows Defender SmartScreen overview (Windows 10) +description: Conceptual info about Windows Defender SmartScreen. +keywords: SmartScreen Filter, Windows SmartScreen +ms.prod: w10 +ms.mktglfcycl: explore +ms.sitesec: library +ms.pagetype: security +author: eross-msft +localizationpriority: high +--- + +# Windows Defender SmartScreen +**Applies to:** + +- Windows 10 +- Windows 10 Mobile + +Windows Defender SmartScreen helps to protect your employees if they try to visit sites previously reported as phishing or malware websites, or if an employee tries to download potentially malicious files. + +>[!NOTE] +>SmartScreen completely blocks apps from the Internet from running on Windows 10 Mobile. + +**SmartScreen determines whether a site is potentially malicious by:** + +- Analyzing visited webpages looking for indications of suspicious behavior. If it finds suspicious pages, SmartScreen shows a warning page, advising caution. + +- Checking the visited sites against a dynamic list of reported phishing sites and malicious software sites. If it finds a match, SmartScreen shows a warning to let the user know that the site might be malicious. + +**SmartScreen determines whether a downloaded app or app installer is potentially malicious by:** + +- Checking downloaded files against a list of reported malicious software sites and programs known to be unsafe. If it finds a match, SmartScreen shows a warning to let the user know that the site might be malicious. + +- Checking downloaded files against a list of files that are well known and downloaded by many Windows users. If the file isn't on that list, SmartScreen shows a warning, advising caution. + + >[!NOTE] + >Before Windows 10, version 1703 this feature was called the SmartScreen Filter when used within the browser and Windows SmartScreen when used outside of the browser. + +## Benefits of Windows Defender SmartScreen +Windows Defender SmartScreen helps to provide an early warning system against websites that might engage in phishing attacks or attempt to distribute malware through a socially-engineered attack. The primary benefits are: + +- **Anti-phishing and anti-malware support.** SmartScreen helps to protect your employees from sites that are reported to host phishing attacks or attempt to distribute malicious software. It can also help protect against deceptive advertisements, scam sites, and drive-by attacks. Drive-by attacks are web-based attacks that tend to start on a trusted site, targeting security vulnerabilities in commonly-used software. Because drive-by attacks can happen even if the user does not click or download anything on the page, the danger often goes unnoticed. For more info about drive-by attacks, see [Evolving Microsoft SmartScreen to protect you from drive-by attacks](https://blogs.windows.com/msedgedev/2015/12/16/SmartScreen-drive-by-improvements/#3B7Bb8bzeAPq8hXE.97) + +- **Reputation-based URL and app protection.** SmartScreen evaluates a website's URLs to determine if they're known to distribute or host unsafe content. It also provides reputation checks for apps, checking downloaded programs and the digital signature used to sign a file. If a URL, a file, an app, or a certificate has an established reputation, your employees won't see any warnings. If however there's no reputation, the item is marked as a higher risk and presents a warning to the employee. + +- **Operating system integration.** SmartScreen is integrated into the Windows 10 operating system, meaning that it checks any files an app (including 3rd-party browsers and email clients) attempts to download and run. + +- **Improved heuristics and telemetry.** SmartScreen is constantly learning and endeavoring to stay up-to-date, so it can help to protect you against potentially malicious sites and files. + +- **Management through Group Policy and Microsoft Intune.** SmartScreen supports using both Group Policy and Microsoft Intune settings. For more info about all available settings, see [Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](windows-defender-smartscreen-available-settings.md). + +## Viewing Windows Defender SmartScreen anti-phishing events +When Windows Defender SmartScreen warns or blocks an employee from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/en-us/scriptcenter/dd565657(v=msdn.10).aspx). + +## Related topics +- [SmartScreen Frequently Asked Questions (FAQ)](https://support.microsoft.com/en-us/products/windows?os=windows-10) + +- [How to recognize phishing email messages, links, or phone calls](https://www.microsoft.com/en-us/safety/online-privacy/phishing-symptoms.aspx) + +- [Keep Windows 10 secure](https://technet.microsoft.com/itpro/windows/keep-secure/index) + +- [Security technologies in Windows 10](https://technet.microsoft.com/itpro/windows/keep-secure/security-technologies) + + +>[!NOTE] +>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md). \ No newline at end of file diff --git a/windows/keep-secure/windows-defender-smartscreen-set-individual-device.md b/windows/keep-secure/windows-defender-smartscreen-set-individual-device.md new file mode 100644 index 0000000000..482d88a367 --- /dev/null +++ b/windows/keep-secure/windows-defender-smartscreen-set-individual-device.md @@ -0,0 +1,80 @@ +--- +title: Set up and use Windows Defender SmartScreen on individual devices (Windows 10) +description: Steps about what happens when an employee tries to run an app, how employees can report websites as safe or unsafe, and how employees can use the Windows Defender Security Center to set Windows Defender SmartScreen for individual devices. +keywords: SmartScreen Filter, Windows SmartScreen +ms.prod: w10 +ms.mktglfcycl: explore +ms.sitesec: library +ms.pagetype: security +author: eross-msft +localizationpriority: high +--- + +# Set up and use Windows Defender SmartScreen on individual devices + +**Applies to:** +- Windows 10, version 1703 +- Windows 10 Mobile + +Windows Defender SmartScreen helps to protect your employees if they try to visit sites previously reported as phishing or malware websites, or if an employee tries to download potentially malicious files. + +## How employees can use Windows Defender Security Center to set up Windows Defender SmartScreen +Starting with Windows 10, version 1703 your employees can use Windows Defender Security Center to set up Windows Defender SmartScreen for an individual device; unless you've used Group Policy or Microsoft Intune to prevent it. + +>[!NOTE] +>If any of the following settings are managed through Group Policy or mobile device management (MDM) settings, it appears as unavailable to the employee. + +**To use Windows Defender Security Center to set up Windows Defender SmartScreen on a device** +1. Open the Windows Defender Security Center app, and then click **App & browser control**. + + ![Windows Defender Security Center](images/windows-defender-security-center.png) + +2. In the **App & browser control** screen, choose from the following options: + + - In the **Check apps and files** area: + + - **Block.** Stops employees from downloading and running unrecognized apps and files from the web. + + - **Warn.** Warns employees that the apps and files being downloaded from the web are potentially dangerous, but allows the action to continue. + + - **Off.** Turns off SmartScreen, so an employee isn't alerted or stopped from downloading potentially malicious apps and files. + + - In the **SmartScreen for Microsoft Edge** area: + + - **Block.** Stops employees from downloading and running unrecognized apps and files from the web, while using Microsoft Edge. + + - **Warn.** Warns employees that sites and downloads are potentially dangerous, but allows the action to continue while running in Microsoft Edge. + + - **Off.** Turns off SmartScreen, so an employee isn't alerted or stopped from downloading potentially malicious apps and files. + + - In the **SmartScreen from Windows Store apps** area: + + - **Block** or **Warn.** Warns employees that the sites and downloads used by Windows Store apps are potentially dangerous, but allows the action to continue. + + - **Off.** Turns off SmartScreen, so an employee isn't alerted or stopped from visiting sites or from downloading potentially malicious apps and files. + + ![Windows Defender Security Center, SmartScreen controls](images/windows-defender-smartscreen-control.png) + +## How SmartScreen works when an employee tries to run an app +Windows Defender SmartScreen checks the reputation of any web-based app the first time it's run from the Internet, checking digital signatures and other factors against a Microsoft-maintained service. If an app has no reputation or is known to be malicious, SmartScreen can warn the employee or block the app from running entirely, depending on how you've configured the feature to run in your organization. + +By default, your employees can bypass SmartScreen protection, letting them run legitimate apps after accepting a warning message prompt. You can also use Group Policy or Microsoft Intune to block employees from using unrecognized apps, or to entirely turn off Windows Defender SmartScreen (not recommended). + +## How employees can report websites as safe or unsafe +You can configure Windows Defender SmartScreen to warn employees from going to a potentially dangerous site. Employees can then choose to report a website as safe from the warning message or as unsafe from within Microsoft Edge and Internet Explorer 11. + +**To report a website as safe from the warning message** +- On the warning screen for the site, click **More Information**, and then click **Report that this site does not contain threats**. The site info is sent to the Microsoft feedback site, which provides further instructions. + +**To report a website as unsafe from Microsoft Edge** +- If a site seems potentially dangerous, employees can report it to Microsoft by clicking **More (...)**, clicking **Send feedback**, and then clicking **Report unsafe site**. + +**To report a website as unsafe from Internet Explorer 11** +- If a site seems potentially dangerous, employees can report it to Microsoft by clicking on the **Tools** menu, clicking **Windows Defender SmartScreen**, and then clicking **Report unsafe website**. + +## Related topics +- [Keep Windows 10 secure](https://technet.microsoft.com/itpro/windows/keep-secure/index) +- [Security technologies in Windows 10](https://technet.microsoft.com/itpro/windows/keep-secure/security-technologies) + +>[!NOTE] +>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to TechNet content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md). \ No newline at end of file diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 530731086d..148d75201f 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -39,8 +39,9 @@ ## [Reset a Windows 10 Mobile device](reset-a-windows-10-mobile-device.md) ## [Application Virtualization (App-V) for Windows](appv-for-windows.md) ### [Getting Started with App-V](appv-getting-started.md) -#### [What's new in App-V](appv-about-appv.md) -##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md) +#### [What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md) +##### [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows.md) +##### [Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md) #### [Evaluating App-V](appv-evaluating-appv.md) #### [High Level Architecture for App-V](appv-high-level-architecture.md) ### [Planning for App-V](appv-planning-for-appv.md) @@ -77,7 +78,10 @@ #### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md) ### [Operations for App-V](appv-operations.md) #### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) -##### [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +##### [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +##### [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) +##### [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) +##### [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) ##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) ##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md) @@ -108,6 +112,7 @@ ##### [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) ##### [How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md) #### [Using the App-V Client Management Console](appv-using-the-client-management-console.md) +##### [Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) #### [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) ##### [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md) #### [Maintaining App-V](appv-maintaining-appv.md) @@ -126,6 +131,7 @@ ##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md) ### [Troubleshooting App-V](appv-troubleshooting.md) ### [Technical Reference for App-V](appv-technical-reference.md) +#### [Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md) #### [Performance Guidance for Application Virtualization](appv-performance-guidance.md) #### [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md) #### [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md) diff --git a/windows/manage/appv-about-appv.md b/windows/manage/appv-about-appv.md index ef43aeed3d..9fc61c9b7d 100644 --- a/windows/manage/appv-about-appv.md +++ b/windows/manage/appv-about-appv.md @@ -1,26 +1,43 @@ --- -title: What's new in App-V for Windows 10 (Windows 10) -description: Information about what's new in App-V for Windows 10. -author: MaggiePucciEvans +title: What's new in App-V for Windows 10, version 1703 and earlier (Windows 10) +description: Information about what's new in App-V for Windows 10, version 1703 and earlier. +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 --- - -# What's new in App-V +# What's new in App-V for Windows 10, version 1703 and earlier **Applies to** -- Windows 10, version 1607 +- Windows 10, version 1703 and earlier -Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally. +Microsoft Application Virtualization (App-V) helps organizations to deliver Win32 applications to employees as virtual apps. Virtual apps are installed on centrally managed servers and delivered to employees as a service – in real time and on an as-needed basis. Employees start virtual apps from familiar access points and interact with them as if they were installed locally. -Application Virtualization (App-V) for Windows 10, version 1607, includes these new features and capabilities compared to App-V 5.1. See [App-V release notes](appv-release-notes-for-appv-for-windows.md) for more information about the App-V for Windows 10, version 1607 release. +## What's new in App-V Windows 10, version 1703 +The following are new features in App-V for Windows 10, version 1703. +### Auto sequence and update your App-V packages singly or as a batch +Previous versions of the App-V Sequencer have required you to manually sequence and update your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. + +Using the automatic sequencer to package your apps provides: +- Automatic virtual machine (VM) provisioning of the sequencing environment. For info about this, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md). + +- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). + +- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). + +### Updates to the App-V project template +Starting with Windows 10, version 1703, you can save an App-V project template (.appvt) file as part of a sequenced App-V package, so it's automatically loaded every time the package opens for editing or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. For more info about this, see [Create and apply an App-V project template to a sequenced App-V package](appv-create-and-use-a-project-template.md) + +### Automatically cleanup unpublished App-V packages from the App-V client +Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart. For more info about this, see [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + +## What's new in App-V in Windows 10, version 1607 +The following are new features in App-V for Windows 10, version 1607. ## App-V is now a feature in Windows 10 - With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack. For information about earlier versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index). @@ -29,26 +46,25 @@ The changes in App-V for Windows 10, version 1607 impact already existing implem - The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client. -- The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. +- The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. ->**Note**
If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. + >[!NOTE] + >If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](appv-migrating-to-appv-from-a-previous-version.md). ->**Important** -You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607. - +>[!IMPORTANT] +>You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607.   ## Support for System Center - App-V supports System Center 2016 and System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager. +## Related topics +- [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows.md) + +- [Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md) ## Have a suggestion for App-V? - Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). -## Related topics - -[Release Notes for App-V](appv-release-notes-for-appv-for-windows.md) diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md new file mode 100644 index 0000000000..2722febd18 --- /dev/null +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -0,0 +1,173 @@ +--- +title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer). +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + +# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. + +In Windows 10, version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This is applicable to all of the sequencing scenarios: + +- Using the New-BatchAppVSequencerPackages cmdlet + +- Using the App-V Sequencer interface + +- Using the new-AppVSequencerPackage cmdlet + +>[!NOTE] +>If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic. + +### Sequence multiple apps by using a PowerShell cmdlet +Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. + +**To create your ConfigFile for use by the PowerShell cmdlet** + +1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. + +2. Add the following required XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<InstallerOptions>.** The command-line options required for the app installation. + + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + + **Example:** + + ```XML + + + + Skype for Windows + D:\Install\New\SkypeforWindows + SkypeSetup.exe + /S + 20 + True + True + + + Power BI + D:\Install\New\MicrosoftPowerBI + PBIDesktop.msi + /S + 20 + True + True + + + + ``` +3. Save your completed file, using the name **ConfigFile**. + + +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing: + + ```ps1 + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath + ``` + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied. + + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. + +### Sequence multiple apps by using the App-V Sequencer interface +Sequencing multipe apps at the same time requires that you create a **ConfigFIle** to collect all of the info related to each round of sequencing. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. + +**To create your ConfigFile for use by the App-V Sequencer interface** + +1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. + +2. Add the following required XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + + **Example:** + + ```XML + + + + Skype for Windows + D:\Install\New\SkypeforWindows + SkypeSetup.exe + 20 + False + True + + + Power BI + D:\Install\New\MicrosoftPowerBI + PBIDesktop.msi + 20 + False + True + + + + ``` + + +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing: + + ```ps1 + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath + ``` + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied. + + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. + +### Review the log files +There are 3 types of log files that occur when you sequence multiple apps at the same time: + +- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the sequencing activities, such as "Copying installer to VM", "Scheduling sequencing task", and so on for each app. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem. + +- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps. + +- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters. + +### Related topics +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) + +- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) + +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + +**Have a suggestion for App-V?**

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md new file mode 100644 index 0000000000..3c9a7531bc --- /dev/null +++ b/windows/manage/appv-auto-batch-updating.md @@ -0,0 +1,177 @@ +--- +title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer). +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + +# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, you'll pass your previously created app package files to the App-V Sequencer cmdlet for updating. + +Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. + +>[!NOTE] +>If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic. + +### Update multiple apps by using a PowerShell cmdlet +Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. + +**To create your ConfigFile for use by the PowerShell cmdlet** + +1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. + +2. Add the following XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<InstallerOptions>.** The command-line options required for the app installation. + + - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. + + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + + **Example:** + ```XML + + + + Skype for Windows Update + D:\Install\Update\SkypeforWindows + SkypeSetup.exe + /S + C:\App-V_Package\Microsoft_Apps\skypeupdate.appv + 20 + True + True + + + Microsoft Power BI Update + D:\Install\Update\PowerBI + PBIDesktop.msi + /S + C:\App-V_Package\MS_Apps\powerbiupdate.appv + 20 + True + True + + + + ``` + +3. Save your completed file, using the name **ConfigFile**. + + +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating: + + ```ps1 + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath + ``` + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied. + + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. + +### Update multiple apps by using the App-V Sequencer interface +Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. + +**To create your ConfigFile for use by the App-V Sequencer interface** + +1. Determine the apps that need to be updated and then open a text editor, such as Notepad. + +2. Add the following XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. + + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + + **Example:** + + ```XML + + + + Skype for Windows Update + D:\Install\Update\SkypeforWindows + SkypeSetup.exe + /S + C:\App-V_Package\Microsoft_Apps\skypeupdate.appv + 20 + False + True + + + Microsoft Power BI Update + D:\Install\Update\PowerBI + PBIDesktop.msi + /S + C:\App-V_Package\MS_Apps\powerbiupdate.appv + 20 + False + True + + + + ``` + +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating: + + ```ps1 + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath + ``` + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied. + + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. + +### Review the log files +There are 3 types of log files that occur when you sequence multiple apps at the same time: + +- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the updating activities, such as "Copying installer to VM", "Scheduling updating task", and so on for each app. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem. + +- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps. + +- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters. + +### Related topics +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) + +- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) + +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) + + +**Have a suggestion for App-V?**

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-clean-unpublished-packages.md b/windows/manage/appv-auto-clean-unpublished-packages.md new file mode 100644 index 0000000000..234222854e --- /dev/null +++ b/windows/manage/appv-auto-clean-unpublished-packages.md @@ -0,0 +1,76 @@ +--- +title: Automatically cleanup unpublished packages on the App-V client (Windows 10) +description: How to automatically clean-up any unpublished packages on your App-V client devices. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically cleanup unpublished packages on the App-V client + +**Applies to** +- Windows 10, version 1703 + +Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart. + +## Cleanup by using PowerShell commands +Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. + +**To turn on the AutoCleanupEnabled option** + +1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality: + + ```ps1 + Set-AppvClientConfiguration -AutoCleanupEnabled 1 + ``` + + The command runs and you should see the following info on the PowerShell screen: + + + + + + + + + + + + + + + + +
NameValueSetbyGroupPolicy
AutoCleanupEnabled1False
+ +2. Run the following command to make sure the configuration is ready to automatically cleanup your packages. + + ```ps1 + Get-AppvClientConfiguration + ``` + You should see the **AutoCleanupEnabled** option turned on (shows a value of "1") in the configuration list. + +## Cleanup by using Group Policy settings +Using Group Policy, you can turn on the **Enable automatic cleanup of unused appv packages** setting to automatically cleanup your unpublished App-V packages from your App-V client devices. + +**To turn on the Enable automatic cleanup of unused appv packages setting** + +1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting. + +2. Click **Enabled**, and then click **OK**. + + After your Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting. + +### Related topics +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186) + +- [Using the App-V Client Management Console](appv-using-the-client-management-console.md) + + +**Have a suggestion for App-V?**

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-auto-provision-a-vm.md b/windows/manage/appv-auto-provision-a-vm.md new file mode 100644 index 0000000000..b4b1819a25 --- /dev/null +++ b/windows/manage/appv-auto-provision-a-vm.md @@ -0,0 +1,127 @@ +--- +title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) + +**Applies to** +- Windows 10, version 1703 + +Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Windows 10, version 1703 introduces two new PowerShell cmdlets, New-AppVSequencerVM and Connect-AppvSequencerVM, which automatically create your sequencing environment for you, including provisioning your virtual machine. + +## Automatic VM provisioning of the sequencing environment +You have 2 options for provisioning an VM for auto-sequencing: +- Using a Virtual Hard Disk (VHD) + + -OR- + +- Updating an existing VM + + >[!NOTE] + >We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings. + +### Provision a new VM by using a VHD file +Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. + +#### Create a VHD file +For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. + +**To create a VHD file by using the Convert-WindowsImage command-line tool** +1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands: + + ```ps1 + Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + ``` + Where *<path_to_iso_image>* is the full path to your ISO image. + + >[!IMPORTANT] + >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + +#### Provision your VM using your VHD file +After you have a VHD file, you must provision your VM for auto-sequencing. + +**To provision your VM using your VHD file** +1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). + +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" + ``` + +This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. + + +### Provision an existing VM for auto-sequencing +If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM. + +**To connect to your existing VM** +- Open PowerShell as an admin and run the following commands on your existing VM: + + - **Set the network category of your connection profile on the VM to _Private_:** + + ```ps1 + Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private + ``` + + - **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:** + + ```ps1 + Enable-NetFirewallRule -DisplayGroup “Remote Desktop” + Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” + ``` + + - **Set the VM to receive remote commands without a confirmation prompt:** + + ```ps1 + Enable-PSRemoting –Force + ``` + +**To provision an existing VM** +1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). + +2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters: + + ```ps1 + Connect-AppvSequencerVM -VMName "" -ADKPath "" + ``` + + Where *<name_of_vm>* is the name of the VM granted during its creation and shown in the Hyper-V Manager tool. + +This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start. + + +### Review the provisioning log files +The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are: + +- **New-AppVSequencerVM-<*time_stamp*>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on. + +- **Connect-AppvSequencerVM-report-<*time_stamp*>.txt**. Includes info about the connections made to the VM, showing whether there were any failures. + + +### Next steps +After provisioning your sequencing environment, you must sequence your apps, either as a group or individually. For more info about sequencing your apps, see [Manually sequence a single new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md), [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md), and [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md). + +After you sequence your packages, you can automatically cleanup any unpublished packages on the App-V client. For more info, see [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md). + +### Related topics +- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) + +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) + +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) + +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + + +**Have a suggestion for App-V?**

+Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/appv-available-mdm-settings.md b/windows/manage/appv-available-mdm-settings.md new file mode 100644 index 0000000000..dc5eb1a61a --- /dev/null +++ b/windows/manage/appv-available-mdm-settings.md @@ -0,0 +1,211 @@ +--- +title: Available Mobile Data Management (MDM) settings for App-V (Windows 10) +description: A list of the available MDM settings for App-V on Windows 10. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + +# Available Mobile Data Management (MDM) settings for App-V +With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Policy nameSupported versionsDetails
NameWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Name
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
VersionWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Version
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
PublisherWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Publisher
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
InstallLocationWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallLocation
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
InstallDateWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/InstallDate
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
UsersWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/Users
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVPackageIDWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageID
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVVersionIDWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVVersionID
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
AppVPackageUriWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<enterprise_id>/<package_family_name>/<package_full_name>/AppVPackageUri
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V packages.
    • +
+
LastErrorWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError
    • +
  • Data type. String
    • +
  • Value. Read-only data, provided by your App-V client.
    • +
+
LastErrorDescriptionWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. No errors returned during publish.
      • +
    • 1. Unpublish groups failed during publish.
      • +
    • 2. Publish no-group packages failed during publish.
      • +
    • 3. Publish group packages failed during publish.
      • +
    • 4. Unpublish packages failed during publish.
      • +
    • 5. New policy write failed during publish.
      • +
    • 6. Multiple non-fatal errors occurred during publish.
      • +
    +
    • +
+
SyncStatusDescriptionWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. App-V publishing is idle.
      • +
    • 1. App-V connection groups publish in progress.
      • +
    • 2. App-V packages (non-connection group) publish in progress.
      • +
    • 3. App-V packages (connection group) publish in progress.
      • +
    • 4. App-V packages unpublish in progress.
      • +
    +
    • +
+
SyncProgressWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress
    • +
  • Data type. String
    • +
  • Values. +
      +
    • 0. App-V Sync is idle.
      • +
    • 1. App-V Sync is initializing.
      • +
    • 2. App-V Sync is in progress.
      • +
    • 3. App-V Sync is complete.
      • +
    • 4. App-V Sync requires device reboot.
      • +
    +
    • +
+
PublishXMLWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML
    • +
  • Data type. String
    • +
  • Value. Custom value, entered by admin.
    • +
+
PolicyWindows 10, version 1703 +
    +
  • URI full path. ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/configurationid/Policy
    • +
  • Data type. String
    • +
  • Value. Custom value, entered by admin.
    • +
+
\ No newline at end of file diff --git a/windows/manage/appv-create-and-use-a-project-template.md b/windows/manage/appv-create-and-use-a-project-template.md index c6a0be63bb..1496e43518 100644 --- a/windows/manage/appv-create-and-use-a-project-template.md +++ b/windows/manage/appv-create-and-use-a-project-template.md @@ -1,55 +1,64 @@ --- -title: How to Create and Use a Project Template (Windows 10) -description: How to Create and Use a Project Template -author: MaggiePucciEvans +title: Create and apply an App-V project template to a sequenced App-V package (Windows 10) +description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package. +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 --- - -# How to Create and Use a Project Template +# Create and apply an App-V project template to a sequenced App-V package **Applies to** - Windows 10, version 1607 -You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. +You can use an App-V project template (.appvt) file to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic. -> **Note**  You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application. +>[!IMPORTANT] +>In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. -App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. -Use the following procedures to create and apply a new template. +## Create a project template +You must first create and save a project template, including a virtual app package with settings to be used by the template. **To create a project template** -1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. - > **Note**  If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure. + >[!NOTE] + >If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure. -2. To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**. +2. On the **File** menu, click **Open**, click **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V project template, and then click **Edit** to change any of the settings or info included in the file. -3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save. +3. On the **File** menu, click **Save As Template**, review the settings associated with the new template, click **OK**, name your new template, and then click **Save**. The new App-V project template is saved in the folder you specified. -**To apply a project template** +## Apply a project template +After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings. -> **Important**  Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported. +>[!IMPORTANT] +>Virtual app packages don't support using both a project template and a Package Accelerator together. -1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. -2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**. +2. On the **File** menu, click **New From Template**, browse to your newly created project template, and then click **Open**. -3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**. +3. Create your new virtual app package. The settings saved with your template are automatically applied. - Create the new virtual application package. The settings saved with the specified template will be applied to the new virtual application package that you are creating. +### Related topics +- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit) -## Have a suggestion for App-V? +- [How to install the App-V Sequencer](appv-install-the-sequencer.md) +- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) + +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) + +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) + +- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md) + +**Have a suggestion for App-V?**

Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -## Related topics - -[Operations for App-V](appv-operations.md) diff --git a/windows/manage/appv-creating-and-managing-virtualized-applications.md b/windows/manage/appv-creating-and-managing-virtualized-applications.md index 861034a883..b6aeefb413 100644 --- a/windows/manage/appv-creating-and-managing-virtualized-applications.md +++ b/windows/manage/appv-creating-and-managing-virtualized-applications.md @@ -68,7 +68,9 @@ The **Options** dialog box in the sequencer console contains the following tabs: App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call. -[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +- [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) ## App-V shell extension support @@ -166,11 +168,7 @@ You can use the sequencer to modify an existing package. The computer on which y [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md) ## Creating a project template - - -A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. - -App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template: +An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template: A template can specify and store multiple settings as follows: @@ -180,10 +178,15 @@ A template can specify and store multiple settings as follows: - **Exclusion Items.** Contains the Exclusion pattern list. +In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. + +>[!IMPORTANT] +>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. + [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md) -## Creating a package accelerator +## Creating a package accelerator **Note**   Package accelerators created using a previous version of App-V must be recreated using App-V. diff --git a/windows/manage/appv-for-windows.md b/windows/manage/appv-for-windows.md index 3938202a14..ed4d234781 100644 --- a/windows/manage/appv-for-windows.md +++ b/windows/manage/appv-for-windows.md @@ -42,10 +42,14 @@ The topics in this section provide information and step-by-step procedures to he [Operations for App-V](appv-operations.md) - [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) - [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md) - [Managing Connection Groups](appv-managing-connection-groups.md) - [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md) - [Using the App-V Client Management Console](appv-using-the-client-management-console.md) +- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) - [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) - [Maintaining App-V](appv-maintaining-appv.md) - [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) diff --git a/windows/manage/appv-modify-client-configuration-with-powershell.md b/windows/manage/appv-modify-client-configuration-with-powershell.md index ef256839b0..e3ca1981bf 100644 --- a/windows/manage/appv-modify-client-configuration-with-powershell.md +++ b/windows/manage/appv-modify-client-configuration-with-powershell.md @@ -16,15 +16,15 @@ ms.prod: w10 Use the following procedure to configure the App-V client configuration. -1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md). +1. To configure the client settings using Windows PowerShell, use the **Set-AppVClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md). -2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppvClientConfiguration** with any required parameters. For example: +2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppVClientConfiguration** with any required parameters. For example: - `$config = Get-AppvClientConfiguration` + `$config = Get-AppVClientConfiguration` - `Set-AppcClientConfiguration $config` + `Set-AppVClientConfiguration $config` - `Set-AppcClientConfiguration –Name1 MyConfig –Name2 “xyz”` + `Set-AppVClientConfiguration –Name1 MyConfig –Name2 “xyz”` ## Have a suggestion for App-V? diff --git a/windows/manage/appv-planning-for-using-appv-with-office.md b/windows/manage/appv-planning-for-using-appv-with-office.md index b18a9df8d0..a08cd69548 100644 --- a/windows/manage/appv-planning-for-using-appv-with-office.md +++ b/windows/manage/appv-planning-for-using-appv-with-office.md @@ -28,20 +28,16 @@ Use the following information to plan how to deploy Office by using Microsoft Ap You can use the App-V Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group. ->**Note**   -Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack. +>[!NOTE]  +>Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack. ## Supported versions of Microsoft Office - - - See [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click) for a list of supported Office products. ->**Note**  You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer. - ->**Note** -Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744) +>[!NOTE] +>You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer. +>Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744) ## Planning for using App-V with coexisting versions of Office @@ -87,8 +83,8 @@ The Office documentation provides extensive guidance on coexistence for Windows The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience. ->**Note**   -Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service. +>[!NOTE]  +>Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.   diff --git a/windows/manage/appv-release-notes-for-appv-for-windows-1703.md b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md new file mode 100644 index 0000000000..9e787d612c --- /dev/null +++ b/windows/manage/appv-release-notes-for-appv-for-windows-1703.md @@ -0,0 +1,121 @@ +--- +title: Release Notes for App-V for Windows 10, version 1703 (Windows 10) +description: A list of known issues and workarounds for App-V running on Windows 10, version 1703. +author: eross-msft +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +--- + + +# Release Notes for App-V for Windows 10, version 1703 + +**Applies to** +- Windows 10, version 1703 + +The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703. + + + + + + + + + + + + + + + + + + + + + + + + +
ProblemWorkaround
Unable to manually create a system-owned folder needed for the set-AppVClientConfiguration PowerShell cmdlet when using the PackageInstallationRoot, IntegrationRootUser, or IntegrationRootGlobal parameters.Don't create this file manually, instead let the Add-AppVClientPackage cmdlet auto-generate it.
Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.Make sure you have the complete App-V package or the MSI file from the original app.
Unable to modify the locale for auto-sequencing.Open the C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: es-ES.
Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the Settings > Apps> Default Apps area.The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <appv:Extensions> tag: +

+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>ftp</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>http</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+<appv:Extension Category="AppV.URLProtocol">
+	<appv:URLProtocol>
+		<appv:Name>https</appv:Name>
+		<appv:ApplicationURLProtocol>
+			<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
+			<appv:ShellCommands>
+				<appv:DefaultCommand>open</appv:DefaultCommand>
+				<appv:ShellCommand>
+					<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
+					<appv:Name>open</appv:Name>
+					<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
+					<appv:DdeExec>
+						<appv:DdeCommand />
+					</appv:DdeExec>
+				</appv:ShellCommand>
+			</appv:ShellCommands>
+		</appv:ApplicationURLProtocol>
+	</appv:URLProtocol>
+</appv:Extension>
+
+
+ + +## Related resources list +For information that can help with troubleshooting App-V for Windows 10, see: +- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx) + +- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/) + +- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference) + +- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv) + +## Have a suggestion for App-V? +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + +## Related topics +- [What's new in App-V for Windows 10](appv-about-appv.md) + +- [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows-1703.md) diff --git a/windows/manage/appv-release-notes-for-appv-for-windows.md b/windows/manage/appv-release-notes-for-appv-for-windows.md index 0982031249..290e4b19b9 100644 --- a/windows/manage/appv-release-notes-for-appv-for-windows.md +++ b/windows/manage/appv-release-notes-for-appv-for-windows.md @@ -1,23 +1,21 @@ --- -title: Release Notes for App-V (Windows 10) -description: Release Notes for App-V -author: MaggiePucciEvans +title: Release Notes for App-V for Windows 10, version 1607 (Windows 10) +description: A list of known issues and workarounds for App-V running on Windows 10, version 1607. +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 --- - # Release Notes for App-V for Windows 10, version 1607 **Applies to** - Windows 10, version 1607 -The following are known issues in Application Virtualization (App-V) for Windows 10, version 1607. +The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607. ## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client - MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail. **Workaround**: @@ -45,13 +43,11 @@ MSI packages that were generated using an App-V sequencer from previous versions where the path is to the new directory (**C:\MyMsiTools\ for this example**). ## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10 - An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10. This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier. **Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients. ## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server - If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration. **Workaround**: Do one of the following: @@ -95,7 +91,6 @@ On the Packages page of the Management Console, if you click **Add or Upgrade** 3. Paste the path into the **Add Package** dialog box input field ## Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred” - If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.” **Workaround**: Run this command on your SQL database: @@ -105,14 +100,11 @@ If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to A where “AppVManagement” is the name of the database. ## Users cannot open a package in a user-published connection group if you add or remove an optional package - In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group. **Workaround**: Have users log out and then log back in. ## Error message is erroneously displayed when the connection group is published only to the user - - When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.” **Workaround**: Do one of the following: @@ -132,40 +124,37 @@ When you run Repair-AppvClientConnectionGroup, the following error is displayed, 3. If the package is currently published, run **Repair-AppvClientPackage** on that package. ## Icons not displayed properly in Sequencer - Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32. **Workaround**: Only use icons that are 16x16 or 32x32. ## InsertVersionInfo.sql script no longer required for the Management Database - - The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3. The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). -**Important**   -**Step 1** is not required for versions of App-V later than App-V 5.0 SP3. - +>[!IMPORTANT]  +>**Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3. ## Microsoft Visual Studio 2012 not supported +App-V doesn't support Visual Studio 2012. - -App-V does not support Visual Studio 2012. - -**Workaround**: None +**Workaround**: Use a newer version of Microsoft Visual Studio. ## Application filename restrictions for App-V Sequencer - - The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated. **Workaround**: Use a different filename -## Have a suggestion for App-V? +## Related resources list +For information that can help with troubleshooting App-V for Windows 10, see: +- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx) +- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/) +- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference) +- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv) +## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). -## Related topics +Help us to improve -[What's new in App-V for Windows 10](appv-about-appv.md) diff --git a/windows/manage/appv-sequence-a-new-application.md b/windows/manage/appv-sequence-a-new-application.md index 24b1fb9ba1..7479636bf9 100644 --- a/windows/manage/appv-sequence-a-new-application.md +++ b/windows/manage/appv-sequence-a-new-application.md @@ -1,7 +1,7 @@ --- -title: How to Sequence a New Application with App-V (Windows 10) -description: How to Sequence a New Application with App-V -author: MaggiePucciEvans +title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to manually sequence a new app using the App-V Sequencer +author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library @@ -9,10 +9,10 @@ ms.prod: w10 --- -# How to Sequence a New Application with App-V +# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** -- Windows 10, version 1607 +- Windows 10, version 1607 and later In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md). @@ -36,8 +36,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD - If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume. -> [!NOTE] -> The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated. +>[!NOTE] +>The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated. **To sequence a new standard application** @@ -47,15 +47,15 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. 4. On the **Type of Application** page, click the **Standard Application (default)** check box, and then click **Next**. 5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. - > [!NOTE] - > If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package. + >[!NOTE] + >If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**. @@ -65,8 +65,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. - > [!IMPORTANT] - > You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. + >[!IMPORTANT] + >You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. @@ -74,8 +74,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run. - > [!NOTE] - > To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step. + >[!NOTE] + >To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step. Click **Next**. @@ -91,23 +91,21 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**. - > [!NOTE] - > If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application. - -   + >[!NOTE] + >If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application. 13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. Click **Next**. - > [!IMPORTANT] - > Make sure that the operating systems you specify here are supported by the application you are sequencing. + >[!IMPORTANT] + >Make sure that the operating systems you specify here are supported by the application you are sequencing. 14. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package. - > [!IMPORTANT] - > The system does not support non-printable characters in **Comments** and **Descriptions**. + >[!IMPORTANT] + >The system does not support non-printable characters in **Comments** and **Descriptions**. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. @@ -115,14 +113,13 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD The package is now available in the sequencer. - > [!IMPORTANT] - > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. - + >[!IMPORTANT] + >After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.   **To sequence an add-on or plug-in application** -> [!NOTE] +>[!NOTE] >Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer. >For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package. @@ -133,9 +130,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. - + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package. 4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**. @@ -143,17 +139,17 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 6. On the **Install Primary** page, ensure that the primary application is installed on the computer that runs the sequencer. Alternatively, you can expand an existing package that has been saved locally on the computer that runs the sequencer. To do this, click **Expand Package**, and then select the package. After you have expanded or installed the parent program, select **I have installed the primary parent program**. - Click **Next**. +7. Click **Next**. -7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console. +8. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console. - Click **Next**. +9. Click **Next**. -8. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**. +10. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**. -9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**. +11. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**. -10. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**. +12. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**. - Optimize how the package will run across a slow or unreliable network. @@ -161,12 +157,10 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD Click **Next**. -11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**. +13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**. - > [!NOTE]    - > If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**. - -   + >[!NOTE]    + >If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**. 12. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Click **Next**. @@ -174,8 +168,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package. - > [!IMPORTANT]    - > The system does not support non-printable characters in Comments and Descriptions. + >[!IMPORTANT]    + >The system does not support non-printable characters in Comments and Descriptions. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. @@ -187,9 +181,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**. - > [!IMPORTANT] - > If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package. - + >[!IMPORTANT] + >If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package. 4. On the **Type of Application** page, select **Middleware**, and then click **Next**. @@ -197,37 +190,35 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD 6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console. - Click **Next**. +7. Click **Next**. -7. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**. +8. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**. -8. On the **Installation** page, wait while the sequencer configures the virtual application package. +9. On the **Installation** page, wait while the sequencer configures the virtual application package. -9. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**. +10. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**. -10. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Click **Next**. +11. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Click **Next**. -11. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. +12. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**. To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package. - > [!IMPORTANT]    - > The system does not support non-printable characters in Comments and Descriptions. + >[!IMPORTANT]    + >The system does not support non-printable characters in Comments and Descriptions. The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. -12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure. +13. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure. The package is now available in the sequencer. To edit the package properties, click **Edit \[Package Name\]**. - > [!IMPORTANT]    - > After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. + >[!IMPORTANT]    + >After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer. ## Have a suggestion for App-V? - Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics - - [Install the App-V Sequencer](appv-install-the-sequencer.md) - [Operations for App-V](appv-operations.md) diff --git a/windows/manage/appv-sequence-a-package-with-powershell.md b/windows/manage/appv-sequence-a-package-with-powershell.md index e1920755b9..1d3143b133 100644 --- a/windows/manage/appv-sequence-a-package-with-powershell.md +++ b/windows/manage/appv-sequence-a-package-with-powershell.md @@ -59,10 +59,15 @@ The following list displays additional optional parameters that can be used with - FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened. -## Have a suggestion for App-V? +In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. -Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +>[!IMPORTANT] +>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. ## Related topics - [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md) + +## Have a suggestion for App-V? + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). \ No newline at end of file diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index 21c950edcb..d6a3868254 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -14,23 +14,31 @@ This topic lists new and updated topics in the [Manage Windows 10](index.md) doc >If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history). - ## RELEASE: Windows 10, version 1703 The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). Some topics have been moved to [Update Windows 10](../update/index.md) or to [Configure Windows 10](../configure/index.md). - +## March 2017 +| New or changed topic | Description | +| --- | --- | +|[Test scenario 6 - Review a reminder suggested by Cortana based on what you’ve promised in email](cortana-at-work-scenario-6.md) |New | +|[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. | +|[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New | +|[Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New | +|[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New | +|[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New | +|[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New | +|[Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md) |New | ## February 2017 - | New or changed topic | Description | | --- | --- | | [Windows Libraries](windows-libraries.md) | New | | [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | New | | [Get started with Update Compliance](update-compliance-get-started.md) | New | | [Use Update Compliance to monitor Windows Updates](update-compliance-using.md) | New | -| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. | -| [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Added Express updates. | +|[Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. | +|[Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |Added Express updates. | | [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. | diff --git a/windows/manage/images/button.png b/windows/manage/images/button.png new file mode 100644 index 0000000000..1ba7590f76 Binary files /dev/null and b/windows/manage/images/button.png differ diff --git a/windows/manage/images/waas-wufb-update-compliance.png b/windows/manage/images/waas-wufb-update-compliance.png new file mode 100644 index 0000000000..0c1bbaea7c Binary files /dev/null and b/windows/manage/images/waas-wufb-update-compliance.png differ diff --git a/windows/manage/windows-store-for-business-overview.md b/windows/manage/windows-store-for-business-overview.md index 81941f86f8..a3a565c261 100644 --- a/windows/manage/windows-store-for-business-overview.md +++ b/windows/manage/windows-store-for-business-overview.md @@ -18,12 +18,12 @@ localizationpriority: high - Windows 10 - Windows 10 Mobile -With the new Windows Store for Business, organizations can make volume purchases of Windows apps. The Store for Business provides app purchases based on organizational identity, flexible distribution options, and the ability to reclaim or re-use licenses. Organizations can also use the Store for Business to create a private store for their employees that includes apps from the Store, as well private Line-of-Business (LOB) apps. +With Windows Store for Business, organizations can make volume purchases of Windows apps. The Store for Business provides app purchases based on organizational identity, flexible distribution options, and the ability to reclaim or re-use licenses. Organizations can also use the Store for Business to create a private store for their employees that includes apps from the Store, as well private Line-of-Business (LOB) apps. ## Features -Organizations of any size can benefit from using the Store for Business provides: +Organizations of any size can benefit from using the Store for Business: - **Scales to fit the size of your business** - For smaller businesses, with Azure AD accounts and Windows 10 devices, you can quickly have an end-to-end process for acquiring and distributing content using the Store for Business. For larger businesses, all the capabilities of the Store for Business are available to you, or you can integrate the Store for Business with management tools, for greater control over access to apps and app updates. You can use existing work or school accounts. @@ -47,7 +47,6 @@ Organizations of any size can benefit from using the Store for Business provides ## Prerequisites - You'll need this software to work with the Store for Business. ### Required @@ -78,7 +77,6 @@ While not required, you can use a management tool to distribute and manage apps. ## How does the Store for Business work? - ### Sign up! The first step for getting your organization started with the Store for Business is signing up. To sign up for the Business store, you need an Azure AD account and you must be a Global Administrator for your organization. diff --git a/windows/update/images/waas-wufb-update-compliance.png b/windows/update/images/waas-wufb-update-compliance.png new file mode 100644 index 0000000000..0c1bbaea7c Binary files /dev/null and b/windows/update/images/waas-wufb-update-compliance.png differ diff --git a/windows/update/waas-delivery-optimization.md b/windows/update/waas-delivery-optimization.md index 7a3e27122c..ffc4f91f43 100644 --- a/windows/update/waas-delivery-optimization.md +++ b/windows/update/waas-delivery-optimization.md @@ -37,24 +37,24 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz Several Delivery Optimization features are configurable: -| Group Policy setting | MDM setting | -| --- | --- | -| [Download mode](#download-mode) | DODownloadMode | -| [Group ID](#group-id) | DOGroupID | -| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | -| [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) | DOMinDiskSizeAllowedToPeer | -| [Max Cache Age](#max-cache-age) | DOMaxCacheAge | -| [Max Cache Size](#max-cache-size) | DOMaxCacheSize | -| [Absolute Max Cache Size](#absolute-max-cache-size) | DOAbsoluteMaxCacheSize | -| [Modify Cache Drive](#modify-cache-drive) | DOModifyCacheDrive | -| [Minimum Peer Caching Content File Size](#minimum-peer-caching-content-file-size) | DOMinFileSizeToCache | -| [Maximum Download Bandwidth](#maximum-download-bandwidth) | DOMaxDownloadBandwidth | -| [Percentage of Maximum Download Bandwidth](#percentage-of-maximum-download-bandwidth) | DOPercentageMaxDownloadBandwidth | -| [Max Upload Bandwidth](#max-upload-bandwidth) | DOMaxUploadBandwidth | -| [Monthly Upload Data Cap](#monthly-upload-data-cap) | DOMonthlyUploadDataCap | -| [Minimum Background QoS](#minimum-background-qos) | DOMinBackgroundQoS | -| [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) | DOAllowVPNPeerCaching | -| [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) | DOMinBatteryPercentageAllowedToUpload | +| Group Policy setting | MDM setting | Supported from version | +| --- | --- | --- | +| [Download mode](#download-mode) | DODownloadMode | 1511 | +| [Group ID](#group-id) | DOGroupID | 1511 | +| [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) | DOMinRAMAllowedToPeer | 1703 | +| [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) | DOMinDiskSizeAllowedToPeer | 1703 | +| [Max Cache Age](#max-cache-age) | DOMaxCacheAge | 1511 | +| [Max Cache Size](#max-cache-size) | DOMaxCacheSize | 1511 | +| [Absolute Max Cache Size](#absolute-max-cache-size) | DOAbsoluteMaxCacheSize | 1607 | +| [Modify Cache Drive](#modify-cache-drive) | DOModifyCacheDrive | 1607 | +| [Minimum Peer Caching Content File Size](#minimum-peer-caching-content-file-size) | DOMinFileSizeToCache | 1703 | +| [Maximum Download Bandwidth](#maximum-download-bandwidth) | DOMaxDownloadBandwidth | 1607 | +| [Percentage of Maximum Download Bandwidth](#percentage-of-maximum-download-bandwidth) | DOPercentageMaxDownloadBandwidth | 1607 | +| [Max Upload Bandwidth](#max-upload-bandwidth) | DOMaxUploadBandwidth | 1607 | +| [Monthly Upload Data Cap](#monthly-upload-data-cap) | DOMonthlyUploadDataCap | 1607 | +| [Minimum Background QoS](#minimum-background-qos) | DOMinBackgroundQoS | 1607 | +| [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) | DOAllowVPNPeerCaching | 1703 | +| [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) | DOMinBatteryPercentageAllowedToUpload | 1703 | When configuring Delivery Optimization on Windows 10 devices, the first and most important thing to configure, would be [Download mode](#download-mode). Download mode dictates how Delivery Optimization downloads Windows updates. @@ -82,7 +82,7 @@ Various controls allow administrators to further customize scenarios where Deliv - [Minimum RAM (inclusive) allowed to use Peer Caching](#minimum-ram-allowed-to-use-peer-caching) sets the minimum RAM required for peer caching to be enabled. - [Minimum disk size allowed to use Peer Caching](#minimum-disk-size-allowed-to-use-peer-caching) sets the minimum disk size required for peer caching to be enabled. - [Enable Peer Caching while the device connects via VPN](#enable-peer-caching-while-the-device-connects-via-vpn) allows clients connected through VPN to use peer caching. -- [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) controls the minimum battery level required for uploads to occur. +- [Allow uploads while the device is on battery while under set Battery level](#allow-uploads-while-the-device-is-on-battery-while-under-set-battery-level) controls the minimum battery level required for uploads to occur. Enabling this policy is required to allow upload while on battery. ### How Microsoft uses Delivery Optimization In Microsoft, to help ensure that ongoing deployments weren’t affecting our network and taking away bandwidth for other services, Microsoft IT used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Based on recommendations from the Delivery Optimization team, we used the "group" configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. More than 76 percent of content came from peer devices versus the Internet. @@ -119,11 +119,11 @@ By default, peer sharing on clients using the group download mode is limited to ### Minimum RAM (inclusive) allowed to use Peer Caching -This setting specifies the minimum RAM size in GB required to use Peer Caching. The value 0 means not limited, which means the cloud service set default value will be used. For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching. The recommended values are 1 to 4 GB. +This setting specifies the minimum RAM size in GB required to use Peer Caching. For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching. The recommended values are 1 to 4 GB, and the default value is 4 GB. ### Minimum disk size allowed to use Peer Caching -This setting specifies the required minimum disk size (capacity in GB) for the device to use Peer Caching. The value 0 means not limited, which means the cloud service set default value will be used. The recommended values are 64 to 256 GB. +This setting specifies the required minimum disk size (capacity in GB) for the device to use Peer Caching. The recommended values are 64 to 256 GB, and the default value is 32 GB. >[!NOTE] >If the [Modify Cache Drive](#modify-cache-drive) policy is set, the disk size check will apply to the new working directory specified by this policy. @@ -143,7 +143,7 @@ This setting specifies the maximum number of gigabytes the Delivery Optimization ### Minimum Peer Caching Content File Size -This setting specifies the minimum content file size in MB enabled to use Peer Caching. The value 0 means "unlimited" which means the cloud service set default value will be used. The recommended values are from 1 to 100000 MB. +This setting specifies the minimum content file size in MB enabled to use Peer Caching. The recommended values are from 1 to 100000 MB. ### Maximum Download Bandwidth @@ -159,7 +159,7 @@ This setting allows you to limit the amount of upload bandwidth individual clien ### Minimum Background QoS -This value specifies the minimum download speed guarantee that a client attempts to achieve and will fulfill by downloading more bytes from Windows Update servers or WSUS. Simply put, the lower this value is, the more content will be sourced using peers on the network rather than Windows Update. The higher this value, the more content is received from Windows Update servers or WSUS, versus peers on the local network. +This value specifies the minimum download speed guarantee that a client attempts to achieve and will fulfill by downloading more kilobytes from Windows Update servers or WSUS. Simply put, the lower this value is, the more content will be sourced using peers on the network rather than Windows Update. The higher this value, the more content is received from Windows Update servers or WSUS, versus peers on the local network. ### Modify Cache Drive @@ -177,7 +177,9 @@ This setting determines whether a device will be allowed to participate in Peer This setting specifies battery levels at which a device will be allowed to upload data. Specify any value between 1 and 100 (in percentage) to allow the device to upload data to LAN and Group peers while on DC power (Battery). Uploads will automatically pause when the battery level drops below the set minimum battery level. The recommended value to set if you allow uploads on battery is 40 (for 40%). The device can download from peers while on battery regardless of this policy. -The value 0 means not limited, which means the cloud service set default value will be used. + +>[!IMPORTANT] +> By default, devices **will not upload while on battery**. To enable uploads while on battery, you need to enable this policy and set the battery value under which uploads pause. ## Set “preferred” cache devices for Delivery Optimization @@ -188,7 +190,7 @@ To specify which devices are preferred, you can set the **Max Cache Age** config On devices that are not preferred, you can choose to set the following policy to prioritize data coming from local peers instead of the Internet: -- Set **DOMinBackgroundQoS** with a low value, for example `65536` which is the equivalent of 64 KB/s. +- Set **DOMinBackgroundQoS** with a low value, for example `64` which is the equivalent of 64 KB/s. ## Learn more diff --git a/windows/update/waas-manage-updates-wufb.md b/windows/update/waas-manage-updates-wufb.md index f15a5388f4..f38ac5333c 100644 --- a/windows/update/waas-manage-updates-wufb.md +++ b/windows/update/waas-manage-updates-wufb.md @@ -104,6 +104,13 @@ Windows Update for Business was first made available in Windows 10, version 1511

Drivers

No driver-specific controls

Drivers can be selectively excluded from Windows Update for Business.

+## Monitor Windows Updates using Update Compliance + +Update Compliance, now **available in public preview**, provides a holistic view of OS update compliance, update deployment progress, and failure troubleshooting for Windows 10 devices. This new service uses telemetry data including installation progress, Windows Update configuration, and other information to provide such insights, at no extra cost and without additional infrastructure requirements. Whether used with Windows Update for Business or other management tools, you can be assured that your devices are properly updated. + +![Update Compliance Dashboard](images/waas-wufb-update-compliance.png) + +For more information about Update Compliance, see [Monitor Windows Updates using Update Compliance](update-compliance-monitor.md). ## Steps to manage updates for Windows 10 @@ -119,9 +126,7 @@ or [Manage Windows 10 updates using System Center Configuration Manager](waas-ma
- ## Related topics - - [Update Windows 10 in the enterprise](index.md) - [Overview of Windows as a service](waas-overview.md) - [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) diff --git a/windows/whats-new/whats-new-windows-10-version-1607.md b/windows/whats-new/whats-new-windows-10-version-1607.md index 265b3b3910..87a9c88d26 100644 --- a/windows/whats-new/whats-new-windows-10-version-1607.md +++ b/windows/whats-new/whats-new-windows-10-version-1607.md @@ -146,7 +146,7 @@ Many users customize their settings for Windows and for specific applications. C With User Experience Virtualization (UE-V), you can capture user-customized Windows and application settings and store them on a centrally managed network file share. When users log on, their personalized settings are applied to their work session, regardless of which device or virtual desktop infrastructure (VDI) sessions they log on to. -With the release of Windows 10, version 1607, UE-V is included with the Windows 10 for Enterprise edition. If you are new to Windows 10 and EU-V or upgrading from a previous version of UE-V, you’ll need to download, activate, and install server- and client-side components to start synchronizing user-customized settings across devices. +With the release of Windows 10, version 1607, UE-V is included with the Windows 10 for Enterprise edition. If you are new to Windows 10 and UE-V or upgrading from a previous version of UE-V, you’ll need to download, activate, and install server- and client-side components to start synchronizing user-customized settings across devices. [Learn how to synchronize user-customized settings with UE-V.](../manage/uev-for-windows.md) diff --git a/windows/whats-new/whats-new-windows-10-version-1703.md b/windows/whats-new/whats-new-windows-10-version-1703.md index fe76aacdf4..22fd04dd94 100644 --- a/windows/whats-new/whats-new-windows-10-version-1703.md +++ b/windows/whats-new/whats-new-windows-10-version-1703.md @@ -1,5 +1,5 @@ --- -title: What's new in Windows 10, version 1703 (Windows 10) +title: New IT Pro content for Windows 10, version 1703 description: This topic lists new and updated topics in the What's new in Windows 10 documentation for Windows 10 and Windows 10 Mobile. keywords: ["What's new in Windows 10", "Windows 10", "creators update"] ms.prod: w10 @@ -10,9 +10,11 @@ localizationpriority: high ms.assetid: dca7c655-c4f6-45f8-aa02-64187b202617 --- -# What's new in Windows 10, version 1703 +# New IT Pro content for Windows 10, version 1703 -Below is a list of some of the new and updated features in Windows 10, version 1703 (also known as the Creators Update). +Below is a list of some of the new and updated content that discusses Information Technology (IT) Pro features in Windows 10, version 1703 (also known as the Creators Update). + +For more general info about Windows 10 features, see [Features available only on Windows 10](https://www.microsoft.com/windows/features). >[!NOTE] >For release dates and servicing options for each version, see [Windows 10 release information](https://technet.microsoft.com/en-us/windows/release-info). @@ -29,12 +31,14 @@ Windows Configuration Designer in Windows 10, version 1703, includes several new [Learn more about Windows Configuration Designer.](../configure/provisioning-packages.md) + ### Bulk enrollment in Azure Active Directory Using the new wizards in Windows Configuration Designer, you can [create provisioning packages to enroll devices in Azure Active Directory](../configure/provisioning-packages.md#configuration-designer-wizards). Bulk enrollment in Azure AD is available in the desktop, mobile, kiosk, and Surface Hub wizards. ![get bulk token action in wizard](images/bulk-token.png) + ### Windows Spotlight The following new Group Policy and mobile device management (MDM) settings are added to help you configure Windows Spotlight user experiences: @@ -48,7 +52,7 @@ The following new Group Policy and mobile device management (MDM) settings are a ### Start and taskbar layout -Enterprises can apply a customized Start and taskbar layout to devices running Windows 10 Pro, version 1703. +Enterprises have been able to apply customized Start and taskbar layouts to devices running Windows 10 Enterprise and Education. In Windows 10, version 1703, customized Start and taskbar layout can also be applied to Windows 10 Pro. Additional MDM policy settings are available for Start and taskbar layout. For details, see [Manage Windows 10 Start and taskbar layout](../configure/windows-10-start-layout-options-and-policies.md). @@ -62,7 +66,11 @@ The Lockdown Designer app helps you configure and create a lockdown XML file to [Learn more about the Lockdown Designer app.](../configure/mobile-lockdown-designer.md) +### Cortana at work +Cortana is Microsoft’s personal digital assistant, who helps busy people get things done, even while at work. Cortana has powerful configuration options, specifically optimized for your business. By signing in with an Azure Active Directory (Azure AD) account, your employees can give Cortana access to their enterprise/work identity, while getting all the functionality Cortana provides to them outside of work. + +Using Azure AD also means that you can remove an employee’s profile (for example, when an employee leaves your organization) while respecting Windows Information Protection (WIP) policies and ignoring enterprise content, such as emails, calendar items, and people lists that are marked as enterprise data. ## Deployment @@ -77,12 +85,6 @@ Additional security features of Windows 10 that are enabled when you boot in UEF For details, see [MBR2GPT.EXE](../deploy/mbr-to-gpt.md). -### Cortana at work - -Cortana is Microsoft’s personal digital assistant, who helps busy people get things done, even while at work. Cortana has powerful configuration options, specifically optimized for your business. By signing in with an Azure Active Directory (Azure AD) account, your employees can give Cortana access to their enterprise/work identity, while getting all the functionality Cortana provides to them outside of work. - -Using Azure AD also means that you can remove an employee’s profile (for example, when an employee leaves your organization) while respecting Windows Information Protection (WIP) policies and ignoring enterprise content, such as emails, calendar items, and people lists that are marked as enterprise data. - ## Security ### Windows Defender Advanced Threat Protection @@ -167,6 +169,17 @@ Added policies include: To check out all the details, see [Configure Delivery Optimization for Windows 10 updates](../update/waas-delivery-optimization.md) +## Manage + +### Application Virtualization for Windows (App-V) +Previous versions of the Microsoft Application Virtualization Sequencer (App-V Sequencer) have required you to manually create your sequencing environment. Windows 10, version 1703 introduces two new PowerShell cmdlets, New-AppVSequencerVM and Connect-AppvSequencerVM, which automatically create your sequencing environment for you, including provisioning your virtual machine. Addtionally, the App-V Sequencer has been updated to let you sequence or update multiple apps at the same time, while automatically capturing and storing your customizations as an App-V project template (.appvt) file, and letting you use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart. + +For more info, see the following topics: +- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](../manage/appv-auto-provision-a-vm.md) +- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](../manage/appv-auto-batch-sequencing.md) +- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](../manage/appv-auto-batch-updating.md) +- [Automatically cleanup unpublished packages on the App-V client](../manage/appv-auto-clean-unpublished-packages.md) + ## Related topics - [Features that are removed or deprecated in Windows 10 Creators Update](https://support.microsoft.com/help/4014193/features-that-are-removed-or-deprecated-in-windows-10-creators-update)