mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jdholo
This commit is contained in:
@ -99,7 +99,7 @@ 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 -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI “tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true
|
||||
Set-CsMeetingRoom -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI "tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true
|
||||
```
|
||||
|
||||
Again, you need to replace the provided domain controller and phone number examples with your own information. The parameter value `$true` stays the same.
|
||||
|
@ -65,7 +65,7 @@ If you deployed Skype for Business Cloud PBX with one of the hybrid voice option
|
||||
If you haven’t created a compatible policy yet, use the following cmdlet (this one creates a policy called "Surface Hubs"). After it’s created, you can apply the same policy to other device accounts.
|
||||
|
||||
```
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
|
||||
$easPolicy = New-MobileDeviceMailboxPolicy -Name "SurfaceHubs" -PasswordEnabled $false
|
||||
```
|
||||
|
||||
After 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. Run the following cmdlets 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 the account and set the password again).
|
||||
|
@ -50,7 +50,7 @@ Deployment of Microsoft Surface UEFI Manager is a typical application deployment
|
||||
|
||||
The command to install Microsoft Surface UEFI Manager is:
|
||||
|
||||
`msiexec /i “SurfaceUEFIManagerSetup.msi” /q`
|
||||
`msiexec /i "SurfaceUEFIManagerSetup.msi" /q`
|
||||
|
||||
The command to uninstall Microsoft Surface UEFI Manager is:
|
||||
|
||||
@ -334,11 +334,11 @@ After your scripts are prepared to configure and enable SEMM on the client devic
|
||||
|
||||
The SEMM Configuration Manager scripts will be added to Configuration Manager as a script application. The command to install SEMM with ConfigureSEMM.ps1 is:
|
||||
|
||||
`Powershell.exe -file “.\ConfigureSEMM.ps1”`
|
||||
`Powershell.exe -file ".\ConfigureSEMM.ps1"`
|
||||
|
||||
The command to uninstall SEMM with ResetSEMM.ps1 is:
|
||||
|
||||
`Powershell.exe -file “.\ResetSEMM.ps1”`
|
||||
`Powershell.exe -file ".\ResetSEMM.ps1"`
|
||||
|
||||
To add the SEMM Configuration Manager scripts to Configuration Manager as an application, use the following process:
|
||||
|
||||
|
Reference in New Issue
Block a user