For those of you new to the Communications Server products then here is a step-by-step walkthrough specifically for Lync. So if you already know how to do this in the OCS R2 client, then follow the same steps. See the end of this article for the changes specific to Lync 2013. This article has been updated yet again (October 2012) to include the new registry path that the Lync 2013 client uses as now it is part of the Office 2013 suite. The original basic configuration was intended for one-off usage or testing, while the newer more secure method is considered best practice for production deployments. This article has been updated (September 2012) to include an additional set of instructions describing a more secure configuration approach meant for production deployments. Enable Custom Presence States within Lync.Disable SIP High Security Mode within Lync.Create a new XML file on the local workstation and customize the presence states and descriptions. ![]() But I have not yet seen one specifically for Lync, so here is a brief overview.īasically the same configuration steps are used as what Office Communicator 2007 R2 required, since a change to the default security behavior was added after the 2007 (R1) client which prevented the use of non HTTPS connections to the configuration file. You can now control you custom presence states using PowerShell, if you have installed the SDK, using the Publish-SfBContactInformation.Office Communicator has supported the customization of up to 4 additional presence states for some times, and there are many articles all over the Internet on this topic. You can find the language ID codes hereĭownload the script here and use PowerShell to control your presence using the Lync 2013 Client SDK described here.If you are in an environment with more than two languages for you Office deployment, make sure you add an LCID per language in the script.Understand that they will also see you as in a meeting, in a call, your note and your location as well.If you want external contacts to see your custom presence state you need to elevate them as colleagues in the relationship pane.For everyone in your Colleagues relationship level as long as they are running a client language version specified above.On Skype for Business clients in your local location retrieved using (Get-Culture).LCID.On English Skype for Business clients for you and your colleagues.The presence states works in the following scenarios.You need to sign out of the client and back in for the changes to take effect.The xml file will get stored under c:\_CustomPresence\CustomPresence.xml if that is your systemdrive.It works for MSI installed Office and Click-to-Run Office.It works for Lync and Skype for Business.To run the script, just type the following in PowerShell in elevated mode from the location you saved it.The presence states that works are: Online, Busy, and Do-Not-Disturb. ![]()
0 Comments
Leave a Reply. |