Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

Now it's time for the for the fir Lync 2013 site. I'm following up with the Topology blog i released earlier. I prepare the first Enterprise Server Lync 2013. Just in the Test Lab, I don't have the Load Balance yet, so what I did was, I gave the only EE Server two IP addresses. The second one is for the POOLLEFT, this is a supported scenario if you only have single pool server in place. First we need all the Pre-Requisites for the new EE Server in place, which I have listed here: PowerShell 3.0 PowerShell 3.0 is not a standalone product, it's part of the Windows Framework 3.0 http://www.microsoft.com/en-us/download/details.aspx?id=34595 .Net Framework 4.5 http://www.microsoft.com/en-us/download/details.aspx?id=30653 Windows Identity Foundation http://www.microsoft.com/en-us/download/details.aspx?id=17331 IIS Windows Desktop Experience SilverLight 4 Visual C++ 11 x64 Active Directory Management tools IIS: Static Content Def...

ACL Problem in AD: Beside the known requirements and pre-requisites in Lync, there are additional confusion in Lync on how to initiate Servers in Sub-Level Domains. We found at one customer a problem deploying Lync in his SubDom. What was happened? We were, with all proper assigned rights for the installation account, setting up the first Lync Server in their sub domain. Simply said it didn’t work. We could see additional Lync attributes written in AD Configuration Partition, saw the additional sub config under the Lync Server. But just the services didn’t start. It was a problem reading the Configuration Partition based information, even if the writing into AD work well. Solution: After digging through the AD structure, validating the Topology and more, the solution found was: for installation in a Sub Level Domain, you must have Enterprise Admin Right too. Wired, isn't it?! This is normally nothing special and even...