At my earlier post on Setting-Up Lync Room System from scratch, I’d mis-configured the display settings on Primary & Secondary Monitor, causing that I wasn’t able to use the Touch/Interactive Flat Panel seamlessly. In the end, I gave up by using the option – Factory Reset which took another 30 minutes to re-flash the LRS Operating System and another 1 Hour+ to reconfigure the entire. This is when I realized there’s a better way:

  1. Temporarily connect a USB keyboard and mouse to the Lync appliance (AM70-L).
  2. Access the system’s settings screens and the system will restart in the administrative settings mode:
  • On the room system console, click Options and then click Settings.
  • Enter the room system’s administrator account credentials.
  1. Select System Settings in the Settings column on the left.
  2. Click Network Connections under Control Panel.
  3. In the Network Connections window, change the address in the address bar to explorer.exe and press ENTER.
    Windows Explorer opens.
  4. In Windows Explorer, go to C:\Program Files\LyncRoom and open the moncfg application.
    A “Please check the display settings” message appears.
  5. Click OK.
    Windows display control panel opens.
  6. Change the display layout and resolution so that the large interactive flat panels are logically arranged to the left of the small console display, and so that the top edge of all displays are aligned as described in chapter 4 of the SMART Room System for Microsoft Lync setup and maintenance guide (smarttech.com/kb/170450)
  7. Click OK.
    A “When done, press OK to continue” message appears.
  8. Click OK.
  9. Close Windows Explorer.
  10. In the Network Connections window, change the address in the address bar to Taskkill.exe /f /im LyncRoomConsole.exe.
    All open windows are forced to close, and the Lync Room Console loads again and refreshes its settings.
  11. Press Apply and Restart to save your changes, and then restart the Lync Room System in user mode.
  12. Disconnect the USB keyboard and mouse

Reference Link – HOW-TO: Forcing a display configuration change in a Lync Room Systen

Finally the moment has arrived! Manage to get my hands on a SMART Lync Room System (SRS-Lync-S) to hook up with my office Lync 2013 infrastructure.

I’ll be skipping the “heavy metal” work on assembling and wall mounting the system as this took us almost half a day just to setup the Mounting Stand and positioning the Interactive Flat Panel (that weights almost 100KGs!).

The crucial part is connecting the console and Interactive Flat Panel where the instructions can be easily found within the boxes that came with the equipment. While I’m trying to locate the exact copy that I’d, this is link that has the closest match how should the connectivity for the LRS.

LRS-Startup

With the display, audio, USB and Power connectivity in-placed, the system which runs on Windows 7 Embedded will walk us through the initial setup that would be required to Calibrate the Flat Panel and Detect the peripherals that are connected to it. The full setup guide can be found here

Here’s some walkthrough (aka HOW-TOs) during the overall setup that may not be too “visible” from the available document:

1. When the wizard initiates the Audio Source, select the Table Speaker instead of the Web Cam. The speaker will not immediately shown that is activate in Green so don’t panic and complete the wizard

2. During the display adjustment, you need to adjust the following resolution: Interactive Panel – 1920 x 1080, Console – 1366 x 768. LRS-Adjust Resolution 01

3. Upon confirming the changes, you’ll receive an error message: ERROR: The right-most monitor isn’t the primary monitor if you did not move the Console to the Right side

LRS-AdjustResolution 02 

4. To fix this, you’ll need to drag the Console screen to the left of the Interactive Flat Panel

LRS-AdjustResolution 03

5. However, this is not the end – upon confirming the changes, you might get this message indicating that the top of the console is not align with the Flat Panel ERROR: The top of the monitor \\.\DISPLAY2 is not aligned.

LRS-AdjustResolution 04

6. To solve this, just move the console screen and align it with the Interactive Flat Panel:

LRS-AdjustResolution 05

7. After this the Wizard will start to configure the System with a couple of reboots and you’ll be brought into the Lync Room System Setup Wizard, which you’ll need a Lync account to be provisioned at the Lync Server 2013

8. Download & follow the  Lync Room System Deployment Guide to setup the Exchange & Lync account for the System

