Clarification. It is emet_conf.exe –refresh <-- There are two dash’s in front of refresh.
From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Friday, May 23, 2014 1:32 PM To: '[email protected]' Subject: RE: [NTSysADM] Chrome update and EMET. It has group policy extensions that you can use. Then you hit the machines with a startup script to run emet_conf –refresh. I just leave that start running all the time. If you don’t run that the GPO makes the registry changes but EMET never actually uses the changes. I fixed my 3000 chrome desktops with this method, deployed it that way…… From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ed Ziots Sent: Friday, May 23, 2014 12:52 PM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] Chrome update and EMET. Quick question on emet is there a central configuration that u can do with the utility to make it easier to deploy across an organization and keep the configuration on browsers in align with all other workstations? Ez On May 23, 2014 12:07 PM, "Jim Majorowicz" <[email protected]<mailto:[email protected]>> wrote: Jim, I'm not sure I've updated my Chrome install yet, but I'm not sure what you mean by opting out of Caller. Is there install notes somewhere that explains this in detail? On Thu, May 22, 2014 at 6:31 AM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: New Chrome update yesterday, it seems to require you opt chrome.exe out of Caller. Don’t forget EMET_Conf –refresh after you make the change.
