While publishing a Lync 2013 topology, the process fails in the first step itself – creating the CMS.
Having a look at the deployment log, one will get the feeling that it is something to do with the permissions.
Error : Syetem.InvalidOperationException. Cannot open service control manager on computer. This operation might require other privileges.
But, I was using the admin account that is a member of Enterprise, Domain & Schema Admin. In addition, the account is also a member of the CSAdministrator and RTCUniversalServerAdmins. It can’t get any better than this ;)
The issue was really simple. In Lync 2013, a standard edition pool fqdn should be the same as the server fqdn. It gets checked while publishing the topology in 2013. I am not sure whether it blocks the topology from being published in Lync 2010.
I edited my topology and changed the pool fqdn from lync.hew.lab to lync13.hew.lab (forgot that I named the machine as Lync13).
As expected, the topology got published successfully.