Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: tony on September 05, 2008, 03:02:46 PM
-
I've a curious request, since some of you may have attempted this already but I wanted a general opinion;
Some of our CCPulse Users are very clever. So clever, that they know the Host Name and Port of both the CCPulse Conifg Proxy Server [b]and [/b] the central Config Server. So, if they get problems (i.e. sloooow log in or white screens) logging their CCPulse Application in using the (default set) CCPulse Config Proxy parameters they crash out of the Application, re-open it, amend the [i]Host Name [/i] and [i]Port [/i] and log into the central Config Server, instead...
Obviously I don't want them to do this - but how can I stop them? Is there a way to disable the [i]Host Name [/i] and [i]Port [/i] input boxes on the CCPulse Login Screen? Or maybe I can set up a CME Access Group to achieve the same...?
As always - thanks for your thoughts!
Tony
-
Tony,
On those network segments where the CCP users are you could alter the DNS lookup of the Config Server........
Pavel
-
If using a Firewall you can ask them that those networks can't access that port on Genesys server.
-
Cool - 2 answers - I am honored...! :)
I'll have a word with "Mr Networks", next week and see what can be done...
Thanks guys!
Tony
-
I did not try it - but a suggestion....
access group for ccpulse users- give this access group full permisssions on config proxy and read only /no permissions on the config server.... worth a try...
-
The problem with Access Groups is that you frequently find staff/Agents/Persons in more than one Group; to give them permissions through a CCPulse User Access Group (to include only a connection to the Config Proxy) and you also have them in the CME Access Group (which includes exclusive access to the Config Layer) will more than likely on add to the problem...?
I'm digging around in DNS Aliases, currently... I think it might also be a victim of the above scenario; If you update a PC via a DNS Alias to sort out a problem with getting the right Host in CCPulse [b]but the User also requires access to CME[/b], the Host (cfg_proxy) and the Host (cfg) both point to (cfg_proxy) - and you can't use CME via (cfg_proxy), as it is read-only...
:(
Thanks!
Tony
-
Change the host that the Config server sits on. If not the host, just the port. Not the quickest of fixes I admit but the one which would seem to resolve most of the issues your coming across.
If you don't want to do this or can't, I would look at using the DNS option previously suggested and then setting up either remote desktop or citrix to allow CME users to access outside the normal office DNS rules.
Can you create a read / write proxy that can be used by these special users in addition to the read-only proxy for the normals?
- I wanted to give you the magic answer but this is all I could come up with! :P
-
hmmm.... Genesys suggested Registry Updates to lock it down - but it can still be changed on the login screen...
-
Which one are you looking at doing?
-
I'll let you know once I've worked it out...! :)
-
Not very elegant, but If the user's PC is fairly well locked down you can remove the original shortcuts for CCPulse and replace it with a script to start CCPulse from the command line with the parameters hard coded. Make this read only and it should work ish...
CallCenter.exe -host HOSTNAME -port 2020 -user USERNAME -pwd PASSWORD -app APPLICATIONNAME -ws WORKSPACENAME
-
Hi Ben! :)
Yeah - I went there but that means hard-coding a Username and Password. We're using individual Logins, so not really viable...
If only I could lock down just the Login Screen entry Fields for Host and Port.... :(
Tony
-
Hi guys,
I cant seem to get CCPulse to launch using the command line script above? It just launches the app with the login box as usual? Any ideas why this doesnt work for me?
-
You need to put in a command line reference, prior to the .exe and -options. Write up a .bat file like this;
SET CCPULSE_ACCESS=COMMAND_LINE
<type in the full path of CCPulse here...>CallCenter.exe -user
<username> -pwd <password> -app <CCPulse CME application name> -ws
<Workspace Name>
Run the .bat and see how it goes..?
Tony
-
So Tony, which solution did you ended up using?
-
None - yet!
Very frustrating when I don't hold all of the keys to get things done "just like that..." I wish it were something I could amend on the Application in CME... :(
Tony
-
Well you made me remember my hacking days hehehe
I got this for you, I only modified some HEX data on UniLogin.dll and wala!
Enjoy!
Copy this DLL on CME folder, it is for CME v7.6 English.
This is a screenshot of what you will get, I know this is dangerous, however...if you like it use it.
-
Damn! We were talking about CCPulse...hehe, let me try if same DLL will work for it...
-
Ok, have tested and seems that it works fine. If not let me know...
-
just thinking, users will go further and maybe modify registry...damn. They are like rats!
-
No - they won't - our PC's are locked down... :)
I'll certainly have a good look at this - thanks!
Tony
-
No prob, hope it helps you :) I owe you many ones ;)
-
Cavagnaro, is it easy enough to set a default application, host etc. using that .dll method?
-
This version only disables setting of the [color=blue][b]Port[/b][/color] number but yes, it would be good to have some "versions" to disable the [color=blue][b]Host[/b][/color] - and perhaps the [color=blue][b]Application[/b][/color], too... but perhaps separately (i.e. 3 different .dll's...) m??
-
So, you need:
1 to disable port
1 to disable port and host
1 to disable port, host and application fields
Right?
Gimme a couple of hours, I already have the HEX map so wouldn't be difficult.
-
Hi,
Ok work done.
Enjoy :D
-
Quick question. I get how this process works for current users. You switch the dll and the application is locked down however what happens for new users?
New users haven't entered the application name, host or port so its not stored on the PCs reg. How do we enter those?
Ta
-
[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
-
Hehe no prob Tony, hope this is usefull for you all!
One one, remember this DLL was a 7.6 version, so should work fine on 7.5 and 7.6 enviroments, however I have not done any tests on 7.X versions previous and 8.X, so please be aware.
[quote]Quick question. I get how this process works for current users. You switch the dll and the application is locked down however what happens for new users?
New users haven't entered the application name, host or port so its not stored on the PCs reg. How do we enter those?
[/quote]
As Tony has described and was my previous concern, this data is stored on the registry, so follow Tonys instructions and you will do it all nice.
Lol, I have even personalized the logos and icons of the app...also now can change some texts...nice.
-
If ever we needed a solution sticky in this forum... *cough@Tony* ;)
-
[quote author=cavagnaro link=topic=3298.msg13952#msg13952 date=1222201156]
Lol, I have even personalized the logos and icons of the app...also now can change some texts...nice.
[/quote]
Put your monkey avatar instead of the app logo ;D
-
hackers :-X
:)>
-
what? oh no no no, we are only guys who adapt a software for a better use of it. ;D
-
...and then we bury it, in code.... lol
-
So did it work for you Tony?
-
I think it will.... updating the Registry Keys to ensure you have the correct Host/Port set - then updating the UniLogin.dll to lock them down are fairly straightforward steps...
I'd call it a "winner"...! :)
Tony
-
:D Nice! Glad I helped you