It was really silly, after updating the topology in the topology builder I found that setup instructed me to run the setup again and run the step “setup or Remove Lync Server Components” to update the local server configuration from the CMS.
looks like I found a way to update the local configuration from the CMS which is using the cmdlet: enable-cscomputer, of course you can use get-cscomputer and pipe it to enable-cscomputer.
this will allow you to rapidly update your servers local configuration if you have large amount of servers.
if you have been reading Jeff’s Post http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/ then you will know that Lync Client is not supported with OCS, for further details I have prepared this Table to list the supported clients against servers:
SendAs permissions granted to users in forests trusted by Microsoft Exchange Server are not visible in the Send As Permission Wizard in Exchange Management Console (EMC)
Active Directory wasn’t prepared using hosting mode.” error message when you install Exchange Server 2010 SP1 from an unattended installation
Mailbox move from Exchange 2007 to Exchange 2010 fails with error “Unable to synchronize manifest”
The Replay Queue Length for Passive Database Copies of a Database Availability Group may continue to grow