9. Go back to the LRS Console

10. If you’re using an internal Microsoft Certificate Authority Server (Microsoft CA), manually add the Root Certificate into the Trusted Root Certificate Store

11. Add the trusted domain into the registry – Adding a Trusted Domain

12. Activate the System License  – Activating On Premise LRS. I’m currently stuck here as I’ve tried a couple of license keys but couldn’t get it activated. However, the LRS still works as per normal but you’ll get an annoying pop-out stating that the Lync Activation has failed . [Updated: 01/08/2014] Got the license key from SMART Technologies and the Lync Room System was successfully activated.

13. Key in the necessary credentials which was created at Step #8.

14. DO NOT SAVE and Restart the System. Run at least a Test Call and the Test Online Meeting, if everything works well, Save and Restart the system

[Updated: 01/08/2014]

15. After the LRS has rebooted into its Normal Mode (in this mode, you’re able to see the Calendar option on the Interactive Flat Panel); however, I wasn’t able to join the Online Meeting when attempting to do so from the screen.

16. To resolve the issue, I’d unplugged the keyboard & mouse (as initially administrating it through those devices seems to be faster to me) and I’d rebooted the system but the problem persists.

17. Booted into the Admin Console and run the calibration – both the Interactive Flat Panel & Console seems to solve the problem after that.

18. Next, is to test out the Online Meeting – it appears that joining the conference for Audio & Video doesn’t pose any issue however the Collaboration Workload (Presenting of Power Point & Desktop Sharing) doesn’t seem to work with the following error:

LRS-OnlineMeeting 01

Surprisingly, this error only occurs on the LRS but not the other machines in the environment. So a quick search at the Internet leads me to this article – Troubleshooting Lync 2013 PowerPoint sharing issue: “There was a problem verifying the certificate from the server. Please contact your support team.” As my problem was due to Access Rights to the Certificate Authority Server, I’ll post my experience on a separate article. In short, the problem happens only on Workgroup machines where the LRS is currently configured under the Workgroup membership.

With the last challenge shared above, the LRS is now fully functional and ready to operate whenever anyone sent a Room/Resource Booking invite – no more messy preparation & configuration of Web Conferencing Meetings!

Feel free to post your Queries/Feedback if you need to know more about the Solution :)

A co-worker of mined had attempted to put in a Exchange 2013 recently – in which causing the UM Server not to work unexpectedly. Although after cleaning up the Exchange 2013, we notice that:

  • Dialing to Voice Mail doesn’t to work anymore
  • Dialing to the Exchange Auto Attendant & Subscriber access seems to just “dropped”
  • Miss call notifications & voice mail no longer arrives in the mailbox

From the Exchange Server, such error kept surfacing when an attempt is made through the Lync Client

The following UM IP gateways did not respond as expected to a SIP OPTIONS request.

Transport = TLS, Address = LyncPoolServer.domain.com Port = 5061, Response Code = 0, Message = This operation timed out

UMNotWorking01

From the Lync Server:

Dial Plan Unknown

Dialplan [DialPlanName.domain.com] not recognized by routing application.

Cause: Dial plan does not exist, or Microsoft Lync Server 2013 does not have permission to read the relevant Active Directory objects.

Resolution: If the dial plan is valid, then run  exchucutil.ps1 in appropriate Exchange forest to give permission to Microsoft Lync Server 2013. If the dial plan is not valid, then clean up proxyAddress attribute for the affected users.

UMNotWorking01

As we suspected that during the Exchange 2013 installation, some of the permissions may have been reset or altered, causing the issue above, so we went ahead and re-run the script of ExchUCUtil.ps1 from the Exchange 2010 Unified Messaging role server and restarted the services.

However, the first error still appears and to confirm this, we’d to check the Dial Plans on the Exchange UM Server:

Get-UMIPGateway | fl

UMNotWorking03

Notice that the Port displays the value of 0 ; to solve this matter, we’d to manually assign the port number of 5061 to each Lync Server 2013:

Set-UMIPGateway -Identity LyncPool.domain.com -Port 5061

