mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 03:43:39 +00:00
Merge remote-tracking branch 'refs/remotes/origin/rs4' into jdrs4holo
This commit is contained in:
Jeanie Decker
@ -20,6 +20,11 @@ This topic lists new and updated topics in the [Microsoft HoloLens documentation
|
||||
The topics in this library have been updated for Windows 10 Holographic for Business, version 1803. The following new topics have been added:
|
||||
|
||||
- >
|
||||
## February 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) | Replaced the instructions for upgrading to Windows Holographic for Business using Microsoft Intune with a link to the new Intune topic.
|
||||
|
||||
## December 2017
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ms.date: 07/27/2017
|
||||
|
||||
# Enroll HoloLens in MDM
|
||||
|
||||
You can manage multiple Microsoft HoloLens devices simultaneously using solutions like Microsoft Intune. You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens) and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies).
|
||||
You can manage multiple Microsoft HoloLens devices simultaneously using solutions like Microsoft Intune. You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies).
|
||||
|
||||
>[!NOTE]
|
||||
>Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens-upgrade-enterprise.md).
|
||||
|
||||
@ -7,12 +7,12 @@ ms.pagetype: hololens, devices
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 02/02/2018
|
||||
---
|
||||
|
||||
# Unlock Windows Holographic for Business features
|
||||
|
||||
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the [Commercial Suite](https://developer.microsoft.com/windows/mixed-reality/release_notes#introducing_microsoft_hololens_commercial_suite), which provides extra features designed for business.
|
||||
Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the [Commercial Suite](https://developer.microsoft.com/windows/mixed-reality/release_notes_-_august_2016#introducing_microsoft_hololens_commercial_suite), which provides extra features designed for business.
|
||||
|
||||
When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic for Business. This license can be applied to the device either through the organization's [mobile device management (MDM) provider](#edition-upgrade-using-mdm) or a [provisioning package](#edition-upgrade-using-a-provisioning-package).
|
||||
|
||||
@ -25,50 +25,12 @@ When you purchase the Commercial Suite, you receive a license that upgrades Wind
|
||||
|
||||
The enterprise license can be applied by any MDM provider that supports the [WindowsLicensing configuration service provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn904983.aspx). The latest version of the Microsoft MDM API will support WindowsLicensing CSP.
|
||||
|
||||
For step-by-step instructions for upgrading HoloLens using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](https://docs.microsoft.com/intune/holographic-upgrade).
|
||||
|
||||
**Overview**
|
||||
|
||||
1. Set up the edition upgrade policy.
|
||||
2. Deploy the policy.
|
||||
3. [Enroll the device through the Settings app](hololens-enroll-mdm.md).
|
||||
|
||||
The procedures in this topic use Microsoft Intune as an example. On other MDM providers, the specific steps for setting up and deploying the policy might vary.
|
||||
|
||||
### Set up the Edition Upgrade policy
|
||||
|
||||
1. Sign into the Intune Dashboard with your Intune admin account.
|
||||
|
||||
2. In the **Policy** workspace, select **Configuration Policies** and then **Add**.
|
||||
|
||||
|
||||
|
||||
3. In **Create a new policy**, select the **Edition Upgrade Policy (Windows 10 Holographic and later** template, and click **Create Policy**.
|
||||
|
||||
|
||||
|
||||
4. Enter a name for the policy.
|
||||
|
||||
5. In the **Edition Upgrade** section, in **License File**, browse to and select the XML license file that was provided when you purchased the Commercial Suite.
|
||||
|
||||
|
||||
|
||||
5. Click **Save Policy**.
|
||||
On other MDM providers, the specific steps for setting up and deploying the policy might vary.
|
||||
|
||||
|
||||
|
||||
### Deploy the Edition Upgrade policy
|
||||
|
||||
Next, you will assign the Edition Upgrade policy to selected groups.
|
||||
|
||||
1. In the **Policy** workspace, select the Edition upgrade policy that you created, and then choose **Manage Deployment**.
|
||||
|
||||
2. In the **Manage Deployment** dialog box, select one or more groups to which you want to deploy the policy, and then choose **Add** > **OK**.
|
||||
|
||||
When these users enroll their devices in MDM, the Edition Upgrade policy will be applied.
|
||||
|
||||
|
||||
For more information about groups, see [Use groups to manage users and devices in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/use-groups-to-manage-users-and-devices-with-microsoft-intune).
|
||||
|
||||
## Edition upgrade using a provisioning package
|
||||
|
||||
Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device.
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 01/17/2018
|
||||
ms.date: 03/06/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -16,6 +16,20 @@ ms.localizationpriority: medium
|
||||
|
||||
This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
|
||||
|
||||
## March 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Create and test a device account (Surface Hub)](create-and-test-a-device-account-surface-hub.md) | Added section for account verification and testing, with link to new Surface Hub Hardware Diagnostic app.
|
||||
|
||||
## February 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md) | Updated instructions for custom settings using Microsoft Intune.
|
||||
[Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Updated instructions and scripts.
|
||||
| [Online deployment](online-deployment-surface-hub-device-accounts.md) | Updated instructions and scripts.
|
||||
|
||||
## January 2018
|
||||
|
||||
New or changed topic | Description
|
||||
|
||||
@ -31,7 +31,7 @@ When connecting external devices and displays to a Surface Hub, there are severa
|
||||
## Guest Mode
|
||||
|
||||
|
||||
Guest Mode uses a wired connection, so people can display content from their devices to the Surface Hub. If the source device is Windows-based, that device can also provide Touchback and Inkback. Surface Hub's internal PC takes video and audio from the connected device and presents them on the Surface Hub. If Surface Hub encounters a High-Bandwidth Digital Content Protection (HDCP) signal, the source will be re-routed through an alternate path, allowing the source to be displayed full-screen without violating HDCP requirements.
|
||||
Guest Mode uses a wired connection, so people can display content from their devices to the Surface Hub. If the source device is Windows-based, that device can also provide Touchback and Inkback. Surface Hub's internal PC takes video and audio from the connected device and presents them on the Surface Hub. If Surface Hub encounters a High-Bandwidth Digital Content Protection (HDCP) signal, the source will be be displayed as a black image. To display your content without violating HDCP requirements, use the keypad on the right side of the Surface Hub to directly choose the external source.
|
||||
|
||||
>[!NOTE]
|
||||
>When an HDCP source is connected, use the side keypad to change source inputs.
|
||||
|
||||
@ -91,7 +91,7 @@ From here on, you'll need to finish the account creation process using PowerShel
|
||||
In order to run cmdlets used by these PowerShell scripts, the following must be installed for the admin PowerShell console:
|
||||
|
||||
- [Microsoft Online Services Sign-In Assistant for IT Professionals BETA](https://go.microsoft.com/fwlink/?LinkId=718149)
|
||||
- [Windows Azure Active Directory Module for Windows PowerShell](https://go.microsoft.com/fwlink/p/?linkid=236297)
|
||||
- [Windows Azure Active Directory Module for Windows PowerShell](https://www.microsoft.com/web/handlers/webpi.ashx/getinstaller/WindowsAzurePowershellGet.3f.3f.3fnew.appids)
|
||||
- [Skype for Business Online, Windows PowerShell Module](http://www.microsoft.com/download/details.aspx?id=39366)
|
||||
|
||||
### Connecting to online services
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 03/06/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -57,7 +57,9 @@ For detailed steps using PowerShell to provision a device account, choose an opt
|
||||
If you prefer to use a graphical user interface (UI), some steps can be done using UI instead of PowerShell.
|
||||
For more information, see [Creating a device account using UI](create-a-device-account-using-office-365.md).
|
||||
|
||||
## Account verification and testing
|
||||
|
||||
There are two methods available that you can use to validate and test a Surface Hub device account: [account verifications scripts](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts) and the [Surface Hub Hardware Diagnostic app](https://www.microsoft.com/store/apps/9nblggh51f2g). The account verification script will validate a previously-created device account using PowerShell from your desktop. The Surface Hub Hardware Diagnostic app is installed on your Surface Hub and provides detailed feedback about signin and communication failures. Both are valuable tools to test newly created device accounts and should be used to ensure optimal account availability.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -164,8 +164,8 @@ Users can sign in to Microsoft Edge to access intranet sites and online resource
|
||||
*Organization policies that this may affect:* <br>
|
||||
-->
|
||||
|
||||
### Telemetry
|
||||
### Diagnostic data
|
||||
|
||||
The Surface Hub OS uses the Windows 10 Connected User Experience and Telemetry component to gather and transmit telemetry data. For more information, see [Configure Windows telemetry in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-telemetry-in-your-organization).
|
||||
The Surface Hub OS uses the Windows 10 Connected User Experience and Telemetry component to gather and transmit diagnostic data. For more information, see [Configure Windows diagnostic data in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-diagnostic-data-in-your-organization).
|
||||
|
||||
*Organization policies that this may affect:* <br> Configure telemetry levels for Surface Hub in the same way as you do for Windows 10 Enterprise.
|
||||
*Organization policies that this may affect:* <br> Configure diagnostic data levels for Surface Hub in the same way as you do for Windows 10 Enterprise.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 10/20/2017
|
||||
ms.date: 02/21/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -38,11 +38,11 @@ Use this procedure if you use Exchange on-premises.
|
||||
|
||||
|
||||
|
||||
3. Enable the remote mailbox.
|
||||
2. Enable the remote mailbox.
|
||||
|
||||
Open your on-premises Exchange Management Shell with administrator permissions, and run this cmdlet.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Enable-RemoteMailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
|
||||
```
|
||||
>[!NOTE]
|
||||
@ -54,7 +54,7 @@ Use this procedure if you use Exchange on-premises.
|
||||
>
|
||||
>msExchRecipientTypeDetails = 8589934592
|
||||
|
||||
2. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Office 365 admin center and verify that the account created in the previous steps has merged to online.
|
||||
3. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Office 365 admin center and verify that the account created in the previous steps has merged to online.
|
||||
|
||||
4. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
|
||||
|
||||
@ -62,8 +62,8 @@ Use this procedure if you use Exchange on-premises.
|
||||
|
||||
The next steps will be run on your Office 365 tenant.
|
||||
|
||||
```ps1
|
||||
Set-ExecutionPolicy Unrestricted
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 'https://ps.outlook.com/powershell' -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
@ -77,13 +77,13 @@ Use this procedure if you use Exchange on-premises.
|
||||
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—-this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
|
||||
Once you have a compatible policy, then you will need to apply the policy to the device account.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
```
|
||||
|
||||
@ -91,31 +91,44 @@ Use this procedure if you use Exchange on-premises.
|
||||
|
||||
Setting Exchange properties on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse 'This is a Surface Hub room!'
|
||||
```
|
||||
|
||||
7. Connect to Azure AD.
|
||||
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
|
||||
```ps1
|
||||
Connect-MsolService -Credential $cred
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
|
||||
8. Assign an Office 365 license.
|
||||
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
|
||||
You can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
Next, you can use `Get-MsolAccountSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
|
||||
Once you list out the SKUs, you can add a license using the `Set-MsolUserLicense` cmdlet. In this case, `$strLicense` is the SKU code that you see (for example, *contoso:STANDARDPACK*).
|
||||
|
||||
```ps1
|
||||
Set-MsolUser -UserPrincipalName 'HUB01@contoso.com' -UsageLocation 'US'
|
||||
Get-MsolAccountSku
|
||||
Set-MsolUserLicense -UserPrincipalName 'HUB01@contoso.com' -AddLicenses $strLicense
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
|
||||
Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-premises](#skype-for-business-on-premises), or [Skype for Business hybrid](#skype-for-business-hybrid).
|
||||
@ -144,25 +157,25 @@ The following table lists the Office 365 plans and Skype for Business options.
|
||||
|
||||
1. Start by creating a remote PowerShell session from a PC to the Skype for Business online environment.
|
||||
|
||||
```ps1
|
||||
Import-Module LyncOnlineConnector
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
|
||||
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity ‘HUB01@contoso.com’| fl *registrarpool*
|
||||
```
|
||||
|
||||
2. Assign Skype for Business license to your Surface Hub account.
|
||||
3. Assign Skype for Business license to your Surface Hub account.
|
||||
|
||||
Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) to the device.
|
||||
|
||||
@ -215,10 +228,10 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
Start a remote PowerShell session on a PC and connect to Exchange. Be sure you have the right permissions set to run the associated cmdlets.
|
||||
|
||||
```ps1
|
||||
Set-ExecutionPolicy Unrestricted
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/ps1-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
|
||||
Import-PSSession $sess
|
||||
```
|
||||
|
||||
@ -228,13 +241,13 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
If you're changing an existing resource mailbox:
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
|
||||
If you’re creating a new resource mailbox:
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
New-Mailbox -MicrosoftOnlineServicesID 'HUB01@contoso.com' -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String <password> -AsPlainText -Force)
|
||||
```
|
||||
|
||||
@ -246,13 +259,13 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
```
|
||||
|
||||
Once you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Regular
|
||||
Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
|
||||
Set-Mailbox 'HUB01@contoso.com' -Type Room
|
||||
@ -264,7 +277,7 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
|
||||
Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
|
||||
```
|
||||
@ -294,24 +307,38 @@ Use this procedure if you use Exchange online.
|
||||
|
||||
7. Connect to Azure AD.
|
||||
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
|
||||
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
|
||||
```ps1
|
||||
Connect-MsolService -Credential $cred
|
||||
```PowerShell
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
|
||||
8. Assign an Office 365 license.
|
||||
|
||||
The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
|
||||
|
||||
Next, you can use `Get-MsolAccountSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
Once you list out the SKUs, you can add a license using the `Set-MsolUserLicense` cmdlet. In this case, `$strLicense` is the SKU code that you see (for example, *contoso:STANDARDPACK*).
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
|
||||
```ps1
|
||||
Set-MsolUser -UserPrincipalName 'HUB01@contoso.com' -UsageLocation 'US'
|
||||
Get-MsolAccountSku
|
||||
Set-MsolUserLicense -UserPrincipalName 'HUB01@contoso.com' -AddLicenses $strLicense
|
||||
```PowerShell
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
|
||||
Next, you enable the device account with [Skype for Business Online](#sfb-online), [Skype for Business on-premises](#sfb-onprem), or [Skype for Business hybrid](#sfb-hybrid).
|
||||
@ -323,22 +350,22 @@ In order to enable Skype for Business, your environment will need to meet the [p
|
||||
|
||||
1. Start by creating a remote PowerShell session to the Skype for Business online environment from a PC.
|
||||
|
||||
```
|
||||
Import-Module LyncOnlineConnector
|
||||
```PowerShell
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
|
||||
2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
|
||||
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool
|
||||
'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
|
||||
|
||||
```
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity 'HUB01@contoso.com'| fl *registrarpool*
|
||||
```
|
||||
|
||||
@ -368,7 +395,7 @@ For validation, you should be able to use any Skype for Business client (PC, And
|
||||
|
||||
To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run:
|
||||
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
@ -383,7 +410,7 @@ In a hybrid Skype environment, you have to create the user on-premises first, th
|
||||
|
||||
In order to have a functional Surface Hub account in a Skype hybrid configuration, create the Skype account as a normal user type account, instead of creating the account as a meetingroom. First follow the Exchange steps - either [online](#exchange-online) or [on-premises](#exchange-on-premises) - and, instead of enabling the user for Skype for Business Online as described, [enable the account](https://technet.microsoft.com/library/gg398711.aspx) on the on-premises Skype server:
|
||||
|
||||
```
|
||||
```PowerShell
|
||||
Enable-CsUser -Identity 'HUB01@contoso.com' -RegistrarPool "registrarpoolfqdn" -SipAddressType UserPrincipalName
|
||||
```
|
||||
|
||||
|
||||
@ -164,6 +164,10 @@ There are a few different ways to install apps on your Surface Hub depending on
|
||||
| Microsoft Store app | | X | |
|
||||
| Supported MDM provider | | | X |
|
||||
|
||||
## More information
|
||||
|
||||
- [Blog post: Deploy Windows Store apps to Surface Hub using Intune](https://blogs.technet.microsoft.com/y0av/2018/01/18/7-2/)
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub, mobility
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 01/17/2018
|
||||
ms.date: 02/16/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -147,7 +147,7 @@ The following tables include info on Windows 10 settings that have been validate
|
||||
|
||||
| Setting | Details | CSP reference | Supported with<br>Intune? | Supported with<br>Configuration Manager? | Supported with<br>SyncML\*? |
|
||||
| --- | --- | --- |---- | --- | --- |
|
||||
| Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | No | No | Yes |
|
||||
| Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes | No | Yes |
|
||||
| Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
| Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent <br> See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes <br> [Use a custom policy.](#example-intune) | Yes.<br> [Use a custom setting.](#example-sccm) | Yes |
|
||||
\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
|
||||
@ -212,38 +212,9 @@ The data type is also stated in the CSP documentation. The most common data type
|
||||
<span id="example-intune">
|
||||
## Example: Manage Surface Hub settings with Microsoft Intune
|
||||
|
||||
You can use Microsoft Intune to manage Surface Hub settings.
|
||||
You can use Microsoft Intune to manage Surface Hub settings. For custom settings, follow the instructions in [How to configure custom device settings in Microsoft Intune](https://docs.microsoft.com/intune/custom-settings-configure). For **Platform**, select **Windows 10 and later**, and in **Profile type**, select **Device restrictions (Windows 10 Team)**.
|
||||
|
||||
**To create a configuration policy from a template**
|
||||
|
||||
You'll use the **Windows 10 Team general configuration policy** as the template.
|
||||
|
||||
1. On the [Intune management portal](https://manage.microsoft.com), sign in with your Intune administrator account.
|
||||
2. On the left-hand navigation menu, click **Policy**.
|
||||
3. In the Overview page, click **Add Policy**.
|
||||
4. On **Select a template for the new policy**, expand **Windows**, select **General Configuration (Windows 10 Team and later)**, and then click **Create Policy**.
|
||||
|
||||
|
||||
5. Configure your policy, then click **Save Policy**
|
||||
|
||||
|
||||
6. When prompted, click **Yes** to deploy your new policy to a user or device group. For more information, see [Use groups to manage users and devices in Microsoft Intune](https://docs.microsoft.com/intune/deploy-use/use-groups-to-manage-users-and-devices-with-microsoft-intune).
|
||||
|
||||
**To create a custom configuration policy**
|
||||
|
||||
You’ll need to create a custom policy using the **Custom Configuration (Windows 10 Desktop and Mobile and later)** template to manage settings that are not available in the **Windows 10 Team general configuration policy** template.
|
||||
|
||||
1. On the [Intune management portal](https://manage.microsoft.com), sign in with your Intune administrator account.
|
||||
2. On the left-hand navigation menu, click **Policy**.
|
||||
3. On the Overview page, click **Add Policy**.
|
||||
4. On **Select a template for the new policy**, expand **Windows**, select **Custom Configuration (Windows 10 Desktop and Mobile and later)**, and then click **Create Policy**.
|
||||
5. Type a name and optional description for the policy.
|
||||
6. Under OMA-URI Settings, click **Add**.
|
||||
7. Complete the form to create a new setting, and then click **OK**.
|
||||
|
||||
|
||||
8. Repeat Steps 6 and 7 for each setting you want to configure with this policy.
|
||||
9. After you're done, click **Save Policy** and deploy it to a user or device group.
|
||||
|
||||
<span id="example-sccm">
|
||||
## Example: Manage Surface Hub settings with System Center Configuration Manager
|
||||
|
||||
@ -86,7 +86,7 @@ This table describes the sample queries in the Surface Hub solution:
|
||||
|
||||
| Alert type | Impact | Recommended remediation | Details |
|
||||
| ---------- | ------ | ----------------------- | ------- |
|
||||
| Software | Error | **Reboot the device**. <br> Reboot manually, or using the [Reboot configuration service provider](https://msdn.microsoft.com/en-us/library/windows/hardware/mt720802(v=vs.85).aspx). <br> Suggest doing this between meetings to minimize impact to your people in your organization. | Trigger conditions: <br> - A critical process in the Surface Hub operating system, such as the shell, projection, or Skype, crashes or becomes non-responsive. <br> - The device hasn't reported a heartbeat in the past 24 hours. This may be due to network connectivity issue or network-related hardware failure, or an error with the telemetry reporting system. |
|
||||
| Software | Error | **Reboot the device**. <br> Reboot manually, or using the [Reboot configuration service provider](https://msdn.microsoft.com/en-us/library/windows/hardware/mt720802(v=vs.85).aspx). <br> Suggest doing this between meetings to minimize impact to your people in your organization. | Trigger conditions: <br> - A critical process in the Surface Hub operating system, such as the shell, projection, or Skype, crashes or becomes non-responsive. <br> - The device hasn't reported a heartbeat in the past 24 hours. This may be due to network connectivity issue or network-related hardware failure, or an error with the diagnostic data reporting system. |
|
||||
| Software | Error | **Check your Exchange service**. <br> Verify: <br> - The service is available. <br> - The device account password is up to date – see [Password management](password-management-for-surface-hub-device-accounts.md) for details.| Triggers when there's an error syncing the device calendar with Exchange. |
|
||||
| Software | Error | **Check your Skype for Business service**. <br> Verify: <br> - The service is available. <br> - The device account password is up to date – see [Password management](password-management-for-surface-hub-device-accounts.md) for details. <br> - The domain name for Skype for Business is properly configured - see [Configure a domain name](use-fully-qualified-domain-name-surface-hub.md). | Triggers when Skype fails to sign in. |
|
||||
| Software | Error | **Reset the device**. <br> This takes some time, so you should take the device offline. <br> For more information, see [Device reset](device-reset-surface-hub.md).| Triggers when there is an error cleaning up user and app data at the end of a session. When this operation repeatedly fails, the device is locked to protect user data. You must reset the device to continue. |
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 08/29/2017
|
||||
ms.date: 02/21/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -25,7 +25,7 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
Be sure you have the right permissions set to run the associated cmdlets.
|
||||
|
||||
```PowerShell
|
||||
Set-ExecutionPolicy Unrestricted
|
||||
Set-ExecutionPolicy RemoteSigned
|
||||
$org='contoso.microsoft.com'
|
||||
$cred=Get-Credential admin@$org
|
||||
$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
|
||||
@ -70,37 +70,52 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
```
|
||||
|
||||
5. Connect to Azure AD.
|
||||
|
||||
|
||||
You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
|
||||
|
||||
```PowerShell
|
||||
Install-Module -Name AzureAD
|
||||
```
|
||||
You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
|
||||
|
||||
```PowerShell
|
||||
Connect-MsolService -Credential $cred
|
||||
Import-Module AzureAD
|
||||
Connect-AzureAD -Credential $cred
|
||||
```
|
||||
|
||||
6. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
|
||||
|
||||
```PowerShell
|
||||
Set-MsolUser -UserPrincipalName 'HUB01@contoso.com' -PasswordNeverExpires $true
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -PasswordPolicies "DisablePasswordExpiration"
|
||||
```
|
||||
|
||||
7. Surface Hub requires a license for Skype for Business functionality. In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](hybrid-deployment-surface-hub-device-accounts.md#sfb-online).
|
||||
|
||||
Next, you can use `Get-MsolAccountSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
|
||||
|
||||
Once you list out the SKUs, you can add a license using the `Set-MsolUserLicense` cmdlet. In this case, `$strLicense` is the SKU code that you see (for example, *contoso:STANDARDPACK*).
|
||||
Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
|
||||
|
||||
```PowerShell
|
||||
Set-MsolUser -UserPrincipalName 'HUB01@contoso.com' -UsageLocation "US"
|
||||
Get-MsolAccountSku
|
||||
Set-MsolUserLicense -UserPrincipalName 'HUB01@contoso.com' -AddLicenses $strLicense
|
||||
Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
|
||||
|
||||
Get-AzureADSubscribedSku | Select Sku*,*Units
|
||||
$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
|
||||
$License.SkuId = SkuId You selected
|
||||
|
||||
$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
|
||||
$AssignedLicenses.AddLicenses = $License
|
||||
$AssignedLicenses.RemoveLicenses = @()
|
||||
|
||||
Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
|
||||
```
|
||||
|
||||
8. Enable the device account with Skype for Business.
|
||||
If the Skype for Business PowerShell module is not installed, [download the Skype for Business Online Windows PowerShell Module](https://www.microsoft.com/download/details.aspx?id=39366).
|
||||
|
||||
- Start by creating a remote PowerShell session from a PC.
|
||||
|
||||
```PowerShell
|
||||
Import-Module LyncOnlineConnector
|
||||
Import-Module SkypeOnlineConnector
|
||||
$cssess=New-CsOnlineSession -Credential $cred
|
||||
Import-PSSession $cssess -AllowClobber
|
||||
```
|
||||
@ -108,12 +123,13 @@ If you have a pure, online (O365) deployment, then you can [use the provided Pow
|
||||
- Next, if you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet (for example, *alice@contoso.com*):
|
||||
|
||||
```PowerShell
|
||||
Get-CsOnlineUser -Identity ‘alice@contoso.com’| fl *registrarpool*
|
||||
(Get-CsTenant).TenantPoolExtension
|
||||
```
|
||||
OR by setting a variable
|
||||
|
||||
```PowerShell
|
||||
$strRegistrarPool = (Get-CsOnlineUser -Identity ‘alice@contoso.com’).RegistrarPool
|
||||
$strRegistrarPool = (Get-CsTenant).TenantPoolExtension
|
||||
$strRegistrarPool = $strRegistrarPool[0].Substring($strRegistrarPool[0].IndexOf(':') + 1)
|
||||
```
|
||||
|
||||
- Enable the Surface Hub account with the following cmdlet:
|
||||
|
||||
@ -40,9 +40,9 @@ Depending on your environment, access to additional ports may be needed:
|
||||
- For online environments, see [Office 365 IP URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US).
|
||||
- For on-premises installations, see [Skype for Business Server: Ports and protocols for internal servers](https://technet.microsoft.com/library/gg398833.aspx).
|
||||
|
||||
Microsoft collects telemetry to help improve your Surface Hub experience. Add these sites to your allow list:
|
||||
- Telemetry client endpoint: `https://vortex.data.microsoft.com/`
|
||||
- Telemetry settings endpoint: `https://settings.data.microsoft.com/`
|
||||
Microsoft collects diagnostic data to help improve your Surface Hub experience. Add these sites to your allow list:
|
||||
- Diagnostic data client endpoint: `https://vortex.data.microsoft.com/`
|
||||
- Diagnostic data settings endpoint: `https://settings.data.microsoft.com/`
|
||||
|
||||
### Proxy configuration
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ To let people in your organization sign in to Surface Hub with their phones and
|
||||
|
||||
- Surface Hub is set up with either a local or domain-joined account.
|
||||
|
||||
Currently, you cannot use Microsoft Authenticator to sign in to Surface Hubs that are joined to an Active Directory domain or to Azure AD.
|
||||
Currently, you cannot use Microsoft Authenticator to sign in to Surface Hubs that are joined to Azure AD.
|
||||
|
||||
## Individual prerequisites
|
||||
|
||||
|
||||
@ -17,21 +17,21 @@ This topic provides links to useful Surface Hub documents, such as product datas
|
||||
|
||||
| Link | Description |
|
||||
| --- | --- |
|
||||
| [Surface Hub Site Readiness Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) | 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://www.microsoft.com/surface/support/surface-hub/surface-hub-setup-guide) | Get a quick overview of how to set up the environment for your new Surface Hub. |
|
||||
| [Surface Hub Quick Reference Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-quick-reference-guide) | Use this quick reference guide to get information about key features and functions of the Surface Hub. |
|
||||
| [Surface Hub Site Readiness Guide (PDF)](http://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)](http://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)](http://download.microsoft.com/download/9/E/E/9EE660F8-3FC6-4909-969E-89EA648F06DB/Surface Hub Quick Reference Guide_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)](http://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://www.microsoft.com/surface/en-us/support/surfacehubssd) | Learn how to replace the solid state drive (SSD) for the 55- and 84-inch Surface Hub. |
|
||||
| [Surface Hub SSD Replacement Guide (PDF)](http://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)](http://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://www.microsoft.com/surface/support/surface-hub/surface-hub-unpacking-guide-84) | 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://www.microsoft.com/surface/support/surface-hub/surface-hub-unpacking-guide-55) | 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) |
|
||||
| [Wall Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-wall-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the wall brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/bf/4d/bf4d6f06-370c-45ee-88e6-c409873914e8.mov?n=04.07.16_installation_video_05_wall_mount.mov) |
|
||||
| [Floor-Supported Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-floor-supported-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the floor-supported brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/ed/de/edde468a-e1d4-4ce8-8b61-c4527dd25c81.mov?n=04.07.16_installation_video_06_floor_support_mount.mov) |
|
||||
| [Rolling Stand Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-rolling-stand-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the rolling stand, and how to mount your Surface Hub onto it. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/1f/94/1f949613-3e4a-41e3-ad60-fe8aa7134115.mov?n=04.07.16_installation_video_04_rolling_stand_mount.mov) |
|
||||
| [Mounts and Stands Datasheet (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-mounts-and-stands-datasheet) | Specifications and prices for all Surface Hub add-on stands and mounts that turn your workspace into a Surface Hub workspace. |
|
||||
| [Surface Hub Stand and Wall Mount Specifications (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-stand-and-wall-mount-specs) | Illustrated specifications for the 55” and 84” Surface Hub rolling stands, wall mounts, and floor-supported wall mounts. |
|
||||
| [Surface Hub Onsite Installation and Onsite Repair/Exchange Services FAQ (PDF)](https://www.microsoft.com/surface/en-us/support/surface-hub/onsite-installation-repair-faq) | Get answers to the most common questions about Surface Hub onsite service offerings and delivery. |
|
||||
| [Unpacking Guide for 84-inch Surface Hub (PDF)](http://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)](http://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) |
|
||||
| [Wall Mounting and Assembly Guide (PDF)](http://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Wall_Mounts_EN-FR-ES-NL-DE-IT-PT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the wall brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/bf/4d/bf4d6f06-370c-45ee-88e6-c409873914e8.mov?n=04.07.16_installation_video_05_wall_mount.mov) |
|
||||
| [Floor-Supported Mounting and Assembly Guide (PDF)](http://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Floor_Support_Mount_EN-FR-ES-NL-DE-IT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the floor-supported brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/ed/de/edde468a-e1d4-4ce8-8b61-c4527dd25c81.mov?n=04.07.16_installation_video_06_floor_support_mount.mov) |
|
||||
| [Rolling Stand Mounting and Assembly Guide (PDF)](http://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Rolling_Stands_EN-FR-ES-NL-DE-IT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the rolling stand, and how to mount your Surface Hub onto it. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/1f/94/1f949613-3e4a-41e3-ad60-fe8aa7134115.mov?n=04.07.16_installation_video_04_rolling_stand_mount.mov) |
|
||||
| [Mounts and Stands Datasheet (PDF)](http://download.microsoft.com/download/5/0/1/501F98D9-1BCC-4448-A1DB-47056CEE33B6/20160711_Surface_Hub_Mounts_and_Stands_Datasheet.pdf) | Specifications and prices for all Surface Hub add-on stands and mounts that turn your workspace into a Surface Hub workspace. |
|
||||
| [Surface Hub Stand and Wall Mount Specifications (PDF)](http://download.microsoft.com/download/7/A/7/7A75BD0F-5A46-4BCE-B313-A80E47AEB581/20160720_Combined_Stand_Wall_Mount_Drawings.pdf) | Illustrated specifications for the 55” and 84” Surface Hub rolling stands, wall mounts, and floor-supported wall mounts. |
|
||||
| [Surface Hub Onsite Installation and Onsite Repair/Exchange Services FAQ (PDF)](http://download.microsoft.com/download/B/D/1/BD16D7C5-2662-4B7D-9C98-272CEB11A6F3/20160816%20SurfaceHub_Onsite%20Services%20FAQs%20FINAL.PDF) | Get answers to the most common questions about Surface Hub onsite service offerings and delivery. |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ The customized Start menu is defined in a Start layout XML file. You have two op
|
||||
- Configure the desired Start menu on a desktop (pinning only apps that are available on Surface Hub), and then [export the layout](https://docs.microsoft.com/windows/configuration/customize-and-export-start-layout#export-the-start-layout).
|
||||
|
||||
>[!TIP]
|
||||
>To add a tile with a web link to your desktop start menu, go the the link in Microsoft Edge, select `...` in the top right corner, and select **Pin this page to Start**. See [a Start layout that includes a Microsoft Edge link](#edge) for an example of how links will appear in the XML.
|
||||
>To add a tile with a web link to your desktop start menu, go to the link in Microsoft Edge, select `...` in the top right corner, and select **Pin this page to Start**. See [a Start layout that includes a Microsoft Edge link](#edge) for an example of how links will appear in the XML.
|
||||
|
||||
To edit the default XML or the exported layout, familiarize yourself with the [Start layout XML](https://docs.microsoft.com/en-us/windows/configuration/start-layout-xml-desktop). There are a few [differences between Start layout on a deskop and a Surface Hub.](#differences)
|
||||
|
||||
@ -176,4 +176,8 @@ This example shows a link to a website and a link to a .pdf file.
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
|
||||
```
|
||||
```
|
||||
|
||||
## More information
|
||||
|
||||
- [Blog post: Changing Surface Hub’s Start Menu](https://blogs.technet.microsoft.com/y0av/2018/02/13/47/)
|
||||
|
||||
@ -7,7 +7,7 @@ ms.pagetype: devices
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 07/27/2017
|
||||
ms.date: 01/18/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
|
||||
@ -524,7 +524,7 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
<tr class="even">
|
||||
<td align="left"><p>0x85002004</p></td>
|
||||
<td align="left"><p>E_FAIL_ABORT</p></td>
|
||||
<td align="left"><p>This error is used to interrupt the hanging sync, and will not be exposed to users. It will be shown in the telemetry if you force an interactive sync, delete the account, or update its settings.</p></td>
|
||||
<td align="left"><p>This error is used to interrupt the hanging sync, and will not be exposed to users. It will be shown in the diagnostic data if you force an interactive sync, delete the account, or update its settings.</p></td>
|
||||
<td align="left"><p>Nothing.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -602,7 +602,7 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
|
||||
## Related content
|
||||
|
||||
- [Troubleshooting Miracast connection to the Surface Hub](https://blogs.msdn.microsoft.com/surfacehub/2017/01/30/troubleshooting-miracast-connection-to-the-surface-hub/)
|
||||
- [Troubleshooting Miracast connection to the Surface Hub](https://docs.microsoft.com/surface-hub/miracast-troubleshooting)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,5 +1,6 @@
|
||||
# [Surface](index.md)
|
||||
## [Deploy Surface devices](deploy.md)
|
||||
### [Windows AutoPilot and Surface devices](windows-autopilot-and-surface-devices.md)
|
||||
### [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsc.md)
|
||||
#### [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md)
|
||||
### [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md)
|
||||
|
||||
@ -5,18 +5,26 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.date: 11/03/2017
|
||||
ms.date: 02/12/2018
|
||||
---
|
||||
|
||||
# Change history for Surface documentation
|
||||
|
||||
This topic lists new and updated topics in the Surface documentation library.
|
||||
|
||||
## February 2018
|
||||
|
||||
|New or changed topic | Description |
|
||||
| --- | --- |
|
||||
|[Surface Dock Updater](surface-dock-updater.md) | Added version 2.12.136.0 information |
|
||||
|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.46.0 information |
|
||||
|
||||
## January 2018
|
||||
|
||||
|New or changed topic | Description |
|
||||
| --- | --- |
|
||||
|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.45 information |
|
||||
|[Windows AutoPilot and Surface devices](windows-autopilot-and-surface-devices.md) | New article |
|
||||
|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.45.0 information |
|
||||
|[Surface device compatibility with Windows 10 Long-Term Servicing Channel (LTSC)](surface-device-compatibility-with-windows-10-ltsc.md) | Updated Current Branch (CB) or Current Branch for Business (CBB) servicing options with Semi-Annual Channel (SAC) information |
|
||||
|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | Added Surface Book 2, Surface Laptop, Surface Pro, Surface Pro with LTE Advanced, and Surface Pro information |
|
||||
|
||||
|
||||
@ -5,8 +5,9 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: heatherpoulsen
|
||||
ms.date: 04/11/2017
|
||||
author: brecords
|
||||
ms.date: 01/29/2018
|
||||
ms.author: jdecker
|
||||
---
|
||||
|
||||
# Deploy Surface devices
|
||||
@ -17,7 +18,8 @@ Get deployment guidance for your Surface devices including information about MDT
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition. |
|
||||
| [Windows AutoPilot and Surface devices](windows-autopilot-and-surface-devices.md) | Find out how to remotely deploy and configure devices with Windows AutoPilot. |
|
||||
| [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSC edition. |
|
||||
| [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md) | Walk through the recommended process of how to deploy Windows 10 to your Surface devices with the Microsoft Deployment Toolkit.|
|
||||
| [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)| Find out how to perform a Windows 10 upgrade deployment to your Surface devices. |
|
||||
| [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)| Walk through the process of customizing the Surface out-of-box experience for end users in your organization.|
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: brecords
|
||||
ms.author: jdecker
|
||||
ms.date: 01/03/2018
|
||||
ms.date: 02/12/2018
|
||||
---
|
||||
|
||||
# Microsoft Surface Data Eraser
|
||||
@ -139,25 +139,32 @@ After you create a Microsoft Surface Data Eraser USB stick, you can boot a suppo
|
||||
|
||||
8. Click the **Yes** button to continue erasing data on the Surface device.
|
||||
|
||||
>[!NOTE]
|
||||
>When you run Surface Data Eraser on the Surface Data Eraser USB drive, a log file is generated in the **SurfaceDataEraserLogs** folder.
|
||||
|
||||
## Changes and updates
|
||||
|
||||
Microsoft Surface Data Eraser is periodically updated by Microsoft. For information about the changes provided in each new version, see the following:
|
||||
|
||||
### Version 3.2.45
|
||||
### Version 3.2.46.0
|
||||
This version of Microsoft Surface Data Eraser adds support for the following:
|
||||
|
||||
- Surface Pro with LTE Advanced
|
||||
|
||||
|
||||
### Version 3.2.45.0
|
||||
|
||||
This version of Microsoft Surface Data Eraser adds support for the following:
|
||||
|
||||
- Surface Book 2
|
||||
|
||||
- Surface Pro with LTE Advanced
|
||||
|
||||
- Surface Pro 1TB
|
||||
|
||||
>[!NOTE]
|
||||
>Surface Data Eraser v3.2.45 and above can be used to restore Surface Pro or Surface Laptop devices with the 1TB storage option in the scenario that the device shows two separate 512GB volumes or encounters errors when attempting to deploy or install Windows 10. See [Surface Pro Model 1796 and Surface Laptop 1TB display two drives](https://support.microsoft.com/en-us/help/4046105/surface-pro-model-1796-and-surface-laptop-1tb-display-two-drives) for more information.
|
||||
>Surface Data Eraser v3.2.45.0 and above can be used to restore Surface Pro or Surface Laptop devices with the 1TB storage option in the scenario that the device shows two separate 512GB volumes or encounters errors when attempting to deploy or install Windows 10. See [Surface Pro Model 1796 and Surface Laptop 1TB display two drives](https://support.microsoft.com/en-us/help/4046105/surface-pro-model-1796-and-surface-laptop-1tb-display-two-drives) for more information.
|
||||
|
||||
|
||||
### Version 3.2.36
|
||||
### Version 3.2.36.0
|
||||
|
||||
This version of Microsoft Surface Data Eraser adds support for the following:
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: brecords
|
||||
ms.date: 11/03/2017
|
||||
ms.date: 02/23/2018
|
||||
ms.author: jdecker
|
||||
---
|
||||
|
||||
@ -116,6 +116,22 @@ Microsoft periodically updates Surface Dock Updater. To learn more about the app
|
||||
>[!Note]
|
||||
>Each update to Surface Dock firmware is included in a new version of Surface Dock Updater. To update a Surface Dock to the latest firmware, you must use the latest version of Surface Dock Updater.
|
||||
|
||||
### Version 2.12.136.0
|
||||
*Release Date: 29 January 2018*
|
||||
|
||||
This version of Surface Dock Updater adds support for the following:
|
||||
* Update for Surface Dock Main Chipset Firmware
|
||||
* Update for Surface Dock DisplayPort Firmware
|
||||
* Improved display stability for external displays when used with Surface Book or Surface Book 2
|
||||
|
||||
Additionally, installation of this version of Surface Dock Updater on Surface Book devices includes the following:
|
||||
* Update for Surface Book Base Firmware
|
||||
* Added support for Surface Dock firmware updates with improvements targeted to Surface Book devices
|
||||
|
||||
>[!Note]
|
||||
>Before the Surface Dock firmware update applied by Surface Dock Updater v2.12.136.0 will take effect on a Surface Book device, a firmware update for the Surface Book Base is required. If you install Surface Dock Updater v2.12.136.0 on a Surface Book and update an attached Surface Dock from that same device, the firmware of the Surface Book Base will automatically be updated when installing the Surface Dock Updater. However, if you update a Surface Dock using Surface Dock Updater v2.12.136.0 on different device, and then connect that Surface Dock to a Surface Book where Surface Dock Updater v2.12.136.0 has not been installed, the benefits of the updated Surface Dock will not be enabled. To enable the benefits of the updated Surface Dock on a Surface Book device, Surface Book Base firmware must also be updated by installing Surface Dock Updater v2.12.136.0 on the Surface Book device. Surface Book Base firmware update is not required on a Surface Book 2 device.
|
||||
|
||||
|
||||
### Version 2.9.136.0
|
||||
*Release date: November 3, 2017*
|
||||
|
||||
|
||||
51
devices/surface/windows-autopilot-and-surface-devices.md
Normal file
51
devices/surface/windows-autopilot-and-surface-devices.md
Normal file
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: Windows AutoPilot and Surface Devices (Surface)
|
||||
description: Find out about Windows AutoPilot deployment options for Surface devices.
|
||||
keywords: autopilot, windows 10, surface, deployment
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, devices
|
||||
ms.sitesec: library
|
||||
author: brecords
|
||||
ms.date: 01/31/2018
|
||||
ms.author: jdecker
|
||||
---
|
||||
|
||||
# Windows AutoPilot and Surface devices
|
||||
|
||||
Windows AutoPilot is a cloud-based deployment technology available in Windows 10. Using Windows AutoPilot, you can remotely deploy and configure devices in a truly zero-touch process right out of the box. Windows AutoPilot registered devices are identified over the internet at first boot using a unique device signature, known as the hardware hash, and automatically enrolled and configured using modern management solutions such as Azure Active Directory (AAD) and Mobile Device Management (MDM).
|
||||
|
||||
With Surface devices, you can choose to register your devices at the time of purchase when purchasing from a Surface partner enabled for Windows AutoPilot. New devices can be shipped directly to your end-users and will be automatically enrolled and configured when the units are unboxed and turned on for the first time. This process can eliminate need to reimage your devices as part of your deployment process, reducing the work required of your deployment staff and opening up new, agile methods for device management and distribution.
|
||||
|
||||
In this article learn how to enroll your Surface devices in Windows AutoPilot with a Surface partner and the options and considerations you will need to know along the way. This article focuses specifically on Surface devices, for more information about using Windows AutoPilot with other devices, or to read more about Windows AutoPilot and its capabilities, see [Overview of Windows AutoPilot](https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/windows-10-autopilot) in the Windows Docs Library.
|
||||
|
||||
## Prerequisites
|
||||
Enrollment of Surface devices in Windows AutoPilot with a Surface partner enabled for Windows AutoPilot has the following licensing requirements for each enrolled Surface device:
|
||||
* **Azure Active Directory Premium** – Required to enroll your devices in your organization and to automatically enroll devices in your organization’s mobile management solution.
|
||||
* **Mobile Device Management (such as Microsoft Intune)** – Required to remotely deploy applications, configure, and manage your enrolled devices.
|
||||
* **Office 365 ProPlus** – Required to deploy Microsoft Office to your enrolled devices.
|
||||
|
||||
These requirements are also met by the following solutions:
|
||||
* Microsoft 365 E3 or E5 (includes Azure Active Directory Premium, Microsoft Intune, and Office 365 ProPlus)
|
||||
|
||||
Or
|
||||
* Enterprise Mobility + Security E3 or E5 (includes Azure Active Directory Premium and Microsoft Intune)
|
||||
* Office 365 ProPlus, E3, or E5 (includes Office 365 ProPlus)
|
||||
|
||||
>[!NOTE]
|
||||
>Deployment of devices using Windows AutoPilot to complete the Out-of-Box Experience (OOBE) is supported without these prerequisites, however will yield deployed devices without applications, configuration, or enrollment in a management solution and is highly discouraged.
|
||||
|
||||
### Windows version considerations
|
||||
Support for broad deployments of Surface devices using Windows AutoPilot, including enrollment performed by Surface partners at the time of purchase, requires devices manufactured with or otherwise installed with Windows 10 Version 1709 (Fall Creators Update). Windows 10 Version 1709 uses a secure 4096-bit (4k) hash value to uniquely identify devices for Windows AutoPilot that is necessary for deployments at scale.
|
||||
|
||||
### Surface device support
|
||||
Surface devices with support for out-of-box deployment with Windows AutoPilot, enrolled during the purchase process with a Surface partner, include the following devices, where the devices ship from the factory with Windows 10 Version 1709:
|
||||
* Surface Pro (Model 1796)
|
||||
* Surface Book 2
|
||||
* Surface Laptop
|
||||
* Surface Studio
|
||||
|
||||
## Surface partners enabled for Windows AutoPilot
|
||||
Enrolling Surface devices in Windows AutoPilot at the time of purchase is a capability provided by select Surface partners that are enabled with the capability to identify individual Surface devices during the purchase process and perform enrollment on an organization’s behalf. Devices enrolled by a Surface partner at time of purchase can be shipped directly to users and configured entirely through the zero-touch process of Windows AutoPilot, Azure Active Directory, and Mobile Device Management.
|
||||
|
||||
You can find a list of Surface partners enabled for Windows AutoPilot at the [Windows AutoPilot for Surface portal](https://www.microsoft.com/en-us/itpro/surface/windows-autopilot-for-surface).
|
||||
Reference in New Issue
Block a user