mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'master' of https://github.com/microsoftdocs/windows-itpro-docs
This commit is contained in:
commit
0241bf0e5a
@ -2,12 +2,14 @@
|
||||
ms.localizationpriority: low
|
||||
ms.mktglfcycl: plan
|
||||
description: Learn about which version of the IEAK 11 you should run, based on your license agreement.
|
||||
author: eross-msft
|
||||
ms.prod: ie11
|
||||
author: pashort
|
||||
ms.author: shortpatti
|
||||
ms.manager: elizapo
|
||||
ms.prod: ie11, ieak11
|
||||
ms.assetid: 69d25451-08af-4db0-9daa-44ab272acc15
|
||||
title: Determine the licensing version and features to use in IEAK 11 (Internet Explorer Administration Kit 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 05/02/2018
|
||||
---
|
||||
|
||||
|
||||
@ -45,7 +47,7 @@ You must pick a version of IEAK 11 to run during installation, either **Externa
|
||||
|Automatic configuration |Not available |
|
||||
|Proxy settings |Proxy settings |
|
||||
|Security and privacy settings |Not available |
|
||||
|Not available |Add a root certificate |
|
||||
|Add a root certificate |Not available |
|
||||
|Programs |Programs |
|
||||
|Additional settings |Not available |
|
||||
|Wizard complete |Wizard complete |
|
||||
|
@ -5,7 +5,7 @@ keywords: Long-Term Servicing Channel, LTSC, LTSB, Semi-Annual Channel, SAC, Win
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: MikeBlodge
|
||||
author: kaushika-msft
|
||||
ms.author: MikeBlodge
|
||||
ms.date: 04/30/2018
|
||||
---
|
||||
|
@ -284,7 +284,7 @@ If you suspect this is the problem, try these steps:
|
||||
|
||||
### Clients aren't able to connect to peers offered by the cloud service
|
||||
|
||||
If you suspect this is the problem, un a Telnet test between two devices on the network to ensure they can connect using port 7680. To do this, follow these steps:
|
||||
If you suspect this is the problem, run a Telnet test between two devices on the network to ensure they can connect using port 7680. To do this, follow these steps:
|
||||
|
||||
1. Install Telnet by running **dism /online /Enable-Feature /FeatureName:TelnetClient** from an elevated command prompt.
|
||||
2. Run the test. For example, if you are on device with IP 192.168.8.12 and you are trying to test the connection to 192.168.9.17 run **telnet 192.168.9.17 7680** (the syntax is *telnet [destination IP] [port]*. You will either see a connection error or a blinking cursor like this /_. The blinking cursor means success.
|
||||
|
@ -36,7 +36,8 @@ The Automated investigations list shows all the investigations that have been in
|
||||
|
||||
## Understand the Automated investigation flow
|
||||
### How the Automated investigation starts
|
||||
Entities are the starting point for Automated investigations. When an alert contains a supported entity for Automated investigation (for example, a file) an Automated investigation starts.
|
||||
Entities are the starting point for Automated investigations. When an alert contains a supported entity for Automated investigation (for example, a file) that resides on a machine that has a *supported operating system for Automated investigation then an Automated investigation can start.
|
||||
*Currently only Windows 10 version 1803 (spring creators update) and above are supported operating systems for Autoamted Investigation
|
||||
|
||||
The alerts start by analyzing the supported entities from the alert and also runs a generic machine playbook to see if there is anything else suspicious on that machine. The outcome and details from the investigation is seen in the Automated investigation view.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user