Next, a restart on the Microsoft Exchange Unified Messaging & Lync Server Front-End services will bring the Voice Mail back “alive”

Read the rest of this entry »

After running through the Hands-On Lab at the Lync Conference 2013 and also Microsoft MTC in Singapore, I’ve been itching to setup a unit of the SMART Interactive Board System or SMART Lync Room System from SCRATCH in which the unit is still not available in this region (Malaysia) – for now.

However, thanks to EP-Tec Solutions, I’ve manage to get an alternate model that leverages on SMART Meeting Pro that support Lync 2013 for interactive collaboration:

LRS_01

Assembling the unit was basically pretty straight forward – a moving wall stand, an interactive flat panel and some cables (VGA, HDMI & USB)

LRS_02

Before powering up the unit, I would recommend to prepare the machine to run on Windows 8.1 with Office 2013 Professional Plus (make sure to choose the Full Installation). Next, go to SMART Technologies download page and download SMART Meeting Pro 4.0

LRS_03

The download already comes with the SMART Meeting Pro Connector for Lync; if you’ve previously installed SMART Meeting Pro Connector for Lync, uninstall of the SMART Meeting software & components, make a reboot before you initiate the installation. Having both applications installed will cause the Microsoft Ink to go missing, which will cause the digital ink from smart unable to “write” onto the document.

Once the installation is completed, you should be able to see a grey side bar at the left at the screen

LRS_04

LRS_05

Once you’ve any of your Office Documents launched, Microsoft Ink will automatically be activated which allows you to write on the document. The system basically allows the document to be saved as a Native file format (docx, pptx & xlsx) after writing in the contents with the digital ink.

LRS_06        LRS_07

This is pretty useful when you perform an Online Meeting with Desktop Sharing is being initiated; however, take note that the Lync Whiteboard DOES NOT work with Microsoft Ink and you’ll need to use the given “Tools” from the whiteboard.

 

Microsoft had just released a public hot fix to remediate issues on iPad 2 running on iOS 7.1 where the Lync Client is unable to place or receive Audio & Video Calls

The Lync 2013 for iPad client cannot place or receive audio or video calls when the client is hosted on iPad 2 devices that are running iOS 7.1

The symptom doesn’t happen on Lync Client running on iPad Mini or the iPad Air, running on iOS 7.1

Kudos to the Lync Engineering team is identifying and resolving this matter!

Was just stumbling through the Windows Store and found a couple of cool apps on Lync

Lync Win8 Apps

Clockwise from the top left:

  1. Lync Handbook – a useful app for users whom are new to Lync
  2. Lync Pre-Call Diagnostic – a MUST for Lync Admin while troubleshooting Quality on Voice
  3. Shortcut Keys for Lync – a cool app that give you more productivity using Lync and your Keyboard (more than just touch!)
  4. Lync News – a RSS reader directly from NextHop

 

We’d two (2) offices physically located at two (2) different countries – SG & MY. A small scale call center is setup within the MY site to undertake Technical Support calls from locally & SG. Nonetheless, this Small Scale Call Center underlying is powered by Lync Server 2013 and Sonus UX1000 Media Gateway.

To give a better visualization of the setup, the layout looks like this:

Recently, the customer from SG site had given feedback that Inbound calls to the Call Center (+656212000) couldn’t get through, where calls are eventually dropped after a single ring tone.

Inbound RSG Failed - 02

However, calls to other SIP users (e.g. +6562120001) still works where the targeted SIP users’ Lync Client/Phone rings when an Inbound call is made. To investigate this, I’d lay down a few possibilities: The TDM-PBX, Media Gateway or the Enterprise Voice number could have been duplicated.

To start off, I’d to reproduced the issue by making an Inbound call and collect Traces from the Sonus Media Gateway & Mediation Server (which is Collocated with the Front-End Pool Server). Outcome from using Sonus Log Exchange (LX):

Inbound RSG Failed - 03

