![microsoft office communicator 2007 manual microsoft office communicator 2007 manual](https://docplayer.net/docs-images/45/11231791/images/page_11.jpg)
- #Microsoft office communicator 2007 manual how to#
- #Microsoft office communicator 2007 manual software#
Enter the absolute path to the presence.xml file using the file:/// URL format.
![microsoft office communicator 2007 manual microsoft office communicator 2007 manual](https://docplayer.net/docs-images/45/11231791/images/page_10.jpg)
#Microsoft office communicator 2007 manual software#
Create a new REG_DWORD value named EnableSIPHighSecurityMode in the Communicator Software Policies key shown below.The first is to allow a local file to be read and removed the HTTPS requirement while the second settings tell Lync where to find the presence configuration file. To trigger the Lync client to import and use the custom state information two settings will need to be set within the local workstation’s registry. The activity string text is limited to a maximum of 64 characters. The availability values are limited to the following strings: Online, Busy, and Do-Not-Disturb.
![microsoft office communicator 2007 manual microsoft office communicator 2007 manual](https://cdn.ttgtmedia.com/digitalguide/images/Misc/ocs_5.jpg)
![microsoft office communicator 2007 manual microsoft office communicator 2007 manual](https://usermanual.wiki/Plantronics/BUA200/User-Guide-1074411-Page-4.png)
This is fine when you want the same custom states to be available for multiple users across all workstations, but for simply adding the additional states to a single primary workstation for yourself using a local file is the best approach.īecause Lync follows the same default behavior of forcing HTTPS then in order to use a local XML file this behavior will need to be disabled, which will be addressed in the next section. The aforementioned change between OC 20 R2 is the default behavior is now to force a secure connection to the XML file, limiting the option to only accessing the file via HTTPS. This file can be accessed by the Lync client using either direct access to the file (via local disk or shared directory on a remote server) or as a web client using HTTP or HTTPS. Unique entries can be created with a few limitations: a maximum of 4 states and a limit of 64 characters in the description text. The custom configuration information is stored in an XML file that must be manually created first. For those of you new to the Communications Server products then here is a step-by-step walkthrough specifically for Lync.
#Microsoft office communicator 2007 manual how to#
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.