Difference between revisions of "Microsoft EMET"
From WPKG | Open Source Software Deployment and Distribution
(Update for 4.1 U1) |
(fixed upgrade process and path weirdness) |
||
| Line 11: | Line 11: | ||
<packages> | <packages> | ||
| − | <package id="emet" name="Microsoft EMET 4.1 Update 1" revision=" | + | <package id="emet" name="Microsoft EMET 4.1 Update 1" revision="7" reboot="false" priority="50"> |
<variable name="pkgstring" value="EMET 4.1 Update 1"/> | <variable name="pkgstring" value="EMET 4.1 Update 1"/> | ||
<variable name="pkgpath" value="EMET 4.1U1"/> | <variable name="pkgpath" value="EMET 4.1U1"/> | ||
| + | <variable name="pfpath" value="EMET 4.1"/> | ||
<variable name="configpath" value="%SOFTWARE%\%pkgpath%\prod-20140521.xml"/> | <variable name="configpath" value="%SOFTWARE%\%pkgpath%\prod-20140521.xml"/> | ||
| Line 21: | Line 22: | ||
<install cmd="msiexec /qn /i "%SOFTWARE%\%pkgpath%\EMET Setup.msi""/> | <install cmd="msiexec /qn /i "%SOFTWARE%\%pkgpath%\EMET Setup.msi""/> | ||
| − | <install architecture="x64" cmd="%PROGRAMFILES(x86)%\% | + | <install architecture="x64" cmd="%PROGRAMFILES(x86)%\%pfpath%\EMET_Conf.exe --import "%configpath%""/> |
| − | <install architecture="x86" cmd="%PROGRAMFILES%\%pkgpath%\EMET_Conf.exe --import "%configpath%""/> | + | <install architecture="x86" cmd="%PROGRAMFILES%\%pfpath%\EMET_Conf.exe --import "%configpath%""/> |
| + | |||
| + | <upgrade cmd="msiexec /qn /i "%SOFTWARE%\%pkgpath%\EMET Setup.msi""> | ||
| + | <exit code="0" /> | ||
| + | <exit code="1638" /> | ||
| + | </upgrade> | ||
| + | <upgrade architecture="x86" cmd="%PROGRAMFILES%\%pfpath%\EMET_Conf.exe --import "%configpath%""/> | ||
| + | <upgrade architecture="x64" cmd="%PROGRAMFILES(x86)%\%pfpath%\EMET_Conf.exe --import "%configpath%""/> | ||
| − | |||
| − | |||
<remove cmd="msiexec /qb /x{6A09FEB2-691C-456B-B982-2F6D21B19602}"/> | <remove cmd="msiexec /qb /x{6A09FEB2-691C-456B-B982-2F6D21B19602}"/> | ||
Revision as of 15:33, 22 May 2014
Enhanced Mitigation Experience Toolkit 4.1 Update 1
This is a silent installer to deploy EMET 4.1 Update 1 and load a custom policy as specified in %configpath%. If you don't want to create a custom policy, EMET comes with sample policies in %PROGRAMFILES(x86)%\EMET 4.1 Update 1\Deployment\Protection Policies.
The EMET GUI is a 32-bit program, but EMET itself works on 32- and 64-bit machines.
Download EMET and its user's guide at http://www.microsoft.com/en-us/download/details.aspx?id=41138
<?xml version="1.0" encoding="UTF-8"?>
<packages>
<package id="emet" name="Microsoft EMET 4.1 Update 1" revision="7" reboot="false" priority="50">
<variable name="pkgstring" value="EMET 4.1 Update 1"/>
<variable name="pkgpath" value="EMET 4.1U1"/>
<variable name="pfpath" value="EMET 4.1"/>
<variable name="configpath" value="%SOFTWARE%\%pkgpath%\prod-20140521.xml"/>
<check type="uninstall" condition="exists" path="%pkgstring%"/>
<!-- N.B. this does not implement checking to see if your policy is loaded! -->
<install cmd="msiexec /qn /i "%SOFTWARE%\%pkgpath%\EMET Setup.msi""/>
<install architecture="x64" cmd="%PROGRAMFILES(x86)%\%pfpath%\EMET_Conf.exe --import "%configpath%""/>
<install architecture="x86" cmd="%PROGRAMFILES%\%pfpath%\EMET_Conf.exe --import "%configpath%""/>
<upgrade cmd="msiexec /qn /i "%SOFTWARE%\%pkgpath%\EMET Setup.msi"">
<exit code="0" />
<exit code="1638" />
</upgrade>
<upgrade architecture="x86" cmd="%PROGRAMFILES%\%pfpath%\EMET_Conf.exe --import "%configpath%""/>
<upgrade architecture="x64" cmd="%PROGRAMFILES(x86)%\%pfpath%\EMET_Conf.exe --import "%configpath%""/>
<remove cmd="msiexec /qb /x{6A09FEB2-691C-456B-B982-2F6D21B19602}"/>
</package>
</packages>