Tuesday, 31 October 2017

Would you use the Microsoft Teams client for telephony?

Hello readers.  Nice to see you.  Hope you're well.

This is just a quick opinion piece to elicit some debate.

Given that Microsoft has announced that all of the features of Skype for Business Online in Office 365, including telephony features of Phone System (formerly Cloud PBX) and Audio Conferencing, are coming to Teams.  I ask, would you use the Teams client for telephony if you could?


The answer for me is less simple since I use Skype for Business Server on-premises.  But the question still stands.

I really like the simplicity of the Skype for Business client.  There isn't much to look at in the client itself.  Unless you have Persistent Chat, there's no reason to stay in the Skype for Business client for very long.  It's an application you go to to start a communication.  

Once you do start a dialogue, the conversation window pops out of the client as a self contained entity.  The conversation window has all of the buttons for controlling or changing that single conversation.  Start with IM and escalate as you see fit, adding voice, video, people and content with the click of the mouse.

Since the conversation window floats above the client, I'm free to go back to the client and start a new, separate conversation and put the two side by side if I wish.  One with voice and video and the other with IM only.  

If I turn off tabbed conversations I can fill my screen with conversations in tiles if I want.

Teams, by comparison, is containerised.  Everything happens inside the application rather than floating above it in a separate conversation window.  You can still initiate a chat and escalate to voice/video, add people and share your screen in that conversation, but if you want to have another conversation at the same time, you have to click away from the first one and into another one.  

Teams does currently have a nice little party piece in that if you do click away from a voice/video call, you get a little peek window at the top showing the video for the active speaker with call controls floating over the top.

This happens in peer-to-peer and multi-party calls and in scheduled or ad-hoc meetings.  You still have to be in Teams to see it though.  If you switch apps, you can't see anything.

In Skype for Business, the call peek is floating free and independent of Skype for Business in general.  If you switch apps and go to Outlook during a video call, you get a call peek which floats above Outlook.  You can even move it wherever you want.

In Teams, the only way to get a floating peek is to share your screen in a meeting or call.

All little things I realise, but they do add up to a lot.  I've been using the Skype for Business client since I was able to get it.  Before that I used the Lync 2013 client (on Lync 2010 and 2013 back end), and before that the Lync 2010 client, and before that I used the OCS client and before that LCS and before that, Messenger.  

So I'm going on 17 years in this product line.  When Microsoft add something (consult Transfer in SfB client) I notice it, when they take away something (Consult transfer which was in OCS client and not in the Lync clients), I notice that too.

I'm more than a user of the product, but I am a user nonetheless.  Change is difficult.

Microsoft is saying to start using Teams alongside Skype for Business to get used to it.  The roadmap is out now and its clear that they have a rough timeline for feature migration.  Below is the calling roadmap which goes to the end of Q4 2018.  

Things slip in roadmaps though, so don't hold your breath.

Back to the original question.  

Would I use Teams as my telephony client?  Like I said, I'm on a Skype for Business Server back end, so my Skype for Business client has all of the features.  More, even, than Skype for Business Online with Phone System.  So I don't have to wait for 14 months for feature parity and I get to use a client I'm used to.  So for right now, the answer is no.

Fast forward 14 months and Teams has feature parity with Skype Online and Phone System.  I know I'll probably still have a Skype for Business Server back end, although probably SfB Server 2019.  I would imagine there will still be differences between the products, but I don't know for sure.  

Differences aside, though, I would probably still edge toward no.  I would still miss the simplicity of the Skype for Business client for all the reasons listed above.  I'd probably be fine using both.

What do you think?  Would you use Teams for everything if you could?  Leave a comment here or hit me up on Twitter or LinkedIn.

That's all folks.
_________________________________________________________________________

I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome. 

Wednesday, 18 October 2017

What is Microsoft Teams?

Hello readers.  Hope you're well.

I've had this as a draft post since February this year.  I've been adding to it here and there as the product has evolved.  And with recent announcements, now seems like a good time to finally publish it.  

What I want to do is give you my take on what Teams is, what it does, how it is/could be used, who will/should use it and how to get it.  Enjoy.

What is Teams?


