19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix H-Setting the <strong>RMX</strong> for Integration Into Microsoft Environment<br />

Running the <strong>Polycom</strong>OCSConfigurator.exe to create the Configuration Files<br />

The <strong>Polycom</strong> configuration utility can be downloaded to a workstation or Office<br />

Communications Server /Lync Server.<br />

Downloading it the Lync Server directly provides one smooth process. If the utility is<br />

downloaded to a PC, you will have first to run the configuration utility on the PC to create<br />

the configuration files and then copy these files to the Lync server and run them there.<br />

To create the configuration files:<br />

1 In the <strong>Polycom</strong> Support site, where you download the <strong>RMX</strong> version (http://<br />

support.polycom.com/<strong>Polycom</strong>Service/home/home.htm), download the<br />

<strong>Polycom</strong>OCSConfigurator.exe utility to your local workstation or the Lync server.<br />

2 Double-click the <strong>Polycom</strong>OCSConfigurator.exe utility.<br />

The <strong>Polycom</strong>OCSConfigurator@1.0.0.5 window opens.<br />

— The Enable option is selected by default. It indicates that any of the users that will<br />

be configured by this utility can start an Ad-hoc conference. When cleared, no user<br />

can start an Ad Hoc conference on the <strong>RMX</strong> and the Click-to-Conference feature is<br />

disabled.<br />

— The All option is automatically selected, indicating that all Office Communications<br />

Server/Lync Client users can start an Ad-hoc conference on the <strong>RMX</strong>.<br />

3 Optional. To restrict the option to start an Ad Hoc conference to selected users, select<br />

the By User File option.<br />

In such a case, you must create and upload a text file named AllowedUsers.txt. This file<br />

contains the list of users that can start an Ad Hoc conference, as defined in the Active<br />

Directory, in the format: user name,1 (or 0) where 1 - means that the user can start an<br />

Ad hoc conference. Each user must be listed in a separate line.<br />

For example:<br />

sm10,1<br />

sm11,1<br />

sm12,1<br />

4 In the Route field, enter the FQDN name of the <strong>RMX</strong> where the conferences will be<br />

hosted, in the format [<strong>RMX</strong> FQDN name].[domain name]. For example,<br />

rmx18630.polycom.com<br />

If <strong>Polycom</strong> configuration utility is run on the Office Communications Server or Lync<br />

Server and an incorrect FQDN was entered for the <strong>RMX</strong>, the system will not be able to<br />

resolve its name and the process will fail.<br />

<strong>Polycom</strong>, Inc. H-61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!