How to set up Integrated Windows Logon

This is a nice feature that's been in the product for some time, but not too many people know about. You can set Enterprise (and Advance) to auto-login when a user logs in to Windows:

a. Set Desktops registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Callmedia\Callmedia Desktop\General\UseWindowsLogonAccount to 1

b. Set Enterprise user logon to Windows logon (ie: luke.talbot).

c. Set Enterprise user password to callmedia

That's it. Your users will no longer have to remember an additional password!

(NB: Prior to 4.3, you had to set the Enterprise user password to blank for this to work).

Configuring Client Extensions

There are many ways to get Clients to obtain a valid Extension number. Well, actually, there are three. Two are quite common, one is less common:

1. Asking users for their Extension number. This is achieved by setting EXTNO=ASK in the CMClient32.ini file.
Advantages: Popular because of its easy deployment (everyone shares identical ini files), and also because on many sites users have to Hotdesk whilst always retaining the same extension number.
Disadvantages: Common issues include users inputting invalid Extension numbers. Server Console offers limited assistance here: you can restrict input to 4 numerical characters for instance. But CMClient32.exe doesn’t support re-entering numbers if they are invalid anyway, which is nice.

2. Hard-coded Extensions, by setting EXTNO=2001, for example.
Advantages: This is useful for people whose extension number is always next to the same Windows machine.
Disadvantages: Common issues with this are the fact that machines and phones sometimes get swapped over, which means the CMClient32.ini file would need to be changed. Deployment is also not easy because all machines have unique ini files; this can be a maintenance/installation nightmare for large sites.

3. Host-Table Lookup. This is configured by adding the ServerLookupUptions=ASKEXT to the [Options] section of the CMClient32.ini file. Client then ignores the EXTNO setting, and asks server to give it an extension number based on the Hostname of the client machine. Nifty. This even works in Terminal Server and Citrix environments (it uses the machine name of the terminal).
Advantages: As with hard-coded extensions, this is great because it takes agent-error out of the equation. It is better than Hard-coding into the ini file however, because the host table is maintained from Server Console. This means that the CMClient32.ini files are all identical, which makes deployment a doddle.
Disadvantages: For this to be effective you have to 100% on which machine is next to which extension. As with Hard-coding, this is pretty much irrelevant if users need to hotdesk and take their extension numbers with them (ie: if they use NICE voice recording).