Teams is a fairly new, out of the blue, platform delivered through Office 365.  I call it a platform rather than an application because, really, Teams is just a jumping off point to get to other systems.  It is an aggregator of communication and collaboration tools and information in a single pane of glass.  It is a work space where you can put everything you need to work with and as a team.  Then once the information is there, you can easily collaborate with team members about that information. 

A New Vision for Communications and Collaboration

Microsoft has a new vision for communications and collaboration that they call Intelligent Communications.  Intelligent Communications is using the full set of capabilities and power of a joined-up platform to surface new, smarter ways of communicating and collaborating.  It is no longer about peer to peer or multi-party single or multi-media communications.  

Instant messaging and peer-to-peer audio/video is communication.  When you add more people and content to the conversation, it becomes collaboration.  Teams takes this concept of collaboration, several steps further.

With more capability at your disposal, collaboration can be more contextual.  Intelligent Communications are about making each interaction or communication be about something specific.  

In Skype for Business right now, I can initiate an IM or a Call with someone, but I have to explain what the context is before continuing with the interaction.  For instance, I want to know about X.  I can take that a step further and apply a little bit of context by initiating the interaction from a connected app such as Outlook.  If I start an IM by hovering over a person in an email, the new IM has the subject of that email at the top.  It’s a nice try, but it is still easy to miss unless you know to look. 

With the right power in your hand, you can start the interaction from the context and make it blatantly obvious what the interaction is about.  If you start from the context, you can unlock something that has the potential to be useful.  Everyone that has access to that context can see the interactions and if they have something to contribute, they can join in to the conversation.  If the person you start with knows someone that knows more, they can mention the correct person and invite them to join the conversation.  

This also goes beyond simple interactions.  In addition to starting a chat or making a call from the context, ithere are documents involved, it is possible to make that the context.  Taking it one or two steps further, you can co-author and chat about the document in line with the context.  

Then if you want to schedule a meeting about the content, and the application suggests the attendees you want in the meeting based on recent conversations.  

If all of that sounds like science fiction, it really isn’t.  

What can you do with Teams?

Chat

Teams is an internal only peer-to-peer and multi-party Instant Messaging (IM), audio and video communications tool.  You can start an ad-hoc chat with anyone in your organisation that is using Teams or Skype for Business Online.  Chat doesn’t currently work between Teams and Skype for Business Server on-premises.  Nor does it work with federated users.  I gather these are both coming.  There is, however, Guest Access and I'll talk about that further down.  

To start a chat, tap the chat icon which is on every page right next to the search bar.
You can start a chat with someone whether or not they are online.  If they are offline, the message will be waiting for them when they log in.  A chat starts as an Instant Message (IM) and you can escalate to an audio or video call.  

The chat interface is really quite good.  The compose box can be maximised to uncover additional formatting options for the text within the chat.  

You can do typical things like bold, underline and italics, as well as more advanced things like bullet points and numbered lists.  It's even possible to highlight text to draw attention to something.  Additionally, you can add headings and subheadings, an indented quote and even code snippets.  

It is possible add files to a chat (either from your computer hard drive or your personal OneDrive for Business).  When you upload a file to a Chat, it is stored in a OneDrive for Business folder called Microsoft Teams Chat Files and shared with the person/people in the chat thread.  You can get to the files you upload in the dedicated Files area as well as within the chat.  

