PowerShell pour Surface Hub (v1)
Remarque
Cette page inclut les scripts PowerShell destinés au Surface Hub d’origine (v1). Pour Surface Hub 2S, consultez Créer et tester un compte d’appareil.
Remarque
Voir aussi Authentification moderne et scripts sans assistance dans Exchange Online PowerShell V2
Conditions préalables
Pour exécuter correctement ces scripts PowerShell, vous devez installer les prérequis suivants :
- Assistant de connexion Microsoft Online Services pour professionnels de l’informatique RTW
- module Microsoft Azure Active Directory pour Windows PowerShell (version 64 bits)
- Module Windows PowerShell pour Skype Entreprise Online
Scripts PowerShell destinés aux administrateurs Surface Hub
À quoi servent les scripts ?
- Créer des comptes d’appareil pour les installations à l’aide d’une forêt unique pure sur site (Microsoft Exchange et Skype 2013 et versions ultérieures uniquement) ou en ligne (Microsoft Office 365), qui sont configurées correctement pour votre Surface Hub.
- Valider des comptes d’appareil existants pour tout programme d’installation (sur site ou en ligne) pour s’assurer qu’ils sont compatibles avec le Surface Hub.
- Fournir un modèle de base pour toutes les personnes souhaitant créer leurs propres scripts de création ou de validation de compte d’appareil.
Quels sont les éléments nécessaires à l’exécution des scripts ?
- Accès PowerShell à distance au domaine ou client de votre organisation, aux serveurs Exchange et aux serveurs Skype Entreprise.
- Informations d’identification du domaine ou du client de votre organisation, des serveurs Exchange et des serveurs Skype Entreprise.
Remarque
Que vous créiez un compte ou que vous modifiiez un compte déjà existant, le script de validation vérifie que votre compte d’appareil est correctement configuré. Vous devez toujours exécuter le script de validation avant d’ajouter un compte d’appareil au Surface Hub.
Exécution des scripts
Les scripts de création de compte effectuent les tâches suivantes :
- Demandez les informations d’identification de l’administrateur.
- Créez des comptes d’appareil dans votre domaine/locataire.
- Créez ou affectez une stratégie ActiveSync compatible avec Le Surface Hub aux comptes d’appareil.
- Définissez différents attributs pour les comptes créés dans Exchange et Skype Entreprise.
- Attribuez des licences et des autorisations aux comptes créés.
Ces attributs sont les attributs définis par les scripts :
| Applet de commande | Attribut | Valeur |
|---|---|---|
Set-Mailbox |
RoomMailboxPassword |
Fourni par l’utilisateur |
EnableRoomMailboxAccount |
Vrai |
|
Type |
Salle |
|
Set-CalendarProcessing |
AutomateProcessing |
AutoAccept |
RemovePrivateProperty |
Faux |
|
DeleteSubject |
Faux |
|
DeleteComments |
Faux |
|
AddOrganizerToSubject |
Faux |
|
AddAdditionalResponse |
Vrai |
|
AdditionalResponse |
« Il s’agit d’une salle Surface Hub ! » |
|
New-MobileDeviceMailboxPolicy |
PasswordEnabled |
Faux |
AllowNonProvisionableDevices |
Vrai |
|
Enable-CSMeetingRoom |
RegistrarPool |
Fourni par l’utilisateur |
SipAddress |
Défini sur le nom d’utilisateur principal (UPN) du compte d’appareil |
|
Set-MsolUserLicense (O365 uniquement) |
AddLicenses |
Fourni par l’utilisateur |
Set-MsolUser (O365 uniquement) |
PasswordNeverExpires |
Vrai |
Set-AdUser (local uniquement) |
Activé |
Vrai |
Set-AdUser (local uniquement) |
PasswordNeverExpires |
Vrai |
Remarque
Les modules PowerShell Azure AD et MSOnline sont déconseillés à compter du 30 mars 2024. Pour en savoir plus, lisez la mise à jour déconseillée. Après cette date, la prise en charge de ces modules est limitée à l’assistance à la migration vers le Kit de développement logiciel (SDK) Microsoft Graph PowerShell et aux correctifs de sécurité. Les modules déconseillés continueront de fonctionner jusqu’au 30 mars 2025.
Nous vous recommandons de migrer vers Microsoft Graph PowerShell pour interagir avec Microsoft Entra ID (anciennement Azure AD). Pour les questions courantes sur la migration, reportez-vous au FAQ sur la migration.
N’oubliez pas que les versions 1.0. x de MSOnline peut subir une interruption après le 30 juin 2024.
Scripts de création de compte
Ces scripts créent un compte d’appareil pour vous. Vous pouvez utiliser le Script de vérification de compte pour vous assurer qu’ils se sont exécutés correctement.
Les scripts de création de compte ne peuvent pas modifier un compte déjà existant, mais peuvent être utilisés pour vous aider à savoir les applets de commande à exécuter pour configurer correctement le compte existant.
Créer un compte local
# SHAccountCreateOnPrem.ps1
$Error.Clear()
$ErrorActionPreference = "Stop"
$status = @{}
# Cleans up set state such as remote powershell sessions
function Cleanup()
{
if ($sessExchange)
{
Remove-PSSession $sessExchange
}
if ($sessCS)
{
Remove-PSSession $sessCS
}
}
function PrintError($strMsg)
{
Write-Host $strMsg -foregroundcolor Red
}
function PrintSuccess($strMsg)
{
Write-Host $strMsg -foregroundcolor Green
}
function PrintAction($strMsg)
{
Write-Host $strMsg -ForegroundColor Cyan
}
# Cleans up and prints an error message
function CleanupAndFail($strMsg)
{
if ($strMsg)
{
PrintError($strMsg);
}
Cleanup
exit 1
}
# Exits if there is an error set and prints the given message
function ExitIfError($strMsg)
{
if ($Error)
{
CleanupAndFail($strMsg);
}
}
## Collect account data ##
$credNewAccount = (Get-Credential -Message "Enter the desired UPN and password for this new account")
$strUpn = $credNewAccount.UserName
$strDisplayName = Read-Host "Please enter the display name you would like to use for $strUpn"
if (!$credNewAccount -Or [System.String]::IsNullOrEmpty($strDisplayName) -Or [System.String]::IsNullOrEmpty($credNewAccount.UserName) -Or $credNewAccount.Password.Length -le 0)
{
CleanupAndFail "Please enter all of the requested data to continue."
exit 1
}
## Sign in to remote powershell for exchange and lync online ##
$credExchange = $null
$credExchange=Get-Credential -Message "Enter credentials of an Exchange user with mailbox creation rights"
if (!$credExchange)
{
CleanupAndFail("Valid credentials are required to create and prepare the account.");
}
$strExchangeServer = Read-Host "Please enter the FQDN of your exchange server (e.g. exch.contoso.com)"
# Lync info
$credLync = Get-Credential -Message "Enter credentials of a Skype for Business admin (or cancel if they are the same as Exchange)"
if (!$credLync)
{
$credLync = $credExchange
}
$strLyncFQDN = Read-Host "Please enter the FQDN of your Lync server (e.g. lync.contoso.com) or enter to use [$strExchangeServer]"
if ([System.String]::IsNullOrEmpty($strLyncFQDN))
{
$strLyncFQDN = $strExchangeServer
}
PrintAction "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
try
{
$sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $credExchange -AllowRedirection -Authentication Kerberos -ConnectionUri "http://$strExchangeServer/powershell" -WarningAction SilentlyContinue
}
catch
{
CleanupAndFail("Failed to connect to exchange. Please check your credentials and try again. If this continues to fail, you may not have permission for remote powershell - if not, please perform the setup manually. Error message: $_")
}
PrintSuccess "Connected to Remote Exchange Shell"
try
{
$sessLync = New-PSSession -Credential $credLync -ConnectionURI "https://$strLyncFQDN/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
}
catch
{
CleanupAndFail("Failed to connect to Lync. Please check your credentials and try again. Error message: $_")
}
PrintSuccess "Connected to Lync Server Remote PowerShell"
Import-PSSession $sessExchange -AllowClobber -WarningAction SilentlyContinue
Import-PSSession $sessLync -AllowClobber -WarningAction SilentlyContinue
## Create the Exchange mailbox ##
> [!Note]
> These exchange commandlets do not always throw their errors as exceptions
# Because Get-Mailbox throws an error if the mailbox isn't found
$Error.Clear()
PrintAction "Creating a new account..."
try
{
$mailbox = $null
$mailbox = (New-Mailbox -UserPrincipalName $credNewAccount.UserName -Alias $credNewAccount.UserName.substring(0,$credNewAccount.UserName.indexOf('@')) -room -Name $strDisplayName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true)
} catch { }
ExitIfError "Failed to create a new mailbox on exchange.";
$status["Mailbox Setup"] = "Successfully created a mailbox for the new account"
$strEmail = $mailbox.WindowsEmailAddress
PrintSuccess "The following mailbox has been created for this room: $strEmail"
## Create or retrieve a policy to be applied to surface hub devices ##
# The policy disables requiring a device password so that the SurfaceHub does not need to be lockable to use Active Sync
$strPolicy = Read-Host 'Please enter the name for a new Surface Hub ActiveSync policy to be created and applied to this account.
We will configure that policy to be compatible with Surface Hub devices.
If this script has been used before, please enter the name of the existing policy.'
$easpolicy = $null
try {
$easpolicy = Get-MobileDeviceMailboxPolicy $strPolicy
}
catch {}
if ($easpolicy)
{
if (!$easpolicy.PasswordEnabled -and ($easpolicy.AllowNonProvisionableDevices -eq $null -or $easpolicy.AllowNonProvisionableDevices ))
{
PrintSuccess "An existing policy has been found and will be applied to this account."
}
else
{
PrintError "The policy you provided is incompatible with the surface hub."
$easpolicy = $null
$status["Device Password Policy"] = "Failed to apply the EAS policy to the account because the policy was invalid."
}
}
else
{
$Error.Clear()
PrintAction "Creating policy..."
$easpolicy = New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false -AllowNonProvisionableDevices $true
if ($easpolicy)
{
PrintSuccess "A new device policy has been created; you can use this same policy for all future Surface Hub device accounts."
}
else
{
PrintError "Could not create $strPolicy"
}
}
if ($easpolicy)
{
# Convert mailbox to user type so we can apply the policy (necessary)
# Sometimes it takes a while for this change to take affect so we have some nasty retry loops
$Error.Clear();
try
{
Set-Mailbox $credNewAccount.UserName -Type Regular
} catch {}
if ($Error)
{
$Error.Clear()
$status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
}
else
{
# Loop until resource type goes away, up to 5 times
for ($i = 0; $i -lt 5 -And (Get-Mailbox $credNewAccount.UserName).ResourceType; $i++)
{
Start-Sleep -s 5
}
# If the mailbox is still a Room we cannot apply the policy
if (!((Get-Mailbox $credNewAccount.UserName).ResourceType))
{
$Error.Clear()
# Set policy for account
Set-CASMailbox $credNewAccount.UserName -ActiveSyncMailboxPolicy $strPolicy
if (!$Error)
{
$status["ActiveSync Policy"] = "Successfully applied $strPolicy to the account"
}
else
{
$status["ActiveSync Policy"] = "Failed to apply the EAS policy to the account."
}
$Error.Clear()
# Convert back to room mailbox
Set-Mailbox $credNewAccount.UserName -Type Room
# Loop until resource type goes back to room
for ($i = 0; ($i -lt 5) -And ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room"); $i++)
{
Start-Sleep -s 5
}
if ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room")
{
# A failure to convert the mailbox back to a room is unfortunate but means the mailbox is unusable.
$status["Mailbox Setup"] = "A mailbox was created but we could not set it to a room resource type."
}
else
{
try
{
Set-Mailbox $credNewAccount.UserName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
} catch { }
if ($Error)
{
$status["Mailbox Setup"] = "A room mailbox was created but we could not set its password."
}
$Error.Clear()
}
}
}
}
PrintSuccess "Account creation completed."
PrintAction "Setting calendar processing rules..."
$Error.Clear();
## Prepare the calendar for automatic meeting responses ##
try {
Set-CalendarProcessing -Identity $credNewAccount.UserName -AutomateProcessing AutoAccept
} catch { }
if ($Error)
{
$status["Calendar Acceptance"] = "Failed to configure the account to automatically accept/decline meeting requests"
}
else
{
$status["Calendar Acceptance"] = "Successfully configured the account to automatically accept/decline meeting requests"
}
$Error.Clear()
try {
Set-CalendarProcessing -Identity $credNewAccount.UserName -RemovePrivateProperty $false -AddOrganizerToSubject $false -AddAdditionalResponse $true -DeleteSubject $false -DeleteComments $false -AdditionalResponse "This is a Surface Hub room!"
} catch { }
if ($Error)
{
$status["Calendar Response Configuration"] = "Failed to configure the account's response properties"
}
else
{
$status["Calendar Response Configuration"] = "Successfully configured the account's response properties"
}
$Error.Clear()
## Configure the Account to not expire ##
PrintAction "Configuring password not to expire..."
Start-Sleep -s 20
try
{
Set-AdUser $mailbox.UserPrincipalName -PasswordNeverExpires $true -Enabled $true
}
catch
{
}
if ($Error)
{
$status["Password Expiration Policy"] = "Failed to set the password to never expire"
}
else
{
$status["Password Expiration Policy"] = "Successfully set the password to never expire"
}
PrintSuccess "Completed Exchange configuration"
## Setup Skype for Business. This is somewhat optional and if it fails we SfbEnable can be used later ##
PrintAction "Configuring account for Skype for Business."
# Getting registrar pool
$strRegPool = $strLyncFQDN
$Error.Clear()
$strRegPoolEntry = Read-Host "Enter a Skype for Business Registrar Pool, or leave blank to use [$strRegPool]"
if (![System.String]::IsNullOrEmpty($strRegPoolEntry))
{
$strRegPool = $strRegPoolEntry
}
# Try to SfB-enable the account. Note that it may not work right away as the account needs to propagate to active directory
PrintAction "Enabling Skype for Business..."
Start-Sleep -s 10
$Error.Clear()
try {
Enable-CsMeetingRoom -Identity $credNewAccount.UserName -RegistrarPool $strRegPool -SipAddressType EmailAddress
}
catch { }
if ($Error)
{
$status["Skype for Business Account Setup"] = "Failed to setup the Skype for Business meeting room - you can run EnableSfb.ps1 to try again."
$Error.Clear();
}
else
{
$status["Skype for Business Account Setup"] = "Successfully enabled account as a Skype for Business meeting room"
}
Write-Host
## Cleanup and print results ##
Cleanup
$strDisplay = $mailbox.DisplayName
$strUsr = $credNewAccount.UserName
PrintAction "Summary for creation of $strUsr ($strDisplay)"
if ($status.Count -gt 0)
{
ForEach($k in $status.Keys)
{
$v = $status[$k]
$color = "yellow"
if ($v[0] -eq "S") { $color = "green" }
elseif ($v[0] -eq "F")
{
$color = "red"
$v += " Go to https://aka.ms/shubtshoot"
}
Write-Host -NoNewline $k -ForegroundColor $color
Write-Host -NoNewline ": "
Write-Host $v
}
}
else
{
PrintError "The account could not be created"
}
Créer un compte d’appareil à l’aide d’Office 365
Crée un compte comme décrit dans Créer un compte d’appareil à l’aide de Office 365.
# SHAccountCreateO365.ps1
$Error.Clear()
$ErrorActionPreference = "Stop"
$status = @{}
# Cleans up set state such as remote powershell sessions
function Cleanup()
{
if ($sessExchange)
{
Remove-PSSession $sessExchange
}
if ($sessCS)
{
Remove-PSSession $sessCS
}
}
function PrintError($strMsg)
{
Write-Host $strMsg -foregroundcolor Red
}
function PrintSuccess($strMsg)
{
Write-Host $strMsg -foregroundcolor Green
}
function PrintAction($strMsg)
{
Write-Host $strMsg -ForegroundColor Cyan
}
# Cleans up and prints an error message
function CleanupAndFail($strMsg)
{
if ($strMsg)
{
PrintError($strMsg);
}
Cleanup
exit 1
}
# Exits if there is an error set and prints the given message
function ExitIfError($strMsg)
{
if ($Error)
{
CleanupAndFail($strMsg);
}
}
## Check dependencies ##
try {
Import-Module SkypeOnlineConnector
Import-Module MSOnline
}
catch
{
PrintError "Some dependencies are missing"
PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to https://www.microsoft.com/download/details.aspx?id=39366"
PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
CleanupAndFail
}
## Collect account data ##
$credNewAccount = (Get-Credential -Message "Enter the desired UPN and password for this new account")
$strUpn = $credNewAccount.UserName
$strDisplayName = Read-Host "Please enter the display name you would like to use for $strUpn"
if (!$credNewAccount -Or [System.String]::IsNullOrEmpty($strDisplayName) -Or [System.String]::IsNullOrEmpty($credNewAccount.UserName) -Or $credNewAccount.Password.Length -le 0)
{
CleanupAndFail "Please enter all of the requested data to continue."
exit 1
}
## Sign in to remote powershell for exchange and lync online ##
$credAdmin = $null
$credAdmin=Get-Credential -Message "Enter credentials of an Exchange and Skype for Business admin"
if (!$credadmin)
{
CleanupAndFail "Valid admin credentials are required to create and prepare the account."
}
PrintAction "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
try
{
$sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $credAdmin -AllowRedirection -Authentication basic -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -WarningAction SilentlyContinue
}
catch
{
CleanupAndFail "Failed to connect to exchange. Please check your credentials and try again. Error message: $_"
}
try
{
$sessCS = New-CsOnlineSession -Credential $credAdmin
}
catch
{
CleanupAndFail "Failed to connect to Skype for Business Online Datacenter. Please check your credentials and try again. Error message: $_"
}
try
{
Connect-MsolService -Credential $credAdmin
}
catch
{
CleanupAndFail "Failed to connect to Azure Active Directory. Please check your credentials and try again. Error message: $_"
}
Import-PSSession $sessExchange -AllowClobber -WarningAction SilentlyContinue
Import-PSSession $sessCS -AllowClobber -WarningAction SilentlyContinue
## Create the Exchange mailbox ##
> [!Note]
> These exchange commandlets do not always throw their errors as exceptions
# Because Get-Mailbox throws an error if the mailbox isn't found
$Error.Clear()
PrintAction "Creating a new account..."
try
{
$mailbox = $null
$mailbox = (New-Mailbox -MicrosoftOnlineServicesID $credNewAccount.UserName -room -Name $strDisplayName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true)
} catch { }
ExitIfError "Failed to create a new mailbox on exchange.";
$status["Mailbox Setup"] = "Successfully created a mailbox for the new account"
$strEmail = $mailbox.WindowsEmailAddress
PrintSuccess "The following mailbox has been created for this room: $strEmail"
## Create or retrieve a policy to be be applied to surface hub devices ##
# The policy disables requiring a device password so that the SurfaceHub does not need to be lockable to use Active Sync
$strPolicy = Read-Host 'Please enter the name for a new Surface Hub ActiveSync policy to be be created and applied to this account.
We will configure that policy to be compatible with Surface Hub devices.
If this script has been used before, please enter the name of the existing policy.'
$easpolicy = $null
try {
$easpolicy = Get-MobileDeviceMailboxPolicy $strPolicy
}
catch {}
if ($easpolicy)
{
if (!$easpolicy.PasswordEnabled -and ($easpolicy.AllowNonProvisionableDevices -eq $null -or $easpolicy.AllowNonProvisionableDevices ))
{
PrintSuccess "An existing policy has been found and will be applied to this account."
}
else
{
PrintError "The policy you provided is incompatible with the surface hub."
$easpolicy = $null
$status["ActiveSync Policy"] = "Failed to apply the EAS policy to the account because the policy was invalid."
}
}
else
{
$Error.Clear()
PrintAction "Creating policy..."
$easpolicy = New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false -AllowNonProvisionableDevices $true
if ($easpolicy)
{
PrintSuccess "A new device policy has been created; you can use this same policy for all future Surface Hub device accounts."
}
else
{
PrintError "Could not create $strPolicy"
}
}
if ($easpolicy)
{
# Convert mailbox to user type so we can apply the policy (necessary)
# Sometimes it takes a while for this change to take affect so we have some nasty retry loops
$Error.Clear();
try
{
Set-Mailbox $credNewAccount.UserName -Type Regular
} catch {}
if ($Error)
{
$Error.Clear()
$status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
PrintError "Failed to convert to regular account"
}
else
{
# Loop until resource type goes away, up to 5 times
for ($i = 0; $i -lt 5 -And (Get-Mailbox $credNewAccount.UserName).ResourceType; $i++)
{
Start-Sleep -s 5
}
# If the mailbox is still a Room we cannot apply the policy
if (!((Get-Mailbox $credNewAccount.UserName).ResourceType))
{
$Error.Clear()
# Set policy for account
Set-CASMailbox $credNewAccount.UserName -ActiveSyncMailboxPolicy $strPolicy
if (!$Error)
{
$status["Device Password Policy"] = "Successfully applied $strPolicy to the account"
}
else
{
$status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
PrintError "Failed to apply policy"
}
$Error.Clear()
# Convert back to room mailbox
Set-Mailbox $credNewAccount.UserName -Type Room
# Loop until resource type goes back to room
for ($i = 0; ($i -lt 5) -And ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room"); $i++)
{
Start-Sleep -s 5
}
if ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room")
{
# A failure to convert the mailbox back to a room is unfortunate but means the mailbox is unusable.
$status["Mailbox Setup"] = "A mailbox was created but we could not set it to a room resource type."
}
else
{
Set-Mailbox $credNewAccount.UserName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
if ($Error)
{
$status["Mailbox Setup"] = "A room mailbox was created but we could not set its password."
}
$Error.Clear()
}
}
}
}
else
{
$status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
PrintError "Failed to obtain policy"
}
PrintSuccess "Account creation completed."
PrintAction "Setting calendar processing rules..."
$Error.Clear();
## Prepare the calendar for automatic meeting responses ##
try {
Set-CalendarProcessing -Identity $credNewAccount.UserName -AutomateProcessing AutoAccept
} catch { }
if ($Error)
{
$status["Calendar Acceptance"] = "Failed to configure the account to automatically accept/decline meeting requests"
}
else
{
$status["Calendar Acceptance"] = "Successfully configured the account to automatically accept/decline meeting requests"
}
$Error.Clear()
try {
Set-CalendarProcessing -Identity $credNewAccount.UserName -RemovePrivateProperty $false -AddOrganizerToSubject $false -AddAdditionalResponse $true -DeleteSubject $false -DeleteComments $false -AdditionalResponse "This is a Surface Hub room!"
} catch { }
if ($Error)
{
$status["Calendar Response Configuration"] = "Failed to configure the account's response properties"
}
else
{
$status["Calendar Response Configuration"] = "Successfully configured the account's response properties"
}
$Error.Clear()
## Configure the Account to not expire ##
PrintAction "Configuring password not to expire..."
try
{
Set-MsolUser -UserPrincipalName $credNewAccount.UserName -PasswordNeverExpires $true
}
catch
{
}
if ($Error)
{
$status["Password Expiration Policy"] = "Failed to set the password to never expire"
}
else
{
$status["Password Expiration Policy"] = "Successfully set the password to never expire"
}
PrintSuccess "Completed Exchange configuration"
## Setup Skype for Business. This is somewhat optional and if it fails we SfbEnable can be used later ##
PrintAction "Configuring account for Skype for Business."
# Getting registrar pool
$strRegPool = $null
try {
$strRegPool = (Get-CsTenant).TenantPoolExtension
}
catch {}
$Error.Clear()
if (![System.String]::IsNullOrEmpty($strRegPool))
{
$strRegPool = $strRegPool.Substring($strRegPool[0].IndexOf(':') + 1)
}
<#
$strRegPoolEntry = Read-Host "Enter a Skype for Business Registrar Pool, or leave blank to use [$strRegPool]"
if (![System.String]::IsNullOrEmpty($strRegPoolEntry))
{
$strRegPool = $strRegPoolEntry
}
#>
# Try to SfB-enable the account. Note that it may not work right away as the account needs to propagate to active directory
PrintAction "Enabling Skype for Business on $strRegPool"
Start-Sleep -s 10
$Error.Clear()
try {
Enable-CsMeetingRoom -Identity $credNewAccount.UserName -RegistrarPool $strRegPool -SipAddressType EmailAddress
}
catch { }
if ($Error)
{
$status["Skype for Business Account Setup"] = "Failed to setup the Skype for Business meeting room - you can run EnableSfb.ps1 to try again."
$Error.Clear();
}
else
{
$status["Skype for Business Account Setup"] = "Successfully enabled account as a Skype for Business meeting room"
}
## Now we need to assign a Skype for Business license to the account ##
# Assign a license to thes
$countryCode = (Get-CsTenant).CountryAbbreviation
$loc = Read-Host "Please enter the usage location for this device account (where the account is being used). This is a 2-character code that is used to assign licenses (e.g. $countryCode)"
try {
$Error.Clear()
Set-MsolUser -UserPrincipalName $credNewAccount.UserName -UsageLocation $loc
}
catch{}
if ($Error)
{
$status["Office 365 License"] = "Failed to assign an Office 365 license to the account"
$Error.Clear()
}
else
{
PrintAction "We found the following licenses available for your tenant:"
$skus = (Get-MsolAccountSku | Where-Object { !$_.AccountSkuID.Contains("INTUNE"); })
$i = 1
$skus | % {
Write-Host -NoNewline $i
Write-Host -NoNewLine ": AccountSKUID: "
Write-Host -NoNewLine $_.AccountSkuid
Write-Host -NoNewLine " Active Units: "
Write-Host -NoNewLine $_.ActiveUnits
Write-Host -NoNewLine " Consumed Units: "
Write-Host $_.ConsumedUnits
$i++
}
$iLicenseIndex = 0;
do
{
$iLicenseIndex = Read-Host 'Choose the number for the SKU you want to pick'
} while ($iLicenseIndex -lt 1 -or $iLicenseIndex -gt $skus.Length)
$strLicenses = $skus[$iLicenseIndex - 1].AccountSkuId
if (![System.String]::IsNullOrEmpty($strLicenses))
{
try
{
$Error.Clear()
Set-MsolUserLicense -UserPrincipalName $credNewAccount.UserName -AddLicenses $strLicenses
}
catch
{
}
if ($Error)
{
$Error.Clear()
$status["Office 365 License"] = "Failed to add a license to the account. Make sure you have remaining licenses."
}
else
{
$status["Office 365 License"] = "Successfully added license to the account"
}
}
else
{
$status["Office 365 License"] = "You opted not to install a license on this account"
}
}
Write-Host
## Cleanup and print results ##
Cleanup
$strDisplay = $mailbox.DisplayName
$strUsr = $credNewAccount.UserName
PrintAction "Summary for creation of $strUsr ($strDisplay)"
if ($status.Count -gt 0)
{
ForEach($k in $status.Keys)
{
$v = $status[$k]
$color = "yellow"
if ($v[0] -eq "S") { $color = "green" }
elseif ($v[0] -eq "F")
{
$color = "red"
$v += " Go to https://aka.ms/shubtshoot for help"
}
Write-Host -NoNewline $k -ForegroundColor $color
Write-Host -NoNewline ": "
Write-Host $v
}
}
else
{
PrintError "The account could not be created"
}
Script de vérification de compte
Ce script de réussite/échec valide le compte d’appareil créé précédemment sur Surface Hub et Surface Hub 2S et génère un rapport de synthèse ou un message d’erreur détaillé. Par exemple :
15 tests executed
0 failures
2 warnings
15 passed
Les détails des paramètres spécifiques ne sont pas affichés.
# SHAccountValidate.ps1
$Error.Clear()
$ErrorActionPreference = "Stop"
# Cleans up set state such as remote powershell sessions
function Cleanup()
{
if ($sessEx)
{
Remove-PSSession $sessEx
}
if ($sessSfb)
{
Remove-PSSession $sessSfb
}
}
function PrintError($strMsg)
{
Write-Host $strMsg -foregroundcolor "red"
}
function PrintSuccess($strMsg)
{
Write-Host $strMsg -foregroundcolor "green"
}
function PrintAction($strMsg)
{
Write-Host $strMsg -ForegroundColor Cyan
}
# Cleans up and prints an error message
function CleanupAndFail($strMsg)
{
if ($strMsg)
{
PrintError($strMsg);
}
Cleanup
exit 1
}
# Exits if there is an error set and prints the given message
function ExitIfError($strMsg)
{
if ($Error)
{
CleanupAndFail($strMsg);
}
}
$strUpn = Read-Host "What is the email address of the account you wish to validate?"
if (!$strUpn.Contains('@'))
{
CleanupAndFail "$strUpn isn't a valid email address"
}
$strExServer = Read-Host "What is your exchange server? (leave blank for online tenants)"
if ($strExServer.Equals(""))
{
$fExIsOnline = $true
}
else
{
$fExIsOnline = $false
}
$credEx = Get-Credential -Message "Please provide exchange user credentials"
$strRegistrarPool = Read-Host ("What is the Skype for Business registrar pool for $strUpn" + "? (leave blank for online tenants)")
$fSfbIsOnline = $strRegistrarPool.Equals("")
$fHasOnPrem = $true
if ($fSfbIsOnline -and $fExIsOnline)
{
do
{
$strHasOnPrem = (Read-Host "Do you have an on-premises Active Directory (Y/N) (No if your domain services are hosted entirely online)").ToUpper()
} while ($strHasOnPrem -ne "Y" -and $strHasOnPrem -ne "N")
$fHasOnPrem = $strHasOnPrem.Equals("Y")
}
$fHasOnline = $false
if ($fSfbIsOnline -or $fExIsOnline)
{
$fHasOnline = $true
}
if ($fSfbIsOnline)
{
try {
Import-Module SkypeOnlineConnector
}
catch
{
CleanupAndFail "To verify Skype for Business in online tenants you need the Lync Online Connector module from https://www.microsoft.com/download/details.aspx?id=39366"
}
}
else
{
$credSfb = (Get-Credential -Message "Please enter Skype for Business admin credentials")
}
if ($fHasOnline)
{
$credSfb = $credEx
try {
Import-Module MSOnline
}
catch
{
CleanupAndFail "To verify accounts in online tenants you need the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
}
}
PrintAction "Connecting to Exchange Powershell Session..."
[System.Management.Automation.Runspaces.AuthenticationMechanism] $authType = [System.Management.Automation.Runspaces.AuthenticationMechanism]::Kerberos
if ($fExIsOnline)
{
$authType = [System.Management.Automation.Runspaces.AuthenticationMechanism]::Basic
}
try
{
$sessEx = $null
if ($fExIsOnline)
{
$sessEx = New-PSSession -ConfigurationName microsoft.exchange -Credential $credEx -AllowRedirection -Authentication $authType -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -WarningAction SilentlyContinue
}
else
{
$sessEx = New-PSSession -ConfigurationName microsoft.exchange -Credential $credEx -AllowRedirection -Authentication $authType -ConnectionUri https://$strExServer/powershell -WarningAction SilentlyContinue
}
}
catch
{
}
if (!$sessEx)
{
CleanupAndFail "Connecting to Exchange Powershell failed, please validate your server is accessible and credentials are correct"
}
PrintSuccess "Connected to Exchange Powershell Session"
PrintAction "Connecting to Skype for Business Powershell Session..."
if ($fSfbIsOnline)
{
$sessSfb = New-CsOnlineSession -Credential $credSfb
}
else
{
$sessSfb = New-PSSession -Credential $credSfb -ConnectionURI "https://$strRegistrarPool/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
}
if (!$sessSfb)
{
CleanupAndFail "Connecting to Skype for Business Powershell failed, please validate your server is accessible and credentials are correct"
}
PrintSuccess "Connected to Skype for Business Powershell"
if ($fHasOnline)
{
$credMsol = $null
if ($fExIsOnline)
{
$credMsol = $credEx
}
elseif ($fSfbIsOnline)
{
$credMsol = $credSfb
}
else
{
CleanupAndFail "Internal error - could not determine MS Online credentials"
}
try
{
PrintAction "Connecting to Azure Active Directory Services..."
Connect-MsolService -Credential $credMsol
PrintSuccess "Connected to Azure Active Directory Services"
}
catch
{
# This really shouldn't happen unless there is a network error
CleanupAndFail "Failed to connect to MSOnline"
}
}
PrintAction "Importing remote sessions into the local session..."
try
{
$importEx = Import-PSSession $sessEx -AllowClobber -WarningAction SilentlyContinue -DisableNameChecking
$importSfb = Import-PSSession $sessSfb -AllowClobber -WarningAction SilentlyContinue -DisableNameChecking
}
catch
{
}
if (!$importEx -or !$importSfb)
{
CleanupAndFail "Import failed"
}
PrintSuccess "Import successful"
$mailbox = $null
try
{
$mailbox = Get-Mailbox -Identity $strUpn
}
catch
{
}
if (!$mailbox)
{
CleanupAndFail "Account exists check failed. Unable to find the mailbox for $strUpn - please make sure the Exchange account exists on $strExServer"
}
$exchange = $null
if (!$fExIsOnline)
{
$exchange = Get-ExchangeServer
if (!$exchange -or !$exchange.IsE14OrLater)
{
CleanupAndFail "A compatible exchange server version was not found. Please use at least exchange 2010."
}
}
$strAlias = $mailbox.UserPrincipalName
$strDisplayName = $mailbox.DisplayName
$strLinkedAccount = $strLinkedDomain = $strLinkedUser = $strLinkedServer = $null
$credLinkedDomain = $Null
if (!$fExIsOnline -and ![System.String]::IsNullOrEmpty($mailbox.LinkedMasterAccount) -and !$mailbox.LinkedMasterAccount.EndsWith("\SELF"))
{
$strLinkedAccount = $mailbox.LinkedMasterAccount
$strLinkedDomain = $strLinkedAccount.substring(0,$strLinkedAccount.IndexOf('\'))
$strLinkedUser = $strLinkedAccount.substring($strLinkedAccount.IndexOf('\') + 1)
$strLinkedServer = Read-Host "What is the domain controller for the $strLinkedDomain"
$credLinkedDomain = (Get-Credential -Message "Please provide credentials for $strLinkedDomain")
}
Write-Host
Write-Host
Write-Host
PrintAction "Performing verification checks on $strDisplayName..."
$Global:iTotalFailures = 0
$global:iTotalWarnings = 0
$Global:iTotalPasses = 0
function Validate()
{
Param(
[string]$Test,
[bool] $Condition,
[string]$FailureMsg,
[switch]$WarningOnly
)
Write-Host -NoNewline -ForegroundColor White $Test.PadRight(100,'.')
if ($Condition)
{
Write-Host -ForegroundColor Green "Passed"
$global:iTotalPasses++
}
else
{
if ($WarningOnly)
{
Write-Host -ForegroundColor Yellow ("Warning: "+$FailureMsg)
$global:iTotalWarnings++
}
else
{
Write-Host -ForegroundColor Red ("Failed: "+$FailureMsg)
$global:iTotalFailures++
}
}
}
## Exchange ##
Validate -WarningOnly -Test "The mailbox $strUpn is enabled as a room account" -Condition ($mailbox.RoomMailboxAccountEnabled -eq $True) -FailureMsg "RoomMailboxEnabled - without a device account, the Surface Hub won't be able to use various key features."
$calendarProcessing = Get-CalendarProcessing -Identity $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
Validate -Test "The mailbox $strUpn is configured to accept meeting requests" -Condition ($calendarProcessing -ne $null -and $calendarProcessing.AutomateProcessing -eq 'AutoAccept') -FailureMsg "AutomateProcessing - the Surface Hub won't be able to send mail or sync its calendar."
Validate -WarningOnly -Test "The mailbox $strUpn won't delete meeting comments" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.DeleteComments) -FailureMsg "DeleteComments - the Surface Hub may be missing some meeting information on the welcome screen and Skype."
Validate -WarningOnly -Test "The mailbox $strUpn keeps private meetings private" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.RemovePrivateProperty) -FailureMsg "RemovePrivateProperty - the Surface Hub will make show private meetings."
Validate -Test "The mailbox $strUpn keeps meeting subjects" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.DeleteSubject) -FailureMsg "DeleteSubject - the Surface Hub won't keep meeting subject information."
Validate -WarningOnly -Test "The mailbox $strUpn does not prepend meeting organizers to subjects" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.AddOrganizerToSubject) -FailureMsg "AddOrganizerToSubject - the Surface Hub won't display meeting subjects as intended."
if ($fExIsOnline)
{
#No online specifics
}
else
{
#No onprem specifics
}
#ActiveSync
$casMailbox = Get-Casmailbox $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
Validate -Test "The mailbox $strUpn has a mailbox policy" -Condition ($casMailbox -ne $null) -FailureMsg "PasswordEnabled - unable to find policy - the Surface Hub won't be able to send mail or sync its calendar."
if ($casMailbox)
{
$policy = $null
if ($fExIsOnline -or $exchange.IsE15OrLater)
{
$strPolicy = $casMailbox.ActiveSyncMailboxPolicy
$policy = Get-MobileDeviceMailboxPolicy -Identity $strPolicy -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
Validate -Test "The policy $strPolicy does not require a device password" -Condition ($policy.PasswordEnabled -ne $True) -FailureMsg "PasswordEnabled - policy requires a device password - the Surface Hub won't be able to send mail or sync its calendar."
}
else
{
$strPolicy = $casMailbox.ActiveSyncMailboxPolicy
$policy = Get-ActiveSyncMailboxPolicy -Identity $strPolicy -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
Validate -Test "The policy $strPolicy does not require a device password" -Condition ($policy.PasswordEnabled -ne $True) -FailureMsg "PasswordEnabled - policy requires a device password - the Surface Hub won't be able to send mail or sync its calendar."
}
if ($policy -ne $null)
{
Validate -Test "The policy $strPolicy allows non-provisionable devices" -Condition ($policy.AllowNonProvisionableDevices -eq $null -or $policy.AllowNonProvisionableDevices -eq $true) -FailureMsg "AllowNonProvisionableDevices - policy won't allow the SurfaceHub to sync"
}
}
# Check the default access level
$orgSettings = Get-ActiveSyncOrganizationSettings
$strDefaultAccessLevel = $orgSettings.DefaultAccessLevel
Validate -Test "ActiveSync devices are allowed" -Condition ($strDefaultAccessLevel -eq 'Allow') -FailureMsg "DeviceType Windows Mail is accessible - devices are not allowed by default - the surface hub won't be able to send mail or sync its calendar."
# Check if there exists a device access rule that bans the device type Windows Mail
$blockingRules = Get-ActiveSyncDeviceAccessRule | where {($_.AccessLevel -eq 'Block' -or $_.AccessLevel -eq 'Quarantine') -and $_.Characteristic -eq 'DeviceType'-and $_.QueryString -eq 'WindowsMail'}
Validate -Test "Windows mail devices are not blocked or quarantined" -Condition ($blockingRules -eq $null -or $blockingRules.Length -eq 0) -FailureMsg "DeviceType Windows Mail is accessible - devices are blocked or quarantined - the surface hub won't be able to send mail or sync its calendar."
## End Exchange ##
## SfB ##
$strLyncIdentity = $null
if ($fSfbIsOnline)
{
$strLyncIdentity = $strUpn
}
else
{
$strLyncIdentity = $strAlias
}
$lyncAccount = $null
try {
$lyncAccount = Get-CsMeetingRoom -Identity $strLyncIdentity -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
} catch {
try {
$lyncAccount = Get-CsUser -Identity $strLyncIdentity -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
} catch { }
}
Validate -Test "There is a Lync or Skype for Business account for $strLyncIdentity" -Condition ($lyncAccount -ne $null -and $lyncAccount.Enabled) -FailureMsg "SfB Enabled - there is no Skype for Business account - meetings won't support Skype for Business"
if ($lyncAccount)
{
Validate -Test "The meeting room has a SIP address" -Condition (![System.String]::IsNullOrEmpty($lyncAccount.SipAddress)) -FailureMsg "SfB Enabled - there is no SIP Address - the device account cannot be used to sign into Skype for Business."
}
## End SFB ##
if ($fHasOnline)
{
#License validation and password expiry
$accountOnline = Get-MsolUser -UserPrincipalName $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
Validate -Test "There is an online user account for $strUpn" -Condition ($accountOnline -ne $null) -FailureMsg "Could not find a Microsoft Online account for this user even though some services are online"
if ($accountOnline)
{
Validate -Test "The password for $strUpn won't expire" -Condition ($accountOnline.PasswordNeverExpires -eq $True) -FailureMsg "PasswordNeverExpires - the admin needs to update the device account's password on the Surface Hub when it expires."
if ($fIsSfbOnline -and !$fIsExOnline)
{
$strLicenseFailureMsg = "Has O365 license - The devices won't be able to use Skype for Business services."
}
elseif ($fIsExOnline -and !$fIsSfbOnline)
{
$strLicenseFailureMsg = "Has O365 license - The devices won't be able to use Exchange Online services."
}
else
{
$strLicenseFailureMsg = "Has O365 license - The devices won't be able to use Skype for Business or Exchange Online services."
}
Validate -Test "$strUpn is licensed" -Condition ($accountOnline.IsLicensed -eq $True) -FailureMsg $strLicenseFailureMsg
Validate -Test "$strUpn is allowed to sign in" -Condition ($accountOnline.BlockCredential -ne $True) -FailureMsg "BlockCredential - This user isn't allowed to sign in."
}
}
#If there is an on-premises component, we can get the authoritative AD user from mailbox
if ($fHasOnPrem)
{
$accountOnPrem = $null
if ($strLinkedAccount)
{
$accountOnPrem = Get-AdUser $strLinkedUser -server $strLinkedServer -credential $credLinkedDomain -properties PasswordNeverExpires -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
}
else
{
#AD User enabled validation
$accountOnPrem = Get-AdUser $mailbox.UserPrincipalName -properties PasswordNeverExpires -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
}
$strOnPremUpn = $accountOnPrem.UserPrincipalName
Validate -Test "There is a user account for $strOnPremUpn" -Condition ($accountOnprem -ne $null) -FailureMsg "Could not find an Active Directory account for this user"
if ($accountOnPrem)
{
Validate -WarningOnly -Test "The password for $strOnPremUpn won't expire" -Condition ($accountOnprem.PasswordNeverExpires -eq $True) -FailureMsg "PasswordNeverExpires - the admin needs to update the device account's password on the Surface Hub when it expires."
Validate -Test "$strOnPremUpn is enabled" -Condition $accountOnPrem.Enabled -FailureMsg "AccountEnabled - this device account won't sign in"
}
}
$global:iTotalTests = ($global:iTotalFailures + $global:iTotalPasses + $global:iTotalWarnings)
Write-Host -NoNewline $global:iTotalTests "tests executed: "
Write-Host -NoNewline -ForegroundColor Red $Global:iTotalFailures "failures "
Write-Host -NoNewline -ForegroundColor Yellow $Global:iTotalWarnings "warnings "
Write-Host -ForegroundColor Green $Global:iTotalPasses "passes "
Cleanup
Activer Skype Entreprise
Ce script active Skype Entreprise sur un compte d’appareil. Utilisez-le uniquement si Skype Entreprise n’a pas été activé précédemment lors de la création de compte.
## This script performs only the Enable for Skype for Business step on an account. It should only be run if this step failed in SHAccountCreate and the other steps have been completed ##
# EnableSfb.ps1
$Error.Clear()
$ErrorActionPreference = "Stop"
# Cleans up set state such as remote powershell sessions
function Cleanup()
{
if ($sessCS)
{
Remove-PSSession $sessCS
}
}
function PrintError($strMsg)
{
Write-Host $strMsg -foregroundcolor "red"
}
function PrintSuccess($strMsg)
{
Write-Host $strMsg -foregroundcolor "green"
}
# Cleans up and prints an error message
function CleanupAndFail($strMsg)
{
if ($strMsg)
{
PrintError($strMsg);
}
Cleanup
exit 1
}
# Exits if there is an error set and prints the given message
function ExitIfError($strMsg)
{
if ($Error)
{
CleanupAndFail($strMsg);
}
}
## Check dependencies ##
$input = Read-Host "Is the account you wish to enable part of an online environment (enter O) or on-premises environment (enter P)"
if ($input -eq "P")
{
$online = $false
}
elseif ($input -eq "O")
{
$online = $true
}
else
{
CleanupAndFail "Invalid selection"
}
if ($online)
{
try {
Import-Module SkypeOnlineConnector
}
catch
{
PrintError "Some dependencies are missing"
PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to https://www.microsoft.com/download/details.aspx?id=39366"
PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
CleanupAndFail
}
}
else
{
$strRegPool = Read-Host "Enter the FQDN of your Skype for Business Registrar Pool"
}
## Collect account data ##
Write-Host "----------- Enter info for the account to enable -----------." -foregroundcolor "magenta"
$strRoomUri=Read-Host 'Please enter the UPN of the account you are enabling (e.g. confroom@surfacehub.microsoft.com)'
if ([System.String]::IsNullOrEmpty($strRoomUri))
{
CleanupAndFail "Please enter all of the requested data to continue."
exit 1
}
Write-Host "--------------------------------------------------------------." -foregroundcolor "magenta"
## Sign in to remote powershell for exchange and lync online ##
Write-Host "`n------------------ Establishing connection -----------------." -foregroundcolor "magenta"
$credAdmin=Get-Credential -Message "Enter credentials of a Skype for Business admin"
if (!$credadmin)
{
CleanupAndFail("Valid admin credentials are required to create and prepare the account.");
}
Write-Host "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
try
{
if ($online)
{
$sessCS = New-CsOnlineSession -Credential $credAdmin
}
else
{
$sessCS = New-PSSession -Credential $credAdmin -ConnectionURI "https://$strRegPool/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
}
}
catch
{
CleanupAndFail("Failed to connect to Skype for Business server. Please check your credentials and try again. Error message: $_")
}
Import-PSSession $sessCS -AllowClobber
Write-Host "--------------------------------------------------------------." -foregroundcolor "magenta"
# Getting registrar pool
if ($online)
{
try {
$strRegPool = $null;
$strRegPool = (Get-CsTenant).RegistrarPool
} catch {}
if ($Error)
{
$Error.Clear();
$strRegPool = "";
Write-Host "We failed to lookup your Skype for Business Registrar Pool, but you can still enter it manually"
}
else
{
$strRegPool = $strRegPool[0].Substring($strRegPool[0].IndexOf(':') + 1)
}
}
$Error.Clear()
try {
Enable-CsMeetingRoom -Identity $strRoomUri -RegistrarPool $strRegPool -SipAddressType EmailAddress
}
catch {}
ExitIfError("Failed to setup Skype for Business meeting room")
PrintSuccess "Successfully enabled $strRoomUri as a Skype for Business meeting room"
Cleanup
Applets de commande utiles
Création d’une stratégie ActiveSync compatible avec le Surface Hub
Un compte d’appareil configuré avec une stratégie ActiveSync compatible doit être mis en service sur l’appareil afin de permettre au Surface Hub d’utiliser les services Exchange. Voici les exigences relatives à cette stratégie :
PasswordEnabled == 0
Dans les applets de commande suivantes, $strPolicy est le nom de la stratégie ActiveSync, et $strRoomUpn l’UPN du compte d’appareil auquel vous voulez appliquer la stratégie.
Pour exécuter les applets de commande, vous devez configurer une session PowerShell distante et :
- Votre compte d’administrateur doit être de type remote-PowerShell-enabled. Ce paramètre permet à l’administrateur d’utiliser les applets de commande PowerShell nécessaires au script. (Cette autorisation peut être définie à l’aide de
set-user $admin -RemotePowerShellEnabled $true) - Votre compte d’administrateur doit disposer du rôle « Réinitialiser le mot de passe » si vous prévoyez d’exécuter les scripts de création. Ce rôle permet à l’administrateur de modifier le mot de passe du compte, ce qui est nécessaire pour le script. Le rôle Réinitialiser le mot de passe peut être activé à l’aide du Centre d’administration Exchange.
Créez la stratégie.
# Create new policy with PasswordEnabled == false
New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false –AllowNonProvisionableDevices $true
Pour appliquer la stratégie, la boîte aux lettres ne peut pas être de type Salle. Vous devez d’abord la convertir en utilisateur.
# Convert user to regular type
Set-Mailbox $strRoomUpn -Type Regular
# Set policy for account
Set-CASMailbox $strRoomUpn -ActiveSyncMailboxPolicy $strPolicy
Maintenant, il suffit de définir de nouveau le type de compte d’appareil sur Salle.
# Convert back to room mailbox
Set-Mailbox $strRoomUpn -Type Room
Autoriser les ID d’appareil pour ActiveSync
Pour autoriser un $strRoomUpn de compte, exécutez la commande suivante :
Set-CASMailbox –Identity $strRoomUpn –ActiveSyncAllowedDeviceIDs “<ID>”
Pour trouver l’ID d’un appareil, exécutez la commande suivante :
Get-ActiveSyncDevice -Mailbox $strRoomUpn
Cette commande récupère les informations d’appareil pour chaque appareil sur lequel le compte a été approvisionné, y compris la DeviceId propriété .
Accepter et refuser automatiquement les demandes de réunion
Pour qu’un compte d’appareil accepte ou refuse automatiquement les demandes de réunion en fonction de sa disponibilité, l’attribut AutomateProcessing doit être défini sur AutoAccept. Cet attribut est recommandé pour empêcher les réunions qui se chevauchent.
Set-CalendarProcessing $strRoomUpn -AutomateProcessing AutoAccept
Accepter les demandes de réunion externes
Pour qu’un compte d’appareil accepte des demandes de réunion externes (une demande de réunion issue d’un compte ne figurant pas sur le même client/domaine), le compte d’appareil doit être défini de manière à autoriser le traitement des demandes de réunion externes. Une fois défini, le compte d’appareil accepte ou refuse automatiquement les demandes de réunion provenant de comptes externes et de comptes locaux.
Remarque
Si l’attribut AutomateProcessing n’est pas défini sur AutoAccept, cette définition n’a aucun effet.
Set-CalendarProcessing $strRoomUpn -ProcessExternalMeetingMessages $true
Commentaires
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultez https://aka.ms/ContentUserFeedback.
Envoyer et afficher des commentaires pour