mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
new attempt on Edge docfx, fixing note references, bookmark links
This commit is contained in:
Liza Poggemeyer
parent
a99b07b1c6
commit
7497140075
@ -14,6 +14,7 @@
|
||||
"resource": [
|
||||
{
|
||||
"files": [
|
||||
"**/images/**",
|
||||
"**/*.png",
|
||||
"**/*.jpg",
|
||||
"**/*.gif"
|
||||
|
||||
@ -37,7 +37,7 @@ Note that the local admin account information is not backed by any directory ser
|
||||
|
||||
### Domain join the device to Active Directory (AD)
|
||||
|
||||
You can domain join the Surface Hub to your AD domain to allow users from a specified security group to configure settings. During first run, choose to use [Active Directory Domain Services](first-run-program-surface-hub.md#a-href-iduse-active-directoryause-active-directory-domain-services). You'll need to provide credentials that are capable of joining the domain of your choice, and the name of an existing security group. Anyone who is a member of that security group can enter their credentials and unlock Settings.
|
||||
You can domain join the Surface Hub to your AD domain to allow users from a specified security group to configure settings. During first run, choose to use [Active Directory Domain Services](first-run-program-surface-hub.md#use-active-directory-domain-services). You'll need to provide credentials that are capable of joining the domain of your choice, and the name of an existing security group. Anyone who is a member of that security group can enter their credentials and unlock Settings.
|
||||
|
||||
#### What happens when you domain join your Surface Hub?
|
||||
Surface Hubs use domain join to:
|
||||
@ -53,7 +53,7 @@ Surface Hub does not support applying group policies or certificates from the do
|
||||
|
||||
### Azure Active Directory (Azure AD) join the device
|
||||
|
||||
You can Azure AD join the Surface Hub to allow IT pros from your Azure AD tenant to configure settings. During first run, choose to use [Microsoft Azure Active Directory](first-run-program-surface-hub.md#a-href-iduse-microsoft-azureause-microsoft-azure-active-directory). You will need to provide credentials that are capable of joining the Azure AD tenant of your choice. After you successfully Azure AD join, the appropriate people will be granted admin rights on the device.
|
||||
You can Azure AD join the Surface Hub to allow IT pros from your Azure AD tenant to configure settings. During first run, choose to use [Microsoft Azure Active Directory](first-run-program-surface-hub.md#use-microsoft-azure-active-directory). You will need to provide credentials that are capable of joining the Azure AD tenant of your choice. After you successfully Azure AD join, the appropriate people will be granted admin rights on the device.
|
||||
|
||||
By default, all **global administrators** will be given admin rights on an Azure AD joined Surface Hub. With **Azure AD Premium** or **Enterprise Mobility Suite (EMS)**, you can add additional administrators:
|
||||
1. In the [Azure classic portal](https://manage.windowsazure.com/), click **Active Directory**, and then click the name of your organization's directory.
|
||||
|
||||
@ -139,7 +139,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
|
||||
<a href="" id="iptype"></a>**IPType**
|
||||
<p style="margin-left: 20px"> Optional. Type: String. Specifies the network protocol of the connection. Available values are "IPv4", "IPv6", "IPv4v6", and "IPv4v6xlat". If a value is not specified, the default value is "IPv4".
|
||||
|
||||
> [!Warning]
|
||||
> [!WARNING]
|
||||
> Do not use IPv6 or IPv4v6xlat on a device or network that does not support IPv6. Data functionality will not work. In addition, the device will not be able to connect to a roaming network that does not support IPv6 unless you configure roaming connections with an IPType of IPv4v6.
|
||||
|
||||
|
||||
@ -149,7 +149,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
|
||||
|
||||
<p style="margin-left: 20px"> To allow MMS when data is set to OFF, set both ExemptFromDisablePolicy and UseRequiresMappingsPolicy to "1". This indicates that the connection is a dedicated MMS connection and that it should not be disabled when all other connections are disabled. As a result, MMS can be sent and received when data is set to OFF. Note that sending MMS while roaming is still not allowed.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> Do not set ExemptFromDisablePolicy to "1", ExemptFromRoaming to "1", or UseRequiresMappingsPolicy to "1" for general purpose connections.
|
||||
|
||||
<p style="margin-left: 20px"> To avoid UX inconsistency with certain value combinations of ExemptFromDisablePolicy and AllowMmsIfDataIsOff, when you do not set ExemptFromDisablePolicy to 1 (default is 0), you should:
|
||||
@ -168,12 +168,11 @@ The following diagram shows the CM\_CellularEntries configuration service provid
|
||||
<a href="" id="idledisconnecttimeout"></a>**IdleDisconnectTimeout**
|
||||
<p style="margin-left: 20px"> Optional. Type: Int. Specifies how long an on-demand connection can be unused before Connection Manager tears the connection down. This value is specified in seconds. Valid value range is 5 to 60 seconds. If not specified, the default is 30 seconds.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> <p style="margin-left: 20px"> You must specify the IdleDisconnectTimeout value when updating an on-demand connection to ensure that the desired value is still configured. If it is not specified, the default value of 30 seconds may be used.
|
||||
>
|
||||
>
|
||||
>
|
||||
> [!Note]
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> If tear-down/activation requests occur too frequently, this value should be set to greater than 5 seconds.
|
||||
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ Supported operations are Add, Delete, Get and Replace.
|
||||
|
||||
The Apps and Settings sections of lockdown XML constitute an Allow list. Any app or setting that is not specified in AssignedAccessXML will not be available on the device to users. The following table describes the entries in lockdown XML.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> When using the AssignedAccessXml in the EnterpriseAssignedAccess CSP through an MDM, the XML must use escaped characters, such as \< instead of < because it is embedded in an XML. The examples provided in the topic are formatted for readability.
|
||||
|
||||
When using the AssignedAccessXml in a provisioning package using the Windows Configuration Designer tool, do not use escaped characters.
|
||||
@ -268,7 +268,7 @@ Here is an example for Windows 10, version 1703.
|
||||
|
||||
Starting in Windows 10, version 1511, you can specify the following quick action settings in the lockdown XML file. The following list shows the quick action settings and settings page dependencies (group and page).
|
||||
|
||||
> [!Note]
|
||||
> [!NOTE]
|
||||
> Only Windows 10, versions 1511 and 1607, the dependent settings group and pages are automatically added when the quick action item is specified in the lockdown XML. In Windows 10, version 1703, Quick action settings no longer require any dependencies from related group or page.
|
||||
|
||||
<ul>
|
||||
@ -376,7 +376,7 @@ Buttons | The following list identifies the hardware buttons on the device that
|
||||
<li><p>Custom3</p></li>
|
||||
</ul>
|
||||
|
||||
> [!Note]
|
||||
> [!NOTE]
|
||||
> Lock down of the Start button only prevents the press and hold event.
|
||||
>
|
||||
> Custom buttons are hardware buttons that can be added to devices by OEMs.
|
||||
@ -400,7 +400,7 @@ Buttons example:
|
||||
```
|
||||
The Search and custom buttons can be <em>remapped</em> or configured to open a specific application. Button remapping takes effect for the device and applies to all users.
|
||||
|
||||
> [!Note]
|
||||
> [!NOTE]
|
||||
> The lockdown settings for a button, per user role, will apply regardless of the button mapping.
|
||||
>
|
||||
> Button remapping can enable a user to open an application that is not in the Allow list. Use button lock down to prevent application access for a user role.
|
||||
@ -498,7 +498,7 @@ Entry | Description
|
||||
----------- | ------------
|
||||
MenuItems | Use **DisableMenuItems** to prevent use of the context menu, which is displayed when a user presses and holds an application in the All Programs list. You can include this entry in the default profile and in any additional user role profiles that you create.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> If **DisableMenuItems** is not included in a profile, users of that profile can uninstall apps.
|
||||
|
||||
MenuItems example:
|
||||
@ -513,12 +513,12 @@ Entry | Description
|
||||
----------- | ------------
|
||||
Tiles | **Turning-on tile manipulation** - By default, under Assigned Access, tile manipulation is turned off (blocked) and only available if enabled in the user’s profile. If tile manipulation is enabled in the user’s profile, they can pin/unpin, move, and resize tiles based on their preferences. When multiple people use one device and you want to enable tile manipulation for multiple users, you must enable it for each user in their user profile.
|
||||
|
||||
> [!Important]
|
||||
> [!IMPORTANT]
|
||||
> If a device is turned off then back on, the tiles reset to their predefined layout. If a device has only one profile, the only way to reset the tiles is to turn off then turn on the device. If a device has multiple profiles, the device resets the tiles to the predefined layout based on the logged-in user’s profile.
|
||||
|
||||
The following sample file contains configuration for enabling tile manipulation.
|
||||
|
||||
> [!Note]
|
||||
> [!NOTE
|
||||
> Tile manipulation is disabled when you don’t have a `<Tiles>` node in lockdown XML, or if you have a `<Tiles>` node but don’t have the `<EnableTileManipulation>` node.
|
||||
|
||||
``` syntax
|
||||
|
||||
@ -26,7 +26,7 @@ manager: dansimp
|
||||
|
||||
<!--Policy-->
|
||||
|
||||
# Cryptography/AllowFipsAlgorithmPolicy
|
||||
## Cryptography/AllowFipsAlgorithmPolicy
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
@ -68,7 +68,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--Policy-->
|
||||
|
||||
# Cryptography/TLSCipherSuites
|
||||
## Cryptography/TLSCipherSuites
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|Home|Pro|Business |Enterprise |Education |Mobile |Mobile Enterprise |
|
||||
@ -103,7 +103,7 @@ Footnote:
|
||||
<!--/Policies-->
|
||||
|
||||
<!--StartSurfaceHub-->
|
||||
# Cryptography policies supported by Microsoft Surface Hub
|
||||
## Cryptography policies supported by Microsoft Surface Hub
|
||||
|
||||
- [Cryptography/AllowFipsAlgorithmPolicy](#cryptography-allowfipsalgorithmpolicy)
|
||||
- [Cryptography/TLSCipherSuites](#cryptography-tlsciphersuites)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user