April 24, 2015

Skype for Business Features Overview

Skype for Business Features Overview

Recently Microsoft published MS Office 2013 and MS Office 365 ProPlus updates (April 14th 2015) with Skype for Business 2015 client. Now whenever you updates Microsoft office 2013 updates you will receive Skype for Business 2015 client. This is new client which is replacement of Lync 2013. Basically Skype for business as Lync 2013 and Skype consumer combination. J

Now questions comes if Skype for Business client replace Lync then will not see consumer Skype in market place? What is feature difference in Skype for Business 2015 and Consumer Skype?

Answer is we will have two different client in market place Skype (consumer) and Skype for Business client.

Skype (Consumer) Features
Skype for Business Features
v Its Consumer grade
v Enterprise grade with licensing
v Free of cost
v Deployment flexibility – On-Prem, hybrid, partner cloud
v Hosted by Microsoft
v Skype for Enterprise client
v Skype client
v No ADs
v Subject to ADs
v 1000+ participants in a Conference call (audio/video/sharing) using “Broadcast Meetings”
v Limit of 10 simultaneous video participants
v Web client for conference access with full fidelity
v No web client available
v Bring your own PSTN Carriage provider
v Paid PSTN Calling
v PABX features (Sim Ring, Call park, Delegation, ACD, Hunt groups, Voicemail)
v No PABX features such as ACD/call park/delegation
v Réception console in Attendant Console
v No reception console

What are the new and improved feature on Skype for Business 2015 client?

1.    New look and feel.

2.    Fast Action Menu

3.    Call via Work

4.    Skype directory integration

5.    Dual user experience

6.    Call Monitor

7.    Rate My Call

8.    Quick access to call controls

9.    Meeting Join from Client

10.Easy to Use Interface

Improved Features:

11.Improved Menus

12.Better Desktop Sharing

13.New Emoticons

14.Improved file transfer

15.OneNote Integration

Skype for Business client complete features details will post in upcoming article.

Thank you.

April 14th 2015 Office 2013 Updates list

April 14th 2015 Office 2013 Updates list.
Here is the updates in the following Microsoft Knowledge Base articles are included in the April 14, 2015 update.

Knowledge Base article number
Access 2013
Excel 2013
Office 2013
Office 2013
Office 2013
Office 2013
Office 2013
Office 2013
Office 2013
Office 2013
OneDrive for Business
OneNote 2013
Outlook 2013
Outlook 2013
Outlook 2013 Junk Email Filter
PowerPoint 2013
Project 2013
Skype for Business
Skype for Business
Visio 2013
Word 2013


Thank you.

April 23, 2015

Step by step process to migrate CMS from Lync Server 2010 to Lync Server 2013.

Step by step process to migrate CMS from Lync Server 2010 to Lync Server 2013.

Recently we have complete Lync migration from 2010 to 2013 and finally

Moved CMS from Lync 2010 to 2013 hence posting this article. I know there are so many article available on web however want to simplify the process.

1.    First check CMS location where and which Lync pool holding CMS database. That you can find using Topology builder or PowerShell command let.

2.    You must have RTCUniversalServerAdmins group permission and SQL Server database sysadmin user rights and permissions on the database where you want to install the Central Management store.

3.    Now login to Front End server using member of above group permission and open Lync Management Shell.

4.    Run “Install-CsDatabase -CentralManagementDatabase –SQLServerFQDN "Sql01.mydomain.com” -SQLInstanceName "Default"

5.    Publish the topology by running “Enable-CsTopology -Verbose”

6.    Now Run “Move-CsManagementServer” from one of the Lync Server 2013 Front Server.


a.     Type Y to continue, or N to stop the move.

7.    Re-run “C:\Program Files\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe” to install the CMS services (Master Replica, File Transfer) on all Lync Front End Server (2013).

8.    On all Lync Server 2010 front end, re-run “C:\Program Files\Microsoft Lync Server 2010\Deployment\Bootstrapper.exe

9.    Reboot the Lync Server 2013 server Front End one at a time. This is required because of a group membership change to access Central Management Server database.

10.Also Reboot Lync Server 2010 Front End one at a time.

11.Verify Replication using “Get-CsManagementStoreReplicationStatus

12.Once replication is verified. Wait for 24 hours and remove 2010 CMS databases.  

Remove the 2010 CMS databases:

13.Run: Uninstall-CsDatabase –CentralManagementDatabase –SQLServerFQDN "hq1-sql2008.corp.brocade.com" -SqlInstanceName "sql2008"


Thank you.

April 11, 2015

We couldn’t sign you in. Please check your sign-in info and try again.

Issue: Unable to log-in to the LRS Admin portal.

Error: We couldn’t sign you in. Please check your sign-in info and try again.
Problem Statement:

Configured Lync Room System Admin portal using TechNet article however unable to login using SIP enabled object. Getting error message ‘We couldn’t sign you in. Please check your sign-in info and try again.’


Troubleshooting step:

1.    Configured and installed LRS room web portal on Front End server.

2.    Using Active Directory object with SIP enabled and proper credential.

3.    Tried to accessing the admin portal using FQDN of the FE server and also using the localhost however still getting the below error.

                                                    i.     We couldn't sign you in. Please check your sign-in info and try again.

4.    Checked the IIS logs and we were getting below errors.

a. 2015-04-09 02:44:26 fe80::81af:590f:4038:d7f4%12 GET /lrs/ login&reason=401&target=https%3A%2F%2F%2Flrs%2F 443 - fe80::81af:590f:4038:d7f4%12 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https:///lrs/ 304 0 0 58

5.    Checked and verified the IIS setting for the LRS virtual directory all were in place, however the SSL was not checked. Later enabled the SSL (checked the SSL required on the LRS v-directory).

6.    Still getting same error. We couldn't sign you in. Please check your sign-in info and try again.

7. Later checked the IIS logs and now getting the below 401 unauthorized errors.

a. 2015-04-09 17:20:57 ::1 GET /lrs/handler - 443 - ::1 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https:///lrs/?login&reason=401&target=https%3A%2F%2F%2Flrs%2F 401 0 0 1

8.    Seeing the requests are hitting the via the IPV6 hence we have disabled the IPV6 using the network setting and also via registry followed below article.

9.    Added the pool name in the config file as per the below article step no 6. (This is not required because have LRS and portal on single pool, however want to do all possible things).

Still getting same errorL.

10.Using the host file entry pointed to the POOL FQDN and tried however still getting same error and also same errors in the IIS logs. L

11.Later tried pointing to the web services FQDN using the host file entry like below.     Lync-Int-web.mydomain.com


This time it worked. J

12.Later have verified all possible combinations to access the portal, but only using the internal web services FQDN able to access Lync room admin portal.


I have not found any article or information from MICROSOFT that Lync Room System Admin portal will work only using internal web service name.


Thank you.