At the first 3 column indicates the calls is being attempted, from my mobile number of 60163735109 to the Call Center number (+65)6212000 and it seems that the signaling is working where the PBX throws the signal to Sonus UX1000 for processing. After which the Media Gateway will need to parse this signal to the Lync Mediation Server role. Further drilling into the log indicates that the Object/Resource wasn’t available:

Inbound RSG Failed - 04

At the Lync Server, using the options selected on Mediation Server, S4 & SIP Stack:

Inbound RSG Failed - 05

As the RGS Service was created under the MY’s Pool Server, the seems to have rejected the call, returning the message back to the UX1000 which caused the message of unavailable to be thrown back:

ms-diagnostics:  1038;reason=”Failed to connect to a peer server”;fqdn=”myfe.child.mydomain.com”;peer-type=”InternalServer”;winsock-code=”10061″;winsock-info=”The peer actively refused the connection attempt”;source=”myfe.child.mydomain.com”

During that moment, I thought of the most simplest method to resolve this issue is to recreate the entire RSG object as it was a weekend; so I went ahead to delete the Workflow, Queue & Group in sequences, when removing the object in Queue, there was a warning message that caught my attention:

Inbound RSG Failed - 06

I ran the command of the DFS Share: \\Child.MyDomain.com\MY-LyncP1F1\ and the folder returned empty, this is when I notice that my DFS mapping could’ve been removed “unintentionally” by another Administrator. To resolve this matter, I’d just to make sure that the correct shared path/directory is also configured under the DFS Management. For pre-caution, I republished the Topology Builder to make sure that the DFS path can be read by my Pool Servers.

Next, I’ve re-created the RSG services and all services had immediately came back online; the RSG folders & objects are also populated onto the File Store without any errors. To make sure that the RGS Service are working, another call was made from my mobile and the calls was routed based on the configured Workflow & Queues.

Conclusion: the RGS objects in the File Store are required to be accessibility as part of the reference when calls are being made, else calls will be dropped:

Inbound RSG Failed - 07

Recently, I’d a couple of request to migrate some of my customer from Google Apps (mainly Gmail) to Microsoft Office365. As using the Out-of-the-Box migrator within the Exchange Online (IMAP) migrator doesn’t seem to be working, I’d an opportunity to conduct a trial using MigrationWiz instead.

To do so, it only takes a few simple steps to get the migration working.

1. First of all, we’ll need to delegate full rights to an Account that we’ll be using for the migration, for simplicity, I’ve used back the Portal Administration. Log onto the Microsoft Online Portal and head over to the Exchange Admin Center. Anchor to the user that will be receiving the migrated email contents and grant full rights to the Administrator:

O365MigWiz - 01

2.  Access the User Mailbox Properties & select Mailbox Delegation. Under Full Access, add in the Administrator Account that will be used to migrate the contents on behalf of the user

O365MigWiz_02

3. Once done, login to MigrationWiz Portal and create a Connector, to link between Google Mail & Exchange Online, using the following configuration:

O365MigWiz_03

  • Create a Project Name (e.g. Company Name – dd/MM/YYYY)
  • License Category: Commercial (Note: this is also subjected to the license that was purchased)
  • Source Settings
    • Service Provider: Google
    • Source Type: Google App/Gmail
  • Destination Settings
    • Service Provider: Microsoft Office 365
    • Destination Type: Microsoft Office 365
    • Access using Admin Credential: Checked
    • Admin Username: Username@domain.onmicrosoft.com
    • Password: password

4. Select the Items that is to be migrated across & click on Create.

O365MigWiz_04

You can also further customized how the migration should behave, such as notification and the period of the contents that is to be migrated across:

O365MigWiz_05

Similar to other migration (On-Premises), the process runs background without any Administrative attention required; hence, it is recommended to have the following notification configured for each migration project:

  • Successful Migrated Mailboxes
    • The email address of the source mailbox being migrated
    • The email address of the destination mailbox being migrated
    • To the MigrationWiz email account that was registered OR Office 365 Admin Email Address
  • Failed Migrated Mailboxes
    • Office 365 Admin Email Address

