• Creating a Response Group in Lync

    It’s been a while since I have been able to blog…but now TechEd is done, and we have launched Lync here in Belgium, so time to blog what I have shown in Berlin for TechEd, and during the Launch.

    First thing I want to blog about, is the enhancements that have been done to the Response Groups in Lync. The following TechNet article lists the New Response Group Application Features (http://technet.microsoft.com/en-us/library/gg398373.aspx):

    • Anonymous calls
      You can configure a response group so that agents can accept incoming calls and make outgoing calls on behalf of the response group without revealing their identity. When anonymous calling is enabled, callers cannot call agents directly unless the agent expressly offers a direct number. During an anonymous call, the agent can see that the call is anonymous. The agent can put the call on hold, make both blind and consultative transfers, and park and retrieve the call. Anonymous calls cannot start from an instant messaging (IM) or audio/video session, but the agent or the caller can add IM and video after the call is established.
      Anonymous calls do not support conferencing, application sharing, desktop sharing, file transfer, whiteboarding and data collaboration, or call recording.
    • Attendant routing method
      With the new attendant routing method, all agents who are signed into Lync Server 2010 and the Response Group application are called at the same time for every incoming call, regardless of their current presence status. With attendant routing, Microsoft Lync 2010 Attendant users who are designated as agents can see all the calls that are waiting and answer waiting calls in any order. When a call is answered, the other Microsoft Lync 2010 Attendant users no longer see the call.
    • Integrated manageability
      In Lync Server 2010, Response Group manageability is integrated with Lync Server 2010 manageability: Lync Server Management Shell cmdlets support all Response Group management tasks, and Microsoft Lync Server 2010 Control Panel supports common Response Group management tasks.
    • Caller experience improvements
      In Lync Server 2010, Response Group supports more flexible interactive voice response (IVR) configurations and prompts, such as for invalid or no response to IVR questions and messages before music on hold or queue timeouts.
    • Web service
      In Lync Server 2010, the Response Group application provides a more robust web service that supports customized agent consoles. You can use the web service to retrieve information about agents, agent group membership, agent sign-in status, call status for groups, and the response groups that support anonymous calls.

    In addition, it is now very easy to create a Response Group, be it a Hunt Group, or a real IVR one. I’ll show you the last ones in a few simple steps.

    Step 1. Create your Lync agents

    Make sure you have create some Lync users, that you can include in your Response Group. In my example, I will use my own demo account of Ilse Van Criekinge, that I want to add to a simple IVR Response Group, called Info.

    Step 2. Create your Response Group

    Use the Lync Control Panel, select Response Groups in the left pane, and click on Group. I have already created the Info Group, click on Edit to be able to select Show Details.

    IVC-0340

    I’ve chosen as Participation Policy, Informal, meaning that every agent will be a member of that group once logged in into Lync. If you set it to Formal, the user will need to check into the response group seperately, using a web interface, as I will show later on, since Ilse is a member of the Helpdesk group as well, were the Participation policy is set to Formal.

    I have chosen in my example to define a custom group of agents, but now it is also possible to use an existing email distribution list!

    IVC-0342

    Another new thing is the routing method Attendant, which means in short that all agents who are signed into Lync Server 2010 and the Response Group application are called at the same time for every incoming call, regardless of their current presence status. With attendant routing, Microsoft Lync 2010 Attendant users who are designated as agents can see all the calls that are waiting and answer waiting calls in any order. When a call is answered, the other Microsoft Lync 2010 Attendant users no longer see the call.

    IVC-0345

    Step 3. Create the Response Group Queue

    Use the Lync Control Panel to create the needed Queue..

    IVC-0346

    IVC-0347

    Step 4. Create the Workflow

    To create the workflow, you need to select the tab Workflow, and you will be guided to the Response Group Configuration Tool.

    IVC-0348

    I choose to edit the existing Interactive Response Group, called Info.

    First I need to Activate and Name the Workflow! (For those of you that have been playing around with Response Groups in OCS R2, you don’t need to create a contact anymore using command line utilities as LCSCMD and so on Smile)

    IVC-0349

    Then you can select a language, configure a welcome message, and specify your business hours.

     

    IVC-0350

    You can even specify your holidays if wanted.

    IVC-0351

    And then it’s time to configure the Interactive Voice Responses. I have chosen to create 2 valid responses (you can define up to 4), and for the second option, I defined two additional choices.

    IVC-0352

    IVC-0353

    Step 5. Check Membership of Agent Groups

    Once logged into Lync, you can easily go to Tools, Response Group Settings, and use the Lync Web portal to sign into formal agent groups, and see to which agent groups you belong. Since Info has been configured with an Informal Participation Policy, the option to clear membership is greyed out Smile

    IVC-0354

    IVC-0355

    Step 6. Time to Test

    Patrick Van Asch calls Info…

    IVC00322

    Ilse will receive the call as follows, I can see it’s a Call for Info.

    IVC-0336

    When I accept the call, this is the info provided to me…thereby I know without any word being said, that the call will probably be about a question on the product Link Smile

    IVC-0337

    Lync + Response Groups = Rocking Smile

     

    Ilse

  • Troubleshooting Lync-Exchange OWA Integration

    Received a lot of feedback on one of my previous blog posts, on how to configure Lync RC and Exchange to enable OWA as a Lync Endpoint:

    Configuring Lync RC and Exchange 2010 Sp1 to Enable OWA as a Lync Endpoint

    And it seems a lot of you are experiencing the same problem I had when configuring it, being, you log into OWA, you get presence for your own account, and the Contact List appears to be “expanding”:

     IVC-0255

    IVC-0254

    But after a while the following error message shows up: “Instant Messaging isn’t available right now. the Contact List will appear when the service becomes available”…

    IVC-0256

    Time to troubleshoot, and here are the steps to follow…

    Step 1. Start the logging tool

    Log into your Lync RC server, and launch the Lync Server Logging Tool

    IVC-0257

    And check that you want to log All Flags for the SIP Stack, and then click Start Logging.

    IVC-0258

    Step 2. Log into OWA again, and wait for the error message to appear, when the error is there, click Stop Logging

    Step 3. Download the OCS R2 Resource Kit on your Lync Management server, where you have launched the Logging tool

    For download, here’s the link: http://www.microsoft.com/downloads/en/details.aspx?familyid=9e79a236-c0df-4a72-aba6-9a9602a93ed0&displaylang=en

    Step 4. Click Analyze Log Files

    IVC-0241

    Have a close look at the given error message! In my case it clearly pointed out that the Peer “cs14ex.lync.local” was not a configured server on this network interface, which was right since I hadn’t added cs14ex.lync.local as a CsTrustedApplication yet.

    What you can check is:

    • Is the certificate used on Lync, and Exchange issued by a trusted CA for both Lync and Exchange
    • Does the certificate have the correct name, both for Lync and Exchange
    • Did you ran Enable-CSTopology after adding Exchange as a csTrustedApplication
    • Is your replication working as it should on Lync, check by using the cmdlet Get-CsManagementStoreReplicationStatus

    IVC-0259

    Good Luck!

    Ilse

  • Exchange 2010: And then there is the long awaited cmdlet Add-MailboxFolderPermission

    So many new features have been included in Exchange 2010, that it would indeed take me more than days to talk about all of these, but there are so many very nice features that you should keep in mind when thinking about Exchange 2010, and one is these is the new built-in cmdlet "Add-MailboxFolderPermission".

    What's this: Add-MailboxFolderPermission

    Looking at the description posted on TechNet this cmdlet enables you to "manage folder-level permissions for all folders within a user's mailbox",  meaning you can use this cmdlet to delegate any of the following roles to any mailbox folder for any mailbox-enabled user in your organization, given you have sufficient permissions :-)

    (Source = Add-MailboxFolderPermission)

    • ReadItems   The user has the right to read items within the specified folder.
    • CreateItems   The user has the right to create items within the specified folder.
    • EditOwnedItems   The user has the right to edit the items that the user owns in the specified folder.
    • DeleteOwnedItems   The user has the right to delete items that the user owns in the specified folder.
    • EditAllItems   The user has the right to edit all items in the specified folder.
    • DeleteAllItems   The user has the right to delete all items in the specified folder.
    • CreateSubfolders   The user has the right to create subfolders in the specified folder.
    • FolderOwner   The user is the owner of the specified folder. The user has the right to view and move the folder and create subfolders. The user can't read items, edit items, delete items, or create items.
    • FolderContact   The user is the contact for the specified public folder.
    • FolderVisible   The user can view the specified folder, but can't read or edit items within the specified public folder.

    The AccessRights parameter also specifies the permissions for the user with the following roles, which are a combination of the rights listed previously:

    • None   FolderVisible
    • Owner   CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
    • PublishingEditor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
    • Editor   CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
    • PublishingAuthor   CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
    • Author   CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
    • NonEditingAuthor   CreateItems, ReadItems, FolderVisible
    • Reviewer   ReadItems, FolderVisible
    • Contributor   CreateItems, FolderVisible

    The following roles apply specifically to calendar folders:

    • AvailabilityOnly   View only availability data
    • LimitedDetails   View availability data with subject and location

    The permissions you need in order to be able to do so, are any of the followin built-in management roles (as stated here), there is no need to have been granted full mailbox access prior to being able to change those folder permissions (!): Organization Management, Recipient Management, Help Desk.

    Let's have a look at an example. Here are the permission settings for my test mailbox Ilse, and as you can see, these are the default settings, without previous changes:

    Can we get this information using the power of the (Remote) Exchange Management Shell? Yes, by using the cmdlet Get-MailboxFolderPermission, as can be seen in the example below, when running Get-MailboxFolderPermission ilsevancriekinge@exchange.local:\Calendar

    And then we can run the following cmdlet to add User7 with the permission of Editor:

    Add-MailboxFolderPermission -Identity ilsevancriekinge@exchange.local :\Calendar -User user7@exchange.local -AccessRights editor

    And when checking with Microsoft Office Outlook, it's clear the permissions have been set:

    -Ilse

  • Add an Alias to a Distribution Group in Exchange Online (Office365), and Removing one...

    Looking back to BPOS, the only way to add an alias to a distribution group, was by using DirSync, as described here:

    http://social.technet.microsoft.com/Forums/ar/onlineservicesexchange/thread/0dab060f-41a2-4ef2-926d-8b6e0b2464c8

    With the arrival of Office365, and Exchange Online, time to see if it is possible now to have one distribution group with multiple email aliasses, even without using DirSync.

    Goal = have a distribution group, with 3 email addresses: Sales@sir.onmicrosoft.com,Sales@vancriekinge.be, and info@sir.onmicrosoft.com

    First I will create the new distribution group, using the Exchange Control Panel. I sign into OWA, and from there click on Options, and select to manage My Organization, and from there I create a new distribution group called Sales:

    SNAG-00458

     

    SNAG-00459

    Now time to add the two other addresses…

    Option 1. Use the Exchange Control Panel

    SNAG-00460

    When selecting the distribution group Sales, and clicking on Details, I can see there is currently one e-mail address, and no Add button:

     

    SNAG-00461

    But when going to the General options, I can see that I can change the e-mailaddress of the group, and that the existing addresses will be kept!

    SNAG-00462

    So I enter Info in the E-Mail address, and press Save:

    SNAG-00463

    When checking the E-Mail Options, I can see there are now two e-mail addresses for my distribution group:

    SNAG-00465

    But no option to remove any of these…

    Option 2. Using the Exchange Management Shell

    Easy Smile After connecting to Exchange Online, I will use a variable to add the e-mail address of info@vancriekinge.be to the distribution group.

    PS C:\Users\ilse> $sales = Get-DistributionGroup sales
    PS C:\Users\ilse> $sales.EmailAddresses
    SMTP:Info@Sir.onmicrosoft.com
    smtp:Sales@Sir.onmicrosoft.com
    PS C:\Users\ilse> $sales.EmailAddresses += "sales@vancriekinge.be"
    PS C:\Users\ilse> $sales.EmailAddresses
    SMTP:Info@Sir.onmicrosoft.com
    smtp:Sales@Sir.onmicrosoft.com
    sales@vancriekinge.be
    PS C:\Users\ilse> Set-DistributionGroup -Identity Sales -EmailAddresses $sales.EmailAddresses
    PS C:\Users\ilse> Get-DistributionGroup sales

    Name                    DisplayName             GroupType               PrimarySmtpAddress
    ----                    -----------             ---------               ------------------
    Sales                   Sales                   Universal               Info@Sir.onmicrosof...


    PS C:\Users\ilse> Get-DistributionGroup sales | fl *emailad*

    EmailAddresses            : {smtp:sales@vancriekinge.be, SMTP:Info@Sir.onmicrosoft.com, smtp:Sales@Sir.onmicrosoft.com}
    EmailAddressPolicyEnabled : False
    WindowsEmailAddress       : Info@Sir.onmicrosoft.com

    Check via ECP, and it’s done Smile

    SNAG-00467

    Using the Shell, it’s different to remove an e-mail address:

    PS C:\Users\ilvancri> Get-DistributionGroup sales | fl *emailad*

    EmailAddresses            : {smtp:sales@vancriekinge.be, SMTP:Info@Sir.onmicrosoft.com, smtp:Sales@Sir.onmicrosoft.com}
    EmailAddressPolicyEnabled : False
    WindowsEmailAddress       : Info@Sir.onmicrosoft.com

    PS C:\Users\ilvancri> Set-DistributionGroup -Identity Sales -EmailAddresses 'smtp:sales@sir.onmicrosoft.com','SMTP:info@sir.onmicrosoft.com'
    PS C:\Users\ilvancri> Get-DistributionGroup sales | fl *emailad*

    EmailAddresses            : {SMTP:info@sir.onmicrosoft.com, smtp:sales@sir.onmicrosoft.com}
    EmailAddressPolicyEnabled : False
    WindowsEmailAddress       : Info@Sir.onmicrosoft.com

    A check in ECP reveals the e-mail address sales@vancriekinge.be is gone…

    SNAG-00468

    Option 3. Using the Exchange Management Console

    As blogged before (http://blogs.technet.com/b/ilvancri/archive/2011/10/14/exchange-online-change-primary-smtp-address-without-changing-sign-in-address.aspx) it is possible to install the Exchange Management Console, and use it to connect to your Exchange Online environment, even if you do not have a Hybrid setup with an Exchange On Premises.

    Using the Exchange Management Console, you can go to the properties of your distribution group, and add/remove e-mail addresses as you need:

    SNAG-00469

     

    SNAG-00470

     

    Exchange rocks!

    Ilse

  • sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile

    A while ago I got a question from someone regarding one of the new features in Exchange 2010, being text messaging. Question was “is it available”…

    Looking at the TechNet article he referred to, it does state:

    Source = http://technet.microsoft.com/en-us/library/dd298136.aspx

    The following is a list of new text messaging features included in Exchange 2010:

    • Missed call and voice mail notifications
    • Calendar and agenda updates
    • Text messages sent and received through Outlook Web App and Outlook 2010
    • Text message synchronization with a mobile phone

    So let’s see.

    Requirements

    You need to have a Windows Mobile device:

    And once you have chosen to sync your text messages, you will see all messages sent and received appear in your inbox, like below:

    Pic0255

    You will also receive an email, notifying you that you are able to send SMS/text messages using OWA/Outlook from now on:

     Pic0252

    What can you do?

    • Send an reply to text messages just as you would e-mail messages

    Pic0251

    • When entering more than 160 characters, an additional SMS text message will be created
    • Messages can be sent to a phone number or to a contact which phone number is filled in
    • Messages on the mobile device are synced and backed up on the server
    • Messages on the device only show up in the text messaging area (not in Outlook Mobile)

    How does it work?

    When a text (sms) message is created using Outlook/OWA, it will be sent to Exchange.  Exchange will use EAS to send/sync the message to the users cell phone. The user’s cell phone will then send that message out over SMS.

    When a user receives a text message, the sent message will be synced to the user’s mailbox using EAS.

     

    Some Q & A

    Q. What if I have more than one SMS Sync enabled phones connected to an account?

    A. The most recently connected one will  be the one used to send the message

     

    Q. Can I disable this feature as an administrator?

    A. Yes, you can, using the Exchange Management Shell for example

     Pic0256

    Pic0258

    Pic0257

    Happy SMS/Text Messaging :-)

     

    Ilse