The files list gives you the file type, name, when it was last modified and the location (such as OneDrive or the team and channel name.  It is also possible to edit and co-author Office documents, either in Teams, from Office Online or Office which is locally installed.  

Editing directly in Teams is a really great experience.  It opens Office Online right in the Teams interface and moves the chat pane to the right of the document so you can chat while you edit.

In addition to files and text in chats, you can also add Emoji 😏, Gif's (Powered by Giphy), as well as Stickers and Memes from a huge list which is broken down into categories.


You also have the ability to personalise the chat space in Teams with extra stuff that's relevant to you and the person/people you are chatting with.  In addition to conversations and files, there is an organisation tab which shows you where they sit in your company organisation chart.  There's also an Activity tab that shows you what else they have been doing in Teams.  It's also possible to add tabs to chats.  

This is currently limited to Power BI and a web page, but I would imagine this list will grow over time.

A chat can be peer to peer or multi-party.  The chats are persistent over time, meaning they stay in the client so you can refer back to it.  Chats in Teams are done outside of Teams and Channels.  Although it is possible to have a conversation within a Channel, it isn't strictly a chat, but rather persistent, threaded conversations with all of the members of the team.  Think of chat as persistent, instant messaging with bells and whistles.

Activity Feed

The activity feed area is a list view of what's been going on in Teams.  The list includes messages, mentions, replies to conversations you've been in, likes and stuff from people or channels you follow.  The activity feed is a really quick way to move between things you might want to reply to or just read without having to go into Teams and look through channels to find stuff.  Clicking on an activity takes you right to the channel or place where the activity took place and you can interact from there.  The activity feed can be filtered to find just the stuff you want to see.  You can also search in Teams, more on that in a sec.

Search
Within every menu item there is a search bar.  
You can search for a keyword or a phrase and you'll get a list of every conversation you have access to where the term is used.  When you click into one of the results, it displays only the message with the term you searched for, along with a link to take you to the channel where the conversation took place, so you can interact if you want.  Search is completely necessary since Teams has the potential to gather vast amounts of data all over the place.

Teams in Teams


Creating a Team in Teams creates a few things on the back end.  Firstly, it creates a site in SharePoint Online for the content including files.  It then creates an Office 365 Group and a OneNote notebook.  Once you have created a Team, you add members.  You can add members from within your company and guests from outside your company.  At the time of writing, you can only add a guest that uses Azure AD and Office 365, basically, anyone with an Exchange Online mailbox and email address.  Microsoft is expanding this to include users with an MPN (msn, hotmail or outlook.com) address.  

When you add a member to a team, it sends the user a notification by email.  If the member already uses Teams, it will just give them access to the Team.  The Team and any channels will appear in the Teams area of the Teams client or site.  If they don’t use Teams it will send them a link to the Teams web client (https://teams.microsoft.com) which will prompt for credentials and then invite them to download the full client.  Once you have a Team and members (although you don’t need any members) you can add content to customise the work space.

Now for some terminology.  

A Channel is a subfolder within the Team.  
A Channel can have a Conversation repository, a file repository, a OneNote notebook, a Wiki page and Tabs.  

A Tab is basically an interface into an application, a web page or a document you need to frequently access.  There a fairly big list of tab types and applications including Office 365 apps like Planner, Power BI, Word and Excel, and apps from external service providers like Wrike, Youtube and Trello, to name but a few.

In addition to all of this, a Channel can link to external services using Connectors.  There’s a huge list of Connectors available from a ton of companies.  Anything from Twitter, or RSS feeds to Salesforce and a lot more.

A conversation within a Team is a lot like Persistent Chat in SfB.  Each conversation is specific to a Channel within the Team.  A Conversation in a Channel is an inline multi-threaded chat and anyone that is a member of the Team can read and contribute.  A user can reply to an existing thread to continue a conversation or start a new thread to start a completely new conversation.  A conversation thread can also be given a subject.  As with Chat, text can be customized and formatted with options for bullet, list, size, colour and style (bold, underline and italics).  Text can also be highlighted.  In addition to text, a user can add Emoji, Gif's and customizable Memes from a large repository in Teams, as well as images from their own source (png and jpg).  This will keep the millennials entertained.  

With the correct permissions, it is possible to delete a comment or an entire conversation from within a Channel.  If something is deleted, it says that it has been deleted and has an Undo link next to it.  Anything that is deleted in Teams (files, conversations and comments) go to a recycle bin in the Team SharePoint site.  It is also possible for a user to edit a comment they made within the Team if, for instance, they made a typo or said something they wanted to change.  Once text has been edited, it says Edited next to it.  

It is also possible to save a conversation or a comment which pins them to a save items list.  It is also possible to un-save something.  

For fans of social media (Twitter, Facebook, LinkedIn), it has a “Like” function that increments up with the likes and collects a list of who liked it.  

In addition to text, Emoji and memes, a user can add a file to a conversation.  There are also @ mentions.  You can mention someone in a conversation and they will be notified that you mentioned them and send a link back to the conversation (as long as they have access to it).  This is similar to the Ego feed in Persistent Chat in Lync and Skype for Business.  You can also @ mention specific Teams and Channels.  Once you type the @, the next letter will start to search for valid target.  Keep in mind that you can only @ mention teams, channels and members of the team you're in.  i.e. If you're in a conversation in a Channel called New Business in the Sales team and the only members besides you are Ted, Ralph and Sally, you can only @ mention Sales, New Business, Ted, Ralph and Sally.  You can't @ mention across teams or to people that don't have access to the Team.

In every Channel in a Team, there is a Files tab.  Files can be uploaded from your own OneDrive for Business drive or your own PC as standard.  However you can also add Cloud Storage sources.  

This is really just a connector that links the Channel to a cloud storage provider.  Once you have added the provider, it will add a folder to the Channel.  As it says in the popup (see below), once you add a cloud storage provider, everyone with access to the Team will have access to the files.

When you click on one of the providers, you'll be asked to authenticate and grant Teams access to the provider.

Once a file is added to a conversation it uploads it to the file store within the Channel and Team, which is SharePoint Online on the back end.  Once there it can be edited in Office, Office online or directly in Teams.  It can also be co-authored if the user clicks Share and invites someone.  Files can be downloaded, edited, copied, moved between Channels (within the same Team only) or deleted (again to the recycle bin).  

It is also possible to make a file a Tab within the Team.  The file Tab is basically an opened version of the file.  For instance, a price list.  It is also possible to click edit on a file to make changes.  This edits the underlying file (in SharePoint) and displays the changes in the tab once it has been saved. 

There is a Notes tab which is a OneNote notebook where users in the Team can build up notes and pages relevant to the Channel.  This is also saved in SharePoint.

Last, but not least, you can add Connectors to a channel. 

A Connector is used to bring external services into a Channel or Team.  There are connectors from Microsoft, of course, for services like Visual Studio Team Services, Dynamics 365 and Yammer as well as 3rd party services like Trello, Salesforce, Wunderlist and Twitter to name a few.  In fact, there are dozens of Connectors.  So many, in fact, you can filter by category to make it easy to find what you're after.

Meetings
Meetings in Teams is a lot like meetings in Skype for Business.  It has it's own tab and links to your Exchange calendar, showing you all of your meetings for the day whether they are Teams meetings, Skype for Business meetings, or just appointments.  

You can schedule meetings from Teams 

or using the new Outlook button.  

It the meeting is a Teams meeting, you can join and attend the meeting, in Teams.  If the meeting is a Skype for Business meeting, you still get a join button in Teams, however, the join button starts the meeting in the Skype for Business client rather than directly in Teams.

Meeting in Teams is quite an experience.  For a start, you get a full screen, 2 x 2 gallery view if you add video.  When I say full screen, I mean full bleed, full screen.  The meeting controls are hidden by default and appear, over the video feed when you move the mouse to the area.  This is very much like Skype for Business on a Mac.
  
This is a stark contrast to the 5 in a row gallery view for a Skype for Business meeting.  

There is also a dedicated device button in the meeting and you can switch devices (audio and video) on the fly.  

You can switch audio devices mid call in Skype for Business, however, not video.  You can switch video if you go in to video settings and change the default device.  Once you switch and click OK, video stops, you then have to start video again.

In Teams, you can switch using the Cameras drop down list to choose another device and it switches live, during the call.  There is also a dedicated camera switching button.

Pressing this button switches the video to the next device in the list.  This is great if you have cameras set up to focus on the meeting ahead of time.  

Camera 1, Camera 2, Camera 1, Camera 2.  

Not so good if you're using a laptop in a docking station and you have front and rear cameras AND connected USB cameras.  Would be nice if you could select the cameras not to use.

Alongside the full screen video, you can chat with the attendees.  You get all the same chat options including formatting, Gif's, stickers and memes.  

You can also attach a file to the chat.  Attendees can open the file online (in a browser, not in the meeting) or download.  

Unfortunately, the only presenter option is screen sharing for now.  I can imagine this will get better over time.  

I'd love there to be a revamped whiteboard app in Teams meetings.  Perhaps the one from the updated Surface Hub.  We'd also need the ability to present PowerPoint and do Q&A and Polls.  These will probably come with federation, if they come at all.

When you share in a Teams meeting, the Teams the interface minimises and you're left with the call progress box along with the call controls.

Meetings are set to get even better in Teams with features like Cloud Record.  Users can attend meetings after the meeting finishes and it plays the whole meeting back as though they were there live.

Workspace of the Future

As you can see, a Team site really can be a workplace for any sized team.  Every possible piece of information that is relevant to the team can be added to the workspace.  Whether it is files, notes or conversations and external services through connectors.  Microsoft call it a Hub for Teamwork.

In a recent conversation I had with Microsoft, they called it an over engineered Persistent Chat role for Skype for Business Online.  The community was asking for Persistent Chat in Office 365, apparently, and they decided to deliver it.  I’m guessing that they also thought of it as an opportunity to compete with Slack intentionally, and Spark by chance. 

Slack came along and took an underdeveloped Persistent Chat role and made it connect with everything.  They gave it away to get users hooked and then started charging for premium features.  Don’t ask me what they are, because I’ve never even been to the Slack website, much less used it.  From what I have seen of Spark, Cisco did the same thing.  They decided that persistent chat and collaboration is the future.  I'm paraphrasing here, but recently Rowan Trollope said that Instant Messaging (IM) is just about getting attention rather than getting information. 

Who could use Teams?

Anyone that works with one or more people in a company and needs to be able to access information and collaborate about it. I can see it being used by Sales, Marketing, Project Management, Engineering or Support, among others. 

I have a Team with no members that I use to quickly get to stuff I need to access frequently.  This includes documents, RSS feeds, a Twitter tab, a few web pages and a couple of YouTube channels.  And that works fine for me.

Crossover with other applications

The most obvious crossover is with Skype for Business.  In Teams, you can do one to one and multi-party instant messaging (Chat), Persistent Chat (conversations in channels), internal voice and video calls, screen sharing and meetings.

You'll have heard some recent announcements that Microsoft is further enhancing Teams by adding the features and functionality of Skype for Business Online, Phone System (formerly Cloud PBX) and Audio Conferencing (formerly PSTN Conferencing) into Teams.  The plan will be to allow companies to run Teams and Skype for Business Online side-by-side for a period of time and eventually get rid of Skype for Business Online.  A controversial topic to be sure.  One for another day.

I've seen a couple of posts recently (One by Richard Bryteson and another by Tom Arbuthnotwhere they suggest disabling features that are also in Skype for Business, such as chat, calling and meetings.  This would ostensibly force users to carry on using Skype for Business for those features rather than have two places for the same thing.  

One advantage of this is that if your company is using archiving in Skype for Business for IM's, that stays as it is until there is shared archiving for Skype and Teams.

Personally, I like having the choice to decide what I use.  What do you think?

What about Skype for Business Server and Teams?

There are plans to enhance the interop between Teams and Skype for Business Server, however, we don't yet know to what extent.  The possibilities are quite exciting, especially in a hybrid scenario.  

I'd love the ability to use the Teams client as the interface for Skype for Business Server.  Chats in Teams could be the interface for Skype for Business IM's going forward.  Same with calling.  The calls tab in Teams could just leverage the calling capability from your Skype for Business Server deployment.  

Most importantly, I'd love to have the choice of which client to use and if possible, use both at the same time.  For instance, if I'm in a meeting with an external party in Teams, I'd like the ability to have a private chat window open in Skype for Business so I could chat privately with someone about the meeting, or even to answer an incoming question from someone else.  I can do that currently in Skype for Business.  If I only used the Teams client and I wanted to chat, I'd have to click away from the meetings tab and into the chat tab to have a conversation, taking my focus completely off the meeting.

Time will tell, but if I had to bet, the interop will come with Skype for Business Server 2019 late next year.

How do you get Teams?

Teams is available exclusively in Microsoft Office 365 and is included as standard with Office 365 Business Premium and Business Essentials, Enterprise plans E1, E3 and E5 as well as Education, Government, Not for Profit and new Firstline Worker plans.

In conclusion

The more I use Teams, the more I like it.  I wouldn't go as far as to say I could use it instead of Skype for Business.  It is missing a lot right now.  That list will shrink over time, surely, but right now it just doesn't cut it.  I also like Skype for Business for its simplicity.  I guess we'll see what happens.


That's all folks.

_________________________________________________________________________


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.  

Wednesday, 20 September 2017

New name for Skype for Business Online/Teams?

Hello Readers.  Hope you're well.

A really quick one today.

I was having a look around the Azure AD portal in my Office 365 tenant and found a section for Enterprise Applications and Microsoft Teams was listed.  In there, I found Provisioning and a provisioning mode which has a drop down list with a single option of Manual.

The interesting thing is the nomenclature they use for the product.  Something I haven't seen before.  But given the recent slip up that told the world that Skype was being replaced by Teams, I am not surprised.

Here's a screenshot of the page.

As you can see, they refer to the product as Skype Team Services.  Is this the new name for the mashup of Skype for Business Online and Teams in Office 365?  I guess we'll find out in the next few days.

If you have seen this or similar in Office 365, leave a comment and feel free to reach out.

That's all folks.

____________________________________________________________________________________


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.  

Tuesday, 19 September 2017

How to change the display name of a guest in Microsoft Teams

Hello Readers.  Hope you're well.

Another quick post.

Microsoft has enabled external Guest access in Teams.  And I know you've all been frantically adding guests to your teams.  

I'm a guest in a couple of teams of like-minded individuals.  One of the biggest complaints is the display name.  When you add a guest to a team in Teams, the display name is the alias of the User Principal Name (UPN) by default.  

I explain in a previous blog post that it is possible to specify the display name before the invite goes out.  In this post I'll go through the ways you can change the display name of your guests after the invite goes out and they've already accessed your team.

There are two ways to do this.  I'll start with the quickest and easiest.  PowerShell.

First, you need the pre-requisites for connecting to Azure AD in PowerShell.

1. You need the Microsoft Online Services Sign-In Assistant for IT Professionals RTW.  Download the version you want and install.

2. Next, you need the Azure Active Directory PowerShell Module.  Download the .msi file, and click Run to run the installer package.

Change the display name of a guest using PowerShell

1. First, open PowerShell as an Administrator

2. Now type Connect-MsolService and enter your admin credentials when prompted.


3. Now enter Get-MsolUser -All | where {$_.UserType -eq "Guest"} to see a list of your guests.


If you know the UPN of the guest you want to display you can do a search:
Get-MsolUser -SearchString "randy.chapman"

4. To change the display name you can simply copy the UserPrincipalName from the results above and run the following command: 
Set-MsolUser -UserPrincipalName first.last_guestdomain.com#EXT#@yourdomain.com -DisplayName "First Last (Company)"
You also have a some more options here to make it a little easier.

You can assign a variable to use in the Set-MsolUser command.
$guest = Get-MsolUser -SearchString "randy.chapman" | select -expandproperty UserPrincipalName

Then you can insert the variable to make the change.
Set-MsolUser -UserPrincipalName $guest -DisplayName "Randy Changed"

Now if you look up the user you changed, you'll see the new display name is shown.

In addition to the Display Name, you can also set loads of other parameters such as FirstName, LastName, Title, PhoneNumber and various address fields.  All good, but your users won't see that info in Teams anyway.  

Remove or disable a guest in PowerShell

You can also use PowerShell to remove a guest or disable them without removing them.

To remove, enter: 
Remove-MsolUser -UserPrincipalName first.last_guestdomain.com#EXT#@yourdomain.com
To disable without removing, enter: 
Set-MsolUser -UserPrincipalName first.last_guestdomain.com#EXT#@yourdomain.com -BlockCredential $True
This is the PowerShell Equivalent of the Block Sign In, in the Azure AD admin portal.


As I said at the beginning of the post, there is another way to do this and that is in the Azure AD admin portal.

Change the display name of a guest in the Azure AD Admin portal

1. First, Sign in to Office 365 Admin portal at https://portal.office.com/adminportal/home.

2. Click on the Admin Tile


3. Scroll Down and expand Admin Centres and click on Azure AD

4. Now click on Users and Groups -> All Users -> click on the user you want to edit 

5. Click on Profile 


6. Enter the new Display Name in the Name field and click Save

You can change multiple settings and even set a photo.  Again, none of this will be visible in Teams, so I wouldn't bother.

Some important notes

I discovered that if you set a First Name and Last name, that is displayed in Teams rather than the DisplayName.

You won't see the guest user display name changes until you completely log out of Teams and then log back in.  Switching teams isn't enough.

That's all folks.

____________________________________________________________________________________


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.