Locking Down CCPulse...?

[tony]

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

[Adam G.]

Tony,

On those network segments where the CCP users are you could alter the DNS lookup of the Config Server........

Pavel

[cavagnaro]

If using a Firewall you can ask them that those networks can't access that port on Genesys server.

[tony]

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

[S]

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...

[tony]

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

[Tefleon]

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! 

[tony]

hmmm.... Genesys suggested Registry Updates to lock it down - but it can still be changed on the login screen...

[Tefleon]

Which one are you looking at doing?

[tony]

I'll let you know once I've worked it out...!

[BenTaylor]

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

[tony]

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

[Scottyjohn]

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?

[tony]

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

[cavagnaro]

So Tony, which solution did you ended up using?