RB_adcom
asked on
The java fiasco on older domains
So given the blanket recomendation by our friends at homeland security to disable java is there a quick fix in the domain environment?
We predominantly have left java to do its thing, neither installing or uninstalling it.
We primarily supports sbs 2003 domains but have 2003 standard and 2008.
Browser enforcement has been left to client end users as the majority of our clientele have a mix of reasons they require particular browsers.
Is there a quick (preferably GPO type deployment) to blanket enforce browser policies (disable IE all together where possible)? Protect Firefox where possible, and create enough trust in chrome to deploy it?
Is there an easy policy that will initiate a removal of all java versions from machines unless they are necessary for client applications?
We primarily run one of the SEP security solutions where customers are willing.
We predominantly have left java to do its thing, neither installing or uninstalling it.
We primarily supports sbs 2003 domains but have 2003 standard and 2008.
Browser enforcement has been left to client end users as the majority of our clientele have a mix of reasons they require particular browsers.
Is there a quick (preferably GPO type deployment) to blanket enforce browser policies (disable IE all together where possible)? Protect Firefox where possible, and create enough trust in chrome to deploy it?
Is there an easy policy that will initiate a removal of all java versions from machines unless they are necessary for client applications?
We primarily run one of the SEP security solutions where customers are willing.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER