A Lync Server web component that allows IT administrators to monitor and manage their organization's Lync Room System devices.
Download from here

Supported Operating System:
Windows Server 2008 R2
Windows Server 2012

Pr-requisites:
In order to use Microsoft Lync Room System Administrative Portal, you must also have the following installed:
Lync Server 2013 Cumulative Update 2

Cheers,

Environment:
Root Domain: domain.local
Domain Controllers: 3
Child Domain: abc.domian.local
Domain Controllers: 3
2 Exchange 2003 running in child domain
6 Exchange 2010 running in child domain

When trying to register/activate the license key for exchange server 2010, I was getting this error.

























Now, I was able to register/activate other server without any issue in the same domain, but this one was failing. I tried Exchange Management Shell and it failed too.
This error message clearly talks about the permission issue, hence I checked the Inheritance blocked on the user account and found that it was unchecked.






















Checked the check box.






















Tried registering/activating the server but failed again with the same error message. I found the event ID 2080 and it has some issue with SACL rights on few domain controllers on the site.




















Ran Setup.com /PrepareAD to fix the SACL right's and checked the event, no changes in the event result. Waited for the replication to complete. After 20 minutes, tried to register/activate the server, not it's failing on different domain controller not the domain controller for which it was failing.

Now, I had one server activated successfully without any issue. So I went on to the server and activated all the 3 servers without any issues.
But, it's a workaround and not a resolution, cause I will get the same error when I start the migration process when moving the mailboxes from 2003 to 2010.
To check if the issue still exist, I created a Test Mailbox on 2003 and tried to move it on to 2010 server, and as expected, it failed with the same error message.

























I checked the Exchange Trusted Sub System Group and Exchange Server Group and found that only one exchange server is a member of these groups not all of them.







































Added all the remaining servers in both the groups.





















Restarted the domain controller on which the move was failing. Moved the mailbox and it moved successfully.
As per my experience, the straight forward resolution is, Inheritance blocked should be checked. But in this case, check box was getting unchecked by itself. And I also ran the /PrepareDomain switch too, But it didn't helped.

It was the issue with AD replication and the permission issue on the user account.
Note: Still monitoring the issue, will move few mailboxes again and check the issue. Will update the post.

Cheers,

While publishing the Topology. I got the error "Error: Cannot open Service Control Manager on computer "servername.domain.com". This operation might require other privileges."

















I checked the connectivity, server could ping each other with IP and NetBIOS name. Checked the firewall setting on both SQL and FE server.
Disabled the Firewall  on SQL server and tried Publishing the Topology and it completed successfully.

I was installing AsteriskNOW-3.0.0 in the LAB (Hyper-V) and got the error "Error Parsing Kickstart Config: The provider network interface eth0 does not exist."















I checked the setting in Hyper-V and the server had the Network Adapter, I restarted the process and it failed again. I checked the settings again and found that Network Adapter is selected by default.



































I turned off the server and removed the Network Adapter and added the new hardware and selected Legacy Network Adapter.



































After adding the Legacy Network Adapter error disappeared and installation completed successfully.
I believe the only reason it need Legacy Network Adapter and not the Network Adapter, because AsteriskNOW-3.0.0 is Linux based application.

Cheers,

Environment Topology:
1 DC/GC and DNS running on Windows Server 2008 R2 with SP1
1 Lync Server 2013 installed on Windows Server 2012
1 Exchange Server 2010 SP3 with RU2
1 Client Windows 8 x64.
1 Office 2013 Lync Client and Office 2013 Basic Lync Client.
1 Certificate Authority and ADFS 2.0 Server
1 Forefront TMG Server 2010 SP2

I am not able to login to Lync 2013 client after the fresh installation of Lync Server 2013 with CU2. I am getting the error standard error message "The user name, password, or domain appears to be incorrect."

































Tried with different accounts as well, but still getting the same error message. I found an update for Lync 2013 client and installed it.















After the update, tried Login, still the same error message. Now I enable the logging on the client so that it will generate the event in case of failure. I found the Event ID 3, 1 and 12.









































































Now as per the event, there's something wrong with the installation or the files of Lync Client 2013 which got installed. I installed the full version of Office 2013 Lync Client, now I tried with Lync Basic client and it failed with the same error message.

































I decided to check the issue with Lync 2010 Client and installed the client after uninstalling the Lync 2013 client from the workstation.
Now I tried to login to the Test account and it worked, no more error with Lync 2010 client.





































Resolution/Workaround: Install Lync 2010 client.
I am not sure, why is it failing to login with Lync 2013 client, I am still looking into the issue and will update the post once I find the solution.

Cheers,