mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge branch 'pr/8'
This commit is contained in:
brbrahm
commit
3f8b3470df
@ -1247,6 +1247,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/custom-ti-api.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-atp/custom-detection-rules.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/custom-detection-rules",
|
||||
"redirect_document_id": true
|
||||
@ -1357,6 +1362,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/experiment-custom-ti.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-atp/fix-unhealhty-sensors-windows-defender-advanced-threat-protection.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/fix-unhealhty-sensors-windows-defender-advanced-threat-protection",
|
||||
"redirect_document_id": true
|
||||
@ -1692,6 +1702,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/powershell-example-code.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/keep-secure/preferences-setup-windows-defender-advanced-threat-protection.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-defender-atp/preferences-setup-windows-defender-advanced-threat-protection",
|
||||
"redirect_document_id": true
|
||||
@ -1762,6 +1777,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/python-example-code.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-atp/rbac-windows-defender-advanced-threat-protection.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/rbac",
|
||||
"redirect_document_id": true
|
||||
@ -1894,7 +1914,7 @@
|
||||
{
|
||||
"source_path": "windows/keep-secure/troubleshoot-windows-defender-antivirus.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-defender-antivirus/troubleshoot-windows-defender-antivirus",
|
||||
"redirect_document_id": true
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/keep-secure/troubleshoot-windows-defender-in-windows-10.md",
|
||||
@ -1927,6 +1947,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/troubleshoot-custom-ti.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/troubleshoot-onboarding-windows-defender-advanced-threat-protection",
|
||||
"redirect_document_id": true
|
||||
@ -1977,6 +2002,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/microsoft-defender-atp/use-custom-ti.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-atp/user-roles-windows-defender-advanced-threat-protection.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/user-roles",
|
||||
"redirect_document_id": true
|
||||
|
||||
@ -41,7 +41,8 @@
|
||||
"depot_name": "Win.microsoft-edge",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Edge"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -44,7 +44,7 @@ If you're having trouble deciding whether Microsoft Edge is right for your organ
|
||||
|
||||
|Microsoft Edge |IE11 |
|
||||
|---------|---------|
|
||||
|Microsoft Edge takes you beyond just browsing to actively engaging with the web through features like Web Note, Reading View, and Cortana.<ul><li>**Web Note.** Microsoft Edge lets you annotate, highlight, and call things out directly on web pages.</li><li>**Reading view.** Microsoft Edge lets you enjoy and print online articles in a distraction-free layout optimized for your screen size. While in reading view, you can also save web pages or PDF files to your reading list, for later viewing.</li><li>**Cortana.** Enabled by default in Microsoft Edge, Cortana lets you highlight words for more info and gives you one-click access to things like restaurant reservations and reviews, without leaving the webpage.</li><li>**Compatibility and security.** Microsoft Edge lets you continue to use IE11 for sites that are on your corporate intranet or that are included on your Enterprise Mode Site List. You must use IE11 to run older, less secure technology, such as ActiveX controls.</li></ul> |IE11 offers enterprises additional security, manageability, performance, backward compatibility, and modern standards support.<ul><li>**Backward compatibility.** IE11 supports 9 document modes that include high-fidelity emulations for older versions of IE.</li><li>**Modern web standards.** IE11 supports modern web technologies like HTML5, CSS3, and WebGL, which help to ensure today's modern websites and apps work just as well as your old, legacy websites and apps. **IE11 does not support some modern CSS properties, JavaScript modules and certain APIs.**</li><li>**More secure.** IE11 was designed with security in mind and is more secure than older versions. Using security features like SmartScreen and Enhanced Protected Mode can help IE11 reduce your risk.</li><li>**Faster.** IE11 is significantly faster than previous versions of Internet Explorer, taking advantage of network optimization and hardware-accelerated text, graphics, and JavaScript rendering.</li><li>**Easier migration to Windows 10.** IE11 is the only version of IE that runs on Windows 7, Windows 8.1, and Windows 10. Upgrading to IE11 on Windows 7 can also help your organization support the next generation of software, services, and devices.</li><li>**Administration.** IE11 can use the Internet Explorer Administration Kit (IEAK) 11 or MSIs for deployment and includes more than 1,600 Group Policies and preferences for granular control.</li></ul> |
|
||||
|Microsoft Edge takes you beyond just browsing to actively engaging with the web through features like Web Note, Reading View, and Cortana.<ul><li>**Web Note.** Microsoft Edge lets you annotate, highlight, and call things out directly on web pages.</li><li>**Reading view.** Microsoft Edge lets you enjoy and print online articles in a distraction-free layout optimized for your screen size. While in reading view, you can also save web pages or PDF files to your reading list, for later viewing.</li><li>**Cortana.** Enabled by default in Microsoft Edge, Cortana lets you highlight words for more info and gives you one-click access to things like restaurant reservations and reviews, without leaving the webpage.</li><li>**Compatibility and security.** Microsoft Edge lets you continue to use IE11 for sites that are on your corporate intranet or that are included on your Enterprise Mode Site List. You must use IE11 to run older, less secure technology, such as ActiveX controls.</li></ul> |IE11 offers enterprises additional security, manageability, performance, backward compatibility, and modern standards support.<ul><li>**Backward compatibility.** IE11 supports 9 document modes that include high-fidelity emulations for older versions of IE.</li><li>**Modern web standards.** IE11 supports modern web technologies like HTML5, CSS3, and WebGL, which help to ensure today's modern websites and apps work just as well as your old, legacy websites and apps. **IE11 does not support some modern CSS properties, JavaScript modules and certain APIs.**</li><li>**More secure.** IE11 was designed with security in mind and is more secure than older versions. Using security features like Windows Defender SmartScreen and Enhanced Protected Mode can help IE11 reduce your risk.</li><li>**Faster.** IE11 is significantly faster than previous versions of Internet Explorer, taking advantage of network optimization and hardware-accelerated text, graphics, and JavaScript rendering.</li><li>**Easier migration to Windows 10.** IE11 is the only version of IE that runs on Windows 7, Windows 8.1, and Windows 10. Upgrading to IE11 on Windows 7 can also help your organization support the next generation of software, services, and devices.</li><li>**Administration.** IE11 can use the Internet Explorer Administration Kit (IEAK) 11 or MSIs for deployment and includes more than 1,600 Group Policies and preferences for granular control.</li></ul> |
|
||||
|
||||
|
||||
## Configure the Enterprise Mode Site List
|
||||
|
||||
@ -3,7 +3,8 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
manager: dansimp
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
@ -26,7 +27,7 @@ ms.topic: include
|
||||
|
||||
To verify Windows Defender SmartScreen is turned off (disabled):
|
||||
1. Click or tap **More** (…) and select **Settings** > **View Advanced settings**.
|
||||
2. Verify the setting **Help protect me from malicious sites and download with SmartScreen Filter** is disabled.<p>
|
||||
2. Verify the setting **Help protect me from malicious sites and download with Windows Defender SmartScreen** is disabled.<p>
|
||||
|
||||
|
||||
### ADMX info and settings
|
||||
|
||||
@ -40,7 +40,7 @@ sections:
|
||||
- items:
|
||||
- type: markdown
|
||||
text: "
|
||||
Microsoft Edge uses Windows Hello and SmartScreen to defend against phishing and malware. Take a look at some of the additional features behind the strong defense that Microsoft Edge provides against web-based attacks.<br>
|
||||
Microsoft Edge uses Windows Hello and Windows Defender SmartScreen to defend against phishing and malware. Take a look at some of the additional features behind the strong defense that Microsoft Edge provides against web-based attacks.<br>
|
||||
<table><tr><td><img src='images/security1.png' width='192' height='192'><br>**NSS Labs web browser security reports**<br>See the results of two global tests measuring how effective browsers are at protecting against socially engineered malware and phishing attacks.<br><a href='https://www.microsoft.com/download/details.aspx?id=54773'>Download the reports</a></td><td><img src='images/security2.png' width='192' height='192'><br>**Microsoft Edge sandbox**<br>See how Microsoft Edge has significantly reduced the attack surface of the sandbox by configuring the app container to further reduce its privilege.<br><a href='https://blogs.windows.com/msedgedev/2017/03/23/strengthening-microsoft-edge-sandbox/'>Find out more</a></td><td><img src='images/security3.png' width='192' height='192'><br>**Windows Defender SmartScreen**<br>Manage your organization's computer settings with Group Policy and MDM settings to display a warning page to employees or block a site entirely.<br><a href='https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview'>Read the docs</a></td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
@ -37,7 +37,8 @@
|
||||
"depot_name": "Win.internet-explorer",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Internet Explorer"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -157,13 +157,13 @@ This table includes the attributes used by the Enterprise Mode schema.
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><version></td>
|
||||
<td>version</td>
|
||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><exclude></td>
|
||||
<td>Specifies the domain or path excluded from applying the behavior and is supported on the <domain> and <path> elements.
|
||||
<td>exclude</td>
|
||||
<td>Specifies the domain or path is excluded from applying Enterprise Mode. This attribute is only supported on the <domain> and <path> elements in the <emie> section.
|
||||
<p><b>Example</b>
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
@ -175,7 +175,7 @@ Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">http
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><docMode></td>
|
||||
<td>docMode</td>
|
||||
<td>Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
|
||||
<p><b>Example</b>
|
||||
<pre class="syntax">
|
||||
|
||||
@ -46,19 +46,19 @@ The following is an example of the v.2 version of the Enterprise Mode schema.
|
||||
|
||||
```xml
|
||||
<site-list version="205">
|
||||
<!--- File creation header --->
|
||||
<!-- File creation header -->
|
||||
<created-by>
|
||||
<tool>EnterpriseSitelistManager</tool>
|
||||
<version>10240</version>
|
||||
<date-created>20150728.135021</date-created>
|
||||
</created-by>
|
||||
<!--- Begin Site List --->
|
||||
<!-- Begin Site List -->
|
||||
<site url="www.cpandl.com">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>MSEdge</open-in>
|
||||
</site>
|
||||
<site url="www.woodgrovebank.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="adatum.com">
|
||||
@ -66,14 +66,15 @@ The following is an example of the v.2 version of the Enterprise Mode schema.
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="contoso.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="relecloud.com"/>
|
||||
<compat-mode>default</compat-mode>
|
||||
<open-in>none</open-in>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
<site url="relecloud.com/about">
|
||||
<compat-mode>IE8Enterprise"</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
</site>
|
||||
<site url="contoso.com/travel">
|
||||
<compat-mode>IE7</compat-mode>
|
||||
@ -232,26 +233,26 @@ These v.1 version schema attributes have been deprecated in the v.2 version of t
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th>Deprecated attribute</th>
|
||||
<th>New attribute</th>
|
||||
<th>Deprecated element/attribute</th>
|
||||
<th>New element</th>
|
||||
<th>Replacement example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><forceCompatView></td>
|
||||
<td>forceCompatView</td>
|
||||
<td><compat-mode></td>
|
||||
<td>Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode></td>
|
||||
<td>Replace forceCompatView="true" with <compat-mode>IE7Enterprise</compat-mode></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><docMode></td>
|
||||
<td>docMode</td>
|
||||
<td><compat-mode></td>
|
||||
<td>Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode></td>
|
||||
<td>Replace docMode="IE5" with <compat-mode>IE5</compat-mode></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><doNotTransition></td>
|
||||
<td>doNotTransition</td>
|
||||
<td><open-in></td>
|
||||
<td>Replace <doNotTransition="true"> with <open-in>none</open-in></td>
|
||||
<td>Replace doNotTransition="true" with <open-in>none</open-in></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><domain> and <path></td>
|
||||
@ -259,25 +260,28 @@ These v.1 version schema attributes have been deprecated in the v.2 version of t
|
||||
<td>Replace:
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
<domain exclude="false">contoso.com</domain>
|
||||
<domain>contoso.com</domain>
|
||||
</emie></pre>
|
||||
With:
|
||||
<pre class="syntax">
|
||||
<site url="contoso.com"/>
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site></pre>
|
||||
<b>-AND-</b><p>
|
||||
Replace:
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
<domain exclude="true">contoso.com
|
||||
<path exclude="false" forceCompatView="true">/about</path>
|
||||
<domain exclude="true" doNotTransition="true">
|
||||
contoso.com
|
||||
<path forceCompatView="true">/about</path>
|
||||
</domain>
|
||||
</emie></pre>
|
||||
With:
|
||||
<pre class="syntax">
|
||||
<site url="contoso.com/about">
|
||||
<compat-mode>IE7Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site></pre></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -71,19 +71,19 @@ This is a view of the [raw EMIE v2 schema.xml file](https://gist.github.com/kypf
|
||||
|
||||
```xml
|
||||
<site-list version="205">
|
||||
<!--- File creation header --->
|
||||
<!-- File creation header -->
|
||||
<created-by>
|
||||
<tool>EnterpriseSiteListManager</tool>
|
||||
<version>10586</version>
|
||||
<date-created>20150728.135021</date-created>
|
||||
</created-by>
|
||||
<!--- Begin Site List --->
|
||||
<!-- Begin Site List -->
|
||||
<site url="www.cpandl.com">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="www.woodgrovebank.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="adatum.com">
|
||||
@ -92,8 +92,8 @@ This is a view of the [raw EMIE v2 schema.xml file](https://gist.github.com/kypf
|
||||
</site>
|
||||
<site url="relecloud.com"/>
|
||||
<!-- default for self-closing XML tag is
|
||||
<compat-mode>default</compat-mode>
|
||||
<open-in>none</open-in>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
-->
|
||||
<site url="relecloud.com/products">
|
||||
<compat-mode>IE8Enterprise"</compat-mode>
|
||||
|
||||
@ -14,11 +14,11 @@ ms.sitesec: library
|
||||
ms.date: 07/27/2017
|
||||
---
|
||||
|
||||
# IExpress Wizard command-line options
|
||||
|
||||
**Applies to:**
|
||||
- Windows Server 2008 R2 with SP1
|
||||
|
||||
# IExpress Wizard command-line options
|
||||
Use command-line options with the IExpress Wizard (IExpress.exe) to control your Internet Explorer custom browser package extraction process.
|
||||
|
||||
These command-line options work with IExpress:<br>
|
||||
|
||||
@ -16,7 +16,7 @@
|
||||
## [Install localized version of HoloLens (1st gen)](hololens1-install-localized.md)
|
||||
## [Getting around HoloLens (1st gen)](hololens1-basic-usage.md)
|
||||
|
||||
# Get started with HoloLens in commercial environments
|
||||
# HoloLens in commercial environments
|
||||
## [Commercial feature overview](hololens-commercial-features.md)
|
||||
## [Deployment planning](hololens-requirements.md)
|
||||
## [Unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md)
|
||||
@ -52,14 +52,16 @@
|
||||
## [Environment considerations for HoloLens](hololens-environment-considerations.md)
|
||||
## [Spatial mapping on HoloLens](hololens-spaces.md)
|
||||
|
||||
# Update and recovery
|
||||
## [Join the Windows Insider program](hololens-insider.md)
|
||||
## [Managing HoloLens updates](hololens-updates.md)
|
||||
# Update, troubleshoot, or recover HoloLens
|
||||
## [Update, troubleshoot, or recover HoloLens](hololens-management-overview.md)
|
||||
## [Update HoloLens](hololens-update-hololens.md)
|
||||
## [Restart, reset, or recover](hololens-recovery.md)
|
||||
## [Troubleshoot HoloLens](hololens-troubleshooting.md)
|
||||
## [Known issues](hololens-known-issues.md)
|
||||
## [Frequently asked questions](hololens-faq.md)
|
||||
|
||||
# [Release Notes](hololens-release-notes.md)
|
||||
# [Hololens status](hololens-status.md)
|
||||
# [Give us feedback](hololens-feedback.md)
|
||||
# [Join the Windows Insider program](hololens-insider.md)
|
||||
# [Change history for Microsoft HoloLens documentation](change-history-hololens.md)
|
||||
|
||||
@ -32,6 +32,8 @@ HoloLens 2 prompts a user to calibrate the device under the following circumstan
|
||||
- The user is using the device for the first time
|
||||
- The user previously opted out of the calibration process
|
||||
- The calibration process did not succeed the last time the user used the device
|
||||
- The user has deleted their calibration profiles
|
||||
- The visor is raised and the lowered and any of the above circumstances apply (this may be disabled in **Settings > System > Calibration**.)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -105,13 +105,12 @@ Here are some things you can try saying (remember to say "Hey Cortana" first).
|
||||
- Take a picture.
|
||||
- Start recording. (Starts recording a video.)
|
||||
- Stop recording. (Stops recording a video.)
|
||||
- Call <*contact*>. (Requires Skype.)
|
||||
- What time is it?
|
||||
- Show me the latest NBA scores.
|
||||
- How much battery do I have left?
|
||||
- Tell me a joke.
|
||||
|
||||
Some Cortana features that you're used to from Windows on your PC or phone (for example, reminders and notifications) aren't supported in Microsoft HoloLens Development Edition. Cortana on HoloLens is English-only, and the Cortana experience may vary from one region to another.
|
||||
Some Cortana features that you're used to from Windows on your PC or phone (for example, reminders and notifications) aren't supported in Microsoft HoloLens, and the Cortana experience may vary from one region to another.
|
||||
|
||||
### Turn Cortana off
|
||||
|
||||
|
||||
@ -117,5 +117,5 @@ If someone else is going to be using your HoloLens, they should run the Calibrat
|
||||
|
||||
## See also
|
||||
|
||||
- [Spatial mapping design](https://docs.microsoft.com/windows/mixed-reality/spatial-mapping-design)
|
||||
- [Spatial mapping design](https://docs.microsoft.com/windows/mixed-reality/spatial-mapping)
|
||||
- [Holograms](https://docs.microsoft.com/windows/mixed-reality/hologram)
|
||||
|
||||
@ -55,7 +55,7 @@ If you use [MDM, Microsoft Intune](#set-up-kiosk-mode-using-microsoft-intune-or-
|
||||
|
||||
### Start layout file for MDM (Intune and others)
|
||||
|
||||
Save the following sample as an XML file. You will select this file when you configure the kiosk in Microsoft Intune (or in another MDM service that provides a kiosk profile).
|
||||
Save the following sample as an XML file. You can use this file when you configure the multi-app kiosk in Microsoft Intune (or in another MDM service that provides a kiosk profile).
|
||||
|
||||
>[!NOTE]
|
||||
>If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, use the [Start layout instructions for a provisioning package](#start-layout-for-a-provisioning-package).
|
||||
|
||||
@ -123,15 +123,6 @@ If your device is still unable to load apps, you can sideload a version of the .
|
||||
|
||||
We appreciate your patience as we have gone through the process to get this issue resolved, and we look forward to continued working with our community to create successful Mixed Reality experiences.
|
||||
|
||||
## Connecting to WiFi
|
||||
|
||||
During HoloLens Setup, there is a credential timeout of 2 minutes. The username/password needs to be entered within 2 minutes otherwise the username field will be automatically cleared.
|
||||
|
||||
We recommend using a Bluetooth keyboard for entering long passwords.
|
||||
|
||||
> [!NOTE]
|
||||
> If the wrong network is selected during HoloLens Setup, the device will need to be fully reset. Instructions can be found [here.](hololens-restart-recover.md)
|
||||
|
||||
## Device Update
|
||||
|
||||
- 30 seconds after a new update, the shell may disappear one time. Please perform the **bloom** gesture to resume your session.
|
||||
|
||||
32
devices/hololens/hololens-management-overview.md
Normal file
32
devices/hololens/hololens-management-overview.md
Normal file
@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Update, troubleshoot, or recover HoloLens
|
||||
description:
|
||||
author: Teresa-Motiv
|
||||
ms.author: v-tea
|
||||
ms.date: 11/27/2019
|
||||
ms.prod: hololens
|
||||
ms.topic: article
|
||||
ms.custom: CSSTroubleshooting
|
||||
audience: ITPro
|
||||
keywords: issues, bug, troubleshoot, fix, help, support, HoloLens
|
||||
manager: jarrettr
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Update, troubleshoot, or recover HoloLens
|
||||
|
||||
The articles in this section help you keep your HoloLens up-to-date and help you resolve any issues that you encounter.
|
||||
|
||||
**In this section**
|
||||
|
||||
| Article | Description |
|
||||
| --- | --- |
|
||||
| [Update HoloLens](hololens-update-hololens.md) | Describes how to identify the build number of your device, and how to update your device manually. |
|
||||
| [Manage updates on many HoloLens](hololens-updates.md) | Describes how to use policies to manage device updates. |
|
||||
| [Restart, reset, or recover](hololens-recovery.md) | Describes how to restart, reset, or recover a HoloLens device |
|
||||
| [Troubleshoot HoloLens](hololens-troubleshooting.md) | Describes solutions to common HoloLens problems. |
|
||||
| [Known issues](hololens-known-issues.md) | Describes known HoloLens issues. |
|
||||
| [Frequently asked questions](hololens-faq.md) | Provides answers to common questions about HoloLens.|
|
||||
@ -116,7 +116,7 @@ To use the tool, you’ll need a computer running Windows 10 or later, with at l
|
||||
|
||||
To recover your HoloLens
|
||||
|
||||
1. Download and install the [Windows Device Recovery Tool](https://dev.azure.com/ContentIdea/ContentIdea/_queries/query/8a004dbe-73f8-4a32-94bc-368fc2f2a895/) on your computer.
|
||||
1. Download and install the [Windows Device Recovery Tool](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq) on your computer.
|
||||
1. Connect the HoloLens (1st gen) to your computer using the Micro USB cable that came with your HoloLens.
|
||||
1. Run the Windows Device Recovery Tool and follow the instructions.
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/14/2019
|
||||
ms.date: 12/02/2019
|
||||
audience: ITPro
|
||||
appliesto:
|
||||
- HoloLens 1
|
||||
@ -19,6 +19,15 @@ appliesto:
|
||||
# HoloLens Release Notes
|
||||
|
||||
## HoloLens 2
|
||||
> [!Note]
|
||||
> HoloLens Emulator Release Notes can be found [here](https://docs.microsoft.com/windows/mixed-reality/hololens-emulator-archive).
|
||||
|
||||
### December Update - build 18362.1042
|
||||
|
||||
- Introduces LSR (Last Stage Reproduction) fixes. Improves visual rendering of holograms to appear more stable and crisp by more accurately accounting for their depth. This will be more noticeable if apps do not set the depth of holograms correctly, after this update.
|
||||
- Fixes stability of exclusive apps and navigation between exclusive apps.
|
||||
- Resolves an issue where Mixed Reality Capture couldn't record video after device is left in standby state for multiple days.
|
||||
- Improves hologram stability.
|
||||
|
||||
### November Update - build 18362.1039
|
||||
|
||||
|
||||
92
devices/hololens/hololens-troubleshooting.md
Normal file
92
devices/hololens/hololens-troubleshooting.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
title: HoloLens troubleshooting
|
||||
description: Solutions for common HoloLens issues.
|
||||
author: mattzmsft
|
||||
ms.author: mazeller
|
||||
ms.date: 12/02/2019
|
||||
ms.prod: hololens
|
||||
ms.topic: article
|
||||
ms.custom: CSSTroubleshooting
|
||||
audience: ITPro
|
||||
ms.localizationpriority: medium
|
||||
keywords: issues, bug, troubleshoot, fix, help, support, HoloLens
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Troubleshooting HoloLens issues
|
||||
|
||||
This article describes how to resolve several common HoloLens issues.
|
||||
|
||||
## My HoloLens is unresponsive or won’t start
|
||||
|
||||
If your HoloLens won't start:
|
||||
|
||||
- If the LEDs next to the power button don't light up, or only one LED briefly blinks, you may need to charge your HoloLens.
|
||||
- If the LEDs light up when you press the power button but you can't see anything on the displays, hold the power button until all five of the LEDs turn off.
|
||||
|
||||
If your HoloLens becomes frozen or unresponsive:
|
||||
|
||||
- Turn off your HoloLens by pressing the power button until all five of the LEDs turn themselves off, or for 10 seconds if the LEDs are unresponsive. To start your HoloLens, press the power button again.
|
||||
|
||||
If these steps don't work, you can try [recovering your device](hololens-recovery.md).
|
||||
|
||||
## Holograms don't look good or are moving around
|
||||
|
||||
If your holograms are unstable, jumpy, or don’t look right, try one of these fixes:
|
||||
|
||||
- Clean your device visor and make sure that nothing is obstructing the sensors.
|
||||
- Make sure that there’s enough light in your room.
|
||||
- Try walking around and looking at your surroundings so that HoloLens can scan them more completely.
|
||||
- Try running the Calibration app. It calibrates your HoloLens to work best for your eyes. Go to **Settings** > **System** > **Utilities**. Under **Calibration**, select **Open Calibration**.
|
||||
|
||||
## HoloLens doesn’t respond to my gestures
|
||||
|
||||
To make sure that HoloLens can see your gestures, keep your hand in the gesture frame. The gesture frame extends a couple of feet on either side of you. When HoloLens can see your hand, the cursor changes from a dot to a ring. Learn more about [using gestures](hololens1-basic-usage.md#use-hololens-with-your-hands).
|
||||
|
||||
If your environment is too dark, HoloLens might not see your hand, so make sure that there’s enough light.
|
||||
|
||||
If your visor has fingerprints or smudges, use the microfiber cleaning cloth that came with the HoloLens to clean your visor gently.
|
||||
|
||||
## HoloLens doesn’t respond to my voice commands.
|
||||
|
||||
If Cortana isn’t responding to your voice commands, make sure Cortana is turned on. On the All apps list, select **Cortana** > **Menu** > **Notebook** > **Settings** to make changes. To learn more about what you can say, see [Use your voice with HoloLens](hololens-cortana.md).
|
||||
|
||||
## I can’t place holograms or see holograms that I previously placed
|
||||
|
||||
If HoloLens can’t map or load your space, it enters Limited mode and you won’t be able to place holograms or see holograms that you’ve placed. Here are some things to try:
|
||||
|
||||
- Make sure that there’s enough light in your environment so HoloLens can see and map the space.
|
||||
- Make sure that you’re connected to a Wi-Fi network. If you’re not connected to Wi-Fi, HoloLens can’t identify and load a known space.
|
||||
- If you need to create a new space, connect to Wi-Fi, then restart your HoloLens.
|
||||
- To see if the correct space is active, or to manually load a space, go to **Settings** > **System** > **Spaces**.
|
||||
- If the correct space is loaded and you’re still having problems, the space may be corrupt. To fix this issue, select the space, then select **Remove**. After you remove the space, HoloLens starts to map your surroundings and create a new space.
|
||||
|
||||
## My HoloLens frequently enters Limited mode or shows a “Tracking lost” message
|
||||
|
||||
If your device often shows a "Limited mode" or "Tracking lost" message, try the suggestions listed in [My Holograms don't look good or are moving around](#holograms-dont-look-good-or-are-moving-around).
|
||||
|
||||
## My HoloLens can’t tell what space I’m in
|
||||
|
||||
If your HoloLens can’t identify and load the space you’re in automatically, check the following factors:
|
||||
|
||||
- Make sure that you’re connected to Wi-Fi
|
||||
- Make sure that there’s plenty of light in the room
|
||||
- Make sure that there haven’t been any major changes to the surroundings.
|
||||
|
||||
You can also load a space manually or manage your spaces by going to **Settings** > **System** > **Spaces**.
|
||||
|
||||
## I’m getting a “low disk space” error
|
||||
|
||||
You’ll need to free up some storage space by doing one or more of the following:
|
||||
|
||||
- Delete some unused spaces. Go to **Settings** > **System** > **Spaces**, select a space that you no longer need, and then select **Remove**.
|
||||
- Remove some of the holograms that you’ve placed.
|
||||
- Delete some pictures and videos from the Photos app.
|
||||
- Uninstall some apps from your HoloLens. In the **All apps** list, tap and hold the app you want to uninstall, and then select **Uninstall**.
|
||||
|
||||
## My HoloLens can’t create a new space
|
||||
|
||||
The most likely problem is that you’re running low on storage space. Try one of the [previous tips](#im-getting-a-low-disk-space-error) to free up some disk space.
|
||||
92
devices/hololens/hololens-update-hololens.md
Normal file
92
devices/hololens/hololens-update-hololens.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
title: Update HoloLens
|
||||
description: Check your HoloLens' build number, update, and roll back updates.
|
||||
keywords: how-to, update, roll back, HoloLens, check build, build number
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/27/2019
|
||||
audience: ITPro
|
||||
ms.reviewer:
|
||||
manager: jarrettr
|
||||
appliesto:
|
||||
- HoloLens (1st gen)
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Update HoloLens
|
||||
|
||||
HoloLens uses Windows Update, just like other Windows 10 devices. Your HoloLens will automatically download and install system updates whenever it is plugged-in to power and connected to the Internet, even when it is in standby.
|
||||
|
||||
This article will walk through HoloLens tools for:
|
||||
|
||||
- viewing your current operating system version (build number)
|
||||
- checking for updates
|
||||
- manually updating HoloLens
|
||||
- rolling back to an older update
|
||||
|
||||
## Check your operating system version (build number)
|
||||
|
||||
You can verify the system version number, (build number) by opening the Settings app and selecting **System** > **About**.
|
||||
|
||||
## Check for updates and manually update
|
||||
|
||||
You can check for updates any time in settings. To see available updates and check for new updates:
|
||||
|
||||
1. Open the **Settings** app.
|
||||
1. Navigate to **Update & Security** > **Windows Update**.
|
||||
1. Select **Check for updates**.
|
||||
|
||||
If an update is available, it will start downloading the new version. After the download is complete, select the **Restart Now** button to trigger the installation. If your device is below 40% and not plugged in, restarting will not start installing the update.
|
||||
|
||||
While your HoloLens is installing the update, it will display spinning gears and a progress indicator. Do not turn off your HoloLens during this time. It will restart automatically once it has completed the installation.
|
||||
|
||||
HoloLens applies one update at a time. If your HoloLens is more than one version behind the latest you may need to run through the update process multiple times to get it fully up to date.
|
||||
|
||||
## Go back to a previous version - HoloLens 2
|
||||
|
||||
In some cases, you might want to go back to a previous version of the HoloLens software. You can do this by using the Advanced Recovery Companion to reset your HoloLens to the earlier version.
|
||||
|
||||
> [!NOTE]
|
||||
> Going back to an earlier version deletes your personal files and settings.
|
||||
|
||||
To go back to a previous version of HoloLens 2, follow these steps:
|
||||
|
||||
1. Make sure that you don't have any phones or Windows devices plugged in to your PC.
|
||||
1. On your PC, download the [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from the Microsoft Store.
|
||||
1. Download the [most recent HoloLens 2 release](https://aka.ms/hololens2download).
|
||||
1. When you have finished these downloads, open **File explorer** > **Downloads**. Right-click the zipped folder that you just downloaded, and select **Extract all** > **Extract** to unzip it.
|
||||
1. Connect your HoloLens to your PC using a USB-A to USB-C cable. (Even if you've been using other cables to connect your HoloLens, this one works best.)
|
||||
1. The Advanced Recovery Companion automatically detects your HoloLens. Select the **Microsoft HoloLens** tile.
|
||||
1. On the next screen, select **Manual package selection** and then select the installation file contained in the folder that you unzipped in step 4. (Look for a file with the .ffu extension.)
|
||||
1. Select **Install software**, and follow the instructions.
|
||||
|
||||
## Go back to a previous version - HoloLens (1st Gen)
|
||||
|
||||
In some cases, you might want to go back to a previous version of the HoloLens software. You can do this by using the Windows Device Recovery Tool to reset your HoloLens to the earlier version.
|
||||
|
||||
> [!NOTE]
|
||||
> Going back to an earlier version deletes your personal files and settings.
|
||||
|
||||
To go back to a previous version of HoloLens 1, follow these steps:
|
||||
|
||||
1. Make sure that you don't have any phones or Windows devices plugged in to your PC.
|
||||
1. On your PC, download the [Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379).
|
||||
1. Download the [HoloLens Anniversary Update recovery package](https://aka.ms/hololensrecovery).
|
||||
1. When the downloads finish, open **File explorer** > **Downloads**. Right-click the zipped folder you just downloaded, and select **Extract all** > **Extract** to unzip it.
|
||||
1. Connect your HoloLens to your PC using the micro-USB cable that it came with. (Even if you've been using other cables to connect your HoloLens, this one works best.)
|
||||
1. The WDRT will automatically detect your HoloLens. Select the **Microsoft HoloLens** tile.
|
||||
1. On the next screen, select **Manual package selection** and choose the installation file contained in the folder you unzipped in step 4. (Look for a file with the .ffu extension.)
|
||||
1. Select **Install software**, and follow the instructions.
|
||||
|
||||
> [!NOTE]
|
||||
> If the WDRT doesn't detect your HoloLens, try restarting your PC. If that doesn't work, select **My device was not detected**, select **Microsoft HoloLens**, and then follow the instructions.
|
||||
|
||||
## Windows Insider Program on HoloLens
|
||||
|
||||
Want to see the latest features in HoloLens? If so, join the Windows Insider Program; you'll get access to preview builds of HoloLens software updates before they're available to the general public.
|
||||
|
||||
[Get Windows Insider preview for Microsoft HoloLens](hololens-insider.md).
|
||||
@ -29,15 +29,15 @@ HoloLens 2 supports the following languages. This support includes voice command
|
||||
- German (Germany)
|
||||
- Italian (Italy)
|
||||
- Japanese (Japan)
|
||||
- Spanish (Mexico)
|
||||
- Spanish (Spain)
|
||||
|
||||
Windows Mixed Reality is also available in the following languages. However, this support does not include speech commands or dictation features.
|
||||
HoloLens 2 is also available in the following languages. However, this support does not include speech commands or dictation features.
|
||||
|
||||
- Chinese Traditional (Taiwan and Hong Kong)
|
||||
- Dutch (Netherlands)
|
||||
- Korean (Korea)
|
||||
- Changing language or keyboard
|
||||
|
||||
## Changing language or keyboard
|
||||
|
||||
> [!NOTE]
|
||||
> Your speech and dictation language depends on the Windows display language.
|
||||
|
||||
@ -26,9 +26,9 @@ Before you get started, make sure you have the following available:
|
||||
|
||||
**A network connection**. You'll need to connect your HoloLens to a network to set it up. With HoloLens 2, you can connect with Wi-Fi or by using ethernet (you'll need a USB-C-to-Ethernet adapter). The first time you connect, you'll need an open or password-protected network that doesn't require navigating to a website or using certificates to connect. [Learn more about the websites that HoloLens uses](hololens-offline.md).
|
||||
|
||||
**A Microsoft account**. You'll also need to sign in to HoloLens with a Microsoft account (or with your work account, if your organization owns the device). If you don't have a Microsoft account, go to [account.microsoft.com](http://account.microsoft.com) and set one up for free.
|
||||
**A Microsoft account**. You'll also need to sign in to HoloLens with a Microsoft account (or with your work account, if your organization owns the device). If you don't have a Microsoft account, go to [account.microsoft.com](https://account.microsoft.com) and set one up for free.
|
||||
|
||||
**A safe, well-lit space with no tripping hazards**. [Health and safety info](http://go.microsoft.com/fwlink/p/?LinkId=746661).
|
||||
**A safe, well-lit space with no tripping hazards**. [Health and safety info](https://go.microsoft.com/fwlink/p/?LinkId=746661).
|
||||
|
||||
**The optional comfort accessories** that came with your HoloLens, to help you get the most comfortable fit. [More on fit and comfort](hololens2-setup.md#adjust-fit).
|
||||
|
||||
@ -58,6 +58,10 @@ HoloLens 2 will walk you through the following steps:
|
||||
HoloLens sets your time zone automatically based on information obtained from the Wi-Fi network. After setup finishes, you can change the time zone by using the Settings app.
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> If you progress past the Wi-Fi step and later need to switch to a different network while still in setup, you can press the **Volume Down** and **Power** buttons simultaneously to return to this step if you are running an OS version from October 2019 or later. For earlier versions, you may need to [reset the device](hololens-recovery.md) or restart it in a location where the Wi-Fi network is not available to prevent it from automatically connecting.
|
||||
>
|
||||
> Also note that during HoloLens Setup, there is a credential timeout of two minutes. The username/password needs to be entered within two minutes otherwise the username field will be automatically cleared.
|
||||
|
||||
1. Sign in to your user account. You'll choose between **My work or school owns it** and **I own it**.
|
||||
- When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens automatically enrolls in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available. In that case, you need to [manually enroll HoloLens in device management](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||
|
||||
@ -56,6 +56,8 @@
|
||||
## Overview
|
||||
### [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
|
||||
### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md)
|
||||
### [Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md)
|
||||
|
||||
## Plan
|
||||
### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
@ -111,7 +113,6 @@
|
||||
## Troubleshoot
|
||||
### [Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md)
|
||||
### [Surface Hub SSD replacement](surface-hub-ssd-replacement.md)
|
||||
|
||||
### [Top support solutions for Surface Hub](support-solutions-surface-hub.md)
|
||||
### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
### [Surface Hub Update History](surface-hub-update-history.md)
|
||||
@ -124,6 +125,4 @@
|
||||
### [Surface Hub may install updates and restart outside maintenance hours](surface-hub-installs-updates-and-restarts-outside-maintenance-hours.md)
|
||||
### [General Data Privacy Regulation and Surface Hub](general-data-privacy-regulation-and-surface-hub.md)
|
||||
### [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
|
||||
### [Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md)
|
||||
### [Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md)
|
||||
### [Change history for Surface Hub](change-history-surface-hub.md)
|
||||
|
||||
@ -51,7 +51,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Surface Hub"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -15,130 +15,131 @@ ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Hybrid deployment (Surface Hub)
|
||||
A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub. If you’re using a hybrid deployment, in which your organization has a mix of services, with some hosted on-premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for [Exchange hosted on-premises](#exchange-on-prem), [Exchange hosted online](#exchange-online), Skype for Business on-premises, Skype for Business online, and Skype for Business hybrid. Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use PowerShell (see [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)) to achieve the same end result as documented here, and for other deployment options. You should then use the provided Powershell script to verify your Surface Hub setup. (See [Account Verification Script](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts).)
|
||||
|
||||
>[!NOTE]
|
||||
>In an Exchange hybrid environment, follow the steps for [Exchange on-premises](#exchange-on-prem). To move Exchange objects to Office 365, use the [New-MoveRequest](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-moverequest?view=exchange-ps) cmdlet.
|
||||
A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub. If you’re using a hybrid deployment, in which your organization has a mix of services, with some hosted on-premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for [Exchange hosted on-premises](#exchange-on-premises), [Exchange hosted online](#exchange-online), Skype for Business on-premises, Skype for Business online, and Skype for Business hybrid. Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use PowerShell (see [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)) to achieve the same end result as documented here, and for other deployment options. You should then use the provided Powershell script to verify your Surface Hub setup. (See [Account Verification Script](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts).)
|
||||
|
||||
> [!NOTE]
|
||||
> In an Exchange hybrid environment, follow the steps for [Exchange on-premises](#exchange-on-premises). To move Exchange objects to Office 365, use the [New-MoveRequest](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-moverequest?view=exchange-ps) cmdlet.
|
||||
|
||||
<span id="exchange-on-prem" />
|
||||
## Exchange on-premises
|
||||
|
||||
Use this procedure if you use Exchange on-premises.
|
||||
|
||||
1. For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account. This account will be synced to Office 365.
|
||||
1. For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account. This account will be synced to Office 365.
|
||||
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.<p>
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.<p>
|
||||
|
||||
|
||||
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
>**Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
> **Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
|
||||
- Click **Finish** to create the account.
|
||||
- Click **Finish** to create the account.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Enable the remote mailbox.
|
||||
|
||||
Open your on-premises Exchange Management Shell with administrator permissions, and run this cmdlet.
|
||||
|
||||
2. Enable the remote mailbox.
|
||||
```PowerShell
|
||||
Enable-RemoteMailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
|
||||
```
|
||||
|
||||
Open your on-premises Exchange Management Shell with administrator permissions, and run this cmdlet.
|
||||
> [!NOTE]
|
||||
> If you don't have an on-premises Exchange environment to run this cmdlet, you can make the same changes directly to the Active Directory object for the account.
|
||||
>
|
||||
> msExchRemoteRecipientType = 33
|
||||
>
|
||||
> msExchRecipientDisplayType = -2147481850
|
||||
>
|
||||
> msExchRecipientTypeDetails = 8589934592
|
||||
|
||||
```PowerShell
|
||||
Enable-RemoteMailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
|
||||
```
|
||||
>[!NOTE]
|
||||
>If you don't have an on-premises Exchange environment to run this cmdlet, you can make the same changes directly to the Active Directory object for the account.
|
||||
>
|
||||
>msExchRemoteRecipientType = 33
|
||||
>
|
||||
>msExchRecipientDisplayType = -2147481850
|
||||
>
|
||||
>msExchRecipientTypeDetails = 8589934592
|
||||
3. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Microsoft 365 admin center and verify that the account created in the previous steps has merged to online.
|
||||
|
||||
3. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Microsoft 365 admin center and verify that the account created in the previous steps has merged to online.
|
||||
4. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
|
||||
|
||||
4. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
|
||||
Start a remote PowerShell session on a PC and connect to Microsoft Exchange. Be sure you have the right permissions set to run the associated cmdlets.
|
||||
|
||||
Start a remote PowerShell session on a PC and connect to Microsoft Exchange. Be sure you have the right permissions set to run the associated cmdlets.
|
||||
The next steps will be run on your Office 365 tenant.
|
||||
|
||||
The next steps will be run on your Office 365 tenant.
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 'https://ps.outlook.com/powershell' -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 'https://ps.outlook.com/powershell' -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
```
|
||||
5. Create a new Exchange ActiveSync policy, or use a compatible existing policy.
|
||||
|
||||
5. Create a new Exchange ActiveSync policy, or use a compatible existing policy.
|
||||
After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy or use a compatible existing policy.
|
||||
|
||||
After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy or use a compatible existing policy.
|
||||
Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
|
||||
|
||||
Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—-this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
Once you have a compatible policy, you will need to apply the policy to the device account.
|
||||
|
||||
Once you have a compatible policy, then you will need to apply the policy to the device account.
|
||||
```PowerShell
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
```
|
||||
6. Set Exchange properties.
|
||||
|
||||
6. Set Exchange properties.
|
||||
Setting Exchange properties on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
|
||||
Setting Exchange properties on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse 'This is a Surface Hub room!'
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse 'This is a Surface Hub room!'
|
||||
```
|
||||
7. Connect to Azure AD.
|
||||
|
||||
7. Connect to Azure AD.
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated PowerShell prompt, run the following command:
|
||||
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
8. Assign an Office 365 license.
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
8. Assign an Office 365 license.
|
||||
|
||||
You can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
You can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
|
||||
Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-premises](#skype-for-business-on-premises), or [Skype for Business hybrid](#skype-for-business-hybrid).
|
||||
|
||||
<span id="sfb-online"/>
|
||||
### Skype for Business Online
|
||||
|
||||
To enable Skype for Business online, your tenant users must have Exchange mailboxes (at least one Exchange mailbox in the tenant is required). The following table explains which plans or additional services you need.
|
||||
@ -162,42 +163,42 @@ The following table lists the Office 365 plans and Skype for Business options.
|
||||
|
||||
1. Start by creating a remote PowerShell session from a PC to the Skype for Business online environment.
|
||||
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
|
||||
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
|
||||
If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity ‘HUB01@contoso.com’| fl *registrarpool*
|
||||
```
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity ‘HUB01@contoso.com’| fl *registrarpool*
|
||||
```
|
||||
|
||||
3. Assign Skype for Business license to your Surface Hub account.
|
||||
|
||||
Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) to the device.
|
||||
Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) license to the device.
|
||||
|
||||
- Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
|
||||
- Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
|
||||
|
||||
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
|
||||
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
|
||||
|
||||
- Click the Surface Hub account, and then click the pen icon to edit the account information.
|
||||
- Click the Surface Hub account, and then click the pen icon to edit the account information.
|
||||
|
||||
- Click **Licenses**.
|
||||
- Click **Licenses**.
|
||||
|
||||
- In **Assign licenses**, select Skype for Business (Plan 1) or Skype for Business (Plan 2), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 2 license if you want to use Enterprise Voice on your Surface Hub.
|
||||
- In **Assign licenses**, select Skype for Business (Plan 1) or Skype for Business (Plan 2), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 2 license if you want to use Enterprise Voice on your Surface Hub.
|
||||
|
||||
- Click **Save**.
|
||||
- Click **Save**.
|
||||
|
||||
>[!NOTE]
|
||||
>You can also use the Windows Azure Active Directory Module for Windows Powershell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
> [!NOTE]
|
||||
> You can also use the Windows Azure Active Directory Module for Windows Powershell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
|
||||
For validation, you should be able to use any Skype for Business client (PC, Android, etc.) to sign in to this account.
|
||||
|
||||
@ -205,7 +206,7 @@ For validation, you should be able to use any Skype for Business client (PC, And
|
||||
|
||||
To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run:
|
||||
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
@ -217,181 +218,181 @@ The Surface Hub requires a Skype account of the type `meetingroom`, while a norm
|
||||
|
||||
In Skype for Business Server 2015 hybrid environment, any user that you want in Skype for Business Online must first be created in the on-premises deployment, so that the user account is created in Active Directory Domain Services. You can then move the user to Skype for Business Online. The move of a user account from on-premises to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet. To move a Csmeetingroom object, use the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&mspperror=-2147217396) cmdlet.
|
||||
|
||||
>[!NOTE]
|
||||
>To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
|
||||
> [!NOTE]
|
||||
> To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
|
||||
|
||||
|
||||
## Exchange online
|
||||
|
||||
Use this procedure if you use Exchange online.
|
||||
|
||||
1. Create an email account in Office 365.
|
||||
1. Create an email account in Office 365.
|
||||
|
||||
Start a remote PowerShell session on a PC and connect to Exchange. Be sure you have the right permissions set to run the associated cmdlets.
|
||||
Start a remote PowerShell session on a PC and connect to Exchange. Be sure you have the right permissions set to run the associated cmdlets.
|
||||
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
```
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
```
|
||||
|
||||
2. Set up mailbox.
|
||||
2. Set up a mailbox.
|
||||
|
||||
After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
|
||||
After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
|
||||
|
||||
If you're changing an existing resource mailbox:
|
||||
If you're changing an existing resource mailbox:
|
||||
|
||||
```PowerShell
|
||||
Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
```PowerShell
|
||||
Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
|
||||
If you’re creating a new resource mailbox:
|
||||
If you’re creating a new resource mailbox:
|
||||
|
||||
```PowerShell
|
||||
New-Mailbox -MicrosoftOnlineServicesID 'HUB01@contoso.com' -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
```PowerShell
|
||||
New-Mailbox -MicrosoftOnlineServicesID 'HUB01@contoso.com' -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
|
||||
3. Create Exchange ActiveSync policy.
|
||||
3. Create Exchange ActiveSync policy.
|
||||
|
||||
After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
|
||||
After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
|
||||
|
||||
Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
|
||||
Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, Exchange services on the Surface Hub (mail, calendar, and joining meetings) will not be enabled.
|
||||
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
|
||||
Once you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too.
|
||||
Once you have a compatible policy, you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too.
|
||||
|
||||
```PowerShell
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Regular
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Room
|
||||
$credNewAccount = Get-Credential -Message "Please provide the Surface Hub username and password"
|
||||
Set-Mailbox 'HUB01@contoso.com' -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
|
||||
```
|
||||
```PowerShell
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Regular
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Room
|
||||
$credNewAccount = Get-Credential -Message "Please provide the Surface Hub username and password"
|
||||
Set-Mailbox 'HUB01@contoso.com' -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
|
||||
```
|
||||
|
||||
4. Set Exchange properties.
|
||||
4. Set Exchange properties.
|
||||
|
||||
Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
|
||||
```
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
|
||||
```
|
||||
|
||||
5. Add email address for your on-premises domain account.
|
||||
5. Add an email address for your on-premises domain account.
|
||||
|
||||
For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account.
|
||||
For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account.
|
||||
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
> [!IMPORTANT]
|
||||
> Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
|
||||
- Click **Finish** to create the account.
|
||||
- Click **Finish** to create the account.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Run directory synchronization.
|
||||
6. Run directory synchronization.
|
||||
|
||||
After you've created the account, run a directory synchronization. When it's complete, go to the users page and verify that the two accounts created in the previous steps have merged.
|
||||
After you've created the account, run a directory synchronization. When it's complete, go to the users page and verify that the two accounts created in the previous steps have merged.
|
||||
|
||||
7. Connect to Azure AD.
|
||||
7. Connect to Azure AD.
|
||||
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated PowerShell prompt, run the following command:
|
||||
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect:
|
||||
|
||||
8. Assign an Office 365 license.
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
8. Assign an Office 365 license.
|
||||
|
||||
Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
|
||||
Next, you enable the device account with [Skype for Business Online](#sfb-online), [Skype for Business on-premises](#sfb-onprem), or [Skype for Business hybrid](#sfb-hybrid).
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
|
||||
Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-premises](#skype-for-business-on-premises), or [Skype for Business hybrid](#skype-for-business-hybrid).
|
||||
|
||||
### Skype for Business Online
|
||||
|
||||
In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](#sfb-online).
|
||||
In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](#skype-for-business-online).
|
||||
|
||||
1. Start by creating a remote PowerShell session to the Skype for Business online environment from a PC.
|
||||
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
|
||||
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool
|
||||
'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool
|
||||
'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
|
||||
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity 'HUB01@contoso.com'| fl *registrarpool*
|
||||
```
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity 'HUB01@contoso.com'| fl *registrarpool*
|
||||
```
|
||||
|
||||
10. Assign Skype for Business license to your Surface Hub account
|
||||
|
||||
Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) to the device.
|
||||
Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) license to the device.
|
||||
|
||||
- Sign in as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
|
||||
- Sign in as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
|
||||
|
||||
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
|
||||
- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
|
||||
|
||||
- Click the Surface Hub account, and then click the pen icon to edit the account information.
|
||||
- Click the Surface Hub account, and then click the pen icon to edit the account information.
|
||||
|
||||
- Click **Licenses**.
|
||||
- Click **Licenses**.
|
||||
|
||||
- In **Assign licenses**, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
|
||||
- In **Assign licenses**, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
|
||||
|
||||
- Click **Save**.
|
||||
- Click **Save**.
|
||||
|
||||
>[!NOTE]
|
||||
> You can also use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
> [!NOTE]
|
||||
> You can also use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
|
||||
|
||||
For validation, you should be able to use any Skype for Business client (PC, Android, etc) to sign in to this account.
|
||||
|
||||
<span id="sfb-onprem"/>
|
||||
### Skype for Business on-premises
|
||||
|
||||
To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run:
|
||||
@ -400,7 +401,6 @@ To run this cmdlet, you will need to connect to one of the Skype front-ends. Ope
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
<span id="sfb-hybrid"/>
|
||||
### Skype for Business hybrid
|
||||
|
||||
If your organization has set up [hybrid connectivity between Skype for Business Server and Skype for Business Online](https://technet.microsoft.com/library/jj205403.aspx), the guidance for creating accounts differs from a standard Surface Hub deployment.
|
||||
@ -409,6 +409,5 @@ The Surface Hub requires a Skype account of the type *meetingroom*, while a norm
|
||||
|
||||
In Skype for Business Server 2015 hybrid environment, any user that you want in Skype for Business Online must first be created in the on-premises deployment, so that the user account is created in Active Directory Domain Services. You can then move the user to Skype for Business Online. The move of a user account from on-premises to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet. To move a Csmeetingroom object, use the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&mspperror=-2147217396) cmdlet.
|
||||
|
||||
>[!NOTE]
|
||||
>To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
|
||||
|
||||
> [!NOTE]
|
||||
> To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
|
||||
|
||||
@ -30,6 +30,7 @@ Surface Hub 2S is an all-in-one digital interactive whiteboard, meetings platfor
|
||||
<p><a href="https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Behind-the-design-Surface-Hub-2S/ba-p/464099" target="_blank">Behind the design: Surface Hub 2S</a></p>
|
||||
<p><a href="surface-hub-2s-whats-new.md">What's new in Surface Hub 2S</a></p>
|
||||
<p><a href="differences-between-surface-hub-and-windows-10-enterprise.md">Operating system essentials</a></p>
|
||||
<p><a href="https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d">Enable Microsoft Whiteboard on Surface Hub</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -117,9 +117,9 @@ The following tables include info on Windows 10 settings that have been validate
|
||||
| Allow Do Not Track | Use to enable Do Not Track headers. | [Browser/AllowDoNotTrack](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDoNotTrack) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow pop-ups | Use to block pop-up browser windows. | [Browser/AllowPopups](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowPopups) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow search suggestions | Use to block search suggestions in the address bar. | [Browser/AllowSearchSuggestionsinAddressBar](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSearchSuggestionsinAddressBar) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow SmartScreen | Keep this enabled to turn on SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | 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 <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | 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 <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Allow Windows Defender SmartScreen | Keep this enabled to turn on Windows Defender SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Prevent ignoring Windows Defender SmartScreen warnings for websites | For extra security, use to stop users from ignoring Windows Defender SmartScreen warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Prevent ignoring Windows Defender SmartScreen warnings for files | For extra security, use to stop users from ignoring Windows Defender SmartScreen 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 <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
|
||||
|
||||
@ -90,7 +90,7 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -PasswordPolicies "DisablePasswordExpiration"
|
||||
```
|
||||
|
||||
7. Surface Hub requires a license for Skype for Business functionality. In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](hybrid-deployment-surface-hub-device-accounts.md#sfb-online).
|
||||
7. Surface Hub requires a license for Skype for Business functionality. In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](hybrid-deployment-surface-hub-device-accounts.md#skype-for-business-online).
|
||||
|
||||
Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
@ -124,13 +124,13 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
- Next, if you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet (for example, <em>alice@contoso.com</em>):
|
||||
|
||||
```PowerShell
|
||||
(Get-CsTenant).TenantPoolExtension
|
||||
Get-CsOnlineUser -Identity 'alice@contoso.com' | fl registrarpool
|
||||
```
|
||||
OR by setting a variable
|
||||
|
||||
```PowerShell
|
||||
$strRegistrarPool = (Get-CsTenant).TenantPoolExtension
|
||||
$strRegistrarPool = $strRegistrarPool[0].Substring($strRegistrarPool[0].IndexOf(':') + 1)
|
||||
$strRegistrarPool = Get-CsOnlineUser -Identity 'alice@contoso.com' | fl registrarpool | out-string
|
||||
$strRegistrarPool = $strRegistrarPool.Substring($strRegistrarPool.IndexOf(':') + 2)
|
||||
```
|
||||
|
||||
- Enable the Surface Hub account with the following cmdlet:
|
||||
|
||||
@ -54,25 +54,26 @@ Instead of using the Microsoft Admin Center portal, you can create the account u
|
||||
|
||||
### Connect to Exchange Online PowerShell
|
||||
|
||||
```
|
||||
$365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential (Get-Credential) -Authentication Basic –AllowRedirection $ImportResults = Import-PSSession $365Session
|
||||
```powershell
|
||||
$365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential (Get-Credential) -Authentication Basic –AllowRedirection
|
||||
$ImportResults = Import-PSSession $365Session
|
||||
```
|
||||
|
||||
### Create a new Room Mailbox
|
||||
|
||||
```
|
||||
```powershell
|
||||
New-Mailbox -MicrosoftOnlineServicesID account@YourDomain.com -Alias SurfaceHub2S -Name SurfaceHub2S -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String "<Enter Strong Password>" -AsPlainText -Force)
|
||||
```
|
||||
|
||||
### Set Calendar Auto processing
|
||||
|
||||
```
|
||||
```powershell
|
||||
Set-CalendarProcessing -Identity "account@YourDomain.com" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This room is equipped with a Surface Hub"
|
||||
```
|
||||
|
||||
### Assign a license
|
||||
|
||||
```
|
||||
```powershell
|
||||
Connect-MsolService
|
||||
Set-Msoluser -UserPrincipalName account@YourDomain.com -UsageLocation IE
|
||||
Set-MsolUserLicense -UserPrincipalName "account@YourDomain.com" -AddLicenses "contoso:MEETING_ROOM"
|
||||
@ -85,10 +86,11 @@ Set-MsolUserLicense -UserPrincipalName "account@YourDomain.com" -AddLicenses "co
|
||||
- [Visual C++ 2017 Redistributable](https://aka.ms/vs/15/release/vc_redist.x64.exe)
|
||||
- [Skype for Business Online PowerShell Module](https://www.microsoft.com/download/confirmation.aspx?id=39366)
|
||||
|
||||
```
|
||||
```powershell
|
||||
Import-Module LyncOnlineConnector
|
||||
$SfBSession = New-CsOnlineSession -Credential (Get-Credential)
|
||||
Import-PSSession $SfBSession -AllowClobber
|
||||
Enable the Skype for Business meeting room
|
||||
|
||||
# Enable the Skype for Business meeting room
|
||||
Enable-CsMeetingRoom -Identity account@YourDomain.com -RegistrarPool(Get-CsTenant).Registrarpool -SipAddressType EmailAddress
|
||||
```
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: greglin
|
||||
manager: laurawi
|
||||
audience: Admin
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.date: 12/05/2019
|
||||
ms.localizationpriority: Medium
|
||||
---
|
||||
|
||||
@ -38,13 +38,15 @@ New in Surface Hub 2S, you can now reinstall the device using a recovery image.
|
||||
Surface Hub 2S lets you reinstall the device using a recovery image, which allows you to reinstall the device to factory settings if you lost the Bitlocker key or no longer have admin credentials to the Settings app.
|
||||
|
||||
1. Begin with a USB 3.0 drive with 8 GB or 16 GB of storage, formatted as FAT32.
|
||||
2. Download recovery image from the [Surface Recovery website](https://support.microsoft.com/en-us/surfacerecoveryimage?devicetype=surfacehub2s) onto the USB drive and connect it to any USB-C or USB A port on Surface Hub 2S.
|
||||
3. Turn off the device. While holding down the Volume down button, press the Power button. Keep holding both buttons until you see the Windows logo. Release the Power button but continue to hold the Volume until the Install UI begins.
|
||||
2. From a separate PC, download the .zip file recovery image from the [Surface Recovery website](https://support.microsoft.com/surfacerecoveryimage?devicetype=surfacehub2s) and then return to these instructions.
|
||||
3. Unzip the downloaded file onto the root of the USB drive.
|
||||
4. Connect the USB drive to any USB-C or USB-A port on Surface Hub 2S.
|
||||
5. Turn off the device. While holding down the Volume down button, press the Power button. Keep holding both buttons until you see the Windows logo. Release the Power button but continue to hold the Volume until the Install UI begins.
|
||||
|
||||
 <br>
|
||||
|
||||
4. In the language selection screen, select the display language for your Surface Hub 2S.
|
||||
5. Choose **Recover from a drive** and **Fully clean the drive** and then select **Recover**. If prompted for a BitLocker key, select **Skip this drive**. Surface Hub 2S reboots several times and takes approximately 30 minutes to complete the recovery process.
|
||||
6. In the language selection screen, select the display language for your Surface Hub 2S.
|
||||
7. Choose **Recover from a drive** and **Fully clean the drive** and then select **Recover**. If prompted for a BitLocker key, select **Skip this drive**. Surface Hub 2S reboots several times and takes approximately 30 minutes to complete the recovery process.
|
||||
Remove the USB drive when the first time setup screen appears.
|
||||
|
||||
## Recover a locked Surface Hub
|
||||
|
||||
@ -7,7 +7,7 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 06/20/2019
|
||||
ms.date: 11/27/2019
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
@ -25,7 +25,7 @@ The intended audiences for this topic include IT and network administrators inte
|
||||
|
||||
Microsoft Surface Hub's security depends extensively on Wi-Fi Direct / Miracast and the associated 802.11, Wi-Fi Protected Access (WPA2), and Wireless Protected Setup (WPS) standards. Since the device only supports WPS (as opposed to WPA2 Pre-Shared Key (PSK) or WPA2 Enterprise), issues traditionally associated with 802.11 encryption are simplified by design.
|
||||
|
||||
It is important to note Surface Hub operates on par with the field of Miracast receivers, meaning that it is protected from, and vulnerable to, a similar set of exploits as all WPS-based wireless network devices. But Surface Hub’s implementation of WPS has extra precautions built in, and its internal architecture helps prevent an attacker – even after compromising the Wi-Fi Direct / Miracast layer – to move past the network interface onto other attack surfaces and connected enterprise networks see [Wi-Fi Direct vulnerabilities and how Surface Hub addresses them](#vulnerabilities).
|
||||
It is important to note Surface Hub operates on par with the field of Miracast receivers, meaning that it is protected from, and vulnerable to, a similar set of exploits as all WPS-based wireless network devices. But Surface Hub’s implementation of WPS has extra precautions built in, and its internal architecture helps prevent an attacker – even after compromising the Wi-Fi Direct / Miracast layer – to move past the network interface onto other attack surfaces and connected enterprise networks.
|
||||
|
||||
## Wi-Fi Direct background
|
||||
|
||||
@ -37,7 +37,7 @@ Security for Wi-Fi Direct is provided by WPA2 using the WPS standard. Authentic
|
||||
|
||||
In Wi-Fi Direct, groups are created as either "persistent," allowing for automatic reconnection using stored key material, or "temporary," where devices cannot re-authenticate without user intervention or action. Wi-Fi Direct groups will typically determine a Group Owner (GO) through a negotiation protocol, which mimics the "station" or "Access Point" functionality for the established Wi-Fi Direct Group. This Wi-Fi Direct GO provides authentication (via an “Internal Registrar”), and facilitate upstream network connections. For Surface Hub, this GO negotiation does not take place, as the network only operates in "autonomous" mode, where Surface Hub is always the Group Owner. Finally, Surface Hub does not and will not join other Wi-Fi Direct networks itself as a client.
|
||||
|
||||
<span id="vulnerabilities" />
|
||||
|
||||
## Wi-Fi Direct vulnerabilities and how Surface Hub addresses them
|
||||
|
||||
**Vulnerabilities and attacks in the Wi-Fi Direct invitation, broadcast, and discovery process**: Wi-Fi Direct / Miracast attacks may target weaknesses in the group establishment, peer discovery, device broadcast, or invitation processes.
|
||||
|
||||
@ -34,9 +34,7 @@ Beginning in version 1802, Endpoint Configuration Manager includes client manage
|
||||
|
||||
## Updating Surface device drivers and firmware
|
||||
|
||||
For devices that receive updates through Windows Update, drivers for Surface components – and even firmware updates – are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS), the option to install drivers and firmware through Windows Update is not available. For these managed devices, the recommended driver management process is the deployment of driver and firmware updates using the Windows Installer (.msi) files, which are provided through the Microsoft Download Center. You can find a list of these downloads at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices).
|
||||
|
||||
As .msi files, deployment of driver and firmware updates is performed in the same manner as deployment of an application. Instead of installing an application as would normally happen when an .msi file is run, the Surface driver and firmware .msi will apply the driver and firmware updates to the device. The single .msi file contains the driver and firmware updates required by each component of the Surface device. The updates for firmware are applied the next time the device reboots. You can read more about the .msi installation method for Surface drivers and firmware in [Manage Surface driver and firmware updates](https://technet.microsoft.com/itpro/surface/manage-surface-pro-3-firmware-updates). For more information about how to deploy applications with Configuration Manager, see [Packages and programs in Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/packages-and-programs).
|
||||
For devices receiving updates through Windows Update, drivers for Surface components—and even firmware updates—are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS) or SCCM, see [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-driver-and-firmware-updates/).
|
||||
|
||||
>[!NOTE]
|
||||
>Surface device drivers and firmware are signed with SHA-256, which is not natively supported by Windows Server 2008 R2. A workaround is available for Configuration Manager environments running on Windows Server 2008 R2 – for more information see [Can't import drivers into System Center Configuration Manager (KB3025419)](https://support.microsoft.com/kb/3025419).
|
||||
@ -86,4 +84,3 @@ To apply an asset tag using the [Surface Asset Tag CLI Utility](https://www.micr
|
||||
When you deploy Windows to a Surface device, the push-button reset functionality of Windows is configured by default to revert the system back to a state where the environment is not yet configured. When the reset function is used, the system discards any installed applications and settings. Although in some situations it can be beneficial to restore the system to a state without applications and settings, in a professional environment this effectively renders the system unusable to the end user.
|
||||
|
||||
Push-button reset can be configured, however, to restore the system configuration to a state where it is ready for use by the end user. Follow the process outlined in [Deploy push-button reset features](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/deploy-push-button-reset-features) to customize the push-button reset experience for your devices.
|
||||
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Deploy the latest firmware and drivers for Surface devices (Surface)
|
||||
description: This article provides a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.
|
||||
ms.assetid: 7662BF68-8BF7-43F7-81F5-3580A770294A
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.reviewer: dansimp
|
||||
manager: kaushika
|
||||
keywords: update Surface, newest, latest, download, firmware, driver, tablet, hardware, device
|
||||
ms.localizationpriority: medium
|
||||
ms.prod: w10
|
||||
@ -12,70 +12,94 @@ ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.audience: itpro
|
||||
ms.date: 10/21/2019
|
||||
ms.date: 11/25/2019
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Deploy the latest firmware and drivers for Surface devices
|
||||
Although Surface devices are typically automatically updated with the latest device drivers and firmware via Windows Update, sometimes it's necessary to download and install updates manually, such as during a Windows deployment.
|
||||
|
||||
## Download MSI files
|
||||
To download MSI files, refer to the following Microsoft Support page:
|
||||
> **Home users:** This article is only intended for technical support agents and IT professionals, and applies only to Surface devices. If you're looking for help to install Surface updates or firmware on a home device, please see [Update Surface firmware and Windows 10](https://support.microsoft.com/help/4023505).
|
||||
|
||||
- [Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware-for-surface)<br>
|
||||
Installation files for administrative tools, drivers for accessories, and updates for Windows are also available for some devices.
|
||||
Under typical conditions, Windows Update automatically keeps Windows Surface devices up-to-date by downloading and installing the latest device drivers and firmware. However, you may sometimes have to download and install updates manually. For example, you may have to manually manage updates when you deploy a new version of Windows.
|
||||
|
||||
## Downloading MSI files
|
||||
|
||||
[Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware-for-surface) provides links to download installation files for the following:
|
||||
|
||||
- Administrative tools
|
||||
- Drivers for accessories
|
||||
- For some devices, updates for Windows
|
||||
|
||||
## Deploying MSI files
|
||||
Driver and firmware updates for Surface devices consisting of all required cumulative updates are packaged in separate MSI files for specific versions of Windows 10.
|
||||
|
||||
The MSI file names contain useful information including the minimum supported Windows build number required to install the drivers and firmware. For example, to install the drivers contained in SurfaceBook_Win10_17763_19.080.2031.0.msi requires Windows 10 Fall Creators Update version 1709 or later installed on your Surface Book.
|
||||
Specific versions of Windows 10 have separate MSI files. Each MSI file contains all required cumulative driver and firmware updates for Surface devices.
|
||||
|
||||
To view build numbers for each version, refer to [Windows 10 release information](https://docs.microsoft.com/windows/windows-10/release-information).
|
||||
The MSI file names contain useful information, including the minimum supported Windows build number that is required to install the drivers and firmware. For example, to install the drivers that are contained in SurfaceBook_Win10_17763_19.080.2031.0.msi on a Surface Book, the device must be running Windows 10 Fall Creators Update, version 1709 or later.
|
||||
|
||||
For more information about build numbers for each Windows version, see [Windows 10 release information](https://docs.microsoft.com/windows/windows-10/release-information).
|
||||
|
||||
### Surface MSI naming convention
|
||||
Beginning in August 2019, MSI files use the following naming formula:
|
||||
|
||||
- Product > Windows release > Windows build number > Version number > Revision of version number (typically zero).
|
||||
Beginning in August, 2019, MSI files have used the following naming convention:
|
||||
|
||||
**Example:**
|
||||
SurfacePro6_Win10_18362_19.073.44195_0.msi :
|
||||
> *Product*\_*Windows release*\_*Windows build number*\_*Version number*\_*Revision of version number (typically zero)*.
|
||||
|
||||
| Product | Windows release | Build | Version | Revision of version |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| SurfacePro6 | Win10 | 18362 | 19.073.44195 | 0 |
|
||||
| | | | Indicates key date and sequence information. | Indicates release history of the update. |
|
||||
| | | | **19:** Signifies the year (2019).<br>**073**: Signifies the month (July) and week of the release (3). <br>**44195**: Signifies the minute of the month that the MSI file was created. |**0:** Signifies it's the first release of version 1907344195 and has not been re-released for any reason. |
|
||||
**Example**
|
||||
|
||||
Consider the following MSI file:
|
||||
|
||||
> SurfacePro6_Win10_18362_19.073.44195_0.msi
|
||||
|
||||
This file name provides the following information:
|
||||
|
||||
- **Product:** SurfacePro6
|
||||
- **Windows release:** Win10
|
||||
- **Build:** 18362
|
||||
- **Version:** 19.073.44195 – This shows the date and time that the file was created, as follows:
|
||||
- **Year:** 19 (2019)
|
||||
- **Month and week:** 073 (third week of July)
|
||||
- **Minute of the month:** 44195
|
||||
- **Revision of version:** 0 (first release of this version)
|
||||
|
||||
### Legacy Surface MSI naming convention
|
||||
Legacy MSI files prior to August 2019 followed the same overall naming formula but used a different method to derive the version number.
|
||||
|
||||
**Example:**
|
||||
SurfacePro6_Win10_16299_1900307_0.msi :
|
||||
Legacy MSI files (files that were built before August, 2019) followed the same overall naming formula, but used a different method to derive the version number.
|
||||
|
||||
| Product | Windows release | Build | Version | Revision of version |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| SurfacePro6 | Win10 | 16299 | 1900307 | 0 |
|
||||
| | | | Indicates key date and sequence information. | Indicates release history of the MSI file. |
|
||||
| | | | **19:** Signifies the year (2019)<br>**003**: Signifies that it’s the third release of 2019.<br>**07**: Signifies the product version number. (Surface Pro 6 is officially the seventh version of Surface Pro.) | **0:** Signifies it's the first release of version 1900307 and has not been re-released for any reason. |
|
||||
**Example**
|
||||
|
||||
Look to the **version** number to determine the latest files that contain the most recent security updates. For example, you might need to install the newest file from the following list:
|
||||
Consider the following MSI file:
|
||||
|
||||
> SurfacePro6_Win10_16299_1900307_0.msi
|
||||
|
||||
This file name provides the following information:
|
||||
|
||||
- **Product:** SurfacePro6
|
||||
- **Windows release:** Win10
|
||||
- **Build:** 16299
|
||||
- **Version:** 1900307 – This shows the date that the file was created and its position in the release sequence, as follows:
|
||||
- **Year:** 19 (2019)
|
||||
- **Number of release:** 003 (third release of the year)
|
||||
- **Product version number:** 07 (Surface Pro 6 is officially the seventh version of Surface Pro)
|
||||
- **Revision of version:** 0 (first release of this version)
|
||||
|
||||
Use the **version** number to determine the latest files that contain the most recent security updates. For example, consider the following list:
|
||||
|
||||
- SurfacePro6_Win10_16299_1900307_0.msi
|
||||
- SurfacePro6_Win10_17134_1808507_3.msi
|
||||
- SurfacePro6_Win10_17763_1808707_3.msi
|
||||
|
||||
The first file — SurfacePro6_Win10_16299_1900307_0.msi — is the newest because its VERSION field has the newest build in 2019; the other files are from 2018.
|
||||
In this list, the newest file is the first file (SurfacePro6_Win10_16299_1900307_0.msi). Its **Version** field has the newest date (2019). The other files are from 2018.
|
||||
|
||||
## Supported devices
|
||||
Downloadable MSI files are available for Surface devices from Surface Pro 2 and later. Information about MSI files for the newest Surface devices such as Surface Pro 7, Surface Pro X, and Surface Laptop 3 will be available from this page upon release.
|
||||
|
||||
>[!NOTE]
|
||||
>There are no downloadable firmware or driver updates available for Surface devices with Windows RT, including Surface RT and Surface 2. Updates can only be applied using Windows Update.
|
||||
For downloadable MSI files for devices that run Surface Pro 2 and later versions, see [Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware-for-surface). This article contains information about MSI files for the newest Surface devices such as Surface Pro 7, Surface Pro X, and Surface Laptop 3, as they are released.
|
||||
|
||||
For more information about deploying Surface drivers and firmware, refer to:
|
||||
> [!NOTE]
|
||||
> There are no downloadable firmware or driver updates available for Surface devices that run Windows RT, including Surface RT and Surface 2. To update these devices, use Windows Update.
|
||||
|
||||
For more information about how to deploy Surface drivers and firmware, see the following articles:
|
||||
|
||||
- [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-pro-3-firmware-updates)
|
||||
|
||||
- [Microsoft Surface support for business](https://www.microsoft.com/surface/support/business)
|
||||
- [Surface for Business help](https://www.microsoft.com/surface/support/business)
|
||||
|
||||
@ -47,7 +47,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Surface"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -19,6 +19,9 @@ ms.audience: itpro
|
||||
|
||||
# Top support solutions for Surface devices
|
||||
|
||||
> [!Note]
|
||||
> **Home users**: This article is only intended for use by IT professionals and technical support agents, and applies only to Surface devices. If you're looking for help with a problem with your home device, please see [Surface Devices Help](https://support.microsoft.com/products/surface-devices).
|
||||
|
||||
Microsoft regularly releases both updates and solutions for Surface devices. To ensure your devices can receive future updates, including security updates, it's important to keep your Surface devices updated. For a complete listing of the update history, see [Surface update history](https://www.microsoft.com/surface/support/install-update-activate/surface-update-history) and [Install Surface and Windows updates](https://www.microsoft.com/surface/support/performance-and-maintenance/install-software-updates-for-surface?os=windows-10&=undefined).
|
||||
|
||||
|
||||
|
||||
@ -50,6 +50,9 @@ You can use Windows Installer commands (Msiexec.exe) to deploy Surface Dock Firm
|
||||
> [!NOTE]
|
||||
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]"
|
||||
|
||||
> [!NOTE]
|
||||
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]"
|
||||
|
||||
For more information, refer to [Command line options](https://docs.microsoft.com/windows/win32/msi/command-line-options) documentation.
|
||||
|
||||
> [!IMPORTANT]
|
||||
@ -89,9 +92,9 @@ Successful completion of Surface Dock Firmware Update results in new registry ke
|
||||
**Table 1. Log files for Surface Dock Firmware Update**
|
||||
|
||||
| Log | Location | Notes |
|
||||
| -------------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Surface Dock Firmware Update log | /l*v %windir%\logs\ SurfaceDockFWI.log | |
|
||||
| Windows Device Install log | %windir%\inf\setupapi.dev.log | For more information about using Device Install Log, refer to [SetupAPI Logging](https://docs.microsoft.com/windows-hardware/drivers/install/setupapi-logging--windows-vista-and-later-). |
|
||||
| -------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Surface Dock Firmware Update log | Path needs to be specified (see note) | Earlier versions of this tool wrote events to Applications and Services Logs\Microsoft Surface Dock Updater. |
|
||||
| Windows Device Install log | %windir%\inf\setupapi.dev.log | For more information about using Device Install Log, refer to [SetupAPI Logging](https://docs.microsoft.com/windows-hardware/drivers/install/setupapi-logging--windows-vista-and-later-) documentation. |
|
||||
|
||||
|
||||
**Table 2. Event log IDs for Surface Dock Firmware Update**<br>
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 11/20/2019
|
||||
ms.date: 12/02/2019
|
||||
ms.reviewer: scottmca
|
||||
manager: dansimp
|
||||
ms.localizationpriority: medium
|
||||
@ -90,7 +90,7 @@ The following list shows all the available devices you can manage in SEMM:
|
||||
| Alternate Boot | Allows you to manage use of an Alternate boot order to boot directly to a USB or Ethernet device by pressing both the Volume Down button and Power button during boot. If you do not configure this setting, Alternate boot is enabled. |
|
||||
| Boot Order Lock | Allows you to lock the boot order to prevent changes. If you do not configure this setting, Boot Order Lock is disabled. |
|
||||
| USB Boot | Allows you to manage booting to USB devices. If you do not configure this setting, USB Boot is enabled. |
|
||||
| Network Stack | Allows you to manage Network Stack boot settings. If you do not configure this setting, the ability to manage Network Stack boot settings is enabled. |
|
||||
| Network Stack | Allows you to manage Network Stack boot settings. If you do not configure this setting, the ability to manage Network Stack boot settings is disabled. |
|
||||
| Auto Power On | Allows you to manage Auto Power On boot settings. If you do not configure this setting, Auto Power on is enabled. |
|
||||
| Simultaneous Multi-Threading (SMT) | Allows you to manage Simultaneous Multi-Threading (SMT) to enable or disable hyperthreading. If you do not configure this setting, SMT is enabled. |
|
||||
|Enable Battery limit| Allows you to manage Battery limit functionality. If you do not configure this setting, Battery limit is enabled |
|
||||
|
||||
@ -24,6 +24,9 @@ System Model and System SKU are variables that are stored in the System Manageme
|
||||
|
||||
| Device | System Model | System SKU |
|
||||
| ---------- | ----------- | -------------- |
|
||||
| AMD Surface Laptop 3 | Surface 3 | Surface_Laptop_3_1873 |
|
||||
| Surface Laptop 3 | Surface 3 | Surface_Laptop_3_1867:1868 |
|
||||
| Surface Laptop 3 | Surface 3 | Surface_3
|
||||
| Surface 3 WiFI | Surface 3 | Surface_3 |
|
||||
| Surface 3 LTE AT&T | Surface 3 | Surface_3_US1 |
|
||||
| Surface 3 LTE Verizon | Surface 3 | Surface_3_US2 |
|
||||
|
||||
@ -1617,7 +1617,7 @@ As a final quality control step, verify the device configuration to ensure that
|
||||
* The device can connect to the Internet and view the appropriate web content in Microsoft Edge.
|
||||
* Windows Update is active and current with software updates.
|
||||
* Windows Defender is active and current with malware Security intelligence.
|
||||
* The SmartScreen Filter is active.
|
||||
* Windows Defender SmartScreen is active.
|
||||
* All Microsoft Store apps are properly installed and updated.
|
||||
* All Windows desktop apps are properly installed and updated.
|
||||
* Printers are properly configured.
|
||||
|
||||
@ -1096,7 +1096,7 @@ As a final quality control step, verify the device configuration to ensure that
|
||||
- The device can connect to the Internet and view the appropriate web content in Microsoft Edge.
|
||||
- Windows Update is active and current with software updates.
|
||||
- Windows Defender is active and current with malware Security intelligence.
|
||||
- The SmartScreen Filter is active.
|
||||
- Windows Defender SmartScreen is active.
|
||||
- All Microsoft Store apps are properly installed and updated.
|
||||
- All Windows desktop apps are properly installed and updated.
|
||||
- Printers are properly configured.
|
||||
|
||||
@ -19,7 +19,7 @@ Microsoft Advanced Group Policy Management (AGPM) extends the capabilities of th
|
||||
## AGPM Version Information
|
||||
|
||||
|
||||
[AGPM 4.0 SP3](agpm-40-sp3-navengl.md) supports Windows 10, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
|
||||
[AGPM 4.0 SP3](agpm-40-sp3-navengl.md) supports Windows 10, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
|
||||
|
||||
[AGPM 4.0 SP2](agpm-40-sp2-navengl.md) supports Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
|
||||
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
---
|
||||
ms.reviewer:
|
||||
title: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
description: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
---
|
||||
ms.reviewer:
|
||||
title: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
description: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
|
||||
@ -49,7 +49,7 @@ The following items are required or recommended for creating the DaRT recovery i
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Debugging Tools for your platform</p></td>
|
||||
<td align="left"><p>Required when you run the <strong>Crash Analyzer</strong> to determine the cause of a computer failure. We recommend that you specify the path of the Windows Debugging Tools at the time that you create the DaRT recovery image. You can download the Windows Debugging Tools here: <a href="https://go.microsoft.com/fwlink/?LinkId=99934" data-raw-source="[Download and Install Debugging Tools for Windows](https://go.microsoft.com/fwlink/?LinkId=99934)">Download and Install Debugging Tools for Windows</a>.</p></td>
|
||||
<td align="left"><p>Required when you run the <strong>Crash Analyzer</strong> to determine the cause of a computer failure. We recommend that you specify the path of the Windows Debugging Tools at the time that you create the DaRT recovery image. You can download the Windows Debugging Tools here: <a href="https://docs.microsoft.com/windows-hardware/drivers/debugger/" data-raw-source="[Download and Install Debugging Tools for Windows](https://docs.microsoft.com/windows-hardware/drivers/debugger/)">Download and Install Debugging Tools for Windows</a>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Optional: Windows symbols files for use with <strong>Crash Analyzer</strong></p></td>
|
||||
@ -62,7 +62,6 @@ The following items are required or recommended for creating the DaRT recovery i
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning to Deploy DaRT 10](planning-to-deploy-dart-10.md)
|
||||
|
||||
|
||||
@ -72,4 +71,3 @@ The following items are required or recommended for creating the DaRT recovery i
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -51,7 +51,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Microsoft Desktop Optimization Pack"
|
||||
},
|
||||
"externalReference": [],
|
||||
"template": "op.html",
|
||||
|
||||
@ -47,7 +47,8 @@
|
||||
"jborsecnik",
|
||||
"tiburd",
|
||||
"garycentric"
|
||||
]
|
||||
],
|
||||
"titleSuffix": "Windows for Small to Midsize Business"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Allow Only Administrators to Enable Connection Groups (Windows 10)
|
||||
title: Only Allow Admins to Enable Connection Groups (Windows 10)
|
||||
description: How to Allow Only Administrators to Enable Connection Groups
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to apply the deployment configuration file by using Windows PowerShell (Windows 10)
|
||||
title: Apply deployment config file via Windows PowerShell (Windows 10)
|
||||
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10.
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Automatically clean up unpublished packages on the App-V client (Windows 10)
|
||||
title: Auto-remove unpublished packages on App-V client (Windows 10)
|
||||
description: How to automatically clean up any unpublished packages on your App-V client devices.
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
title: Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
description: How to Install the App-V Publishing Server on a Remote Computer
|
||||
author: lomayor
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -42,7 +42,8 @@
|
||||
"depot_name": "MSDN.win-app-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Windows Application Management"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
|
||||
@ -46,15 +46,22 @@ Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-gu
|
||||
>
|
||||
>`net localgroup "Remote Desktop Users" /add "AzureAD\the-UPN-attribute-of-your-user"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD.
|
||||
>
|
||||
> This command only works for AADJ device users already added to any of the local groups (administrators).
|
||||
> Otherwise this command throws the below error. For example: </br>
|
||||
> for cloud only user: "There is no such global user or group : *name*" </br>
|
||||
> for synced user: "There is no such global user or group : *name*" </br>
|
||||
>
|
||||
>In Windows 10, version 1709, the user does not have to sign in to the remote device first.
|
||||
>
|
||||
>In Windows 10, version 1709, you can add other Azure AD users to the **Administrators** group on a device in **Settings** and restrict remote credentials to **Administrators**. If there is a problem connecting remotely, make sure that both devices are joined to Azure AD and that TPM is functioning properly on both devices.
|
||||
|
||||
4. Enter **Authenticated Users**, then click **Check Names**. If the **Name Not Found** window opens, click **Locations** and select this PC.
|
||||
|
||||
>[!TIP]
|
||||
>When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
|
||||
> [!TIP]
|
||||
> When you connect to the remote PC, enter your account name in this format: `AzureAD UPN`. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.
|
||||
|
||||
> [!Note]
|
||||
> If you cannot connect using Remote Desktop Connection 6.0, then you must turn off new features of RDP 6.0 and revert back to RDP 5.0 by changing a few changes in the RDP file. See the details in the [support article](https://support.microsoft.com/help/941641/remote-desktop-connection-6-0-prompts-you-for-credentials-before-you-e).
|
||||
|
||||
## Supported configurations
|
||||
|
||||
|
||||
@ -44,7 +44,8 @@
|
||||
"depot_name": "MSDN.win-client-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Windows Client Management"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
description: A full-sized view of the boot sequence flowchart.
|
||||
title: Boot sequence flowchart
|
||||
description: A full-sized view of the boot sequence flowchart.
|
||||
ms.date: 11/16/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
@ -10,8 +10,8 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Boot sequence flowchart
|
||||
|
||||
Return to: [Advanced troubleshooting for Windows boot problems](advanced-troubleshooting-boot-problems.md)<br>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -12,13 +12,13 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Manage the Settings app with Group Policy
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10, Windows Server 2016
|
||||
|
||||
|
||||
# Manage the Settings app with Group Policy
|
||||
|
||||
You can now manage the pages that are shown in the Settings app by using Group Policy. This lets you hide specific pages from users. Before Windows 10, version 1703, you could either show everything in the Settings app or hide it completely.
|
||||
To make use of the Settings App group polices on Windows server 2016, install fix [4457127](https://support.microsoft.com/help/4457127/windows-10-update-kb4457127) or a later cumulative update.
|
||||
|
||||
|
||||
@ -31,6 +31,7 @@ When the server that stores the mandatory profile is unavailable, such as when t
|
||||
User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) of each user's profile in the file system of the profile server from `NTuser.dat` to `NTuser.man`. The `.man` extension causes the user profile to be a read-only profile.
|
||||
|
||||
<span id="extension"/>
|
||||
|
||||
## Profile extension for each Windows version
|
||||
|
||||
The name of the folder in which you store the mandatory profile must use the correct extension for the operating system it will be applied to. The following table lists the correct extension for each operating system version.
|
||||
|
||||
@ -237,7 +237,6 @@
|
||||
#### [Security](policy-csp-security.md)
|
||||
#### [ServiceControlManager](policy-csp-servicecontrolmanager.md)
|
||||
#### [Settings](policy-csp-settings.md)
|
||||
#### [SmartScreen](policy-csp-smartscreen.md)
|
||||
#### [Speech](policy-csp-speech.md)
|
||||
#### [Start](policy-csp-start.md)
|
||||
#### [Storage](policy-csp-storage.md)
|
||||
@ -253,6 +252,7 @@
|
||||
#### [Wifi](policy-csp-wifi.md)
|
||||
#### [WindowsConnectionManager](policy-csp-windowsconnectionmanager.md)
|
||||
#### [WindowsDefenderSecurityCenter](policy-csp-windowsdefendersecuritycenter.md)
|
||||
#### [WindowsDefenderSmartScreen](policy-csp-smartscreen.md)
|
||||
#### [WindowsInkWorkspace](policy-csp-windowsinkworkspace.md)
|
||||
#### [WindowsLogon](policy-csp-windowslogon.md)
|
||||
#### [WindowsPowerShell](policy-csp-windowspowershell.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ApplicationControl CSP
|
||||
description: ApplicationControl CSP
|
||||
title: ApplicationControl CSP DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the **ApplicationControl** configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -40,7 +40,7 @@ This node is the policy binary itself, which is encoded as base64.
|
||||
|
||||
Scope is dynamic. Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
Value type is b64. Supported value is any well-formed WDAC policy, i.e. the base64-encoded content output by the ConvertFrom-CIPolicy cmdlet.
|
||||
Value type is b64. Supported value is a binary file, converted from the policy XML file by the ConvertFrom-CIPolicy cmdlet.
|
||||
|
||||
Default value is empty.
|
||||
|
||||
@ -80,6 +80,7 @@ This node specifies whether the policy is authorized to be loaded by the enforce
|
||||
Scope is dynamic. Supported operation is Get.
|
||||
|
||||
Value type is bool. Supported values are as follows:
|
||||
|
||||
- True — Indicates that the policy is authorized to be loaded by the enforcement engine on the system.
|
||||
- False — Indicates that the policy is not authorized to be loaded by the enforcement engine on the system. This is the default.
|
||||
|
||||
@ -113,31 +114,39 @@ Scope is dynamic. Supported operation is Get.
|
||||
Value type is char.
|
||||
|
||||
## Usage Guidance
|
||||
|
||||
> ![Note]
|
||||
> If using Intune standalone or for hybrid management with Configuration Manager (SCCM) through Microsoft Endpoint Manager, refer to [Deploy Windows Defender Application Control policies by using Microsoft Intune](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune) for more information on deploying policies with ApplicationControl CSP. Microsoft Intune handles the creation of a policy node and does all the below steps to deploy policies on your behalf, so you shouldn't do any of the below steps if using Intune to leverage ApplicationControl CSP.
|
||||
|
||||
In order to use ApplicationControl CSP, you must:
|
||||
|
||||
- Know a generated policy’s GUID, which can be found in the policy xml as `<PolicyID>` or `<PolicyTypeID>` for pre-1903 systems.
|
||||
- Convert the policies to binary format using the ConvertFrom-CIPolicy cmdlet in order to be deployed. The binary policy may be signed or unsigned.
|
||||
- Create a policy node (a Base64-encoded blob of the binary policy representation) using the certutil -encode command line tool.
|
||||
|
||||
Here is a sample certutil invocation:
|
||||
|
||||
```
|
||||
certutil -encode WinSiPolicy.p7b WinSiPolicy.cer
|
||||
```
|
||||
|
||||
An alternative to using certutil would be to use the following PowerShell invocation:
|
||||
|
||||
```powershell
|
||||
[Convert]::toBase64String($(Get-Content -Encoding Byte -ReadCount 0 -Path <bin file>))
|
||||
```
|
||||
|
||||
### Deploy policies
|
||||
|
||||
In order to deploy a new base policy or supplemental policy using the CSP:
|
||||
|
||||
- Perform an ADD on **./Vendor/MSFT/ApplicationControl/Policies/_{Policy GUID}_/Policy** using the Base64-encoded policy node as {Data} with the GUID and policy data for the base policy. Refer to the the Format section in the Example 1 below.
|
||||
- Repeat for each base or supplemental policy (with its own GUID and data).
|
||||
|
||||
The following example shows the deployment of two base policies and a supplemental policy. Because the supplemental policy already specifies the base policy it supplements, that does not need to be repeated in the ADD.
|
||||
|
||||
**Example 1: Add first base policy**
|
||||
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>1</CmdID>
|
||||
@ -152,7 +161,9 @@ The following example shows the deployment of two base policies and a supplement
|
||||
</Item>
|
||||
</Add>
|
||||
```
|
||||
|
||||
**Example 2: Add second base policy**
|
||||
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>1</CmdID>
|
||||
@ -167,7 +178,9 @@ The following example shows the deployment of two base policies and a supplement
|
||||
</Item>
|
||||
</Add>
|
||||
```
|
||||
|
||||
**Example 3: Add supplemental policy**
|
||||
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>1</CmdID>
|
||||
@ -182,6 +195,7 @@ The following example shows the deployment of two base policies and a supplement
|
||||
</Item>
|
||||
</Add>
|
||||
```
|
||||
|
||||
### Get policies
|
||||
|
||||
Perform a GET using a deployed policy’s GUID to interrogate/inspect the policy itself or information about it.
|
||||
@ -199,6 +213,7 @@ The following table displays the result of Get operation on different nodes:
|
||||
|./Vendor/MSFT/ApplicationControl/Policies/_Policy GUID_/PolicyInfo/FriendlyName|Friendly name per the policy|
|
||||
|
||||
The following is an example of Get command:
|
||||
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -211,16 +226,20 @@ The following is an example of Get command:
|
||||
```
|
||||
|
||||
### Delete policies
|
||||
|
||||
To delete an unsigned policy, perform a DELETE on **./Vendor/MSFT/ApplicationControl/Policies/_{Policy GUID}_/Policy**.
|
||||
|
||||
Only signed things should be able to update signed policies. Hence, performing a DELETE on **./Vendor/MSFT/ApplicationControl/Policies/_{Policy GUID}_/Policy** is not sufficient to delete a signed policy.
|
||||
> [!Note]
|
||||
> Only signed things should be able to update signed policies. Hence, performing a DELETE on **./Vendor/MSFT/ApplicationControl/Policies/_{Policy GUID}_/Policy** is not sufficient to delete a signed policy.
|
||||
|
||||
To delete a signed policy:
|
||||
|
||||
1. Replace it with a signed update allowing unsigned policy.
|
||||
2. Deploy another update with unsigned policy.
|
||||
3. Perform delete.
|
||||
|
||||
The following is an example of Delete command:
|
||||
|
||||
```xml
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking CSP
|
||||
description: EnrollmentStatusTracking CSP
|
||||
title: EnrollmentStatusTracking DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the EnrollmentStatusTracking configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking CSP
|
||||
description: EnrollmentStatusTracking CSP
|
||||
description: During Autopilot deployment, you can configure the Enrollment Status Page (ESP) to block the device use until the required apps are installed.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
@ -11,7 +11,6 @@ ms.date: 05/21/2019
|
||||
|
||||
# EnrollmentStatusTracking CSP
|
||||
|
||||
|
||||
During Autopilot deployment, you can configure the Enrollment Status Page (ESP) to block the device use until the required apps are installed. You can select the apps that must be installed before using the device. The EnrollmentStatusTracking configuration service provider (CSP) is used by Intune's agents, such as SideCar to configure ESP for blocking the device use until the required Win32 apps are installed. It tracks the installation status of the required policy providers and the apps they install and sends it to ESP, which displays the installation progress message to the user. For more information on ESP, see [Windows Autopilot Enrollment Status page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status).
|
||||
|
||||
ESP uses the EnrollmentStatusTracking CSP along with the DMClient CSP to track the installation of different apps. The EnrollmentStatusTracking CSP tracks Win32 apps installations and DMClient CSP tracks MSI and Universal Windows Platform apps installations. In DMClient CSP, the **FirstSyncStatus/ExpectedMSIAppPackages** and **FirstSyncStatus/ExpectedModernAppPackages** nodes list the apps to track their installation. See [DMClient CSP](dmclient-csp.md) for more information.
|
||||
|
||||
@ -504,7 +504,7 @@ Supported operation is Get.
|
||||
|
||||
|
||||
|
||||
<a href="" id="appinstallation-packagefamilyname-lasterrordescription"></a>**AppInstallation/*PackageFamilyName*/LastErrorDescription**
|
||||
<a href="" id="appinstallation-packagefamilyname-lasterrordescription"></a>**AppInstallation/*PackageFamilyName*/LastErrorDesc**
|
||||
Required. Description of last error relating to the app installation.
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Implement server-side support for mobile application management on Windows
|
||||
title: Provide server-side support for mobile app management on Windows
|
||||
description: The Windows version of mobile application management (MAM) is a lightweight solution for managing company data access and security on personal devices. MAM support is built into Windows on top of Windows Information Protection (WIP).
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
|
||||
@ -10,7 +10,6 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.date: 01/25/2019
|
||||
---
|
||||
|
||||
# Mobile device management
|
||||
@ -34,7 +33,7 @@ With Windows 10, version 1809, Microsoft is also releasing a Microsoft MDM secur
|
||||
|
||||
The MDM security baseline includes policies that cover the following areas:
|
||||
|
||||
- Microsoft inbox security technology (not deprecated) such as Bitlocker, Smartscreen, and DeviceGuard (virtual-based security), ExploitGuard, Defender, and Firewall
|
||||
- Microsoft inbox security technology (not deprecated) such as Bitlocker, Windows Defender Smartscreen, and DeviceGuard (virtual-based security), ExploitGuard, Defender, and Firewall
|
||||
- Restricting remote access to devices
|
||||
- Setting credential requirements for passwords and PINs
|
||||
- Restricting use of legacy technology
|
||||
@ -42,14 +41,16 @@ The MDM security baseline includes policies that cover the following areas:
|
||||
- And much more
|
||||
|
||||
For more details about the MDM policies defined in the MDM security baseline and what Microsoft’s recommended baseline policy values are, see:
|
||||
|
||||
- [MDM Security baseline for Windows 10, version 1909](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1909-MDM-SecurityBaseLine-Document.zip)
|
||||
- [MDM Security baseline for Windows 10, version 1903](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1903-MDM-SecurityBaseLine-Document.zip)
|
||||
|
||||
- [MDM Security baseline for Windows 10, version 1809](https://download.microsoft.com/download/2/C/4/2C418EC7-31E0-4A74-8928-6DCD512F9A46/1809-MDM-SecurityBaseLine-Document-[Preview].zip)
|
||||
|
||||
For information about the MDM policies defined in the Intune security baseline public preview, see [Windows security baseline settings for Intune](https://docs.microsoft.com/intune/security-baseline-settings-windows)
|
||||
|
||||
|
||||
<span id="mmat" />
|
||||
|
||||
## Learn about migrating to MDM
|
||||
|
||||
When an organization wants to move to MDM to manage devices, they should prepare by analyzing their current Group Policy settings to see what they need to transition to MDM management. Microsoft created the [MDM Migration Analysis Tool](https://aka.ms/mmat/) (MMAT) to help. MMAT determines which Group Policies have been set for a target user or computer and then generates a report that lists the level of support for each policy settings in MDM equivalents. For more information, see [MMAT Instructions](https://github.com/WindowsDeviceManagement/MMAT/blob/master/MDM%20Migration%20Analysis%20Tool%20Instructions.pdf).
|
||||
|
||||
@ -84,7 +84,7 @@ Valid values:
|
||||
|
||||
The data type is integer. Supported operations are Get and Replace. Starting in Windows 10, version 1803, the Delete operation is also supported.
|
||||
|
||||
# Configuration Example
|
||||
## Configuration Example
|
||||
|
||||
These generic code portions for the options **ProxySettingsPerUser**, **Autodetect**, and **SetupScriptURL** can be used for a specific operation, for example Replace. Only enter the portion of code needed in the **Replace** section.
|
||||
```xml
|
||||
|
||||
@ -190,7 +190,7 @@ Default value is false. If you set this policy to true, Remote Windows Hello for
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business.*
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business prior to Windows 10 version 1903 (May 2019 Update).*
|
||||
|
||||
<a href="" id="tenantid-policies-usehellocertificatesassmartcardcertificates"></a>***TenantId*/Policies/UseHelloCertificatesAsSmartCardCertificates** (only for ./Device/Vendor/MSFT)
|
||||
Added in Windows 10, version 1809. If you enable this policy setting, applications use Windows Hello for Business certificates as smart card certificates. Biometric factors are unavailable when a user is asked to authorize the use of the certificate's private key. This policy setting is designed to allow compatibility with applications that rely exclusively on smart card certificates.
|
||||
@ -206,7 +206,7 @@ This node is deprecated. Use **Biometrics/UseBiometrics** node instead.
|
||||
|
||||
<a href="" id="biometrics--only-for---device-vendor-msft-"></a>**Biometrics** (only for ./Device/Vendor/MSFT)
|
||||
Node for defining biometric settings. This node was added in Windows 10, version 1511.
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business.*
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business prior to Windows 10 version 1903 (May 2019 Update).*
|
||||
|
||||
<a href="" id="biometrics-usebiometrics--only-for---device-vendor-msft-"></a>**Biometrics/UseBiometrics** (only for ./Device/Vendor/MSFT)
|
||||
Boolean value used to enable or disable the use of biometric gestures, such as face and fingerprint, as an alternative to the PIN gesture for Windows Hello for Business. Users must still configure a PIN if they configure biometric gestures to use in case of failures. This node was added in Windows 10, version 1511.
|
||||
@ -230,7 +230,7 @@ Note that enhanced anti-spoofing for Windows Hello face authentication is not re
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business.*
|
||||
*Not supported on Windows Holographic and Windows Holographic for Business prior to Windows 10 version 1903 (May 2019 Update).*
|
||||
|
||||
<a href="" id="deviceunlock"></a>**DeviceUnlock** (only for ./Device/Vendor/MSFT)
|
||||
Added in Windows 10, version 1803. Interior node.
|
||||
|
||||
@ -3202,7 +3202,7 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
### SmartScreen policies
|
||||
### Windows Defender SmartScreen policies
|
||||
|
||||
<dl>
|
||||
<dd>
|
||||
|
||||
@ -1748,7 +1748,7 @@ Most restricted value: 1
|
||||
To verify AllowSmartScreen is set to 0 (not allowed):
|
||||
|
||||
1. Click or tap **More** (…) and select **Settings** > **View Advanced settings**.
|
||||
2. Verify the setting **Help protect me from malicious sites and download with SmartScreen Filter** is disabled.
|
||||
2. Verify that the setting **Help protect me from malicious sites and download with Windows Defender SmartScreen** is disabled.
|
||||
|
||||
<!--/Validation-->
|
||||
<!--/Policy-->
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Policy CSP - TimeLanguageSettings
|
||||
title: Policy CSP - DeviceHealthMonitoring
|
||||
description: Policy CSP - TimeLanguageSettings
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
|
||||
@ -2448,7 +2448,7 @@ ADMX Info:
|
||||
|
||||
Value and index pairs in the SyncML example:
|
||||
- http://adfs.contoso.org 1
|
||||
- http://microsoft.com 2
|
||||
- https://microsoft.com 2
|
||||
|
||||
<!--/Example-->
|
||||
<!--/Policy-->
|
||||
@ -3253,11 +3253,11 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting determines whether the user can bypass warnings from SmartScreen Filter. SmartScreen Filter prevents the user from browsing to or downloading from sites that are known to host malicious content. SmartScreen Filter also prevents the execution of files that are known to be malicious.
|
||||
This policy setting determines whether the user can bypass warnings from Windows Defender SmartScreen. Windows Defender SmartScreen prevents the user from browsing to or downloading from sites that are known to host malicious content. Windows Defender SmartScreen also prevents the execution of files that are known to be malicious.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter warnings block the user.
|
||||
If you enable this policy setting, Windows Defender SmartScreen warnings block the user.
|
||||
|
||||
If you disable or do not configure this policy setting, the user can bypass SmartScreen Filter warnings.
|
||||
If you disable or do not configure this policy setting, the user can bypass Windows Defender SmartScreen warnings.
|
||||
|
||||
<!--/Description-->
|
||||
> [!TIP]
|
||||
@ -3324,11 +3324,11 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting determines whether the user can bypass warnings from SmartScreen Filter. SmartScreen Filter warns the user about executable files that Internet Explorer users do not commonly download from the Internet.
|
||||
This policy setting determines whether the user can bypass warnings from Windows Defender SmartScreen. Windows Defender SmartScreen warns the user 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 user.
|
||||
If you enable this policy setting, Windows Defender SmartScreen warnings block the user.
|
||||
|
||||
If you disable or do not configure this policy setting, the user can bypass SmartScreen Filter warnings.
|
||||
If you disable or do not configure this policy setting, the user can bypass Windows Defender SmartScreen warnings.
|
||||
|
||||
<!--/Description-->
|
||||
> [!TIP]
|
||||
@ -6501,13 +6501,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -8604,13 +8604,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -9561,13 +9561,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -10518,13 +10518,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -11481,13 +11481,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -12286,13 +12286,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -13170,13 +13170,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -14054,13 +14054,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -14733,11 +14733,11 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting prevents the user from managing SmartScreen Filter, which warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing," or is known to host malware.
|
||||
This policy setting prevents the user from managing Windows Defender SmartScreen, which warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing," or is known to host malware.
|
||||
|
||||
If you enable this policy setting, the user is not 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 user.
|
||||
If you enable this policy setting, the user is not prompted to turn on Windows Defender SmartScreen. All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the user.
|
||||
|
||||
If you disable or do not configure this policy setting, the user is prompted to decide whether to turn on SmartScreen Filter during the first-run experience.
|
||||
If you disable or do not configure this policy setting, the user is prompted to decide whether to turn on Windows Defender SmartScreen during the first-run experience.
|
||||
|
||||
<!--/Description-->
|
||||
> [!TIP]
|
||||
@ -16477,13 +16477,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
@ -19053,13 +19053,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
This policy setting controls whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you enable this policy setting, Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
|
||||
If you disable this policy setting, Windows Defender SmartScreen does not scan pages in this zone for malicious content.
|
||||
|
||||
If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
|
||||
If you do not configure this policy setting, the user can choose whether Windows Defender SmartScreen scans pages in this zone for malicious content.
|
||||
|
||||
Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
|
||||
|
||||
|
||||
@ -173,6 +173,9 @@ manager: dansimp
|
||||
|
||||
<hr/>
|
||||
|
||||
> [!NOTE]
|
||||
> To find data formats (and other policy-related details), see [Policy DDF file](https://docs.microsoft.com/windows/client-management/mdm/policy-ddf-file).
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="localpoliciessecurityoptions-accounts-blockmicrosoftaccounts"></a>**LocalPoliciesSecurityOptions/Accounts_BlockMicrosoftAccounts**
|
||||
|
||||
@ -3698,4 +3701,3 @@ Footnotes:
|
||||
- 6 - Added in Windows 10, version 1903.
|
||||
|
||||
<!--/Policies-->
|
||||
|
||||
|
||||
@ -130,3 +130,8 @@ Value type is Base64. Supported operation is Replace.
|
||||
Retrieves the binary result package of previous Settings2/Apply operation. This binary package contains XML describing the action taken for each individual setting.
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
[UEFI DDF file](./uefi-ddf.md)
|
||||
|
||||
@ -296,21 +296,13 @@ For links to these classes, see [**MDM Bridge WMI Provider**](https://msdn.micro
|
||||
[**Win32\_UninterruptiblePowerSupply**](https://msdn.microsoft.com/library/windows/hardware/aa394503) |
|
||||
[**Win32\_USBController**](https://msdn.microsoft.com/library/windows/hardware/aa394504) |
|
||||
[**Win32\_UTCTime**](https://msdn.microsoft.com/library/windows/hardware/aa394510) | 
|
||||
[**Win32\_VideoController**](https://msdn.microsoft.com/library/windows/hardware/aa394505) |
|
||||
[**Win32\_VideoController**](https://docs.microsoft.com/windows/win32/cimwin32prov/win32-videocontroller) |
|
||||
**Win32\_WindowsUpdateAgentVersion** |
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Configuration service provider reference](configuration-service-provider-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
10/10/2016
|
||||
|
||||
|
||||
|
||||
|
||||
## Related Links
|
||||
[CIM Video Controller](https://docs.microsoft.com/windows/win32/cimwin32prov/cim-videocontroller)
|
||||
|
||||
@ -23,7 +23,7 @@ ms.topic: reference
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Windows 10 includes the following new policies for management. [Download the complete set of Administrative Template (.admx) files for Windows 10](https://www.microsoft.com/download/details.aspx?id=56121).
|
||||
Windows 10 includes the following new policies for management. [Download the complete set of Administrative Template (.admx) files for Windows 10](https://www.microsoft.com/download/100591).
|
||||
|
||||
|
||||
## New Group Policy settings in Windows 10, version 1809
|
||||
@ -497,4 +497,3 @@ No new [Exchange ActiveSync policies](https://go.microsoft.com/fwlink/p/?LinkId=
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device
|
||||
title: Advanced advice for Stop error 7B, Inaccessible_Boot_Device
|
||||
description: Learn how to troubleshoot Stop error 7B or Inaccessible_Boot_Device
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
|
||||
@ -634,12 +634,12 @@ The following settings for Microsoft Edge on Windows 10 Mobile can be managed.
|
||||
- **Allow InPrivate** Whether users can use InPrivate browsing
|
||||
- **Allow Password Manager** Whether users can use Password Manager to save and manage passwords locally
|
||||
- **Allow Search Suggestions in Address Bar** Whether search suggestions are shown in the address bar
|
||||
- **Allow SmartScreen** Whether SmartScreen Filter is enabled
|
||||
- **Allow Windows Defender SmartScreen** Whether Windows Defender SmartScreen is enabled
|
||||
- **Cookies** Whether cookies are allowed
|
||||
- **Favorites** Configure Favorite URLs
|
||||
- **First Run URL** The URL to open when a user launches Microsoft Edge for the first time
|
||||
- **Prevent SmartScreen Prompt Override** Whether users can override the SmartScreen warnings for URLs
|
||||
- **Prevent Smart Screen Prompt Override for Files** Whether users can override the SmartScreen warnings for files
|
||||
- **Prevent Windows Defender SmartScreen Prompt Override** Whether users can override the Windows Defender SmartScreen warnings for URLs
|
||||
- **Prevent Smart Screen Prompt Override for Files** Whether users can override the Windows Defender SmartScreen warnings for files
|
||||
|
||||
## Manage
|
||||
|
||||
|
||||
@ -18,23 +18,23 @@ Microsoft regularly releases both updates for Windows Server. To ensure your ser
|
||||
|
||||
This section contains advanced troubleshooting topics and links to help you resolve issues with Windows 10 in an enterprise or IT pro environment. Additional topics will be added as they become available.
|
||||
|
||||
### Troubleshoot 802.1x Authentication
|
||||
## Troubleshoot 802.1x Authentication
|
||||
- [Advanced Troubleshooting 802.1X Authentication](https://docs.microsoft.com/windows/client-management/advanced-troubleshooting-802-authentication)
|
||||
- [Data collection for troubleshooting 802.1X authentication](https://docs.microsoft.com/windows/client-management/data-collection-for-802-authentication)
|
||||
|
||||
### Troubleshoot BitLocker
|
||||
- [BitLocker overview and requirements FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq)
|
||||
- [BitLocker Upgrading FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-upgrading-faq)
|
||||
- [BitLocker frequently asked questions (FAQ) (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-deployment-and-administration-faq)
|
||||
- [BitLocker Key Management FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-key-management-faq)
|
||||
- [BitLocker To Go FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-to-go-faq)
|
||||
- [BitLocker and Active Directory Domain Services (AD DS) FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-and-adds-faq)
|
||||
- [BitLocker Security FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-security-faq)
|
||||
- [BitLocker frequently asked questions (FAQ) (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-network-unlock-faq)
|
||||
- [Using BitLocker with other programs FAQ (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-using-with-other-programs-faq)
|
||||
- [BitLocker recovery guide (Windows 10)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-recovery-guide-plan)
|
||||
## Troubleshoot BitLocker
|
||||
- [Guidelines for troubleshooting BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/troubleshoot-bitlocker)
|
||||
- [BitLocker cannot encrypt a drive: known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-cannot-encrypt-issues)
|
||||
- [Enforcing BitLocker policies by using Intune: known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-intune-issues)
|
||||
- [BitLocker Network Unlock: known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-network-unlock-issues)
|
||||
- [BitLocker recovery: known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-recovery-issues)
|
||||
- [BitLocker configuration: known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-config-issues)
|
||||
- [BitLocker cannot encrypt a drive: known TPM issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-cannot-encrypt-tpm-issues)
|
||||
- [BitLocker and TPM: other known issues](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-tpm-issues)
|
||||
- [Decode Measured Boot logs to track PCR changes](https://docs.microsoft.com/windows/security/information-protection/bitlocker/ts-bitlocker-decode-measured-boot-logs)
|
||||
- [BitLocker frequently asked questions (FAQ)](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-frequently-asked-questions)
|
||||
|
||||
### Troubleshoot Bugcheck and Stop errors
|
||||
## Troubleshoot Bugcheck and Stop errors
|
||||
- [Introduction to the page file](https://docs.microsoft.com/windows/client-management/introduction-page-file)
|
||||
- [How to determine the appropriate page file size for 64-bit versions of Windows](https://docs.microsoft.com/windows/client-management/determine-appropriate-page-file-size)
|
||||
- [Configure system failure and recovery options in Windows](https://docs.microsoft.com/windows/client-management/system-failure-recovery-options)
|
||||
@ -44,20 +44,20 @@ This section contains advanced troubleshooting topics and links to help you reso
|
||||
- [Blue Screen Data - Windows drivers](https://docs.microsoft.com/windows-hardware/drivers/debugger/blue-screen-data)
|
||||
- [Bug Check Code Reference - Windows drivers](https://docs.microsoft.com/windows-hardware/drivers/debugger/bug-check-code-reference2)
|
||||
|
||||
### Troubleshoot Credential Guard
|
||||
## Troubleshoot Credential Guard
|
||||
- [Windows Defender Credential Guard - Known issues (Windows 10)](https://docs.microsoft.com/windows/security/identity-protection/credential-guard/credential-guard-known-issues)
|
||||
|
||||
### Troubleshoot Disks
|
||||
## Troubleshoot Disks
|
||||
- [MBR2GPT](https://docs.microsoft.com/windows/deployment/mbr-to-gpt)
|
||||
- [Windows and GPT FAQ](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-and-gpt-faq)
|
||||
|
||||
### Troubleshoot Kiosk mode
|
||||
## Troubleshoot Kiosk mode
|
||||
- [Troubleshoot kiosk mode issues](https://docs.microsoft.com/windows/configuration/kiosk-troubleshoot)
|
||||
|
||||
### Troubleshoot No Boot
|
||||
## Troubleshoot No Boot
|
||||
- [Advanced troubleshooting for Windows boot problems](https://docs.microsoft.com/windows/client-management/advanced-troubleshooting-boot-problems)
|
||||
|
||||
### Troubleshoot Push Button Reset
|
||||
## Troubleshoot Push Button Reset
|
||||
- [Push-button reset frequently-asked questions (FAQ)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/pbr-faq)
|
||||
- [Push-button reset frequently-asked questions (FAQ)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/pbr-validation)
|
||||
- [Recovery components](https://docs.microsoft.com/windows-hardware/manufacture/desktop/recovery-strategy-for-common-customizations)
|
||||
@ -66,46 +66,46 @@ This section contains advanced troubleshooting topics and links to help you reso
|
||||
- [Modern Standby FAQs](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby-faqs)
|
||||
|
||||
|
||||
### Troubleshoot Secure Boot
|
||||
## Troubleshoot Secure Boot
|
||||
- [Secure Boot isn't configured correctly: troubleshooting](https://docs.microsoft.com/windows-hardware/manufacture/desktop/secure-boot-isnt-configured-correctly-troubleshooting)
|
||||
|
||||
|
||||
### Troubleshoot Setup and Install
|
||||
## Troubleshoot Setup and Install
|
||||
- [Deployment Troubleshooting and Log Files](https://docs.microsoft.com/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files)
|
||||
|
||||
|
||||
### Troubleshoot Start Menu
|
||||
## Troubleshoot Start Menu
|
||||
- [Troubleshoot Start menu errors](https://docs.microsoft.com/windows/configuration/start-layout-troubleshoot)
|
||||
|
||||
|
||||
### Troubleshoot Subscription Activation
|
||||
## Troubleshoot Subscription Activation
|
||||
- [Deploy Windows 10 Enterprise licenses](https://docs.microsoft.com/windows/deployment/deploy-enterprise-licenses)
|
||||
|
||||
### Troubleshoot System Hang
|
||||
## Troubleshoot System Hang
|
||||
- [Advanced troubleshooting for Windows-based computer freeze issues](https://docs.microsoft.com/windows/client-management/troubleshoot-windows-freeze)
|
||||
|
||||
### Troubleshoot TCP/IP Communication
|
||||
## Troubleshoot TCP/IP Communication
|
||||
- [Collect data using Network Monitor](https://docs.microsoft.com/windows/client-management/troubleshoot-tcpip-netmon)
|
||||
- [Troubleshoot TCP/IP connectivity](https://docs.microsoft.com/windows/client-management/troubleshoot-tcpip-connectivity)
|
||||
- [Troubleshoot port exhaustion issues](https://docs.microsoft.com/windows/client-management/troubleshoot-tcpip-port-exhaust)
|
||||
- [Troubleshoot Remote Procedure Call (RPC) errors](https://docs.microsoft.com/windows/client-management/troubleshoot-tcpip-rpc-errors)
|
||||
|
||||
### Troubleshoot User State Migration Toolkit (USMT)
|
||||
## Troubleshoot User State Migration Toolkit (USMT)
|
||||
- [Common Issues](https://docs.microsoft.com/windows/deployment/usmt/usmt-common-issues)
|
||||
- [Frequently Asked Questions](https://docs.microsoft.com/windows/deployment/usmt/usmt-faq)
|
||||
- [Log Files](https://docs.microsoft.com/windows/deployment/usmt/usmt-log-files)
|
||||
- [Return Codes](https://docs.microsoft.com/windows/deployment/usmt/usmt-return-codes)
|
||||
|
||||
### Troubleshoot Windows Hello for Business (WHFB)
|
||||
## Troubleshoot Windows Hello for Business (WHFB)
|
||||
- [Windows Hello for Business Frequently Asked Questions](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-faq)
|
||||
- [Windows Hello errors during PIN creation (Windows 10)](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-errors-during-pin-creation)
|
||||
- [Event ID 300 - Windows Hello successfully created (Windows 10)](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-event-300)
|
||||
|
||||
|
||||
### Troubleshoot Windows Analytics
|
||||
## Troubleshoot Windows Analytics
|
||||
- [Frequently asked questions and troubleshooting Windows Analytics](https://docs.microsoft.com/windows/deployment/update/windows-analytics-faq-troubleshooting)
|
||||
|
||||
### Troubleshoot Windows Update
|
||||
## Troubleshoot Windows Update
|
||||
- [How Windows Update works](https://docs.microsoft.com/windows/deployment/update/how-windows-update-works)
|
||||
- [Windows Update log files](https://docs.microsoft.com/windows/deployment/update/windows-update-logs)
|
||||
- [Windows Update troubleshooting](https://docs.microsoft.com/windows/deployment/update/windows-update-troubleshooting)
|
||||
@ -114,7 +114,7 @@ This section contains advanced troubleshooting topics and links to help you reso
|
||||
- [Get started with Windows Update](https://docs.microsoft.com/windows/deployment/update/windows-update-overview)
|
||||
- [Servicing stack updates](https://docs.microsoft.com/windows/deployment/update/servicing-stack-updates)
|
||||
|
||||
### Troubleshoot Windows Upgrade
|
||||
## Troubleshoot Windows Upgrade
|
||||
- [Quick fixes - Windows IT Pro](https://docs.microsoft.com/windows/deployment/upgrade/quick-fixes)
|
||||
- [SetupDiag](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag)
|
||||
- [Troubleshoot Windows 10 upgrade errors - Windows IT Pro](https://docs.microsoft.com/windows/deployment/upgrade/troubleshoot-upgrade-errors)
|
||||
@ -123,10 +123,10 @@ This section contains advanced troubleshooting topics and links to help you reso
|
||||
- [Log files - Windows IT Pro](https://docs.microsoft.com/windows/deployment/upgrade/log-files)
|
||||
- [Resolution procedures - Windows IT Pro](https://docs.microsoft.com/windows/deployment/upgrade/resolution-procedures)
|
||||
|
||||
### Troubleshoot Windows Recovery (WinRE)
|
||||
## Troubleshoot Windows Recovery (WinRE)
|
||||
- [Windows RE troubleshooting features](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-re-troubleshooting-features)
|
||||
|
||||
### Troubleshoot Wireless Connection
|
||||
## Troubleshoot Wireless Connection
|
||||
- [Advanced Troubleshooting Wireless Network Connectivity](https://docs.microsoft.com/windows/client-management/advanced-troubleshooting-wireless-network-connectivity)
|
||||
|
||||
## Other Resources
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use Group Policy and mobile device management (MDM) settings to configure Cortana in your organization (Windows 10)
|
||||
title: Configure Cortana with Group Policy and MDM settings (Windows 10)
|
||||
description: The list of Group Policy and mobile device management (MDM) policy settings that apply to Cortana at work.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 1 - Sign-in to Azure AD and use Cortana to manage the notebook (Windows 10)
|
||||
title: Sign-in to Azure AD and manage notebook with Cortana (Windows 10)
|
||||
description: A test scenario walking you through signing in and managing the notebook.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 2 - Perform a quick search with Cortana at work (Windows 10)
|
||||
title: Perform a quick search with Cortana at work (Windows 10)
|
||||
description: A test scenario about how to perform a quick search with Cortana at work.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 3 - Set a reminder for a specific location using Cortana at work (Windows 10)
|
||||
title: Set a reminder for a location with Cortana at work (Windows 10)
|
||||
description: A test scenario about how to set a location-based reminder using Cortana at work.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 4 - Use Cortana at work to find your upcoming meetings (Windows 10)
|
||||
title: Use Cortana at work to find your upcoming meetings (Windows 10)
|
||||
description: A test scenario about how to use Cortana at work to find your upcoming meetings.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 5 - Use Cortana to send email to a co-worker (Windows 10)
|
||||
title: Use Cortana to send email to a co-worker (Windows 10)
|
||||
description: A test scenario about how to use Cortana at work to send email to a co-worker.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 6 - Review a reminder suggested by Cortana based on what you’ve promised in email (Windows 10)
|
||||
title: Review a reminder suggested by Cortana (Windows 10)
|
||||
description: A test scenario about how to use Cortana with the Suggested reminders feature.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Test scenario 7 - Use Cortana and Windows Information Protection (WIP) to help protect your organization’s data on a device (Windows 10)
|
||||
title: Help protect data with Cortana and WIP (Windows 10)
|
||||
description: An optional test scenario about how to use Cortana at work with Windows Information Protection (WIP).
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Customize Windows 10 Start and taskbar with mobile device management (MDM) (Windows 10)
|
||||
title: Alter Windows 10 Start and taskbar via mobile device management
|
||||
description: In Windows 10, you can use a mobile device management (MDM) policy to deploy a customized Start and tasbkar layout to users.
|
||||
ms.assetid: F487850D-8950-41FB-9B06-64240127C1E4
|
||||
ms.reviewer:
|
||||
|
||||
@ -42,7 +42,8 @@
|
||||
"depot_name": "MSDN.win-configuration",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"titleSuffix": "Configure Windows"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
|
||||
@ -97,6 +97,8 @@ In addition to the settings in the table, you may want to set up **automatic log
|
||||
> [!TIP]
|
||||
> You can also configure automatic sign-in [using the Autologon tool from Sysinternals](https://docs.microsoft.com/sysinternals/downloads/autologon).
|
||||
|
||||
> [!NOTE]
|
||||
> If you are also using [Custom Logon](https://docs.microsoft.com/windows-hardware/customize/enterprise/custom-logon) with **HideAutoLogonUI** enabled, you might experience a black screen after a password expires. We recommend that you consider [setting the password to never expire](https://docs.microsoft.com/windows-hardware/customize/enterprise/troubleshooting-custom-logon#the-device-displays-a-black-screen-when-a-password-expiration-screen-is-displayed).
|
||||
|
||||
## Interactions and interoperability
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use Windows Configuration Designer to configure Windows 10 Mobile devices (Windows 10)
|
||||
description:
|
||||
title: Configure Windows 10 Mobile devices with Configuration Designer
|
||||
description: Use Windows Configuration Designer to configure Windows 10 Mobile devices
|
||||
keywords: phone, handheld, lockdown, customize
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Settings and quick actions that can be locked down in Windows 10 Mobile (Windows 10)
|
||||
title: Lock down settings and quick actions in Windows 10 Mobile
|
||||
description: This topic lists the settings and quick actions that can be locked down in Windows 10 Mobile.
|
||||
ms.assetid: 69E2F202-D32B-4FAC-A83D-C3051DF02185
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Introduction to configuration service providers (CSPs) for IT pros (Windows 10)
|
||||
title: Intro to configuration service providers for IT pros (Windows 10)
|
||||
description: Configuration service providers (CSPs) expose device configuration settings in Windows 10.
|
||||
ms.assetid: 25C1FDCA-0E10-42A1-A368-984FFDB2B7B6
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Settings changed when you uninstall a provisioning package (Windows 10)
|
||||
title: Uninstall a provisioning package - reverted settings (Windows 10)
|
||||
description: This topic lists the settings that are reverted when you uninstall a provisioning package.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Managing the UE-V Service and Packages with Windows PowerShell and WMI
|
||||
title: Manage UE-V Service and Packages with Windows PowerShell and WMI
|
||||
description: Managing the UE-V service and packages with Windows PowerShell and WMI
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, virtualization
|
||||
|
||||
@ -135,8 +135,8 @@ This section describes the **Policies** settings that you can configure in [prov
|
||||
| [PreventCertErrorOverrides](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-preventcerterroroverrides) | Specify whether to override security warnings about sites that have SSL errors. | X | X | X | | X |
|
||||
| [PreventFirstRunPage](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventfirstrunpage) | Specify whether to enable or disable the First Run webpage. | X | | | | |
|
||||
| [PreventLiveTileDataCollection](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventlivetiledatacollection) | Specify whether Microsoft can collect information to create a Live Tile when pinning a site to Start from Microsoft Edge. | X | X | X | | X |
|
||||
| [PreventSmartScreenPromptOverride](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventsmartscreenpromptoverride) | Specify whether users can override the Windows Defender SmartScreen Filter warnings about potentially malicious websites. | X | X | X | | X |
|
||||
| [PreventSmartScreenPromptOverrideForFiles](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventsmartscreenpromptoverrideforfiles) | Specify whether users can override the Windows Defender SmartScreen Filter warnings about downloading unverified files. | X | X | X | | X |
|
||||
| [PreventSmartScreenPromptOverride](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventsmartscreenpromptoverride) | Specify whether users can override the Windows Defender SmartScreen warnings about potentially malicious websites. | X | X | X | | X |
|
||||
| [PreventSmartScreenPromptOverrideForFiles](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventsmartscreenpromptoverrideforfiles) | Specify whether users can override the Windows Defender SmartScreen warnings about downloading unverified files. | X | X | X | | X |
|
||||
PreventTabPreloading | Prevent Microsoft Edge from starting and loading the Start and New Tab page at Windows startup and each time Microsoft Edge is closed. Applies to Windows 10, version 1803 and earlier only. | X | | | | |
|
||||
| [PreventTurningOffRequiredExtensions](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-forceenabledextensions) | Enter a list of extensions in Microsoft Edge that users cannot turn off, using a semi-colon delimited list of extension package family names. | X | | | | |
|
||||
| [PreventUsingLocalHostIPAddressForWebRTC](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#browser-preventusinglocalhostipaddressforwebrtc) | Specify whether a user's localhost IP address is displayed while making phone calls using the WebRTC protocol. | X | X | X | | X |
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Create a task sequence with Configuration Manager and MDT (Windows 10)
|
||||
title: Create a task sequence with Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard.
|
||||
ms.assetid: 0b069bec-5be8-47c6-bf64-7a630f41ac98
|
||||
ms.reviewer:
|
||||
@ -11,7 +11,8 @@ ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: mdt
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use the MDT database to stage Windows 10 deployment information (Windows 10)
|
||||
title: Use MDT database to stage Windows 10 deployment info (Windows 10)
|
||||
description: This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini).
|
||||
ms.assetid: 8956ab54-90ba-45d3-a384-4fdec72c4d46
|
||||
ms.reviewer:
|
||||
@ -11,7 +11,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Create an application to deploy with Windows 10 using Configuration Manager (Windows 10)
|
||||
title: Create an app to deploy with Windows 10 using Configuration Manager
|
||||
description: Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||
ms.reviewer:
|
||||
@ -10,7 +10,8 @@ ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Finalize the operating system configuration for Windows 10 deployment with Configuration Manager (Windows 10)
|
||||
title: Finalize operating system configuration for Windows 10 deployment
|
||||
description: This topic walks you through the steps to finalize the configuration of your Windows 10 operating deployment, which includes enablement of the optional Microsoft Deployment Toolkit (MDT) monitoring for Microsoft System Center 2012 R2 Configuration Manager, logs folder creation, rules configuration, content distribution, and deployment of the previously created task sequence.
|
||||
ms.assetid: 38b55fa8-e717-4689-bd43-8348751d493e
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Monitor the Windows 10 deployment with Configuration Manager (Windows 10)
|
||||
title: Monitor the Windows 10 deployment with Configuration Manager
|
||||
description: In this topic, you will learn how to monitor a Windows 10 deployment that was started previously using Microsoft System Center 2012 R2 Configuration Manager and the Microsoft Deployment Toolkit (MDT) Deployment Workbench.
|
||||
ms.assetid: 4863c6aa-6369-4171-8e1a-b052ca195fce
|
||||
ms.reviewer:
|
||||
@ -10,7 +10,8 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user