From 4eaf8f808dd3f79564507c26161c883b7a14c7c1 Mon Sep 17 00:00:00 2001 From: Jeanie Decker Date: Fri, 13 Apr 2018 17:41:54 +0000 Subject: [PATCH] Merged PR 7138: Fix powershell sample and add validation to cellular config --- ...-deployment-surface-hub-device-accounts.md | 8 ++--- ...change-history-for-configure-windows-10.md | 1 + windows/configuration/provisioning-apn.md | 34 +++++++++++++++++++ 3 files changed, 38 insertions(+), 5 deletions(-) diff --git a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md b/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md index 7ef2ae24a6..aeeeb108e0 100644 --- a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md +++ b/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md @@ -9,7 +9,7 @@ ms.sitesec: library ms.pagetype: surfacehub author: jdeckerms ms.author: jdecker -ms.date: 07/27/2017 +ms.date: 04/13/2018 ms.localizationpriority: medium --- @@ -100,10 +100,8 @@ If you have a single-forest on-premises deployment with Microsoft Exchange 2013 8. OPTIONAL: You can also allow your Surface Hub to make and receive public switched telephone network (PSTN) phone calls by enabling Enterprise Voice for your account. Enterprise Voice isn't a requirement for Surface Hub, but if you want PSTN dialing functionality for the Surface Hub client, here's how to enable it: - ```PowerShell - Set-CsMeetingRoom HUB01 -DomainController DC-ND-001.contoso.com - -LineURItel: +14255550555;ext=50555" Set-CsMeetingRoom -DomainController DC-ND-001.contoso.com - -Identity HUB01 -EnterpriseVoiceEnabled $true + ```PowerShell + Set-CsMeetingRoom -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI “tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true ``` Again, you'll need to replace the provided domain controller and phone number examples with your own information. The parameter value `$true` stays the same. diff --git a/windows/configuration/change-history-for-configure-windows-10.md b/windows/configuration/change-history-for-configure-windows-10.md index b328c042ce..8ca1f3e376 100644 --- a/windows/configuration/change-history-for-configure-windows-10.md +++ b/windows/configuration/change-history-for-configure-windows-10.md @@ -20,6 +20,7 @@ This topic lists new and updated topics in the [Configure Windows 10](index.md) New or changed topic | Description --- | --- [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md) | Updated endpoints. +[Configure cellular settings for tablets and PCs](provisioning-apn.md) | Added instructions for confirming that the settings were applied. ## March 2018 diff --git a/windows/configuration/provisioning-apn.md b/windows/configuration/provisioning-apn.md index 20fc7040aa..a83a991b31 100644 --- a/windows/configuration/provisioning-apn.md +++ b/windows/configuration/provisioning-apn.md @@ -76,5 +76,39 @@ For users who work in different locations, you can configure one APN to connect 9. [Apply the package to devices.](provisioning-packages/provisioning-apply-package.md) +## Confirm the settings + +After you apply the provisioning package, you can confirm that the settings have been applied. + +1. On the configured device, open a command prompt as an administrator. + +2. Run the following command: + + ``` + netsh mbn show profiles + ``` + +3. The command will list the mobile broadband profiles. Using the "Name" for the listed mobile broadband profile, run: + + ``` + netsh mbn show profiles name="name" + ``` + + This command will list details for that profile, including Access Point Name. + + +Alternatively, you can also use the command: + +``` +netsh mbn show interface +``` + +From the results of that command, get the name of the cellular/mobile broadband interface and run: + +``` +netsh mbn show connection interface="name" +``` + +The result of that command will show details for the cellular interface, including Access Point Name.