True, but IMHO the biggest issue with zap files is documented in the article kb231747 you refer to:
Non-MSI program can be published only to users, and are installed using their existing Setup programs. Because non-MSI programs use their existing Setup programs, these programs cannot:
• Take advantage of elevated privileges for installation.
ZAP files install with the user privileges. In most cases, you would have to make the user a local admin.
It also is only to be used at user level of the GPO, not computer level.
About where to find the kix executable (kix32.exe or wkix32.exe)
I only maintain one copy of the file in \\domain\netlogon (same as \\domain.ext\sysvol\domain.ext\scripts)
The paths I give are:
Script Name
\\domain.ext\sysvol\domain.ext\scripts\wkix32.exe
Script Parameters
\\domain.ext\sysvol\domain.ext\scripts\script.kix $INI="\\domain.ext\sysvol\domain.ext\scripts\script.ini" $Section="Package Name"
IMHO this makes the script and the executable much easier to maintain and you can use it over and over again for other policies. Just ad sections to the INI file per installation. Create a group policy per installation.
