mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge pull request #113 from MicrosoftDocs/from-public
From public, 5/3
This commit is contained in:
Liza Poggemeyer
GitHub
commit
f9204a5fb5
BIN
devices/surface/images/sdt-install.png
Normal file
BIN
devices/surface/images/sdt-install.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 89 KiB |
@ -56,9 +56,14 @@ Full Brightness | Default: 100 <br>Option: Range of 0-100 percent of screen b
|
||||
| Inactivity Timeout| Default: 30 seconds <br>Option: Any numeric value <br>Data Type: Integer <br> Type: REG_DWORD | This setting allows you to manage the period of inactivity before dimming the device. If you do not configure this setting, the inactivity timeout is 30 seconds.|
|
||||
| Telemetry Enabled | Default: 01 <br>Option: 01, 00 <br> Type: REG_BINARY | This setting allows you to manage the sharing of app usage information to improve software and provide better user experience. To disable telemetry, set the value to 00. If you do not configure this setting, telemetry information is shared with Microsoft in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement). |
|
||||
|
||||
## Changes and updates
|
||||
|
||||
### Version 1.12.239.0
|
||||
*Release Date: 26 April 2019*<br>
|
||||
This version of Surface Brightness Control adds support for the following:
|
||||
- Touch delay fixes.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Battery limit setting](battery-limit.md)
|
||||
|
||||
|
||||
@ -27,13 +27,11 @@ Specifically, SDT for Business enables you to:
|
||||
|
||||
To run SDT for Business, download the components listed in the following table.
|
||||
|
||||
>[!NOTE]
|
||||
>In contrast to the way you typically install MSI packages, the SDT distributable MSI package can only be created by running Windows Installer (msiexec.exe) at a command prompt and setting the custom flag `ADMINMODE = 1`. For details, see [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md).
|
||||
|
||||
Mode | Primary scenarios | Download | Learn more
|
||||
--- | --- | --- | ---
|
||||
Desktop mode | Assist users in running SDT on their Surface devices to troubleshoot issues.<br>Create a custom package to deploy on one or more Surface devices allowing users to select specific logs to collect and analyze. | SDT distributable MSI package:<br>Microsoft Surface Diagnostic Toolkit for Business Installer<br>[Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) | [Use Surface Diagnostic Toolkit in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
|
||||
Command line | Directly troubleshoot Surface devices remotely without user interaction, using standard tools such as Configuration Manager. It includes the following commands:<br>`-DataCollector` collects all log files<br>`-bpa` runs health diagnostics using Best Practice Analyzer.<br>`-windowsupdate` checks Windows update for missing firmware or driver updates.<br><br>**Note:** Support for the ability to confirm warranty information will be available via the command `-warranty` | SDT console app:<br>Microsoft Surface Diagnostics App Console<br>[Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) | [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md)
|
||||
Command line | Directly troubleshoot Surface devices remotely without user interaction, using standard tools such as Configuration Manager. It includes the following commands:<br>`-DataCollector` collects all log files<br>`-bpa` runs health diagnostics using Best Practice Analyzer.<br>`-windowsupdate` checks Windows update for missing firmware or driver updates.<br>`-warranty` checks warranty information. <br><br>| SDT console app:<br>Microsoft Surface Diagnostics App Console<br>[Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) | [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md)
|
||||
|
||||
## Supported devices
|
||||
|
||||
@ -57,16 +55,40 @@ SDT for Business is supported on Surface 3 and later devices, including:
|
||||
|
||||
## Installing Surface Diagnostic Toolkit for Business
|
||||
|
||||
To create an SDT package that you can distribute to users in your organization, you first need to install SDT at a command prompt and set a custom flag to install the tool in admin mode. SDT contains the following install option flags:
|
||||
To create an SDT package that you can distribute to users in your organization:
|
||||
|
||||
1. Sign in to your Surface device using the Administrator account.
|
||||
2. Download SDT Windows Installer Package (.msi) from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703) and copy it to a preferred location on your Surface device, such as Desktop.
|
||||
3. The SDT setup wizard appears, as shown in figure 1. Click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>If the setup wizard does not appear, ensure that you are signed into the Administrator account on your computer.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Surface Diagnostic Toolkit setup wizard*
|
||||
|
||||
4. When the SDT setup wizard appears, click **Next**, accept the End User License Agreement (EULA)
|
||||
|
||||
5. On the Install Options screen, change the default install location if desired.
|
||||
6. Under Setup Type, select **Advanced**.
|
||||
|
||||
>[!NOTE]
|
||||
>The standard option allows users to run the diagnostic tool directly on their Surface device provided they are signed into their device using an Administrator account.
|
||||
|
||||
|
||||
|
||||
7. Click **Next** and then click **Install**.
|
||||
|
||||
## Installing using the command line
|
||||
If desired, you can install SDT at a command prompt and set a custom flag to install the tool in admin mode. SDT contains the following install option flags:
|
||||
|
||||
- `SENDTELEMETRY` sends telemetry data to Microsoft. The flag accepts `0` for disabled or `1` for enabled. The default value is `1` to send telemetry.
|
||||
- `ADMINMODE` configures the tool to be installed in admin mode. The flag accepts `0` for client mode or `1` for IT Administrator mode. The default value is `0`.
|
||||
|
||||
**To install SDT in ADMINMODE:**
|
||||
### To install SDT from the command line:
|
||||
|
||||
1. Sign in to your Surface device using the Administrator account.
|
||||
2. Download SDT Windows Installer Package (.msi) from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703) and copy it to a preferred location on your Surface device, such as Desktop.
|
||||
3. Open a command prompt and enter:
|
||||
1. Open a command prompt and enter:
|
||||
|
||||
```
|
||||
msiexec.exe /i <the path of installer> ADMINMODE=1.
|
||||
@ -77,19 +99,6 @@ To create an SDT package that you can distribute to users in your organization,
|
||||
C:\Users\Administrator> msiexec.exe/I"C:\Users\Administrator\Desktop\Microsoft_Surface_Diagnostic_Toolkit_for_Business_Installer.msi" ADMINMODE=1
|
||||
```
|
||||
|
||||
4. The SDT setup wizard appears, as shown in figure 1. Click **Next**.
|
||||
|
||||
>[!NOTE]
|
||||
>If the setup wizard does not appear, ensure that you are signed into the Administrator account on your computer.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Surface Diagnostic Toolkit setup wizard*
|
||||
|
||||
5. When the SDT setup wizard appears, click **Next**, accept the End User License Agreement (EULA), and select a location to install the package.
|
||||
|
||||
6. Click **Next** and then click **Install**.
|
||||
|
||||
## Locating SDT on your Surface device
|
||||
|
||||
Both SDT and the SDT app console are installed at `C:\Program Files\Microsoft\Surface\Microsoft Surface Diagnostic Toolkit for Business`.
|
||||
@ -154,7 +163,14 @@ You can select to run a wide range of logs across applications, drivers, hardwar
|
||||
- [Use Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
|
||||
|
||||
|
||||
|
||||
## Changes and updates
|
||||
### Version 2.36.139.0
|
||||
*Release date: April 26, 2019*<br>
|
||||
This version of Surface Diagnostic Toolkit for Business adds support for the following:
|
||||
- Advanced Setup option to unlock admin capabilities through the installer UI, without requiring command line configuration.
|
||||
- Accessibility improvements.
|
||||
- Surface brightness control settings included in logs.
|
||||
- External monitor compatibility support link in report generator.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -95,12 +95,12 @@ If your apps require custom prerequisites, such as Microsoft SQL Server, we reco
|
||||
2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```ps1
|
||||
Connect-AppvSequencerVM -VMName "<name_of_vm>" -ADKPath "<path_to_adk_install_folder>"
|
||||
Connect-AppvSequencerVM -VMName "<name_of_vm>"
|
||||
```
|
||||
|
||||
Where ```<name_of_vm>``` is the name of the VM as 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.
|
||||
This command connects to an existing Hyper-V VM using the provided VM name for auto-sequencing.
|
||||
|
||||
### Review the provisioning log files
|
||||
|
||||
|
||||
@ -12,6 +12,9 @@ ms.topic: article
|
||||
|
||||
# Use Upgrade Readiness to manage Windows upgrades
|
||||
|
||||
>[!IMPORTANT]
|
||||
>>**The OMS portal has been deprecated, so you need to switch to the [Azure portal](https://portal.azure.com) now.** The two portals offer the same experience, with some key differences. Learn how to use [Windows Analytics in the Azure Portal](../update/windows-analytics-azure-portal.md). Find out more about the [OMS portal moving to Azure](https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-portal-transition), or jump right in and [Get started with Upgrade Readiness](https://docs.microsoft.com/windows/deployment/upgrade/upgrade-readiness-get-started).
|
||||
|
||||
You can use Upgrade Readiness to prioritize and work through application and driver issues, assign and track issue resolution status, and identify computers that are ready to upgrade. Upgrade Readiness enables you to deploy Windows with confidence, knowing that you’ve addressed potential blocking issues.
|
||||
|
||||
- Based on diagnostic data from user computers, Upgrade Readiness identifies application and driver compatibility issues that may block Windows upgrades, allowing you to make data-driven decisions about your organization’s upgrade readiness.
|
||||
|
||||
@ -20,6 +20,9 @@ ms.date: 12/10/2018
|
||||
|
||||
- [Windows Defender Advanced Threat Protection (Windows Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> [Windows Defender Advanced Threat Protection ](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/defender-compatibility-windows-defender-advanced-threat-protection) does not adhere to Windows Defender Antivirus exclusion settings. This means that any Windows Defender exclusions, no matter how you created them, are not applied by Windows Defender ATP.
|
||||
|
||||
You can exclude certain files from Windows Defender Antivirus scans by modifying exclusion lists.
|
||||
|
||||
Generally, you shouldn't need to apply exclusions. Windows Defender Antivirus includes a number of automatic exclusions based on known operating system behaviors and typical management files, such as those used in enterprise management, database management, and other enterprise scenarios and situations.
|
||||
|
||||
@ -31,10 +31,14 @@ You should have beginner-level experience in macOS and BASH scripting. You must
|
||||
You should also have access to Windows Defender Security Center.
|
||||
|
||||
### System Requirements
|
||||
Microsoft Defender ATP for Mac system requirements:
|
||||
- macOS version: 10.14 (Mojave), 10.13 (High Sierra), 10.12 (Sierra)
|
||||
- Disk space during preview: 1GB
|
||||
|
||||
Beta versions of macOS are not supported.
|
||||
|
||||
> [!CAUTION]
|
||||
> Running other third-party endpoint protection along with Microsoft Defender ATP for Mac may lead to performance problems and unpredictable side effects.
|
||||
|
||||
After you've enabled the service, you may need to configure your network or firewall to allow outbound 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:
|
||||
|
||||
@ -87,6 +87,12 @@ netsh winhttp set proxy <proxy>:<port>
|
||||
```
|
||||
For example: netsh winhttp set proxy 10.0.0.6:8080
|
||||
|
||||
To reset the winhttp proxy, enter the following command and press **Enter**
|
||||
```
|
||||
netsh winhttp reset proxy
|
||||
```
|
||||
See [Netsh Command Syntax, Contexts, and Formatting](https://docs.microsoft.com/windows-server/networking/technologies/netsh/netsh-contexts) to learn more.
|
||||
|
||||
## Enable access to Windows Defender ATP service URLs in the proxy server
|
||||
If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that the following URLs are not blocked by default. Do not disable security monitoring or inspection of these URLs, but allow them as you would other internet traffic. They permit communication with Windows Defender ATP service in port 80 and 443:
|
||||
|
||||
|
||||
@ -69,6 +69,7 @@ You'll need to tak the following steps if you choose to onboard servers through
|
||||
- Turn on server monitoring from Windows Defender Security Center.
|
||||
- If you're already leveraging System Center Operations Manager (SCOM) or Azure Monitor (formerly known as Operations Management Suite (OMS)), simply attach the Microsoft Monitoring Agent (MMA) to report to your Windows Defender ATP workspace through Multi Homing support. Otherwise, install and configure MMA to report sensor data to Windows Defender ATP as instructed below. For more information, see [Collect log data with Azure Log Analytics agent](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent).
|
||||
|
||||
|
||||
>[!TIP]
|
||||
> After onboarding the machine, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Windows Defender ATP endpoint](run-detection-test-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
|
||||
@ -50,12 +50,23 @@ Windows Defender SmartScreen helps to provide an early warning system against we
|
||||
## 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/scriptcenter/dd565657(v=msdn.10).aspx).
|
||||
|
||||
|
||||
## Viewing Windows event logs for SmartScreen
|
||||
SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug log in Event Viewer.
|
||||
|
||||
|
||||
|EventID | Description |
|
||||
| :---: | :---: |
|
||||
|1000 | Application SmartScreen Event|
|
||||
|1001 | Uri SmartScreen Event|
|
||||
|1002 | User Decision SmartScreen Event|
|
||||
|
||||
## Related topics
|
||||
- [SmartScreen Frequently Asked Questions (FAQ)](https://feedback.smartscreen.microsoft.com/smartscreenfaq.aspx)
|
||||
|
||||
- [How to recognize phishing email messages, links, or phone calls](https://www.microsoft.com/en-us/safety/online-privacy/phishing-symptoms.aspx)
|
||||
|
||||
- [Threat protection](../index.md)
|
||||
|
||||
- [Available Windows Defender SmartScreen Group Policy and mobile device management (MDM) settings](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-available-settings)
|
||||
|
||||
>[!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).
|
||||
Loading…
x
Reference in New Issue
Block a user