Polycom Trio Introduction + Setup – Creating AD, Exchange, and Lync/Skype4B accounts

Polycom Trio registers to Lync/Skype4B and provides cost effective high quality audio and video conferencing.  A setup consists of a number of parts – Polycom Trio, Visual+, and Logitech camera.  A screen with HDMI connectivity is required to display video and content.  For best effect I’ve found the screen displaying video should be placed at the end of the table so remote participants will seem to be sitting in the room with you.

What do I like best about the Trio?

  • Integration with meetings hosted on Lync/Skype4B
  • Excellent video and audio quality
  • Lync/Skype4B client to control meeting and share content
  • Schedulding and join experience
  • Simplicity

As great as the device is I have noticied a few drawbacks

  • Issue where video does not display and device requires reboot
  • Unable to enable video when joining conference using dial in numbers
  • No gallery view causes some confusion if people are used to other Polycom end points

To function the device is registered to Lync or Skype4B pool utilising the following

  • Active Directory user account
  • Exchange mailbox to provide scheduling
  • Lync/Skype4B meeting room account

Depending on the environment there may be a need to configure

  • Conference policy
  • Enterprise voice dial plan and voice policy for PSTN connectivity.
  • To easily allow anyone to share content then configure your environment to allow anyone from your organisation to be a presenter. Otherwise a meeting organiser will be required to assign presenters during the meeting.

The following powershell commands create required accounts and apply configuration.

# Following commands require Exchange powershell add in
# Create AD Account and Exchange mailbox, calendar processing, and mail tips
New-Mailbox -Name 'Polycom Trio Room' -Alias 'polycomTrio' -OrganizationalUnit 'nomoredeskphone.local/Accounts' -UserPrincipalName 'polycomTrio@nomoredeskphone.local' -SamAccountName 'polycomTrio' -FirstName '' -Initials '' -LastName '' -Room

Set-CalendarProcessing -Identity PolycomTrio -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -RemovePrivateProperty $false -DeleteSubject $false
Set-Mailbox -Identity polycomTrio@nomoredeskphone.local -MailTip "Polycom Trio Meeting Room"

# Following commands require Active Directory powershell add in
# Set meeting room account password & enable account
 Set-ADAccountPassword -Identity polycomTrio
 Enable-ADAccount -Identity polycomTrio

# Following commands require Lync powershell add in
# Enable meeting room account on Microsoft Lync
Enable-CsMeetingRoom -SipAddress "sip:polycomTrio@nomoredeskphone.local" -RegistrarPool fe01@nomoredeskphone.local -Identity PolycomTrio

# Enable for enterprise voice and assign E.164 phone number
set-csMeetingRoom polycomTrio -enterpriseVoiceEnabled $true
set-csMeetingRoom polycomTrio -lineURI "tel:+613XXXXXXXX;ext=XXXX"

# Assign enterprise voice dial plans and voice policies
grant-CsDialPlan -identity polycomTrio -policyName "Dial Plan - Australia - Victoria"
grant-csVoicePolicy -identity polycomTrio -policyName "Voice Policy - Australia - National Calls"

The next blog post shall describe how to get the Trio onto the network, signed in, additional calendar processing configuration, and scheduling and joining a video conference.

The plain text archive

Introduction
A project I am currently heavily involved with is to implement email archiving. Because email archiving can alleviate Exchange storage constraints it is a feature many mail administrators get excited about. Even more exciting is the prospect of a 3rd party offsite archive as storage and system maintenance is someone elses problem.

Problem
The project was running smoothly and the initial implementation had progressed very well.  Email was successfully journaled to the archive and end users were able to read and action content.  However some email content was only viewable as plain text and clearly this had to be resolved asap.

Only some content displayed as plaint text?  Was there a pattern?  There was and it seemed email that had been sent or received with an external recipient was able to be viewed correctly where as internal only communications were affected. There are a couple places where email may be delivered to the archive and this includes the email security gateway and Exchange journaling.  Email routing via the security gateway takes precedence over Exchange when arriving to the archive and these emails were not affected.  Something was happening within Exchange to cause plain text only email to be sent to the archive.

Symptoms
Affected emails displayed as plain text and images no longer displayed within the email and were now attachments.  Below is an example

plain text email

Troubleshooting steps
I quickly start looking through Exchange configuration in an attempt to find anything that may indicate what caused the problem.  After sifting through transport configuration, browsing logs, reviewing send and receive connectors nothing stood out.  Realising remote domains configuration also affects formatting I took a look via the management console.  Nothing specifying plain text was misconfigured.  

Next I looked through Outlook client settings even though I was confident this wouldn’t have any affect on the problem.  Still I wanted to see if i could do something that may change what I see in the archive.  No luck here.  

The focus returned to troubleshooting Exchange server and this time remote domains configuration was reviewed using Exchange management shell and this returns more detail than is viewable in the management console and it revealed what may be the root cause. 

get-remoteDomain | fl identity, domainName, contentType

plain-text-archive_01

ContentType can be configured as MimeHTMLText, MimeText, or MimeHTML.  A quick call to PS to confirmed this would need to be changed from MimeText to MimeHTMLText however I was a little hesitant to make a change during business hours and only internally journaled email was affected.  

Solution/Workaround
The solution was to create a new remote domain for journal specific email and configure the correct content type.  I had no issue implementing this change during business hours and it was performed using the following command 

new-remoteDomain -identity JournalEmail -domain journal@nomoredeskphone.com

Conclusion
When creating a new remote domain the content type is automatically set to MimeHTMLText so no further changes were required after the new journal remote domain configuration was made.  So why was default remote domain set to MimeText? Obviously a legacy setting that hasn’t changed as Exchange versions have been upgraded.  Why did this only affect journal email and nothing else?  I haven’t dug that deep yet however problem resolved and now archive content displays using the correct format.

And remember to always check configuration using the management shell as it returns more detail than the console.