[b][color=red]***This post suggests updating Windows Registry Entries - please ensure that you are aware of the affects of doing so (i.e. test *EVERYTHING* thoroughly/rigorously) before proceeding into a Production environment***[/color][/b]
This is great stuff cavagnaro! It not only works for CCPulse+, but also for CME, SCI, OCM...
Here's a plan - in case you want to try to deploy it, yourselves:
(Obviously chose what you want to lock-down first and unzip/create the relevant UniLogin.dll somewhere that is accessible, from across your Network)
1. Create a generic user account and password for the update (and delete it as soon as the updates are complete).
2. Create a batch script for User Desktops;
2.1 Update the local Registry entries for CCPulse+
2.2 Run CCPulse+ with the default parameters
2.3 Close CCPulse+
2.4 rename the old CCPulse+ version of .dll "UniLogin.dll" to "UniLogin.old"
2.5 Copy in the new "lockdown" .dll, to replace the previous version
Something like this:
***REGISTRY UPDATES***
My Computer\HKEY_CURRENT_USER\Software\GCTI\CallCenter\LoginInfo
Name: Host1
Data: <Hostname>
Name: Port1
Data <Port Number>
***END OF REGISTRY UPDATES***
***OPEN CCPULSE+ WITH GENERIC CREDENTIALS***
SET CCPULSE_ACCESS=COMMAND_LINE
<type in the full path of CCPulse+ here...>CallCenter.exe -user
<generic username> -pwd <generic password> -app <CCPulse CME application name> -ws
<generic Workspace Name>
***CLOSE CCPULSE+***
taskkill /IM CallCenter.exe
***Rename UniLogin.dll***
REN <type in the full path of the CCPulse+ executable command here...>UniLogin.dll UniLogin.old
***Copy in new "locked down" .dll***
COPY <type in the full path of location of "locked down" UniLogin.dll> <type in the full path of CCPulse+ executable command here...>
END
- obviously, you will have to play around with this, since it's not strictly "code" but I think you get the idea...?
Thanks again cavagnaro!
Tony