You may only want to notify the users that the mailbox has been migrated when it is successful so the users would know that the contents has been successfully copied into Office 365 account; on the other hand, the failed mailboxes needs to attended by the Administrators and we shouldn’t be bothering the users – shouldn’t we? :)

In almost every migration activities, organizations are concerns on how fast and how quick can the migration be completed, hence choosing the nearest Data Center for the migration is very crucial. To determine that, you’ll need to check where are the email contents placed at Google App. For Microsoft Office 365, make sure the mailbox are selected to the correct country when assigning the Exchange Online license:

O365MigWiz_06a

O365MigWiz_06

You can also create a filter of the duration of the contents and which folders to excluded in the process of migrating the mailboxes

O365MigWiz_07

You can also convert Gmail’s labels to Microsoft’s Exchange/Outlook’s Category model:

O365MigWiz_08

Save the configured settings but don’t start the migration yet.

Logon to the Gmail Account that is planned for the migration, take down the total number of items under the Inbox:

O365MigWiz_09

Now go back to MigrationWiz to initiate the migration:

O365MigWiz_10

  • Source Mailbox
    • Put in the source email address under Gmail (in most cases, it should be the original email address)
    • Username would likely be the same as the previous entry = your source email address
    • Password
  • Destination Mailbox
    • The Office 365 Mailbox Account: username@domain.onmicrosoft.com

Confirm the Advance Settings (you may choose to further customized or use back the default values that was configured earlier) and proceed with the migration.

The migration is now ready to be migrated

O365MigWiz_11

Start the migration process by clicking on the  Cloud Icon O365MigWiz_11a  and MigrationWiz will then start to verify the credentials at Google Mail which was input earlier:

O365MigWiz_12

Once it is successful, the mailbox will then start the migration

O365MigWiz_13

O365MigWiz_14

When the migration completes, you get to view the overall statistics of the migration:

O365MigWiz_15

O365MigWiz - 16 O365MigWiz - 17 O365MigWiz - 18

Now, the final step is to verify the contents that has been migrated over to Office 365

O365MigWiz - 19

It appears that the 10 years ago dilemma is reoccurring, where updates from Microsoft are not Quality Assured before releasing to the public. In the most recent Office 2013 Security releases, received by my Admin via Intune, running on Windows 8 64-bit installed with Office 2013 32-bit, the right pane was “blank” once the system reboots after a successful installation:

Outlook 2013 Blank Right Pane

 

After running by the Internet, it appears that the Sept 2013 was the cause and the update has been pulled back. Although there’re several workarounds to this, I still prefer to have my Right Pane back as it is.

First of all, uninstall the following Office Security Updates:

  1. Security Update for Microsoft Office 2013 KB2810009
  2. Update for Microsoft Office 2013 KB2817630

Reboot the system, download and install KB2817347; take note this Hotfix needs to be requested and couldn’t be located from Windows Update. Upon completing the installation, reboot and you’ll get back the Right Pane.

I hope after this incident, Microsoft Quality Assurance Team for the Windows Update will validate any upcoming releases before releasing it to the public or History shall repeat itself (e.g. BSODs during the Windows 2000 days)

In a recent Response Group Service (RGS), call forwarding is required if the call is unattended after 20 seconds. However, when the call doesn’t get routed to the next number after the timeout.

Using the OCS Logger, this is what has been captured:

RGS Transfer Fail 01

Based on the third trace a SIP 2.0 403 Forbidden error message was thrown with a diagnostic message:

ms-diagnostics: 12001;reason=”User Policy does not contain phone route usage”;source=”MY-FE.MyDomain.com”;UserUri=”sip:MY-Helpdesk@MyDomain.com”;appName=”OutboundRouting

It appears that the account doesn’t have sufficient rights to route/forward the call out on behalf of the caller. To address this issue, the following commands needs to be executed:

Get-CsApplicationEndpoint sip:MY-Helpdesk@MyDomain.com| Grant-CsVoicePolicy -PolicyName “MyCall Policy”

Once the PowerShell has been execute, wait for the next User Replicator to take effect and the calls are now able to be routed to the specified destination! :D

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: