Follow the below steps to setup an 'All Rooms' distribution list to enable connection between Evoko Naso and your room resources.
Note: You do not need to follow this step if you already have a global 'All Rooms' distribution list for your room resources.
Step 1: Set Execution Policy
Open a new PowerShell session in Administration mode and run the following command:
PS C:\WINDOWS\system32> Set-ExecutionPolicy RemoteSigned
Results
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
http://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
Step 2: Confirm Execution Policy
A response is required to the Exchange Execution Policy. Enter Y
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): Y
Step 3: Authenticate
Once the exchange policy execution is complete, run the following command:
PS C:\WINDOWS\system32> $UserCredential = Get-Credential
Results
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
A pop-up will display requesting authentication. Enter your administrator username and password.
Step 4: Start new session
Once your credentials are validated, run the following command:
PS C:\WINDOWS\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Step 5: Import commands
Now run the following command:
PS C:\WINDOWS\system32> Import-PSSession $Session
Results
WARNING: The names of some imported commands from the module 'tmp_uhj2eecg.u10' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, runthe Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Step 6: Create distribution group
You now need to create your 'All Rooms' distribution group. Run the following command:
PS C:\WINDOWS\system32> New-DistributionGroup -Name "AllRooms" -OrganizationalUnit "company.onmicrosoft.com" -RoomList
Note: You must replace "company.onmicrosoft.com' domain with your domain.
Results
New! Office 365 Groups are the next generation of distribution lists.
Groups give teams shared tools for collaborating using email, files, a calendar, and more.
You can start right away using the New-UnifiedGroup cmdlet.
Name DisplayName GroupType PrimarySmtpAddress
---- ----------- --------- ------------------
Step 7: Confirm group created
Now check to make sure you setup your distribution list correctly. Run the following command:
PS C:\WINDOWS\system32> Get-DistributionGroup
Your new distribution group 'All Rooms' should be displayed in the list of results.
Step 8: Add members to group
Now you need to add the member to the group. Run the following command:
PS C:\WINDOWS\system32> Add-DistributionGroupMember -Identity "AllRooms" -Member [room.name.here]@company.onmicrosoft.com
Note: You must replace "company.onmicrosoft.com' domain with your domain and replace [room.name.here] with the name of the room you would like to add to the distribution list.
Step 9: Confirm group membership
Check your group membership. Run the following command:
PS C:\WINDOWS\system32> Get-DistributionGroupMember AllRooms
Results
cmdlet Get-DistributionGroupMember at command pipeline position 1
Supply values for the following parameters:
Identity: All rooms
Name RecipientType
---- -------------
Step 10: Wait for synchronization
Now that you have completed setup of your distribution group, wait overnight for account synchronization.