03-29-2005 06:10 AM - edited 03-09-2019 10:46 AM
Is there a way to deploy the CSA to users and have them not know about it? i don't want them to see the icon or the pop ups....
thanks
Steve Luciano
03-29-2005 11:30 AM
"No user interaction" on the client kit default group should do it.
03-30-2005 05:03 AM
Can you tell me where to find this? i've search groups and policies and haven't been able to find No user interaction.
thank
03-30-2005 09:43 PM
It is in the Group setting - look for a check box near where the Polling Interval is defined and the Test Mode box is located.
Let us know if you cannot find it and we'll post a screen shot.
thanks
peter
05-12-2005 05:01 PM
Hi there!,
I've got an interesting problem. What if I had two user groups deployed with CSA agent. User group A is an admin group and User group B is a normal user group. User group A has rights to access the agent (red flag icon) and User Group B doesn't have (no red flag for them). If I disabled the User Interaction rule in Rule 608 under the All Windows Group, everyone gets affected. This group appears to be Global. But yet at the same time I only want Group A to have rights to the red flag icon. I found out the only way to work around this is to create a seperate UI control policy. Turn off the 'All Windows Groups' UI control rule, then insert my *new* UI control Policy(with User interaction checkboxes ON) into Group A, but NOT in group B. So hence Group A retains precedence of UI control 'On', but because Group B does not have the *new* UI control policy and is still governed by the All Groups UI control being off; Group B remains off.
Uhh..anyone get what I mean? Is there a better way of doing this? It seems CSA has a precedence for the 'ON' controls/rules over the 'OFF' controls/rules.
04-01-2005 01:19 AM
At which level you would like to hide csa installation? How far should this hiding go?
With no user interaction they will still get a popup during installation that csa installer has disabled a/v on access scanner(e.g. McAfee) and as far as i remember correctly one popup indicating that the machine should be manually rebooted (or if checked reboots with countdown to autoreboot popup). In addition to this at the end of the installation the user could notice the new red flag of the csa TSR in taskbar. That`s the deal.
04-01-2005 05:58 AM
peter
thanks, i found it. i am going to deploy it to see how it will appear, if at all, to the user.
thanks again
05-05-2005 11:23 PM
Hi,
I've got an interesting problem. What if I had two user groups deployed with CSA agent. User group A is an admin group and User group B is a normal user group. User group A has rights to access the agent (red flag icon) and User Group B doesn't have (no red flag for them). If I disabled the User Interaction rule in Rule 608 under the All Windows Group, everyone gets affected. This group appears to be Global. But yet at the same time I only want Group A to have rights to the red flag icon. I found out the only way to work around this is to create a seperate UI control policy. Turn off the 'All Windows Groups' UI control rule, then insert my *new* UI control Policy(with User interaction checkboxes ON) into Group A, but NOT in group B. So hence Group A retains precedence of UI control 'On', but because Group B does not have the *new* UI control policy and is still governed by the All Groups UI control being off; Group B remains off.
Uhh..anyone get what I mean? Is there a better way of doing this? It seems CSA has a precedence for the 'ON' controls/rules over the 'OFF' controls/rules.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide