In this article we will see the options to configure external access and few limitations that we have on them.
Once the above is done you can download the Skype for Business client for the test users and start testing the client functionality.Ĭonfiguring external access in lync 2013 is one of the challenging part for the administrators. Grant-CsClientPolicy -Identity username -PolicyName SkypeForBusiness Run the below command to grant the client policy to the users for testing this client functionality. New-CsClientPolicy -Identity SkypeforBusiness -EnableSkypeUI $True Run the below command to create a test client policy So its better to create a new Client Policy to test this client on the few user accounts. It is better not to play around with this since it will affect all the users if at all there is any issues. In most of the cases we might be having only default global policy. If we have any test client policy already you can try with the policy. Inorder to to that follow the below stepsįirst run Get-CsClientPolicy to check how many policies you have. īut before setting this policy to all the users it is better that if we test this new client in few of the users and then we can deploy them to rest of the users.
If you have the above build version on your Lync 2013 server you can go ahead and start testing. Minimum server Build for Lync 2010 – Deploy server build. Minimum server Build for Lync 2013 – Deploy server build. But specific server builds are required on Lync Server 2013 and Lync Server 2010 onpremise in order to set client policiesīelow are the prerequisites for Lync 2010 & 2013 OnPremise Servers This Skype for business client will be working on Lync 2010 & 2013 on premise registrars servers and Lync Online. Lync 2013 client will become Skype for Business after Apas part of regular Office monthly updates if performed by the organizations. Microsoft has released Skype for Business Client.
0 kommentar(er)
