mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
Merge branch 'master' into ddv-new-images
This commit is contained in:
Dani Halfin
GitHub
commit
c6e09eea82
@ -2,46 +2,13 @@
|
||||
"build_entry_point": "",
|
||||
"docsets_to_publish": [
|
||||
{
|
||||
"docset_name": "bcs-VSTS",
|
||||
"build_source_folder": "bcs",
|
||||
"build_output_subfolder": "bcs-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "education-VSTS",
|
||||
"docset_name": "education",
|
||||
"build_source_folder": "education",
|
||||
"build_output_subfolder": "education-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "eula-vsts",
|
||||
"build_source_folder": "windows/eulas",
|
||||
"build_output_subfolder": "eula-vsts",
|
||||
"build_output_subfolder": "education",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
@ -51,44 +18,12 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "gdpr",
|
||||
"build_source_folder": "gdpr",
|
||||
"build_output_subfolder": "gdpr",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "internet-explorer-VSTS",
|
||||
"build_source_folder": "browsers/internet-explorer",
|
||||
"build_output_subfolder": "internet-explorer-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "itpro-hololens-VSTS",
|
||||
"docset_name": "hololens",
|
||||
"build_source_folder": "devices/hololens",
|
||||
"build_output_subfolder": "itpro-hololens-VSTS",
|
||||
"build_output_subfolder": "hololens",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -96,35 +31,32 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "keep-secure-VSTS",
|
||||
"docset_name": "internet-explorer",
|
||||
"build_source_folder": "browsers/internet-explorer",
|
||||
"build_output_subfolder": "internet-explorer",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "keep-secure",
|
||||
"build_source_folder": "windows/keep-secure",
|
||||
"build_output_subfolder": "keep-secure-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "known-issues",
|
||||
"build_source_folder": "windows/known-issues",
|
||||
"build_output_subfolder": "known-issues",
|
||||
"build_output_subfolder": "keep-secure",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
@ -134,11 +66,12 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "mdop-VSTS",
|
||||
"docset_name": "mdop",
|
||||
"build_source_folder": "mdop",
|
||||
"build_output_subfolder": "mdop-VSTS",
|
||||
"build_output_subfolder": "mdop",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -146,31 +79,12 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "microsoft-edge-VSTS",
|
||||
"docset_name": "microsoft-edge",
|
||||
"build_source_folder": "browsers/edge",
|
||||
"build_output_subfolder": "microsoft-edge-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "privacy",
|
||||
"build_source_folder": "windows/privacy",
|
||||
"build_output_subfolder": "privacy",
|
||||
"build_output_subfolder": "microsoft-edge",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
@ -184,9 +98,9 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "security",
|
||||
"build_source_folder": "windows/security",
|
||||
"build_output_subfolder": "security",
|
||||
"docset_name": "release-information",
|
||||
"build_source_folder": "windows/release-information",
|
||||
"build_output_subfolder": "release-information",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
@ -194,18 +108,18 @@
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content",
|
||||
"LandingData": "Content"
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "smb-VSTS",
|
||||
"docset_name": "smb",
|
||||
"build_source_folder": "smb",
|
||||
"build_output_subfolder": "smb-VSTS",
|
||||
"build_output_subfolder": "smb",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -213,16 +127,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "store-for-business-VSTS",
|
||||
"docset_name": "store-for-business",
|
||||
"build_source_folder": "store-for-business",
|
||||
"build_output_subfolder": "store-for-business-VSTS",
|
||||
"build_output_subfolder": "store-for-business",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -230,33 +143,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "surface-hub-VSTS",
|
||||
"build_source_folder": "devices/surface-hub",
|
||||
"build_output_subfolder": "surface-hub-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "surface-VSTS",
|
||||
"docset_name": "surface",
|
||||
"build_source_folder": "devices/surface",
|
||||
"build_output_subfolder": "surface-VSTS",
|
||||
"build_output_subfolder": "surface",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -264,16 +159,31 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-access-protection-VSTS",
|
||||
"docset_name": "surface-hub",
|
||||
"build_source_folder": "devices/surface-hub",
|
||||
"build_output_subfolder": "surface-hub",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-access-protection",
|
||||
"build_source_folder": "windows/access-protection",
|
||||
"build_output_subfolder": "win-access-protection-VSTS",
|
||||
"build_output_subfolder": "win-access-protection",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -281,16 +191,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-app-management-VSTS",
|
||||
"docset_name": "win-app-management",
|
||||
"build_source_folder": "windows/application-management",
|
||||
"build_output_subfolder": "win-app-management-VSTS",
|
||||
"build_output_subfolder": "win-app-management",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -298,16 +207,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-client-management-VSTS",
|
||||
"docset_name": "win-client-management",
|
||||
"build_source_folder": "windows/client-management",
|
||||
"build_output_subfolder": "win-client-management-VSTS",
|
||||
"build_output_subfolder": "win-client-management",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -315,16 +223,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-configuration-VSTS",
|
||||
"docset_name": "win-configuration",
|
||||
"build_source_folder": "windows/configuration",
|
||||
"build_output_subfolder": "win-configuration-VSTS",
|
||||
"build_output_subfolder": "win-configuration",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -332,16 +239,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-development-VSTS",
|
||||
"docset_name": "win-deployment",
|
||||
"build_source_folder": "windows/deployment",
|
||||
"build_output_subfolder": "win-development-VSTS",
|
||||
"build_output_subfolder": "win-deployment",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -349,16 +255,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-device-security-VSTS",
|
||||
"docset_name": "win-device-security",
|
||||
"build_source_folder": "windows/device-security",
|
||||
"build_output_subfolder": "win-device-security-VSTS",
|
||||
"build_output_subfolder": "win-device-security",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -366,16 +271,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-configure-VSTS",
|
||||
"docset_name": "windows-configure",
|
||||
"build_source_folder": "windows/configure",
|
||||
"build_output_subfolder": "windows-configure-VSTS",
|
||||
"build_output_subfolder": "windows-configure",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -383,16 +287,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-deploy-VSTS",
|
||||
"docset_name": "windows-deploy",
|
||||
"build_source_folder": "windows/deploy",
|
||||
"build_output_subfolder": "windows-deploy-VSTS",
|
||||
"build_output_subfolder": "windows-deploy",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -400,16 +303,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-hub-VSTS",
|
||||
"docset_name": "windows-hub",
|
||||
"build_source_folder": "windows/hub",
|
||||
"build_output_subfolder": "windows-hub-VSTS",
|
||||
"build_output_subfolder": "windows-hub",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -417,16 +319,31 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-manage-VSTS",
|
||||
"docset_name": "windows-known-issues",
|
||||
"build_source_folder": "windows/known-issues",
|
||||
"build_output_subfolder": "windows-known-issues",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-manage",
|
||||
"build_source_folder": "windows/manage",
|
||||
"build_output_subfolder": "windows-manage-VSTS",
|
||||
"build_output_subfolder": "windows-manage",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -434,16 +351,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-plan-VSTS",
|
||||
"docset_name": "windows-plan",
|
||||
"build_source_folder": "windows/plan",
|
||||
"build_output_subfolder": "windows-plan-VSTS",
|
||||
"build_output_subfolder": "windows-plan",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -451,16 +367,47 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-update-VSTS",
|
||||
"docset_name": "windows-privacy",
|
||||
"build_source_folder": "windows/privacy",
|
||||
"build_output_subfolder": "windows-privacy",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-security",
|
||||
"build_source_folder": "windows/security",
|
||||
"build_output_subfolder": "windows-security",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-update",
|
||||
"build_source_folder": "windows/update",
|
||||
"build_output_subfolder": "windows-update-VSTS",
|
||||
"build_output_subfolder": "windows-update",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -468,16 +415,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-threat-protection-VSTS",
|
||||
"docset_name": "win-threat-protection",
|
||||
"build_source_folder": "windows/threat-protection",
|
||||
"build_output_subfolder": "win-threat-protection-VSTS",
|
||||
"build_output_subfolder": "win-threat-protection",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -485,16 +431,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-whats-new-VSTS",
|
||||
"docset_name": "win-whats-new",
|
||||
"build_source_folder": "windows/whats-new",
|
||||
"build_output_subfolder": "win-whats-new-VSTS",
|
||||
"build_output_subfolder": "win-whats-new",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -502,9 +447,7 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
}
|
||||
],
|
||||
"notification_subscribers": [
|
||||
@ -544,10 +487,6 @@
|
||||
"master": [
|
||||
"Publish",
|
||||
"Pdf"
|
||||
],
|
||||
"atp-api-danm": [
|
||||
"Publish",
|
||||
"Pdf"
|
||||
]
|
||||
},
|
||||
"need_generate_pdf_url_template": true,
|
||||
|
||||
@ -19,14 +19,13 @@
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "microsoft-edge",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "shortpatti",
|
||||
"ms.date": "04/05/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.microsoft-edge"
|
||||
"depot_name": "Win.microsoft-edge",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -1,96 +1,52 @@
|
||||
---
|
||||
title: Microsoft Edge - Frequently Asked Questions (FAQs) for IT Pros
|
||||
description: Answers to frequently asked questions about Microsoft Edge features, integration, support, and potential problems.
|
||||
author: shortpatti
|
||||
ms.author: pashort
|
||||
author: lizap
|
||||
ms.author: elizapo
|
||||
ms.prod: edge
|
||||
ms.topic: reference
|
||||
ms.topic: article
|
||||
ms.mktglfcycl: general
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/05/2018
|
||||
---
|
||||
|
||||
# Frequently Asked Questions (FAQs) for IT Pros
|
||||
|
||||
>Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
|
||||
|
||||
**Q: Why is the Sync settings option under Settings \> Accounts \> Sync your settings permanently disabled?
|
||||
## How can I get the next major version of Microsoft Edge, based on Chromium?
|
||||
In December 2018, Microsoft [announced](https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/#8jv53blDvL6TIKuS.97) our intention to adopt the Chromium open source project in the development of Microsoft Edge on the desktop, to create better web compatibility for our customers and less fragmentation of the web for all web developers. You can get more information at the [Microsoft Edge Insiders site](https://www.microsoftedgeinsider.com/).
|
||||
|
||||
**A:** In the Windows 10 Anniversary Update, domain-joined users who connected their Microsoft Account (MSA) could roam settings and data between Windows devices. A group policy to prevent users from connecting their MSAs exists, but this setting also prevents users from easily accessing their personal Microsoft services. Enterprises can still enable Enterprise State Roaming with Azure Active Directory.
|
||||
## What’s the difference between Microsoft Edge and Internet Explorer 11? How do I know which one to use?
|
||||
Microsoft Edge is the default browser for all Windows 10 devices. It’s built to be highly compatible with the modern web. For some enterprise web apps and a small set of sites that were built to work with older technologies like ActiveX, [you can use Enterprise Mode](emie-to-improve-compatibility.md) to automatically send users to Internet Explorer 11.
|
||||
|
||||
>In a nutshell, any fresh install of Windows 10 Creators Update or higher does not support funtionality if it's under an Active Directory, but works for Azure Active Directory.
|
||||
For more information on how Internet Explorer and Microsoft Edge work together to support your legacy web apps, while still defaulting to the higher security and modern experiences enabled by Microsoft Edge, see [Legacy apps in the enterprise](https://blogs.windows.com/msedgedev/2017/04/07/legacy-web-apps-enterprise/#RAbtRvJSYFaKu2BI.97).
|
||||
|
||||
**Q: What is the size of the local storage for Microsoft Edge overall and per domain?**
|
||||
## Does Microsoft Edge work with Enterprise Mode?
|
||||
[Enterprise Mode](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11) helps you run many legacy web applications with better backward compatibility. You can configure both Microsoft Edge and Internet Explorer to use the same Enterprise Mode Site List, switching seamlessly between browsers to support both modern and legacy web apps.
|
||||
|
||||
**A:** The limits are 5MB per subdomain, 10MB per domain, and 50MB total.
|
||||
## How do I customize Microsoft Edge and related settings for my organization?
|
||||
You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/group-policies/) for a list of policies currently available for Microsoft Edge and configuration information. Note that the preview release of Chromium-based Microsoft Edge might not include management policies or other enterprise functionality; our focus during the preview is modern browser fundamentals.
|
||||
|
||||
**Q: What is the difference between Microsoft Edge and Internet Explorer 11? How do I know which one to use?**
|
||||
## Is Adobe Flash supported in Microsoft Edge?
|
||||
Adobe Flash is currently supported as a built-in feature of Microsoft Edge on PCs running Windows 10. In July 2017, Adobe announced that Flash support will end after 2020. With this change to Adobe support, we’ve started to phase Flash out of Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting group policy](https://docs.microsoft.com/microsoft-edge/deploy/available-policies#configure-the-adobe-flash-click-to-run-setting) - this lets you control which websites can run Adobe Flash content.
|
||||
|
||||
**A:** Microsoft Edge is the default browser for all Windows 10 devices. It is built to be highly compatible with the modern web. For some enterprise web apps and a small set of sites on the web that were built to work with older technologies like ActiveX, [you can use Enterprise Mode](https://docs.microsoft.com/microsoft-edge/deploy/emie-to-improve-compatibility) to automatically send users to Internet Explorer 11 for those sites.
|
||||
To learn more about Microsoft’s plan for phasing Flash out of Microsoft Edge and Internet Explorer, see [The End of an Era — Next Steps for Adobe Flash](https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/#3Bcc3QjRw0l7XsZ4.97) (blog article).
|
||||
|
||||
For more information on how Internet Explorer and Microsoft Edge can work together to support your legacy web apps, while still defaulting to the higher bar for security and modern experiences enabled by Microsoft Edge, see [Legacy apps in the enterprise](https://blogs.windows.com/msedgedev/2017/04/07/legacy-web-apps-enterprise/#RAbtRvJSYFaKu2BI.97).
|
||||
## Does Microsoft Edge support ActiveX controls or BHOs like Silverlight or Java?
|
||||
No. Microsoft Edge doesn’t support ActiveX controls and BHOs like Silverlight or Java. If you’re running web apps that use ActiveX controls, x-ua-compatible headers, or legacy document modes, you need to keep running them in IE11. IE11 offers additional security, manageability, performance, backward compatibility, and standards support.
|
||||
|
||||
**Q: Does Microsoft Edge work with Enterprise Mode?**
|
||||
## How often will Microsoft Edge be updated?
|
||||
In Windows 10, we’re delivering Windows as a service, updated on a cadence driven by quality and the availability of new features. Microsoft Edge security updates are released every two to four weeks, while bigger feature updates are included in the Windows 10 releases on a semi-annual cadence.
|
||||
|
||||
**A:** [Enterprise Mode](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11) offers better backward compatibility and enables customers to run many legacy web applications. Microsoft Edge and Internet Explorer can be configured to use the same Enterprise Mode Site List, switching seamlessly between browsers to support both modern and legacy web apps.
|
||||
## How can I provide feedback on Microsoft Edge?
|
||||
Microsoft Edge is an evergreen browser - we’ll continue to evolve both the web platform and the user interface with regular updates. To send feedback on user experience, or on broken or malicious sites, use the **Send Feedback** option under the ellipses icon (**...**) in the Microsoft Edge toolbar.
|
||||
|
||||
## Will Internet Explorer 11 continue to receive updates?
|
||||
We’re committed to keeping Internet Explorer a supported, reliable, and safe browser. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it’s installed. For details, see [Lifecycle FAQ - Internet Explorer](https://support.microsoft.com/help/17454/). While we continue to support and update Internet Explorer, the latest features and platform updates will only be available in Microsoft Edge.
|
||||
|
||||
**Q: I have Windows 10, but I don’t seem to have Microsoft Edge. Why?**
|
||||
|
||||
**A:** Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016 and Windows Server 2019, don't include Microsoft Edge or many other Universal Windows Platform (UWP) apps. These apps and their services are frequently updated with new functionality and can't be supported on systems running LTSB operating systems. For customers who require the LTSB for specialized devices, we recommend using Internet Explorer 11.
|
||||
|
||||
**Q: How do I get the latest Canary/Beta/Preview version of Microsoft Edge?**
|
||||
|
||||
**A:** You can access the latest preview version of Microsoft Edge by updating to the latest Windows 10 preview via the [Windows Insider Program](https://insider.windows.com/). To run the preview version of Microsoft Edge on a stable version of Windows 10 (or any other OS), you can download a [Virtual Machine](https://developer.microsoft.com/microsoft-edge/tools/vms/windows/) that we provide or use the upcoming RemoteEdge service.
|
||||
|
||||
**Q: How do I customize Microsoft Edge and related settings for my organization?**
|
||||
|
||||
**A:** You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/group-policies/index) for a list of available policies for Microsoft Edge and configuration combinations.
|
||||
|
||||
**Q: Is Adobe Flash supported in Microsoft Edge?**
|
||||
|
||||
**A:** Currently, Adobe Flash is supported as a built-in feature of Microsoft Edge on devices running the desktop version of Windows 10. In July 2017, Adobe announced that Flash will no longer be supported after 2020. With Adobe no longer supporting Flash after 2020, Microsoft has started to phase out Flash from Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting](available-policies.md#configure-the-adobe-flash-click-to-run-setting) group policy giving you a way to control the list of websites that have permission to run Adobe Flash content.
|
||||
|
||||
|
||||
|
||||
To learn more about Microsoft’s plan for phasing out Flash from Microsoft Edge and Internet Explorer, see [The End of an Era — Next Steps for Adobe Flash]( https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/#3Bcc3QjRw0l7XsZ4.97) (blog article).
|
||||
|
||||
|
||||
**Q: Does Microsoft Edge support ActiveX controls or BHOs like Silverlight or Java?**
|
||||
|
||||
**A:** No. Microsoft Edge does not support ActiveX controls and BHOs such as Silverlight or Java. If you are running web apps that continue to use ActiveX controls, x-ua-compatible headers, or legacy document modes, you need to keep running them in IE11. IE11 offers additional security, manageability, performance, backward compatibility, and modern standards support.
|
||||
|
||||
|
||||
**Q: How often will Microsoft Edge be updated?**
|
||||
|
||||
**A:** In Windows 10, we are delivering Windows as a service, updated on a cadence driven by quality and the availability of new features. Microsoft Edge security updates are released every two to four weeks, and the bigger feature updates are currently pushed out with the Windows 10 releases on a semi-annual cadence.
|
||||
|
||||
**Q: How can I provide feedback on Microsoft Edge?**
|
||||
|
||||
**A:** Microsoft Edge is an evergreen browser and we will continue to evolve both the web platform and the user interface with regular updates. To send feedback on user experience, or on broken or malicious sites, you can use the **Send Feedback** option under the ellipses icon (**...**) in the Microsoft Edge toolbar. You can also provide feedback through the [Microsoft Edge Dev Twitter](https://twitter.com/MSEdgeDev) account.
|
||||
|
||||
**Q: Will Internet Explorer 11 continue to receive updates?**
|
||||
|
||||
**A:** We will continue to deliver security updates to Internet Explorer 11 through its supported lifespan. To ensure consistent behavior across Windows versions, we will evaluate Internet Explorer 11 bugs for servicing on a case by case basis. The latest features and platform updates will only be available in Microsoft Edge.
|
||||
|
||||
**Q: I loaded a web page and Microsoft Edge sent me to Internet Explorer - what happened?**
|
||||
|
||||
**A:** In some cases, Internet Explorer loads automatically for sites that still rely on legacy technologies such as ActiveX. For more information, read [Legacy web apps in the enterprise](https://blogs.windows.com/msedgedev/2017/04/07/legacy-web-apps-enterprise/#uHpbs94kAaVsU1qB.97).
|
||||
|
||||
**Q: Why is Do Not Track (DNT) off by default in Microsoft Edge?**
|
||||
|
||||
**A:** When Microsoft first set the Do Not Track setting to “On” by default in Internet Explorer 10, industry standards had not yet been established. We are now making this default change as the World Wide Web Consortium (W3C) formalizes industry standards to recommend that default settings allow customers to actively indicate whether they want to enable DNT. As a result, DNT will not be enabled by default in upcoming versions of Microsoft’s browsers, but we will provide customers with clear information on how to turn this feature on in the browser settings should you wish to do so.
|
||||
|
||||
**Q: How do I find out what version of Microsoft Edge I have?**
|
||||
|
||||
**A:** Open Microsoft Edge. In the upper right corner click the ellipses icon (**…**), and then click **Settings**. Look in the **About this app** section to find your version.
|
||||
|
||||
**Q: What is Microsoft EdgeHTML?**
|
||||
|
||||
**A:** Microsoft EdgeHTML is the new web rendering engine that powers the Microsoft Edge web browser and Windows 10 web app platform, and that helps web developers build and maintain a consistent site across all modern browsers. The Microsoft EdgeHTML engine also helps to defend against hacking through support for the W3C standard for [Content Security Policy (CSP)](https://developer.microsoft.com/microsoft-edge/platform/documentation/dev-guide/security/content-Security-Policy), which can help web developers defend their sites against cross-site scripting attacks, and support for the [HTTP Strict Transport Security (HSTS)](https://developer.microsoft.com/microsoft-edge/platform/documentation/dev-guide/security/HSTS/) security feature (IETF-standard compliant), which helps ensure that connections to important sites, such as to your bank, are always secured.
|
||||
|
||||
**Q: Will Windows 7 or Windows 8.1 users get Microsoft Edge or the new Microsoft EdgeHTML rendering engine?**
|
||||
|
||||
**A:** No. Microsoft Edge has been designed and built to showcase Windows 10 features like Cortana, and is built on top of the Universal Windows Platform.
|
||||
## How do I find out what version of Microsoft Edge I have?
|
||||
In the upper right corner of Microsoft Edge, click the ellipses icon (**...**), and then click **Settings**. Look in the **About Microsoft Edge** section to find your version.
|
||||
|
||||
## What is Microsoft EdgeHTML?
|
||||
Microsoft EdgeHTML is the web rendering engine that powers the current Microsoft Edge web browser and Windows 10 web app platform. (As opposed to *Microsoft Edge, based on Chromium*.)
|
||||
|
||||
@ -27,7 +27,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.internet-explorer"
|
||||
"depot_name": "Win.internet-explorer",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -12,5 +12,6 @@
|
||||
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
|
||||
## [Install apps on HoloLens](hololens-install-apps.md)
|
||||
## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
|
||||
## [Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md)
|
||||
## [How HoloLens stores data for spaces](hololens-spaces.md)
|
||||
## [Change history for Microsoft HoloLens documentation](change-history-hololens.md)
|
||||
@ -9,16 +9,17 @@ author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/05/2018
|
||||
---
|
||||
|
||||
# Change history for Microsoft HoloLens documentation
|
||||
|
||||
This topic lists new and updated topics in the [Microsoft HoloLens documentation](index.md).
|
||||
|
||||
## Windows 10 Holographic for Business, version 1809
|
||||
## April 2019
|
||||
|
||||
The topics in this library have been updated for Windows 10 Holographic for Business, version 1809.
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md) | New
|
||||
|
||||
## November 2018
|
||||
|
||||
@ -26,6 +27,10 @@ New or changed topic | Description
|
||||
--- | ---
|
||||
[How HoloLens stores data for spaces](hololens-spaces.md) | New
|
||||
|
||||
## Windows 10 Holographic for Business, version 1809
|
||||
|
||||
The topics in this library have been updated for Windows 10 Holographic for Business, version 1809.
|
||||
|
||||
|
||||
## October 2018
|
||||
|
||||
|
||||
@ -40,7 +40,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.itpro-hololens"
|
||||
"depot_name": "Win.itpro-hololens",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
60
devices/hololens/hololens-recovery.md
Normal file
60
devices/hololens/hololens-recovery.md
Normal file
@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Restore HoloLens 2 using Advanced Recovery Companion
|
||||
description: How to use Advanced Recovery Companion to flash an image to HoloLens 2.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Restore HoloLens 2 using Advanced Recovery Companion
|
||||
|
||||
>[!TIP]
|
||||
>If you're having issues with HoloLens (the first device released), see [Restart, reset, or recover HoloLens](https://support.microsoft.com/help/13452/hololens-restart-reset-or-recover-hololens). Advanced Recovery Companion is only supported for HoloLens 2.
|
||||
|
||||
>[!WARNING]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
The Advanced Recovery Companion is a new app in Microsoft Store that you can use to restore the operating system image to your HoloLens device.
|
||||
|
||||
When your HoloLens 2 is unresponsive, not running properly, or is experiencing software or update problems, try these things in order:
|
||||
|
||||
1. [Restart](#restart-hololens-2) the HoloLens 2.
|
||||
2. [Reset](#reset-hololens-2) the HoloLens 2.
|
||||
3. [Recover](#recover-hololens-2) the HoloLens 2.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Resetting or recovering your HoloLens will erase all of your personal data, including apps, games, photos, and settings. You won’t be able to restore a backup once the reset is complete.
|
||||
|
||||
## Restart HoloLens 2
|
||||
|
||||
A device restart can often "fix" a computer issue. First, say "Hey Cortana, restart the device."
|
||||
|
||||
If you’re still having problems, press the power button for 4 seconds, until all of the battery indicators fade out. Wait 1 minute, then press the power button again to turn on the device.
|
||||
|
||||
If neither of those things works, force restart the device. Hold down the power button for 10 seconds. Release it and wait 30 seconds, then press the power button again to turn on the device.
|
||||
|
||||
## Reset HoloLens 2
|
||||
|
||||
If the device is still having a problem after restart, use reset to return the HoloLens 2 to factory settings.
|
||||
|
||||
To reset your HoloLens 2, go to **Settings > Update > Reset** and select **Reset device**.
|
||||
|
||||
>[!NOTE]
|
||||
>The battery needs at least 40 percent charge to reset.
|
||||
|
||||
## Recover HoloLens 2
|
||||
|
||||
If the device is still having a problem after reset, you can use Advanced Recovery Companion to flash the device with a new image.
|
||||
|
||||
1. On your computer, get [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from Microsoft Store.
|
||||
2. Connect HoloLens 2 to your computer.
|
||||
3. Start Advanced Recovery Companion.
|
||||
4. On the **Welcome** page, select your device.
|
||||
5. On the **Device info** page, select **Install software** to install the default package. (If you have a Full Flash Update (FFU) image that you want to install instead, select **Manual package selection**.)
|
||||
6. Software installation will begin. Do not use the device or disconnect the cable during installation. When you see the **Installation finished** page, you can disconnect and use your device.
|
||||
|
||||
>[!NOTE]
|
||||
>[Learn about FFU image file formats.](https://docs.microsoft.com/windows-hardware/manufacture/desktop/wim-vs-ffu-image-file-formats)
|
||||
@ -2,6 +2,7 @@
|
||||
## [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
|
||||
## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
## [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
### [Surface Hub Site Readiness Guide](surface-hub-site-readiness-guide.md)
|
||||
### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
|
||||
### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
|
||||
#### [Online deployment](online-deployment-surface-hub-device-accounts.md)
|
||||
@ -40,11 +41,15 @@
|
||||
### [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
|
||||
### [Enable 802.1x wired authentication](enable-8021x-wired-authentication.md)
|
||||
### [Using a room control system](use-room-control-system-with-surface-hub.md)
|
||||
### [Implement Quality of Service on Surface Hub](surface-hub-qos.md)
|
||||
### [Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md)
|
||||
### [Surface Hub SSD replacement](surface-hub-ssd-replacement.md)
|
||||
## [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md)
|
||||
## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
|
||||
## [Top support solutions for Surface Hub](support-solutions-surface-hub.md)
|
||||
## [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
## [Troubleshoot Miracast on Surface Hub](miracast-troubleshooting.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)
|
||||
@ -64,8 +64,11 @@ Surface Hubs use Azure AD join to:
|
||||
- Grant admin rights to the appropriate users in your Azure AD tenant.
|
||||
- Backup the device's BitLocker recovery key by storing it under the account that was used to Azure AD join the device. See [Save your BitLocker key](save-bitlocker-key-surface-hub.md) for details.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Surface Hub does not currently support automatic enrollment to Microsoft Intune through Azure AD join. If your organization automatically enrolls Azure AD joined devices into Intune, you must disable this policy for Surface Hub before joining the device to Azure AD.
|
||||
### Automatic enrollment via Azure Active Directory join
|
||||
|
||||
Surface Hub now supports the ability to automatically enroll in Intune by joining the device to Azure Active Directory.
|
||||
|
||||
For more information, see [Enable Windows 10 automatic enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment).
|
||||
|
||||
### Which should I choose?
|
||||
|
||||
|
||||
@ -7,7 +7,6 @@ ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 07/12/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -15,6 +14,16 @@ ms.localizationpriority: medium
|
||||
|
||||
This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
|
||||
|
||||
## April 2019
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Surface Hub Site Readiness Guide](surface-hub-site-readiness-guide.md) | New; previously available for download only
|
||||
[Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
|
||||
[Technical information for 84” Microsoft Surface Hub ](surface-hub-technical-84.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
|
||||
[Surface Hub SSD replacement](surface-hub-ssd-replacement.md) | New; previously available for download only
|
||||
[Implement Quality of Service on Surface Hub](surface-hub-qos.md) | New
|
||||
|
||||
## July 2018
|
||||
|
||||
New or changed topic | Description
|
||||
|
||||
@ -76,7 +76,7 @@ If the device account gets into an unstable state or the Admin account is runnin
|
||||
|
||||
On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset or recover the device from [Windows RE](https://technet.microsoft.com/library/cc765966.aspx).
|
||||
|
||||
1. From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide (PDF)](https://download.microsoft.com/download/3/8/8/3883E991-DFDB-4E70-8D28-20B26045FC5B/Surface-Hub-Site-Readiness-Guide_EN.pdf) for help with locating the power switch.
|
||||
1. From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide (PDF)](surface-hub-site-readiness-guide.md) for help with locating the power switch.
|
||||
2. The device should automatically boot into Windows RE.
|
||||
3. After the Surface Hub enters Windows RE, select **Recover from the cloud**. (Optionally, you can choose **Reset**, however **Recover from the cloud** is the recommended approach.)
|
||||
|
||||
|
||||
@ -29,7 +29,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.surface-hub"
|
||||
"depot_name": "Win.surface-hub",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
BIN
devices/surface-hub/images/35mm.png
Normal file
BIN
devices/surface-hub/images/35mm.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.1 KiB |
BIN
devices/surface-hub/images/analog.png
Normal file
BIN
devices/surface-hub/images/analog.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.1 KiB |
BIN
devices/surface-hub/images/caution.PNG
Normal file
BIN
devices/surface-hub/images/caution.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.3 KiB |
BIN
devices/surface-hub/images/dport.png
Normal file
BIN
devices/surface-hub/images/dport.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 609 B |
BIN
devices/surface-hub/images/dportio.png
Normal file
BIN
devices/surface-hub/images/dportio.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.2 KiB |
BIN
devices/surface-hub/images/dportout.png
Normal file
BIN
devices/surface-hub/images/dportout.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 374 B |
BIN
devices/surface-hub/images/hdmi.png
Normal file
BIN
devices/surface-hub/images/hdmi.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.3 KiB |
BIN
devices/surface-hub/images/iec.png
Normal file
BIN
devices/surface-hub/images/iec.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 434 B |
BIN
devices/surface-hub/images/key-55.png
Normal file
BIN
devices/surface-hub/images/key-55.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.5 KiB |
BIN
devices/surface-hub/images/qos-create.png
Normal file
BIN
devices/surface-hub/images/qos-create.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface-hub/images/qos-setting.png
Normal file
BIN
devices/surface-hub/images/qos-setting.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
devices/surface-hub/images/replacement-port-55.PNG
Normal file
BIN
devices/surface-hub/images/replacement-port-55.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
BIN
devices/surface-hub/images/replacement-port-84.PNG
Normal file
BIN
devices/surface-hub/images/replacement-port-84.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
devices/surface-hub/images/rj11.png
Normal file
BIN
devices/surface-hub/images/rj11.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.5 KiB |
BIN
devices/surface-hub/images/rj45.png
Normal file
BIN
devices/surface-hub/images/rj45.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
BIN
devices/surface-hub/images/sh-55-bottom.png
Normal file
BIN
devices/surface-hub/images/sh-55-bottom.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
devices/surface-hub/images/sh-55-clearance.png
Normal file
BIN
devices/surface-hub/images/sh-55-clearance.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
BIN
devices/surface-hub/images/sh-55-front.png
Normal file
BIN
devices/surface-hub/images/sh-55-front.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
devices/surface-hub/images/sh-55-hand-rear.png
Normal file
BIN
devices/surface-hub/images/sh-55-hand-rear.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
devices/surface-hub/images/sh-55-hand.png
Normal file
BIN
devices/surface-hub/images/sh-55-hand.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
devices/surface-hub/images/sh-55-rear.png
Normal file
BIN
devices/surface-hub/images/sh-55-rear.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
devices/surface-hub/images/sh-55-top.png
Normal file
BIN
devices/surface-hub/images/sh-55-top.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
devices/surface-hub/images/sh-84-bottom.png
Normal file
BIN
devices/surface-hub/images/sh-84-bottom.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
BIN
devices/surface-hub/images/sh-84-clearance.png
Normal file
BIN
devices/surface-hub/images/sh-84-clearance.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface-hub/images/sh-84-front.png
Normal file
BIN
devices/surface-hub/images/sh-84-front.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
devices/surface-hub/images/sh-84-hand-top.png
Normal file
BIN
devices/surface-hub/images/sh-84-hand-top.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
devices/surface-hub/images/sh-84-hand.png
Normal file
BIN
devices/surface-hub/images/sh-84-hand.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface-hub/images/sh-84-rear.png
Normal file
BIN
devices/surface-hub/images/sh-84-rear.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
devices/surface-hub/images/sh-84-side.png
Normal file
BIN
devices/surface-hub/images/sh-84-side.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.0 KiB |
BIN
devices/surface-hub/images/sh-84-top.png
Normal file
BIN
devices/surface-hub/images/sh-84-top.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
devices/surface-hub/images/sh-84-wall.png
Normal file
BIN
devices/surface-hub/images/sh-84-wall.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
BIN
devices/surface-hub/images/ssd-click.PNG
Normal file
BIN
devices/surface-hub/images/ssd-click.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
devices/surface-hub/images/ssd-lift-door.PNG
Normal file
BIN
devices/surface-hub/images/ssd-lift-door.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
devices/surface-hub/images/ssd-location.PNG
Normal file
BIN
devices/surface-hub/images/ssd-location.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
BIN
devices/surface-hub/images/ssd-lock-tab.PNG
Normal file
BIN
devices/surface-hub/images/ssd-lock-tab.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
devices/surface-hub/images/ssd-pull-tab.PNG
Normal file
BIN
devices/surface-hub/images/ssd-pull-tab.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
BIN
devices/surface-hub/images/switch.png
Normal file
BIN
devices/surface-hub/images/switch.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 873 B |
BIN
devices/surface-hub/images/usb.png
Normal file
BIN
devices/surface-hub/images/usb.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
BIN
devices/surface-hub/images/vga.png
Normal file
BIN
devices/surface-hub/images/vga.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 641 B |
Binary file not shown.
@ -46,7 +46,7 @@ In some ways, adding your new Surface Hub is just like adding any other Microsof
|
||||
| [Top support solutions for Surface Hub](support-solutions-surface-hub.md) | These are the top Microsoft Support solutions for common issues experienced using Surface Hub. |
|
||||
| [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md) | Troubleshoot common problems, including setup issues, Exchange ActiveSync errors. |
|
||||
| [Troubleshoot Miracast on Surface Hub](miracast-troubleshooting.md) | Learn how to resolve Miracast issues. |
|
||||
| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide. |
|
||||
| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents. |
|
||||
| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation library. |
|
||||
|
||||
|
||||
|
||||
@ -41,6 +41,7 @@ Learn about managing and updating Surface Hub.
|
||||
[Enable 802.1x wired authentication](enable-8021x-wired-authentication.md) | 802.1x Wired Authentication MDM policies have been enabled on Surface Hub devices.
|
||||
| [Using a room control system](https://technet.microsoft.com/itpro/surface-hub/use-room-control-system-with-surface-hub) | Room control systems can be used with your Microsoft Surface Hub.|
|
||||
[Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md) | Use the Surface Hub Recovery Tool to re-image the Surface Hub SSD.
|
||||
[Surface Hub SSD replacement](surface-hub-ssd-replacement.md) | Learn how to remove and replace the solid state drive in your Surface Hub.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ms.localizationpriority: medium
|
||||
# Physically install Microsoft Surface Hub
|
||||
|
||||
|
||||
The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation. You can download the Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718144). It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.
|
||||
The [Microsoft Surface Hub Readiness Guide](surface-hub-site-readiness-guide.md) will help make sure that your site is ready for the installation. It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.
|
||||
|
||||
You may also want to check out the Unpacking Guide. It will show you how to unpack the devices efficiently and safely. There are two guides, one for the 55" and one for the 84". A printed version of the Unpacking Guide is attached to the outside front of each unit's shipping crate.
|
||||
|
||||
|
||||
@ -12,16 +12,14 @@ ms.localizationpriority: medium
|
||||
|
||||
# Useful downloads for Microsoft Surface Hub
|
||||
|
||||
This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide.
|
||||
This topic provides links to useful Surface Hub documents, such as product datasheets and user's guide.
|
||||
|
||||
| Link | Description |
|
||||
| --- | --- |
|
||||
| [Surface Hub Site Readiness Guide (PDF)](https://download.microsoft.com/download/3/8/8/3883E991-DFDB-4E70-8D28-20B26045FC5B/Surface-Hub-Site-Readiness-Guide_EN.pdf) | Make sure your site is ready for Surface Hub, including structural and power requirements, and get technical specs for Surface Hub. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/27/aa/27aa7dd7-7cb7-40ea-9bd6-c7de0795f68c.mov?n=04.07.16_installation_video_01_site_readiness.mov) |
|
||||
| [Surface Hub Setup Guide (English, French, Spanish) (PDF)](https://download.microsoft.com/download/0/1/6/016363A4-8602-4F01-8281-9BE5C814DC78/Setup-Guide_EN-FR-SP.pdf) | Get a quick overview of how to set up the environment for your new Surface Hub. |
|
||||
| [Surface Hub Quick Reference Guide (PDF)](https://download.microsoft.com/download/9/E/E/9EE660F8-3FC6-4909-969E-89EA648F06DB/Surface%20Hub%20Quick%20Reference%20Guide_en-us.pdf) | Use this quick reference guide to get information about key features and functions of the Surface Hub. |
|
||||
| [Surface Hub User Guide (PDF)](https://download.microsoft.com/download/3/6/B/36B6331E-0C63-4E71-A05D-EE88D05081F8/surface-hub-user-guide-en-us.pdf) | Learn how to use Surface Hub in scheduled or ad-hoc meetings. Invite remote participants, use the built-in tools, save data from your meeting, and more. |
|
||||
| [Surface Hub Replacement PC Drivers](https://www.microsoft.com/download/details.aspx?id=52210) | The Surface Hub Replacement PC driver set is available for those customers who have chosen to disable the Surface Hub’s internal PC and use an external computer with their 84” or 55” Surface Hub. This download is meant to be used with the Surface Hub Admin Guide , which contains further details on configuring a Surface Hub Replacement PC. |
|
||||
| [Surface Hub SSD Replacement Guide (PDF)](https://download.microsoft.com/download/1/F/2/1F202254-7156-459F-ABD2-39CF903A25DE/surface-hub-ssd-replacement-guide_en-us.pdf) | Learn how to replace the solid state drive (SSD) for the 55- and 84-inch Surface Hub. |
|
||||
| [Microsoft Surface Hub Rollout and Adoption Success Kit (ZIP)](https://download.microsoft.com/download/F/A/3/FA3ADEA4-4966-456B-8BDE-0A594FD52C6C/Surface_Hub_Adoption_Kit_Final_0519.pdf) | Best practices for generating awareness and implementing change management to maximize adoption, usage, and benefits of Microsoft Surface Hub. The Rollout and Adoption Success Kit zip file includes the Rollout and Adoption Success Kit detailed document, Surface Hub presentation, demo guidance, awareness graphics, and more. |
|
||||
| [Unpacking Guide for 84-inch Surface Hub (PDF)](https://download.microsoft.com/download/5/2/B/52B4007E-D8C8-4EED-ACA9-FEEF93F6055C/84_Unpacking_Guide_English_French-Spanish.pdf) | Learn how to unpack your 84-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/75/2b/752b73dc-6e9d-4692-8ba1-0f9fc03bff6b.mov?n=04.07.16_installation_video_03_unpacking_84.mov) |
|
||||
| [Unpacking Guide for 55-inch Surface Hub (PDF)](https://download.microsoft.com/download/2/E/7/2E7616A2-F936-4512-8052-1E2D92DFD070/55_Unpacking_Guide_English-French-Spanish.PDF) | Learn how to unpack your 55-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/a9/d6/a9d6b4d7-d33f-4e8b-be92-28f7fc2c06d7.mov?n=04.07.16_installation_video_02_unpacking_55.mov) |
|
||||
|
||||
51
devices/surface-hub/surface-hub-qos.md
Normal file
51
devices/surface-hub/surface-hub-qos.md
Normal file
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: Implement Quality of Service on Surface Hub
|
||||
description: Learn how to configure QoS on Surface Hub.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Implement Quality of Service (QoS) on Surface Hub
|
||||
|
||||
Quality of Service (QoS) is a combination of network technologies that allows the administrators to optimize the experience of real time audio/video and application sharing communications.
|
||||
|
||||
Configuring [QoS for Skype for Business](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp) on the Surface Hub can be done using your [mobile device management (MDM) provider](manage-settings-with-mdm-for-surface-hub.md) or through a [provisioning package](provisioning-packages-for-surface-hub.md).
|
||||
|
||||
|
||||
This procedure explains how to configure QoS for Surface Hub using Microsoft Intune.
|
||||
|
||||
1. In Intune, [create a custom policy](https://docs.microsoft.com/intune/custom-settings-configure).
|
||||
|
||||
|
||||
|
||||
2. In **Custom OMA-URI Settings**, select **Add**. For each setting that you add, you will enter a name, description (optional), data type, OMA-URI, and value.
|
||||
|
||||
|
||||
|
||||
3. Add the following custom OMA-URI settings:
|
||||
|
||||
Name | Data type | OMA-URI<br>./Device/Vendor/MSFT/NetworkQoSPolicy | Value
|
||||
--- | --- | --- | ---
|
||||
Audio Source Port | String | /HubAudio/SourcePortMatchCondition | Get the values from your Skype administrator
|
||||
Audio DSCP | Integer | /HubAudio/DSCPAction | 46
|
||||
Video Source Port | String | /HubVideo/SourcePortMatchCondition | Get the values from your Skype administrator
|
||||
Video DSCP | Integer | /HubVideo/DSCPAction | 34
|
||||
Audio Process Name | String | /HubAudio/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
|
||||
Video Process Name | String | /HubVideo/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Each **OMA-URI** path begins with `./Device/Vendor/MSFT/NetworkQoSPolicy`. The full path for the audio source port setting, for example, will be `./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/SourcePortMatchCondition`.
|
||||
|
||||
|
||||
|
||||
|
||||
4. When the policy has been created, [deploy it to the Surface Hub.](manage-settings-with-mdm-for-surface-hub.md#manage-surface-hub-settings-with-mdm)
|
||||
|
||||
|
||||
>[!WARNING]
|
||||
>Currently, you cannot configure the setting **IPProtocolMatchCondition** in the [NetworkQoSPolicy CSP](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp). If this setting is configured, the policy will fail to apply.
|
||||
|
||||
@ -16,7 +16,7 @@ ms.localizationpriority: medium
|
||||
|
||||
The [Microsoft Surface Hub Recovery Tool](https://www.microsoft.com/download/details.aspx?id=52210) helps you re-image your Surface Hub Solid State Drive (SSD) using a Windows 10 desktop device, without calling support or replacing the SSD. With this tool, you can reimage an SSD that has an unknown Administrator password, boot errors, was unable to complete a cloud recovery, or for a device that has an older version of the operating system. The tool will not fix physically damaged SSDs.
|
||||
|
||||
To re-image the Surface Hub SSD using the Recovery Tool, you'll need to remove the SSD from the Surface Hub, connect the drive to the USB-to-SATA cable, and then connect the cable to the desktop PC on which the Recovery Tool is installed. For more information on how to remove the existing drive from your Surface Hub, please refer to the [Surface Hub SSD Replacement Guide (PDF)](https://download.microsoft.com/download/1/F/2/1F202254-7156-459F-ABD2-39CF903A25DE/surface-hub-ssd-replacement-guide_en-us.pdf).
|
||||
To re-image the Surface Hub SSD using the Recovery Tool, you'll need to remove the SSD from the Surface Hub, connect the drive to the USB-to-SATA cable, and then connect the cable to the desktop PC on which the Recovery Tool is installed. For more information on how to remove the existing drive from your Surface Hub, see [Surface Hub SSD replacement](surface-hub-ssd-replacement.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Do not let the device go to sleep or interrupt the download of the image file.
|
||||
@ -73,7 +73,8 @@ Install Surface Hub Recovery Tool on the host PC.
|
||||
|
||||
|
||||
|
||||
5. When the download is complete, the tool instructs you to connect an SSD drive. If the tool is unable to locate the attached drive, there is a good chance that the cable being used is not reporting the name of the SSD to Windows. The imaging tool must find the name of the drive as "LITEON L CH-128V2S USB Device" before it can continue. For more information on how to remove the existing drive from your Surface Hub, please refer to the [Surface Hub SSD Replacement Guide (PDF)](https://download.microsoft.com/download/1/F/2/1F202254-7156-459F-ABD2-39CF903A25DE/surface-hub-ssd-replacement-guide_en-us.pdf).
|
||||
5. When the download is complete, the tool instructs you to connect an SSD drive. If the tool is unable to locate the attached drive, there is a good chance that the cable being used is not reporting the name of the SSD to Windows. The imaging tool must find the name of the drive as "LITEON L CH-128V2S USB Device" before it can continue. For more information on how to remove the existing drive from your Surface Hub, see [Surface Hub SSD replacement](surface-hub-ssd-replacement.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
135
devices/surface-hub/surface-hub-site-readiness-guide.md
Normal file
135
devices/surface-hub/surface-hub-site-readiness-guide.md
Normal file
@ -0,0 +1,135 @@
|
||||
---
|
||||
title: Surface Hub Site Readiness Guide
|
||||
description: Use this Site Readiness Guide to help plan your Surface Hub installation.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Surface Hub Site Readiness Guide
|
||||
|
||||
Use this Site Readiness Guide to help plan your Surface Hub installation. In this guide, you’ll find:
|
||||
- Site readiness topics
|
||||
- Detailed hardware specifications on power, ports, and cables
|
||||
- Recommendations for moving and storage
|
||||
- Links to guidance on unpacking and mounting
|
||||
|
||||
## Site readiness planning
|
||||
|
||||
The room needs to be large enough to provide good viewing angles, but small enough for the microphones to pick up clear signals from the people in the room. Most rooms that are about 22 feet (seven meters) long will provide a good meeting experience. In the conference area, mount Surface Hub where:
|
||||
|
||||
- Everyone in the room can see it.
|
||||
- People can reach all four edges of the touchscreen.
|
||||
- The screen is not in direct sunlight, which could affect viewing or damage the screen.
|
||||
- Ventilation openings are not blocked.
|
||||
- Microphones are not affected by noise sources, such as fans or vents.
|
||||
You can find more details in the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections. For cleaning, care, and safety information, see the mounting guides and user guide at http://www.microsoft.com/surface/support/surface-hub.
|
||||
|
||||
### Hardware considerations
|
||||
|
||||
Surface Hub arrives with:
|
||||
- Two Microsoft Surface Hub pens
|
||||
- A Microsoft wireless keyboard, customized for Surface Hub
|
||||
- A 9-foot NEMA 5-15P (US Standard) to C13 power cable
|
||||
|
||||
You’ll need to provide:
|
||||
- Cat-5e or Cat-6 network cables
|
||||
- Display cables (optional)
|
||||
- Audio cable (optional)
|
||||
- Type A to B USB cable (optional)
|
||||
|
||||
For details about cable ports, see the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections. For details about cables, see [Wired Connect](#wired).
|
||||
|
||||
Microsoft Surface Hub has an internal PC and does not require an external computer system.
|
||||
|
||||
For power recommendations, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md). For power cable safety warnings, see the mounting guides at http://www.microsoft.com/surface/support/surface-hub.
|
||||
|
||||
### Data and other connections
|
||||
|
||||
To use Surface Hub, you need an active Ethernet port and a standard power outlet. In addition, you may want to:
|
||||
|
||||
- Equip the conference table for Wired Connect.
|
||||
- Expand the wall outlet configuration to include:
|
||||
- Additional AC outlets
|
||||
- Ethernetports
|
||||
- Audio ports
|
||||
- Video ports (DisplayPort, HDMI, VGA, etc.)
|
||||
|
||||
|
||||
## When Surface Hub arrives
|
||||
|
||||
Surface Hub is large and heavy, so let Receiving know when it will arrive and what they should do to handle it safely. For details on the packing weights and other specifications, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md).
|
||||
|
||||
Consider the following:
|
||||
- Wait to unpack Surface Hub from the shipping container until you’ve moved it to the conference area where you plan to install it.
|
||||
- Make sure your loading dock can accept a shipment on a pallet and hold it securely until it can be installed.
|
||||
- Check for local labor union rules that would require you to use union labor to unload or move Surface Hub.
|
||||
- Do not leave Surface Hub in a hot or humid environment. As with any computer-based or display equipment, heat and humidity can damage Surface Hub. The recommended storage temperatures are 32°F to 95°F with a relative humidity of less than 70 percent.
|
||||
|
||||
### Moving Surface Hub
|
||||
|
||||
Before you move Surface Hub, make sure that all the doorways, thresholds, hallways, and elevators are big enough to accommodate it. For information on the dimensions and weight of your Surface Hub in its shipping container, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md).
|
||||
|
||||
### Unpacking Surface Hub
|
||||
|
||||
For unpacking information, refer to the unpacking guide included in the shipping container. You can open the unpacking instructions before you open the shipping container. These instructions can also be found here: http://www.microsoft.com/surface/support/surface-hub
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Retain and store all Surface Hub shipping materials—including the pallet, container, and screws—in case you need to ship Surface Hub to a new location or send it
|
||||
for repairs. For the 84” Surface Hub, retain the lifting handles.
|
||||
|
||||
### Lifting Surface Hub
|
||||
|
||||
The 55” Surface Hub requires two people to safely lift and mount. The 84” Surface Hub requires four people to safely lift and mount. Those assisting must be able to lift 70 pounds to waist height. Review the unpacking and mounting guide for details on lifting Surface Hub. You can find it at http://www.microsoft.com/surface/support/surface-hub.
|
||||
|
||||
## Mounting and setup
|
||||
|
||||
See the [Technical information]() section, or your mounting guide at http://www.microsoft.com/surface/support/surface-hub, for detailed instructions.
|
||||
|
||||
There are three ways to mount your Surface Hub:
|
||||
|
||||
- **Wall mount**: Lets you permanently hang Surface Hub on a conference space wall.
|
||||
- **Floor support mount**: Supports Surface Hub on the floor while it is permanently anchored to a conference space wall.
|
||||
- **Rolling stand**: Supports Surface Hub and lets you move it to other conference locations. For links to guides that provide details about each mounting method, including building requirements, see http://www.microsoft.com/surface/support/surface-hub.
|
||||
|
||||
|
||||
## The Connect experience
|
||||
|
||||
Connect lets people project their laptop, tablet, or phone to the Surface Hub screen. Connect allows wireless or wired connection types.
|
||||
|
||||
#### Wireless connect
|
||||
|
||||
Since wireless connect is based on Miracast, you don’t need cables or additional setup planning to use it. Your users can load Miracast on most Miracast-enabled Windows 8.1 and Windows 10 devices. Then they can project their display from their computer or phone to the Surface Hub screen.
|
||||
|
||||
<span id="wired" />
|
||||
#### Wired connect
|
||||
|
||||
With wired connect, a cable transmits information from computers, tablets, or phones to Surface Hub. There are three video cable options, and they all use the same USB 2.0 cable. The cable bundle can include one or all of these connection options.
|
||||
|
||||
- DisplayPort (DisplayPort cable + USB 2.0 cable)
|
||||
- HDMI (HDMI cable + USB 2.0 cable)
|
||||
- VGA (VGA cable + 3.5mm audio cable + USB 2.0 cable)
|
||||
|
||||
For example, to provide audio, video, and touchback capability to all three video options, your Wired Connect cable bundle must include:
|
||||
|
||||
- A DisplayPort cable
|
||||
- An HDMI cable
|
||||
- A VGA cable
|
||||
- A USB 2.0 cable
|
||||
- A 3.5mm cable
|
||||
|
||||
When you create your wired connect cable bundles, check the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections for specific technical and physical details and port locations for each type of Surface Hub. Make the cables long enough to reach from Surface Hub to where the presenter will sit or stand.
|
||||
|
||||
For details on Touchback and Inkback, see the user guide at http://www.microsoft.com/surface/support/surface-hub.
|
||||
|
||||
|
||||
|
||||
## See also
|
||||
|
||||
[Watch the video (opens in a pop-up media player)][http://compass.xbox.com/assets/27/aa/27aa7dd7-7cb7-40ea-9bd6-c7de0795f68c.mov?n=04.07.16_installation_video_01_site_readiness.mov)
|
||||
|
||||
|
||||
|
||||
52
devices/surface-hub/surface-hub-ssd-replacement.md
Normal file
52
devices/surface-hub/surface-hub-ssd-replacement.md
Normal file
@ -0,0 +1,52 @@
|
||||
---
|
||||
title: Surface Hub SSD replacement
|
||||
description: Learn how to replace the solid state drive in a Surface Hub.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Surface Hub SSD replacement
|
||||
|
||||
You might need to remove the solid state drive (SSD) from your Surface Hub so that you can reimage it using the [Surface Hub Recovery Tool](surface-hub-recovery-tool.md) or because you've been sent a replacement drive. You would reimage your SSD when the operating system is no longer bootable, such as from a Windows update failure, BitLocker issues, reset failure, or hardware failure.
|
||||
|
||||
|
||||
>[!WARNING]
|
||||
>Make sure the Surface Hub is turned off at the AC switch.
|
||||
|
||||
1. Locate the SSD compartment door on the rear, upper portion of the Surface Hub in the locations illustrated below. The door is identifiable as it doesn't have open ventilation slots.
|
||||
|
||||
|
||||
|
||||
*Surface Hub hard drive locations*
|
||||
|
||||
2. Locate the locking tab on the hard drive compartment door. On the Surface Hub 55, the locking tab will be located on the left-hand side of the door. On the Surface Hub 84, it will be on the right-hand side as shown in the illustration.
|
||||
|
||||
|
||||
|
||||
*Locking tab on hard drive compartment door*
|
||||
|
||||
3. Lift open the compartment door to access the hard drive.
|
||||
|
||||
|
||||
|
||||
*Lift compartment door*
|
||||
|
||||
4. Locate the pull tab, which may be partially hidden under the rear cover. Pull on the tab to eject the hard drive from the compartment.
|
||||
|
||||
|
||||
|
||||
*Pull tab*
|
||||
|
||||
5. Slide the replacement drive into place until you hear it click.
|
||||
|
||||
|
||||
|
||||
*Slide replacement drive into place*
|
||||
|
||||
6. Close the compartment door.
|
||||
|
||||
7. Apply power to the Surface Hub.
|
||||
151
devices/surface-hub/surface-hub-technical-55.md
Normal file
151
devices/surface-hub/surface-hub-technical-55.md
Normal file
@ -0,0 +1,151 @@
|
||||
---
|
||||
title: Technical information for 55" Surface Hub
|
||||
description: Specifications for the 55" Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Technical information for 55" Surface Hub
|
||||
|
||||
## Measurements
|
||||
|
||||
|
|
||||
--- | ---
|
||||
Pricing | Starting at $8,999
|
||||
Size | 31.75” x 59.62” x 3.38” (806.4mm x 1514.3mm x 85.8mm)
|
||||
Storage/RAM | SSD 128GB with 8GB RAM
|
||||
Processor | 4th Generation Intel® Core™ i5
|
||||
Graphics | Intel® HD 4600
|
||||
Ports | **Internal PC**<br>• (1) USB 3.0 (bottom) + (1) USB 3.0 (side access) <br>• (2) USB 2.0<br>• Ethernet 1000 Base-T<br>• DisplayPort <br>• Video Output<br>• 3.5mm Stereo Out<br>• RJ11 Connector for system-level control<br>**Alternate PC**<br>• (2) USB 2.0 type B output<br>• Connection for Camera, Sensors, Microphone, Speakers<br>• (1) DisplayPort Video Input<br>**Guest PC**<br>• DisplayPort Video Input<br>• HDMI Video Input<br>• VGA Video Input<br>• 3.5mm Stereo Input<br>• (1) USB 2.0 type B Touchback™ Output
|
||||
Sensors | (2) Passive Infrared Presence Sensors, Ambient Light Sensors
|
||||
Speakers | (2) Front-facing stereo speakers
|
||||
Microphone | High-Performance, 4-Element Array
|
||||
Camera | (2) Wide angle HD cameras 1080p @ 30fps
|
||||
Pen | (2) Powered, active, subpixel accuracy
|
||||
Physical side buttons | Power, Input Select, Volume, Brightness
|
||||
Software | Windows 10 + Office (Word, PowerPoint, Excel)
|
||||
What’s in the box | • Surface Hub 55”<br>• (2) Surface Hub Pens<br>• Power Cable<br>• Setup Guide<br>• Start Guide<br>• Safety and Warranty documents<br>• Wireless All-in-One Keyboard
|
||||
Mounting features | 4X VESA standard, 400mm x 400mm plus 1150mm x 400mm pattern, 8X M6 X 1.0 threaded mounting locations
|
||||
Display height from floor | Recommended height of 55 inches (139.7 cm) to center of screen
|
||||
Product weight | Approx. 105 lb. (47.6 kg) without accessories
|
||||
Product shipping weight | Approx. 150 lb. (68 kg)
|
||||
Product dimensions HxWxD | 31.63 x 59.62 x 3.2 inches (80.34 x 151.44 x 8.14 cm)
|
||||
Product shipping dimensions HxWxD | 43 x 65 x 20 inches (109 x 165 x 51 cm)
|
||||
Product thickness | Touch surface to mounting surface: ≤ 2.4 inches (6 cm)
|
||||
Orientation | Landscape only. Display cannot be used in a portrait orientation.
|
||||
BTU | 1706 BTU/h
|
||||
Image resolution | 1920 x 1080
|
||||
Frame rate | 120Hz
|
||||
EDID preferred timing, replacement PC | 1920 x 1080, 120Hz vertical refresh
|
||||
EDID preferred timing, wired connect | 1920 x 1080, 60Hz vertical refresh
|
||||
Input voltage | (50/60Hz) 110/230v nominal, 90-265v max
|
||||
Input power, operating | 500W max
|
||||
Input power, standby | 5W nominal
|
||||
|
||||
|
||||
## Replacement PC connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
Switch, bottom I/O |  | Switches the function between using internal PC or external PC.
|
||||
Display port, bottom I/O |  | Provides input for replacement PC.
|
||||
USB type B, bottom I/O |  | Provides USB connection for replacement PC to internal peripherals.
|
||||
USB type B, bottom I/O |  | Provides USB connection for integrated hub.
|
||||
|
||||
|
||||
## Wired connect connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
Display port, bottom I/O |  | Provides input for wired connect PC.
|
||||
HDMI, bottom I/O |  | Provides HDMI input for wired connect PC.
|
||||
VGA, bottom I/O |  | Provides VGA input for wired connect PC.
|
||||
3.5mm, bottom I/O |  | Provides analog audio input.
|
||||
USB type B, bottom I/O |  | Provides USB connection for video ingest touchback.
|
||||
|
||||
## Additional connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
USB type A, side I/O |  | Provides 1 USB 3.0 connection for USB devices. Wake-on USB capable.
|
||||
USB type A, bottom I/O with blue insulator |  | Provides USB 3.0 connection.
|
||||
3.5mm, bottom I/O |  | Provides analog audio out.
|
||||
Display port, bottom I/O |  | Provides mirrored video out function to another display.
|
||||
IEC/EN60320-C13 receptable with hard switch |  | Provides AC input and compliance with EU power requirements.
|
||||
RJ45, bottom I/O |  | Connects to Ethernet.
|
||||
RJ11, bottom I/O |  | Connects to room control systems.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Diagrams of ports and clearances
|
||||
|
||||
***Top view of 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Front view of 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Bottom view of 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Replacement PC ports on 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Keypad on right side of 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Rear view of 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Clearances for 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Front and bottom handholds and clearances for 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Rear handholds and clearances for 55" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
157
devices/surface-hub/surface-hub-technical-84.md
Normal file
157
devices/surface-hub/surface-hub-technical-84.md
Normal file
@ -0,0 +1,157 @@
|
||||
---
|
||||
title: Technical information for 84" Surface Hub
|
||||
description: Specifications for the 84" Surface Hub
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Technical information for 84" Surface Hub
|
||||
|
||||
## Measurements
|
||||
|
||||
|
|
||||
--- | ---
|
||||
Pricing | Starting at $21,999
|
||||
Size | 46.12” x 86.7” x 4.15” (1171.5mm x 2202.9mm x 105.4mm)
|
||||
Storage/RAM | SSD 128GB with 8GB RAM
|
||||
Processor | 4th Generation Intel® Core™ i7
|
||||
Graphics | NVIDIA Quadro K2200
|
||||
Ports | **Internal PC**<br>• (1) USB 3.0 (bottom) + (1) USB 3.0 (side access)<br>• (4) USB 2.0<br>• Ethernet 1000 Base-T<br>• DisplayPort Video Output<br>• 3.5mm Stereo Out<br>• RJ11 Connector for system-level control<br>**Alternate PC**<br>• (2) USB 2.0 type B output<br>• connection for Camera, Sensors, Microphone, Speakers<br>• (2) DisplayPort Video Input<br>**Guest PC**<br>• DisplayPort Video Input<br>• HDMI Video Input<br>• VGA Video Input<br>• 3.5mm Stereo Input<br>• (1) USB 2.0 type B Touchback™ Output
|
||||
Sensors | (2) Passive Infrared Presence Sensors, Ambient Light Sensors
|
||||
Speakers | (2) Front-facing stereo speakers
|
||||
Microphone | High-Performance, 4-Element Array
|
||||
Camera | (2) Wide angle HD cameras 1080p @ 30fps
|
||||
Pen | (2) Powered, active, subpixel accuracy
|
||||
Physical side buttons | Power, Input Select, Volume, Brightness
|
||||
Software | Windows 10 + Office (Word, PowerPoint, Excel)
|
||||
What’s in the box | • Surface Hub 84”<br>• (2) Surface Hub Pens<br>• Power Cable<br>• Setup Guide<br>• Safety and Warranty documents<br>• Wireless All-in-One Keyboard
|
||||
Mounting features | 4X VESA standard, 1200mm x 600mm pattern, 8X M8 X 1.25 threaded mounting locations
|
||||
Display height from floor | Recommended height of 54 inches (139.7 cm) to center of screen
|
||||
Product weight | Approx. 280 lb. (127 kg.)
|
||||
Product shipping weight | Approx. 580 lb. (263 kg.)
|
||||
Product dimensions HxWxD | 46 x 86.9 x 4.1 inches (116.8 x 220.6 x 10.4 cm)
|
||||
Product shipping dimensions HxWxD | 66.14 x 88.19 x 24.4 inches (168 x 224 x 62 cm)
|
||||
Product thickness | Touch surface to mounting surface: ≤ 3.1 inches (7.8 cm)
|
||||
Orientation | Landscape only. Display cannot be used in a portrait orientation.
|
||||
BTU | 3070.8 BTU/h
|
||||
Image resolution | 3840 x 2160
|
||||
Frame rate | 120Hz
|
||||
Contrast Ratio | 1400:1
|
||||
EDID preferred timing, replacement PC | 3840 x 2140, 120Hz vertical refresh
|
||||
EDID preferred timing, wired connect | 1920 x 1080, 60Hz vertical refresh
|
||||
Input voltage | 110/230v nominal, 90-265v max
|
||||
Input power, operating | 900W max
|
||||
Input power, standby | 5W nominal, 1-10W max
|
||||
|
||||
|
||||
## Replacement PC connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
Switch, bottom I/O |  | Switches the function between using internal PC or external PC.
|
||||
Display port, bottom I/O |  | Provides input for replacement PC.
|
||||
Display port, bottom I/O |  | Provides second input for replacement PC.
|
||||
USB type B, bottom I/O |  | Provides USB connection for replacement PC to internal peripherals.
|
||||
USB type B, bottom I/O |  | Provides USB connection for integrated hub.
|
||||
|
||||
|
||||
## Wired connect connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
Display port, bottom I/O |  | Provides input for wired connect PC.
|
||||
HDMI, bottom I/O |  | Provides HDMI input for wired connect PC.
|
||||
VGA, bottom I/O |  | Provides VGA input for wired connect PC.
|
||||
3.5mm, bottom I/O |  | Provides analog audio input.
|
||||
USB type B, bottom I/O |  | Provides USB connection for video ingest touchback.
|
||||
|
||||
## Additional connections
|
||||
|
||||
Connector and location | Label | Description
|
||||
--- | --- | ---
|
||||
USB type A, side I/O |  | Provides 1 USB 3.0 connection for USB devices. Wake-on USB capable.
|
||||
USB type A, bottom I/O with blue insulator |  | Provides USB 3.0 connection.
|
||||
3.5mm, bottom I/O |  | Provides analog audio out.
|
||||
Display port, bottom I/O |  | Provides mirrored video out function to another display.
|
||||
IEC/EN60320-C13 receptable with hard switch |  | Provides AC input and compliance with EU power requirements.
|
||||
RJ45, bottom I/O |  | Connects to Ethernet.
|
||||
RJ11, bottom I/O |  | Connects to room control systems.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Diagrams of ports and clearances
|
||||
|
||||
***Top view of 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Front view of 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Bottom view of 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Replacement PC ports on 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Rear view of 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
***Clearances for 84" Surface Hub***
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Removable lifting handles on 84” Surface Hub ***
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
***Wall mount threads on back of 84” Surface Hub ***
|
||||
|
||||
|
||||
|
||||
---
|
||||
***Lifting handles in top view of 84” Surface Hub***
|
||||
|
||||
|
||||
|
||||
---
|
||||
***Side view of 84” Surface Hub***
|
||||
|
||||
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ sections:
|
||||
- type: markdown
|
||||
text: "
|
||||
Prepare to deploy Surface Hub in your organization. Explore site readiness, assembly, configuration, and Exchange and ActiveSync policies. <br>
|
||||
<table><tr><td><img src='images/plan1.png' width='192' height='192'><br>**Get ready for Surface Hub**<br>Explore the steps you'll need to take to set up Surface Hub.<br><a href='https://download.microsoft.com/download/3/8/8/3883E991-DFDB-4E70-8D28-20B26045FC5B/Surface-Hub-Site-Readiness-Guide_EN.pdf'>Surface Hub Site Readiness Guide</a> (PDF, 1.48 MB)<br><a href='https://docs.microsoft.com/surface-hub/surface-hub-downloads'>Unpacking guides</a></td><td><img src='images/plan2.png' width='192' height='192'><br>**Assembly for Surface Hub**<br>Learn how to assemble your Surface Hub.<br><a href='https://download.microsoft.com/download/0/1/6/016363A4-8602-4F01-8281-9BE5C814DC78/Setup-Guide_EN-FR-SP.pdf'>Surface Hub Setup Guide</a> (PDF, 1.43 MB)<br><a href='https://docs.microsoft.com/surface-hub/surface-hub-downloads'>Mounting and assembling guides</a></td><td><img src='images/plan3.png' width='192' height='192'><br>**Prepare your environment**<br>Learn about setup dependencies and account requirements.<br><a href='https://docs.microsoft.com/surface-hub/prepare-your-environment-for-surface-hub'>Prepare your environment</a><br><a href='https://docs.microsoft.com/surface-hub/create-and-test-a-device-account-surface-hub'>Create and test a device account</a></td></tr>
|
||||
<table><tr><td><img src='images/plan1.png' width='192' height='192'><br>**Get ready for Surface Hub**<br>Explore the steps you'll need to take to set up Surface Hub.<br><a href='https://docs.microsoft.com/surface-hub/surface-hub-site-readiness.guide'>Surface Hub Site Readiness Guide</a> (PDF, 1.48 MB)<br><a href='https://docs.microsoft.com/surface-hub/surface-hub-downloads'>Unpacking guides</a></td><td><img src='images/plan2.png' width='192' height='192'><br>**Assembly for Surface Hub**<br>Learn how to assemble your Surface Hub.<br><a href='https://download.microsoft.com/download/0/1/6/016363A4-8602-4F01-8281-9BE5C814DC78/Setup-Guide_EN-FR-SP.pdf'>Surface Hub Setup Guide</a> (PDF, 1.43 MB)<br><a href='https://docs.microsoft.com/surface-hub/surface-hub-downloads'>Mounting and assembling guides</a></td><td><img src='images/plan3.png' width='192' height='192'><br>**Prepare your environment**<br>Learn about setup dependencies and account requirements.<br><a href='https://docs.microsoft.com/surface-hub/prepare-your-environment-for-surface-hub'>Prepare your environment</a><br><a href='https://docs.microsoft.com/surface-hub/create-and-test-a-device-account-surface-hub'>Create and test a device account</a></td></tr>
|
||||
</table>
|
||||
"
|
||||
- title: Deploy
|
||||
|
||||
@ -26,7 +26,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.surface"
|
||||
"depot_name": "Win.surface",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -26,7 +26,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.education"
|
||||
"depot_name": "Win.education",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -27,7 +27,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.mdop"
|
||||
"depot_name": "Win.mdop",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -14,7 +14,7 @@ ms.date: 04/23/2017
|
||||
# How to Enable BitLocker by Using MBAM as Part of a Windows Deployment
|
||||
|
||||
|
||||
This topic explains how to enable BitLocker on an end user's computer by using MBAM as part of your Windows imaging and deployment process. If you see a black screen at restart (after Install phase concludes) indicating that the drive cannot be unlocked, see [Windows versions prior Windows 10 build 1511 fail to start after "Setup Windows and Configuration Manager" step when Pre-Provision BitLocker is used with Windows PE 10.0.586.0 (1511)](https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2016/03/30/windows-versions-prior-windows-10-build-1511-fail-to-start-after-setup-windows-and-configuration-manager-step-when-pre-provision-bitlocker-is-used-with-windows-pe-10-0-586-0-1511/).
|
||||
This topic explains how to enable BitLocker on an end user's computer by using MBAM as part of your Windows imaging and deployment process. If you see a black screen at restart (after Install phase concludes) indicating that the drive cannot be unlocked, see [Earlier Windows versions don't start after "Setup Windows and Configuration Manager" step if Pre-Provision BitLocker is used with Windows 10, version 1511](https://support.microsoft.com/en-us/help/4494799/earlier-windows-versions-don-t-start-after-you-use-pre-provision-bitlo).
|
||||
|
||||
**Prerequisites:**
|
||||
|
||||
|
||||
@ -36,7 +36,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "TechNet.smb"
|
||||
"depot_name": "TechNet.smb",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -63,9 +63,12 @@ There are several items to download or create for offline-licensed apps. The app
|
||||
**To download an offline-licensed app**
|
||||
|
||||
1. Sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com/) or [Microsoft Store for Education](https://educationstore.microsoft.com).
|
||||
2. Click **Manage**, and then choose **Apps & software**.
|
||||
3. Refine results by **License type** to show apps with offline licenses.
|
||||
4. Find the app you want to download, click the ellipses under **Actions**, and then choose **Download for offline use**.
|
||||
2. Click **Manage**.
|
||||
3. Under **Shopping Experience**, set **Show offline apps** to **On**.
|
||||
4. Click **Shop for my group**. Search for the required inbox-app, select it, change the License type to **Offline**, and click **Get the app**, which will add the app to your inventory.
|
||||
5. Click **Manage**. You now have access to download the appx bundle package metadata and license file.
|
||||
6. Go to **Products & services**, and select **Apps & software**. (The list may be empty, but it will auto-populate after some time.)
|
||||
|
||||
- **To download app metadata**: Choose the language for the app metadata, and then click **Download**. Save the downloaded app metadata. This is optional.
|
||||
- **To download app package**: Click to expand the package details information, choose the Platform and Architecture combination that you need for your organization, and then click **Download**. Save the downloaded app package. This is required.
|
||||
- **To download an app license**: Choose either **Encoded**, or **Unencoded**, and then click **Generate license**. Save the downloaded license. This is required.
|
||||
|
||||
@ -43,7 +43,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.store-for-business"
|
||||
"depot_name": "MSDN.store-for-business",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -360,7 +360,7 @@ Customers in these markets can use Microsoft Store for Business and Education to
|
||||
- Ukraine
|
||||
|
||||
### Support to only manage products
|
||||
Customers in these markets can use Microsoft Store for Business and Education only to manage products that they've purchased from other channels. For example, they might have purchased products through Volume Licensing Service Center. However, they can't purhcase apps directly from Microsoft Store for Business and Education.
|
||||
Customers in these markets can use Microsoft Store for Business and Education only to manage products that they've purchased from other channels. For example, they might have purchased products through Volume Licensing Service Center. However, they can't purchase apps directly from Microsoft Store for Business and Education.
|
||||
- Puerto Rico
|
||||
|
||||
This table summarize what customers can purchase, depending on which Microsoft Store they are using.
|
||||
|
||||
@ -81,6 +81,6 @@ This table lists the roles and their permissions.
|
||||
>You need to be a Global Administrator, or have the Billing account owner role to access **Permissions**.
|
||||
|
||||
2. Select **Manage**, and then select **Permissions**.
|
||||
3. On **Roles**, or **Purchasing roles**, select **Assing roles**.
|
||||
3. On **Roles**, or **Purchasing roles**, select **Assign roles**.
|
||||
4. Enter a name, choose the role you want to assign, and select **Save**.
|
||||
If you don't find the name you want, you might need to add people to your Azure AD directory. For more information, see [Manage user accounts](manage-users-and-groups-microsoft-store-for-business.md).
|
||||
@ -24,8 +24,8 @@ The Microsoft Store for Business and Education has a group of settings that admi
|
||||
| Private store | Update the name for your private store. The new name will be displayed on a tab in the Store. For more information, see [Manage private store settings](manage-private-store-settings.md). | **Settings - Distribute** |
|
||||
| Offline licensing | Configure whether or not to make offline-licensed apps available in the Microsoft Store for Business and Education. For more information, see [Distribute offline apps](distribute-offline-apps.md). | **Settings - Shop** |
|
||||
| Allow users to shop | Configure whether or not people in your organization or school can see and use the shop function in Store for Business or Store for Education. For more information, see [Allow users to shop](acquire-apps-microsoft-store-for-business.md#allow-users-to-shop). | **Settings - Shop** |
|
||||
| Make everyone a Basic Purchaser | Allow everyone in your organization to automatically become a Basic Purchaser. This allows them to purchase apps and manage them. For more information, see [Make everyone a Basic Purchaser](https://docs.microsoft.com/education/windows/education-scenarios-store-for-business#basic-purchaser-role). </br> **Make everyone a Basic Purchaser** is only available in Microsoft Store for Education. | **Settings - Shop** |
|
||||
| App request | Configure whether or not people in your organization can request apps for admins to purchase. For more information, see [Distribute offline apps](acquire-apps-microsoft-store-for-business.md). | **Settings - Distribute** |
|
||||
| Make everyone a Basic Purchaser | Allow everyone in your organization to automatically become a Basic Purchaser. This allows them to purchase apps and manage them. For more information, see [Make everyone a Basic Purchaser](https://docs.microsoft.com/education/windows/education-scenarios-store-for-business#basic-purchaser-role). | **Settings - Shop** |
|
||||
| App request | Configure whether or not people in your organization can request apps for admins to purchase. For more information, see [Distribute offline apps](acquire-apps-microsoft-store-for-business.md). | **Settings - Shop** |
|
||||
| Management tools | Management tools that are synced with Azure AD are listed on this page. You can choose one to use for managing app updates and distribution. For more information, see [Configure MDM provider](configure-mdm-provider-microsoft-store-for-business.md). | **Settings - Distribute** |
|
||||
| Device Guard signing | Use the Device Guard signing portal to add unsigned apps to a code integrity policy, or to sign code integrity policies. For more information, see [Device Guard signing portal](device-guard-signing-portal.md). | **Settings - Devices** |
|
||||
| Permissions | Manage permissions for your employees. For more information, see [Roles and permissions in the Microsoft Store for Business and Education](roles-and-permissions-microsoft-store-for-business.md). | **Permissions - Roles**, **Permissions - Purchasing roles**, and **Permissions - Blocked basic purchasers** |
|
||||
|
||||
@ -38,7 +38,8 @@
|
||||
"ms.author": "justinha",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-access-protection"
|
||||
"depot_name": "MSDN.win-access-protection",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -61,7 +61,7 @@ Here are the provisioned Windows apps in Windows 10 versions 1703, 1709, 1803 an
|
||||
| Microsoft.OneConnect | [Paid Wi-Fi & Cellular](ms-windows-store://pdp/?PFN=Microsoft.OneConnect_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.People | [Microsoft People](ms-windows-store://pdp/?PFN=Microsoft.People_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.Print3D | [Print 3D](ms-windows-store://pdp/?PFN=Microsoft.Print3D_8wekyb3d8bbwe) | | x | x | x | No |
|
||||
| Microsoft.SkreenSketch | [Snip & Sketch](ms-windows-store://pdp/?PFN=Microsoft.ScreenSketch_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.ScreenSketch | [Snip & Sketch](ms-windows-store://pdp/?PFN=Microsoft.ScreenSketch_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.SkypeApp | [Skype](ms-windows-store://pdp/?PFN=Microsoft.SkypeApp_kzf8qxf38zg5c) | x | x | x | x | No |
|
||||
| Microsoft.StorePurchaseApp | [Store Purchase App](ms-windows-store://pdp/?PFN=Microsoft.StorePurchaseApp_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.VP9VideoExtensions | | | | | x | No |
|
||||
|
||||
@ -41,7 +41,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-app-management"
|
||||
"depot_name": "MSDN.win-app-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -17,17 +17,20 @@ When you update a computer running Windows 10, version 1703 or 1709, you might s
|
||||
>[!NOTE]
|
||||
>* This issue only occurs after a feature update (from one version to the next), not monthly updates or security-related updates.
|
||||
>* This only applies to first-party apps that shipped with Windows 10. This doesn't apply to third-party apps, Microsoft Store apps, or LOB apps.
|
||||
>* This issue can occur whether you removed the app using `Remove-appxprovisionedpackage` or `Get-AppxPackage -allusers | Remove-AppxPackage -Allusers`.
|
||||
|
||||
To remove a provisioned app, you need to remove the provisioning package. The apps might reappear if you removed the packages in one of the following ways:
|
||||
To remove a provisioned app, you need to remove the provisioning package. The apps might reappear if you [removed the packages](https://docs.microsoft.com/powershell/module/dism/remove-appxprovisionedpackage) in one of the following ways:
|
||||
|
||||
* If you removed the packages while the wim file was mounted when the device was offline.
|
||||
* If you removed the packages by running a PowerShell cmdlet on the device while Windows was online. Although the apps won't appear for new users, you'll still see the apps for the user account you signed in as.
|
||||
|
||||
When you remove a provisioned app, we create a registry key that tells Windows not to reinstall or update that app the next time Windows is updated. If the computer isn't online when you deprovision the app, then we don't create that registry key. (This behavior is fixed in Windows 10, version 1803. If you're running Windows 10, version 1709, apply the latest security update to fix it.)
|
||||
When you [remove a provisioned app](https://docs.microsoft.com/powershell/module/dism/remove-appxprovisionedpackage), we create a registry key that tells Windows not to reinstall or update that app the next time Windows is updated. If the computer isn't online when you deprovision the app, then we don't create that registry key. (This behavior is fixed in Windows 10, version 1803. If you're running Windows 10, version 1709, apply the latest security update to fix it.)
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If you remove a provisioned app while Windows is online, it's only removed for *new users*—the user that you signed in as will still have that provisioned app. That's because the registry key created when you deprovision the app only applies to new users created *after* the key is created. This doesn't happen if you remove the provisioned app while Windows is offline.
|
||||
|
||||
|
||||
To prevent these apps from reappearing at the next update, manually create a registry key for each app, then update the computer.
|
||||
|
||||
## Create registry keys for deprovisioned apps
|
||||
@ -38,7 +41,7 @@ Use the following steps to create a registry key:
|
||||
2. Create a .reg file to generate a registry key for each app. Use [this list of Windows 10, version 1709 registry keys](#registry-keys-for-provisioned-apps) as your starting point.
|
||||
1. Paste the list of registry keys into Notepad (or a text editor).
|
||||
2. Remove the registry keys belonging to the apps you want to keep. For example, if you want to keep the Bing Weather app, delete this registry key:
|
||||
```
|
||||
```yaml
|
||||
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\A ppxAllUserStore\Deprovisioned\Microsoft.BingWeather_8wekyb3d8bbwe]
|
||||
```
|
||||
3. Save the file with a .txt extension, then right-click the file and change the extension to .reg.
|
||||
@ -158,3 +161,9 @@ Windows Registry Editor Version 5.00
|
||||
|
||||
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned\Microsoft.ZuneVideo_8wekyb3d8bbwe]
|
||||
```
|
||||
|
||||
|
||||
|
||||
[Get-AppxPackage](https://docs.microsoft.com/powershell/module/appx/get-appxpackage)
|
||||
[Get-AppxPackage -allusers](https://docs.microsoft.com/powershell/module/appx/get-appxpackage)
|
||||
[Remove-AppxPackage](https://docs.microsoft.com/powershell/module/appx/remove-appxpackage)
|
||||
|
||||
@ -41,7 +41,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
|
||||
>[!NOTE]
|
||||
>You can specify individual Azure AD accounts for remote connections by having the user sign in to the remote device at least once and then running the following PowerShell cmdlet:
|
||||
>
|
||||
>`net localgroup "Remote Desktop Users" /add "AzureAD\FirstnameLastname"`, where *FirstnameLastname* is the name of the user profile in C:\Users\, which is created based on DisplayName attribute in Azure AD.
|
||||
>`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.
|
||||
>
|
||||
>In Windows 10, version 1709, the user does not have to sign in to the remote device first.
|
||||
>
|
||||
@ -50,7 +50,7 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
|
||||
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: `AzureADName\YourAccountName`.
|
||||
>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.
|
||||
|
||||
|
||||
## Supported configurations
|
||||
|
||||
@ -40,7 +40,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-client-management"
|
||||
"depot_name": "MSDN.win-client-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -895,6 +895,7 @@ Status Get
|
||||
<xs:enumeration value="RestartShell" />
|
||||
<xs:enumeration value="RestartDevice" />
|
||||
<xs:enumeration value="ShutdownDevice" />
|
||||
<xs:enumeration value="DoNothing" />
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
|
||||
@ -338,7 +338,7 @@ Delete a provider
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-provderguid-tracelevel"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProvderGUID*/TraceLevel**
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-providerguid-tracelevel"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProviderGUID*/TraceLevel**
|
||||
Specifies the level of detail included in the trace log.
|
||||
|
||||
The data type is an integer.
|
||||
@ -407,7 +407,7 @@ Set provider **TraceLevel**
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-provderguid-keywords"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProvderGUID*/Keywords**
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-providerguid-keywords"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProviderGUID*/Keywords**
|
||||
Specifies the provider keywords to be used as MatchAnyKeyword for this provider.
|
||||
|
||||
the data type is a string.
|
||||
@ -461,7 +461,7 @@ Set provider **Keywords**
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-provderguid-state"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProvderGUID*/State**
|
||||
<a href="" id="etwlog-collectors-collectorname-providers-providerguid-state"></a>**EtwLog/Collectors/*CollectorName*/Providers/*ProviderGUID*/State**
|
||||
Specifies if this provider is enabled in the trace session.
|
||||
|
||||
The data type is a boolean.
|
||||
|
||||
@ -50,6 +50,12 @@ ms.date: 03/15/2018
|
||||
<td></td>
|
||||
</tr>
|
||||
</table>
|
||||
Footnote:
|
||||
|
||||
- 1 - Added in Windows 10, version 1607.
|
||||
- 2 - Added in Windows 10, version 1703.
|
||||
- 3 - Added in Windows 10, version 1709.
|
||||
- 4 - Added in Windows 10, version 1803.
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
<!--Scope-->
|
||||
@ -132,15 +138,7 @@ Here is an example:
|
||||
<hr/>
|
||||
|
||||
Take note:
|
||||
* You must include the local administrator in the administrators group or the policy will fail
|
||||
* You should include the local administrator while modifying the administrators group to prevent accidental loss of access
|
||||
* Include the entire UPN after AzureAD
|
||||
|
||||
Footnote:
|
||||
|
||||
- 1 - Added in Windows 10, version 1607.
|
||||
- 2 - Added in Windows 10, version 1703.
|
||||
- 3 - Added in Windows 10, version 1709.
|
||||
- 4 - Added in Windows 10, version 1803.
|
||||
|
||||
<!--/Policies-->
|
||||
|
||||
|
||||
@ -666,6 +666,13 @@ The following list shows the supported values:
|
||||
Enabling this policy prevents context menus from being invoked in the Start Menu.
|
||||
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 (default) – False (Do not disable).
|
||||
- 1 - True (disable).
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP English name: *Disable context menus in the Start Menu*
|
||||
@ -1091,6 +1098,13 @@ Added in Windows 10, version 1709. Enabling this policy removes the people icon
|
||||
Value type is integer.
|
||||
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 (default) – False (do not hide).
|
||||
- 1 - True (hide).
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP English name: *Remove the People Bar from the taskbar*
|
||||
|
||||
@ -33,6 +33,9 @@ ms.date: 01/14/2019
|
||||
<dd>
|
||||
<a href="#storage-configstoragesensecloudcontentdehydrationthreshold">Storage/ConfigStorageSenseCloudContentDehydrationThreshold</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#storage-configstoragesensedownloadscleanupthreshold">Storage/ConfigStorageSenseDownloadsCleanupThreshold</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#storage-configstoragesenseglobalcadence">Storage/ConfigStorageSenseGlobalCadence</a>
|
||||
</dd>
|
||||
@ -160,7 +163,7 @@ If you do not configure this policy setting, Storage Sense is turned off by defa
|
||||
ADMX Info:
|
||||
- GP English name: *Allow Storage Sense*
|
||||
- GP name: *SS_AllowStorageSenseGlobal*
|
||||
- GP path: *SOFTWARE/Policies/Microsoft/Windows/StorageSense*
|
||||
- GP path: *System/Storage Sense*
|
||||
- GP ADMX file name: *StorageSense.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
@ -285,7 +288,7 @@ When Storage Sense runs, it can dehydrate cloud-backed content that hasn’t bee
|
||||
|
||||
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||
|
||||
If you enable this policy setting, you must provide the number of days since a cloud-backed file has been opened before Storage Sense will dehydrate it. Supported values are: 0–365.
|
||||
If you enable this policy setting, you must provide the minimum number of days a cloud-backed file can remain unopened before Storage Sense dehydrates it. Supported values are: 0–365.
|
||||
|
||||
If you set this value to zero, Storage Sense will not dehydrate any cloud-backed content. The default value is 0, which never dehydrates cloud-backed content.
|
||||
|
||||
@ -350,11 +353,11 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
When Storage Sense runs, it can delete files in the user’s Downloads folder if they have been there for over a certain amount of days.
|
||||
When Storage Sense runs, it can delete files in the user’s Downloads folder if they haven’t been opened for more than a certain number of days.
|
||||
|
||||
If the Storage/AllowStorageSenseGlobal policy is disabled, then this policy does not have any effect.
|
||||
|
||||
If you enable this policy setting, you must provide the minimum age threshold (in days) of a file in the Downloads folder before Storage Sense will delete it. Supported values are: 0–365.
|
||||
If you enable this policy setting, you must provide the minimum number of days a file can remain unopened before Storage Sense deletes it from the Downloads folder. Supported values are: 0-365.
|
||||
|
||||
If you set this value to zero, Storage Sense will not delete files in the user’s Downloads folder. The default is 0, or never deleting files in the Downloads folder.
|
||||
|
||||
@ -438,8 +441,8 @@ If you do not configure this policy setting, then the Storage Sense cadence is s
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP English name: *Configure Storage Sense cadence*
|
||||
- GP name: *RemovableDisks_DenyWrite_Access_2*
|
||||
- GP path: *SOFTWARE/Policies/Microsoft/Windows/StorageSense*
|
||||
- GP name: *SS_ConfigStorageSenseGlobalCadence*
|
||||
- GP path: *System/Storage Sense*
|
||||
- GP ADMX file name: *StorageSense.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
|
||||
@ -681,11 +681,13 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Specifies whether to allow the user to factory reset the phone by using control panel and hardware key combination.
|
||||
Specifies whether to allow the user to factory reset the device by using control panel and hardware key combination.
|
||||
|
||||
Most restricted value is 0.
|
||||
|
||||
<!--/Description-->
|
||||
> [!TIP]
|
||||
> This policy is also applicable to Windows 10 and not exclusive to phone.
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
orted values:
|
||||
|
||||
@ -66,6 +66,15 @@ Here are examples of data fields. The encoded 0xF000 is the standard delimiter/s
|
||||
```
|
||||
<Data></Data>
|
||||
```
|
||||
If you use Intune custom profiles to assign UserRights policies, you must use the CDATA tag (`<![CDATA[...]]>`) to wrap the data fields. You can specify one or more user groups within the CDATA tag by using 0xF000 as the delimiter/separator.
|
||||
|
||||
> [!Note]
|
||||
> `` is the entity encoding of 0xF000.
|
||||
|
||||
For example, the following syntax grants user rights to Authenticated Users and Replicator user groups:
|
||||
```
|
||||
<![CDATA[Authenticated UsersReplicator]]>
|
||||
```
|
||||
|
||||
<hr/>
|
||||
|
||||
|
||||
@ -151,7 +151,7 @@ If set to True, this DomainName rule will trigger the VPN
|
||||
|
||||
By default, this value is false.
|
||||
|
||||
Value type is bool. Persistent
|
||||
Value type is bool.
|
||||
|
||||
<a href="" id="vpnv2-profilename-domainnameinformationlist-dnirowid-persistent"></a>**VPNv2/***ProfileName***/DomainNameInformationList/***dniRowId***/Persistent**
|
||||
Added in Windows 10, version 1607. A boolean value that specifies if the rule being added should persist even when the VPN is not connected. Value values:
|
||||
@ -624,10 +624,10 @@ Profile example
|
||||
</Authentication>
|
||||
<RoutingPolicyType>SplitTunnel</RoutingPolicyType>
|
||||
</NativeProfile>
|
||||
<DomainNameInformation>
|
||||
<DomainNameInformationList>
|
||||
<DomainName>.contoso.com</DomainName>
|
||||
<DNSServers>10.5.5.5</DNSServers>
|
||||
</DomainNameInformation>
|
||||
</DomainNameInformationList>
|
||||
<TrafficFilter>
|
||||
<App>%ProgramFiles%\Internet Explorer\iexplore.exe</App>
|
||||
</TrafficFilter>
|
||||
|
||||
@ -47,6 +47,9 @@ When the ADMX policies are imported, the registry keys to which each policy is w
|
||||
- software\policies\microsoft\vba\security\
|
||||
- software\microsoft\onedrive
|
||||
|
||||
> [!Warning]
|
||||
> Some operating system components have built in functionality to check devices for domain membership. MDM enforces the configured policy values only if the devices are domain joined, otherwise it does not. However, you can still import ADMX files and set ADMX-backed policies regardless of whether the device is domain joined or non-domain joined.
|
||||
|
||||
## <a href="" id="ingesting-an-app-admx-file"></a>Ingesting an app ADMX file
|
||||
|
||||
The following ADMX file example shows how to ingest a Win32 or Desktop Bridge app ADMX file and set policies from the file. The ADMX file defines eight policies.
|
||||
|
||||
@ -13,7 +13,7 @@ ms.date: 06/26/2017
|
||||
# WindowsSecurityAuditing CSP
|
||||
|
||||
|
||||
The WindowsSecurityAuditing configuration service provider (CSP) is used to enable logging of security audit events. This CSP was added in Windows 10, version 1511.
|
||||
The WindowsSecurityAuditing configuration service provider (CSP) is used to enable logging of security audit events. This CSP was added in Windows 10, version 1511 for Mobile and Mobile Enterprise. Make sure to consult the [Configuration service provider reference](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference) to see if this CSP and others are supported on your Windows installation.
|
||||
|
||||
The following diagram shows the WindowsSecurityAuditing configuration service provider in tree format.
|
||||
|
||||
|
||||
@ -10,13 +10,19 @@ ms.localizationpriority: medium
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.date: 11/07/2018
|
||||
---
|
||||
|
||||
# Change history for Configure Windows 10
|
||||
|
||||
This topic lists new and updated topics in the [Configure Windows 10](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
## April 2019
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Added information for Shell Launcher v2, coming in the next feature update to Windows 10.
|
||||
[Prepare a device for kiosk configuration](kiosk-prepare.md) | Added new recommendations for policies to manage updates.
|
||||
|
||||
## February 2019
|
||||
|
||||
New or changed topic | Description
|
||||
|
||||
@ -41,7 +41,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-configuration"
|
||||
"depot_name": "MSDN.win-configuration",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -49,6 +49,8 @@ In Windows 10, version 1803 and later, you can install the **Kiosk Browser** app
|
||||
|
||||
>[!NOTE]
|
||||
>Kiosk Browser supports a single tab. If a website has links that open a new tab, those links will not work with Kiosk Browser. Kiosk Browser does not support .pdfs.
|
||||
>
|
||||
>Kiosk Browser cannot access intranet websites.
|
||||
|
||||
|
||||
**Kiosk Browser** must be downloaded for offline licensing using Microsoft Store For Business. You can deploy **Kiosk Browser** to devices running Windows 10, version 1803 (Pro, Business, Enterprise, and Education).
|
||||
|
||||
BIN
windows/configuration/images/slv2-oma-uri.png
Normal file
BIN
windows/configuration/images/slv2-oma-uri.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
@ -8,7 +8,6 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/13/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -30,7 +29,7 @@ Topic | Description
|
||||
[Policies enforced on kiosk devices](kiosk-policies.md) | Learn about the policies enforced on a device when you configure it as a kiosk.
|
||||
[Assigned access XML reference](kiosk-xml.md) | The XML and XSD for kiosk device configuration.
|
||||
[Use AppLocker to create a Windows 10 kiosk](lock-down-windows-10-applocker.md) | Learn how to use AppLocker to configure a kiosk device running Windows 10 Enterprise or Windows 10 Education, version 1703 and earlier, so that users can only run a few specific apps.
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface.
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Using Shell Launcher, you can configure a kiosk device that runs a Windows application as the user interface.
|
||||
[Use MDM Bridge WMI Provider to create a Windows 10 kiosk](kiosk-mdm-bridge.md) | Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
[Troubleshoot kiosk mode issues](kiosk-troubleshoot.md) | Tips for troubleshooting multi-app kiosk configuration.
|
||||
|
||||
|
||||
@ -12,6 +12,9 @@ ms.topic: article
|
||||
|
||||
# Configure kiosks and digital signs on Windows desktop editions
|
||||
|
||||
>[!WARNING]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
Some desktop devices in an enterprise serve a special purpose, such as a PC in the lobby that customers can use to view your product catalog or a PC displaying visual content as a digital sign. Windows 10 offers two different locked-down experiences for public or specialized use:
|
||||
|
||||
| | |
|
||||
@ -43,6 +46,7 @@ You can use this method | For this edition | For this kiosk account type
|
||||
[Assigned access cmdlets](kiosk-single-app.md#powershell) | Pro, Ent, Edu | Local standard user
|
||||
[The kiosk wizard in Windows Configuration Designer](kiosk-single-app.md#wizard) | Pro (version 1709), Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Microsoft Intune or other mobile device management (MDM)](kiosk-single-app.md#mdm) | Pro (version 1709), Ent, Edu | Local standard user, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) v2 | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
|
||||
<span id="classic" />
|
||||
## Methods for a single-app kiosk running a Windows desktop application
|
||||
@ -50,8 +54,8 @@ You can use this method | For this edition | For this kiosk account type
|
||||
You can use this method | For this edition | For this kiosk account type
|
||||
--- | --- | ---
|
||||
[The kiosk wizard in Windows Configuration Designer](kiosk-single-app.md#wizard) | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Microsoft Intune or other mobile device management (MDM)](kiosk-single-app.md#mdm) | Pro (version 1709), Ent, Edu | Local standard user, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) v1 and v2 | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
|
||||
<span id="desktop" />
|
||||
## Methods for a multi-app kiosk
|
||||
|
||||
@ -8,7 +8,6 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 01/09/2019
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -35,8 +34,10 @@ For a more secure kiosk experience, we recommend that you make the following con
|
||||
|
||||
Recommendation | How to
|
||||
--- | ---
|
||||
Hide update notifications<br>(New in Windows 10, version 1809) | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Display options for update notifications**<br>-or-<br>Use the MDM setting **Update/UpdateNotificationLevel** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updatenotificationlevel)<br>-or-<br>Add the following registry keys as DWORD (32-bit) type:</br>`HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\SetUpdateNotificationLevel` with a value of `1`, and `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\UpdateNotificationLevel` with a value of `1` to hide all notifications except restart warnings, or value of `2` to hide all notifications, including restart warnings.
|
||||
Replace "blue screen" with blank screen for OS errors | Add the following registry key as DWORD (32-bit) type with a value of `1`:</br></br>`HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\DisplayDisabled`
|
||||
Hide update notifications<br>(New in Windows 10, version 1809) | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Display options for update notifications**<br>-or-<br>Use the MDM setting **Update/UpdateNotificationLevel** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updatenotificationlevel)<br>-or-<br>Add the following registry keys as type DWORD (32-bit) in the path of **HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate**:<br>**\SetUpdateNotificationLevel** with a value of `1`, and **\UpdateNotificationLevel** with a value of `1` to hide all notifications except restart warnings, or value of `2` to hide all notifications, including restart warnings.
|
||||
Enable and schedule automatic updates | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Configure Automatic Updates**, and select `option 4 (Auto download and schedule the install)`<br>-or-<br>Use the MDM setting **Update/AllowAutoUpdate** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate), and select `option 3 (Auto install and restart at a specified time)`<br><br>**Note:** Installations can take from between 30 minutes and 2 hours, depending on the device, so you should schedule updates to occur when a block of 3-4 hours is available.<br><br>To schedule the automatic update, configure **Schedule Install Day**, **Schedule Install Time**, and **Schedule Install Week**.
|
||||
Enable automatic restart at the scheduled time | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Always automatically restart at the scheduled time**
|
||||
Replace "blue screen" with blank screen for OS errors | Add the following registry key as DWORD (32-bit) type with a value of `1`:</br></br>**HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\DisplayDisabled**
|
||||
Put device in **Tablet mode**. | If you want users to be able to use the touch (on screen) keyboard, go to **Settings** > **System** > **Tablet mode** and choose **On.** Do not turn on this setting if users will not interact with the kiosk, such as for a digital sign.
|
||||
Hide **Ease of access** feature on the sign-in screen. | See [how to disable the Ease of Access button in the registry.](https://docs.microsoft.com/windows-hardware/customize/enterprise/complementary-features-to-custom-logon#welcome-screen)
|
||||
Disable the hardware power button. | Go to **Power Options** > **Choose what the power button does**, change the setting to **Do nothing**, and then **Save changes**.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use Shell Launcher to create a Windows 10 kiosk (Windows 10)
|
||||
description: A single-use device such as a digital sign is easy to set up in Windows 10 for desktop editions (Pro, Enterprise, and Education).
|
||||
description: Shell Launcher lets you change the default shell that launches when a user signs in to a device.
|
||||
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
||||
keywords: ["assigned access", "kiosk", "lockdown", "digital sign", "digital signage"]
|
||||
ms.prod: w10
|
||||
@ -8,7 +8,6 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/01/2018
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -16,26 +15,36 @@ ms.topic: article
|
||||
|
||||
|
||||
**Applies to**
|
||||
>App type: Windows desktop application
|
||||
>
|
||||
>OS edition: Windows 10 Ent, Edu
|
||||
>
|
||||
>Account type: Local standard user or administrator, Active Directory, Azure AD
|
||||
- Windows 10 Ent, Edu
|
||||
|
||||
>[!WARNING]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface. The application that you specify replaces the default shell (explorer.exe) that usually runs when a user logs on.
|
||||
Using Shell Launcher, you can configure a device that runs an application as the user interface, replacing the default shell (explorer.exe). In **Shell Launcher v1**, available in Windows 10, version 1809 and earlier, you can only specify a Windows desktop application as the replacement shell. In **Shell Launcher v2**, available in the next feature update to Windows 10, you can also specify a UWP app as the replacement shell.
|
||||
|
||||
>[!NOTE]
|
||||
>Using the Shell Launcher controls which application the user sees as the shell after sign-in. It does not prevent the user from accessing other desktop applications and system components.
|
||||
>Shell Launcher controls which application the user sees as the shell after sign-in. It does not prevent the user from accessing other desktop applications and system components.
|
||||
>
|
||||
>Methods of controlling access to other desktop applications and system components can be used in addition to using the Shell Launcher. These methods include, but are not limited to:
|
||||
>- [Group Policy](https://www.microsoft.com/download/details.aspx?id=25250) - example: Prevent access to registry editing tools
|
||||
>- [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-overview) - Application control policies
|
||||
>- [Mobile Device Management](https://docs.microsoft.com/windows/client-management/mdm) - Enterprise management of device security policies
|
||||
>
|
||||
>You can also configure a kiosk device that runs a Windows desktop application by using the [Provision kiosk devices wizard](kiosk-single-app.md#wizard).
|
||||
|
||||
You can apply a custom shell through Shell Launcher [by using PowerShell](#configure-a-custom-shell-using-powershell). In Windows 10, version 1803 and later, you can also [use mobile device management (MDM)](#configure-a-custom-shell-in-mdm) to apply a custom shell through Shell Launcher.
|
||||
|
||||
|
||||
## Differences between Shell Launcher v1 and Shell Launcher v2
|
||||
|
||||
Shell Launcher v1 replaces `explorer.exe`, the default shell, with `eshell.exe` which can launch a Windows desktop application.
|
||||
|
||||
Shell Launcher v2 replaces `explorer.exe` with `customshellhost.exe`. This new executable file can launch a Windows desktop application or a UWP app.
|
||||
|
||||
In addition to allowing you to use a UWP app for your replacement shell, Shell Launcher v2 offers additional enhancements:
|
||||
- You can use a custom Windows desktop application that can then launch UWP apps, such as **Settings** and **Touch Keyboard**.
|
||||
- From a custom UWP shell, you can launch secondary views and run on multiple monitors.
|
||||
- The custom shell app runs in full screen, and and can run other apps in full screen on user’s demand.
|
||||
|
||||
For sample XML configurations for the different app combinations, see [Samples for Shell Launcher v2](https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/ShellLauncherV2).
|
||||
|
||||
## Requirements
|
||||
|
||||
@ -44,16 +53,15 @@ Using Shell Launcher, you can configure a kiosk device that runs a Windows deskt
|
||||
>
|
||||
>- Shell Launcher doesn't support a custom shell with an application that launches a different process and exits. For example, you cannot specify **write.exe** in Shell Launcher. Shell Launcher launches a custom shell and monitors the process to identify when the custom shell exits. **Write.exe** creates a 32-bit wordpad.exe process and exits. Because Shell Launcher is not aware of the newly created wordpad.exe process, Shell Launcher will take action based on the exit code of **Write.exe**, such as restarting the custom shell.
|
||||
|
||||
- A domain or local user account.
|
||||
- A domain, Azure Active Directory, or local user account.
|
||||
|
||||
- A Windows desktop application that is installed for that account. The app can be your own company application or a common app like Internet Explorer.
|
||||
- A Windows application that is installed for that account. The app can be your own company application or a common app like Internet Explorer.
|
||||
|
||||
[See the technical reference for the shell launcher component.](https://go.microsoft.com/fwlink/p/?LinkId=618603)
|
||||
[See the technical reference for the shell launcher component.](https://docs.microsoft.com/windows-hardware/customize/enterprise/shell-launcher)
|
||||
|
||||
## Enable Shell Launcher feature
|
||||
|
||||
## Configure Shell Launcher
|
||||
|
||||
To set a Windows desktop application as the shell, you first turn on the Shell Launcher feature, and then you can set your custom shell as the default using PowerShell.
|
||||
To set a custom shell, you first turn on the Shell Launcher feature, and then you can set your custom shell as the default using PowerShell or MDM.
|
||||
|
||||
**To turn on Shell Launcher in Windows features**
|
||||
|
||||
@ -63,7 +71,7 @@ To set a Windows desktop application as the shell, you first turn on the Shell L
|
||||
|
||||
2. Select **Shell Launcher** and **OK**.
|
||||
|
||||
Alternatively, you can turn on Shell Launcher using Windows Configuration Designer in a provisioning package, using `SMISettings > ShellLauncher`, or the Deployment Image Servicing and Management (DISM.exe) tool.
|
||||
Alternatively, you can turn on Shell Launcher using Windows Configuration Designer in a provisioning package, using `SMISettings > ShellLauncher`, or you can use the Deployment Image Servicing and Management (DISM.exe) tool.
|
||||
|
||||
**To turn on Shell Launcher using DISM**
|
||||
|
||||
@ -74,9 +82,70 @@ Alternatively, you can turn on Shell Launcher using Windows Configuration Design
|
||||
Dism /online /Enable-Feature /all /FeatureName:Client-EmbeddedShellLauncher
|
||||
```
|
||||
|
||||
**To set your custom shell**
|
||||
|
||||
Modify the following PowerShell script as appropriate. The comments in the sample script explain the purpose of each section and tell you where you will want to change the script for your purposes. Save your script with the extension .ps1, open Windows PowerShell as administrator, and run the script on the kiosk device.
|
||||
## Configure a custom shell in MDM
|
||||
|
||||
You can use XML and a [custom OMA-URI setting](#custom-oma-uri-setting) to configure Shell Launcher in MDM.
|
||||
|
||||
### XML for Shell Launcher configuration
|
||||
|
||||
The following XML sample works for **Shell Launcher v1**:
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<ShellLauncherConfiguration xmlns="http://schemas.microsoft.com/ShellLauncher/2018/Configuration">
|
||||
<Profiles>
|
||||
<Profile ID="{24A7309204F3F-44CC-8375-53F13FE213F7}">
|
||||
<Shell Shell="%ProgramFiles%\Internet Explorer\iexplore.exe -k www.bing.com" />
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<!--local account-->
|
||||
<Account Name="ShellLauncherUser"/>
|
||||
<Profile ID="{24A7309204F3F-44CC-8375-53F13FE213F7}"/>
|
||||
</Configs>
|
||||
</ShellLauncherConfiguration>
|
||||
```
|
||||
|
||||
For **Shell Launcher v2**, you will use a different schema reference and a different app type for `Shell`, as shown in the following example.
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<ShellLauncherConfiguration xmlns="http://schemas.microsoft.com/ShellLauncher/2018/Configuration"
|
||||
xmlns:v2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration">
|
||||
<Profiles>
|
||||
<DefaultProfile>
|
||||
<Shell Shell="ShellLauncherV2DemoUwp_5d7tap497jwe8!App" v2:AppType="UWP" v2:AllAppsFullScreen="true">
|
||||
<DefaultAction Action="RestartShell"/>
|
||||
</Shell>
|
||||
</DefaultProfile>
|
||||
</Profiles>
|
||||
<Configs/>
|
||||
</ShellLauncherConfiguration>
|
||||
```
|
||||
|
||||
>[!TIP]
|
||||
>In the XML for Shell Launcher v2, note the **AllAppsFullScreen** attribute. When set to **True**, Shell Launcher will run every app in full screen, or maximized for desktop apps. When this attribute is set to **False** or not set, only the custom shell app runs in full screen; other apps launched by the user will run in windowed mode.
|
||||
|
||||
[Get XML examples for different Shell Launcher v2 configurations.](https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/ShellLauncherV2)
|
||||
|
||||
### Custom OMA-URI setting
|
||||
|
||||
In your MDM service, you can create a [custom OMA-URI setting](https://docs.microsoft.com/intune/custom-settings-windows-10) to configure Shell Launcher v1 or v2. (The [XML](#xml-for-shell-launcher-configuration) that you use for your setting will determine whether you apply Shell Launcher v1 or v2.)
|
||||
|
||||
The OMA-URI path is `./Device/Vendor/MSFT/AssignedAccess/ShellLauncher`.
|
||||
|
||||
For the value, you can select data type `String` and paste the desired configuration file content into the value box. If you wish to upload the xml instead of pasting the content, choose data type `String (XML file)` instead.
|
||||
|
||||
|
||||
|
||||
After you configure the profile containing the custom Shell Launcher setting, select **All Devices** or selected groups of devices to apply the profile to. Don't assign the profile to users or user groups.
|
||||
|
||||
## Configure a custom shell using PowerShell
|
||||
|
||||
For scripts for Shell Launcher v2, see [Shell Launcher v2 Bridge WMI sample scripts](https://github.com/Microsoft/Windows-iotcore-samples/blob/develop/Samples/ShellLauncherV2/SampleBridgeWmiScripts/README.md).
|
||||
|
||||
For Shell Launcher v1, modify the following PowerShell script as appropriate. The comments in the sample script explain the purpose of each section and tell you where you will want to change the script for your purposes. Save your script with the extension .ps1, open Windows PowerShell as administrator, and run the script on the kiosk device.
|
||||
|
||||
```
|
||||
# Check if shell launcher license is enabled
|
||||
|
||||
@ -42,6 +42,8 @@ Method | Description
|
||||
|
||||
>[!TIP]
|
||||
>You can also configure a kiosk account and app for single-app kiosk within [XML in a provisioning package](lock-down-windows-10-to-specific-apps.md) by using a [kiosk profile](lock-down-windows-10-to-specific-apps.md#profile).
|
||||
>
|
||||
>Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
|
||||
|
||||
|
||||
|
||||
@ -169,8 +171,6 @@ Set-AssignedAccess -AppName <CustomApp> -UserSID <usersid>
|
||||
|
||||
[Learn how to get the AppName](https://msdn.microsoft.com/library/windows/hardware/mt620046%28v=vs.85%29.aspx) (see **Parameters**).
|
||||
|
||||
[Learn how to get the SID](https://go.microsoft.com/fwlink/p/?LinkId=615517).
|
||||
|
||||
To remove assigned access, using PowerShell, run the following cmdlet.
|
||||
|
||||
```
|
||||
|
||||
@ -40,7 +40,8 @@ New features and improvements | In update
|
||||
You can configure multi-app kiosks using [Microsoft Intune](#intune) or a [provisioning package](#provision).
|
||||
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
|
||||
|
||||
<span id="intune"/>
|
||||
## Configure a kiosk in Microsoft Intune
|
||||
@ -516,8 +517,6 @@ Provisioning packages can be applied to a device during the first-run experience
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<span id="alternate-methods" />
|
||||
### Use MDM to deploy the multi-app configuration
|
||||
|
||||
|
||||
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