Install Shield Silent 响应文件（.iss 文件）是否依赖于登录用户权限
Is the Install Shield Silent response file (.iss file) login user rights dependent
所以我有一个场景，我正在使用 ISS 文件在 windows 系统上安装 oraclexe 实例。
它适用于所有具有 "Administrator"(localadmin) 权限的机器。
但是它在域用户登录时失败（这些登录是管理员组的一部分）。
当我在那台机器上单独安装 oracle 时，我们安装得很好。
我怀疑安装程序响应文件是旧的并且可能记录在管理员登录中。
有没有这种可能。
Application Repackaging: In corporate settings one often resorts to application repackaging to deal with legacy setup.exe
setups, and this is usually exactly because of their problematic
behavior in silent installation scenarios. I describe this process
here:
How to monitor and log manual installation
(section "Capture / Repackaging").
Technical Details: At a technical level Application Repackaging is shockingly simple in its approach. It involves scanning the system
before install and after the install and then capture the changes,
clean out a lot of junk settings and wrap the finished, new installer
in an MSI package (or some other format). Despite the technical
simplicity, the quality of such packages depend a lot on the knowledge
of its creator. Badly packaged MSI files can be loose cannons.
Package Format: Application Repackaging can be done in various formats, but the established MSI format (Windows Installer) has
a number of benefits for corporate use centering around reliable silent running and reliable remote management - arguably the
most important aspects of corporate deployment. Please see this answer
for some more details:
How to create windows installer.
Once you have an MSI you install it silently using standard
msiexec.exe command lines.
Tools: Commercial tools Advanced Installer and Installshield are the most well-known repackaging tools. They are
quite pricey. Sometimes people pay deployment consultants to do the
single package they have to convert. Very advisable in terms of the
knowledge needed to succeed as well. List of repackaging tools from
installsite.org.
Technical Limitations: Repackaging has limitations. Localization (support for different language versions) is one problem area - you capture the English version, so where are the
German files for the German version? That kind of stuff. These issues
are always different from setup to setup. It is reverse engineering to
be honest. Also, dynamically generated content that is
machine and user specific such as license keys, certificates, database connection strings with machine names and similar means you
might have to do a lot of work to get things to operate correctly, and
sometimes it is even technically impossible. It is a black art, but
when done right MSI files of excellent quality results that deploy
silently without much drama.
(Re)Packaging Team: Many corporations have whole teams dedicated to capturing and preparing legacy and modern setups for large scale
deployment. Many of them are offshore and unknown to most employees. I
would check if your company has such a team.
日志记录？：日志文件说明了什么？这是遗留的 setup.exe 安装程序还是在后台安装 MSI 文件？我还会检查 系统的事件日志 以寻找任何线索 - 特别是如果您没有良好的日志文件。应该在同一目录中创建一个默认的 Setup.log 文件，并且与响应文件具有相同的名称（扩展名除外）。
/f2参数可用于指定不同的日志路径：
setup.exe /s /f2"C:\Setup.log"
这是一篇关于静默安装主题的 Flexera 文章：https://resources.flexera.com/web/pdf/archive/silent_installs.pdf
最常见的带有日志记录命令行的静默安装：
setup.exe /s /f1"C:\sample\uninstall.iss" /f2"C:\sample\uninstall.log"
Response Files：老实说，静默响应文件从来都不可靠实现静默运行ning。经常发生的是弹出一个从未记录在响应文件 运行 中的特殊对话框，然后一切都崩溃了。这可以是 "low disk space" 警告或其他任何形式的意想不到的随机对话，没有人预料到会出现。
意外对话：因此，当您作为管理员组成员的域用户安装时，确实会出现一些不同的东西，尽管我真的想不出有什么特别的东西可以作为可能的候选人出现在脑海中。我想这个问题也可能是特权和访问权之一。例如，在标准用户列表中可能有某些 NT 权限被拒绝的帐户。所有只是理论，我会去记录日志以获得一些具体的开始。
Installshield Help File:
There are several relevant sections in the Installshield help file.
Please study these if you need more tweaking of the installation parameters. All switches are documented here - these links are for
the 2018 edition of Installshield:
- Setup.exe and Update.exe Command-Line Parameters (Basic MSI, Installscript MSI)
- Advanced UI and Suite/Advanced UI Setup.exe Command-Line Parameters (Suite Projects)
部分链接:
- Create MSI from extracted setup files
所以我有一个场景，我正在使用 ISS 文件在 windows 系统上安装 oraclexe 实例。 它适用于所有具有 "Administrator"(localadmin) 权限的机器。 但是它在域用户登录时失败（这些登录是管理员组的一部分）。
当我在那台机器上单独安装 oracle 时，我们安装得很好。 我怀疑安装程序响应文件是旧的并且可能记录在管理员登录中。 有没有这种可能。
Application Repackaging: In corporate settings one often resorts to
application repackagingto deal with legacysetup.exesetups, and this is usually exactly because of their problematic behavior in silent installation scenarios. I describe this process here: How to monitor and log manual installation (section "Capture / Repackaging").Technical Details: At a technical level Application Repackaging is shockingly simple in its approach. It involves scanning the system before install and after the install and then capture the changes, clean out a lot of junk settings and wrap the finished, new installer in an MSI package (or some other format). Despite the technical simplicity, the quality of such packages depend a lot on the knowledge of its creator. Badly packaged MSI files can be loose cannons.
Package Format: Application Repackaging can be done in various formats, but the established
MSI format(Windows Installer) has a number of benefits for corporate use centering aroundreliable silent runningandreliable remote management- arguably the most important aspects of corporate deployment. Please see this answer for some more details: How to create windows installer. Once you have an MSI you install it silently usingstandard msiexec.exe command lines.Tools: Commercial tools Advanced Installer and Installshield are the most well-known repackaging tools. They are quite pricey. Sometimes people pay deployment consultants to do the single package they have to convert. Very advisable in terms of the knowledge needed to succeed as well. List of repackaging tools from installsite.org.
Technical Limitations: Repackaging has limitations.
Localization(support for different language versions) is one problem area - you capture the English version, so where are the German files for the German version? That kind of stuff. These issues are always different from setup to setup. It is reverse engineering to be honest. Also,dynamically generated contentthat ismachine and user specificsuch as license keys, certificates, database connection strings with machine names and similar means you might have to do a lot of work to get things to operate correctly, and sometimes it is even technically impossible. It is a black art, but when done right MSI files of excellent quality results that deploy silently without much drama.(Re)Packaging Team: Many corporations have whole teams dedicated to capturing and preparing legacy and modern setups for large scale deployment. Many of them are offshore and unknown to most employees. I would check if your company has such a team.
日志记录？：日志文件说明了什么？这是遗留的 setup.exe 安装程序还是在后台安装 MSI 文件？我还会检查 系统的事件日志 以寻找任何线索 - 特别是如果您没有良好的日志文件。应该在同一目录中创建一个默认的 Setup.log 文件，并且与响应文件具有相同的名称（扩展名除外）。
/f2参数可用于指定不同的日志路径：
setup.exe /s /f2"C:\Setup.log"
这是一篇关于静默安装主题的 Flexera 文章：https://resources.flexera.com/web/pdf/archive/silent_installs.pdf
最常见的带有日志记录命令行的静默安装：
setup.exe /s /f1"C:\sample\uninstall.iss" /f2"C:\sample\uninstall.log"
Response Files：老实说，静默响应文件从来都不可靠实现静默运行ning。经常发生的是弹出一个从未记录在响应文件 运行 中的特殊对话框，然后一切都崩溃了。这可以是 "low disk space" 警告或其他任何形式的意想不到的随机对话，没有人预料到会出现。
意外对话：因此，当您作为管理员组成员的域用户安装时，确实会出现一些不同的东西，尽管我真的想不出有什么特别的东西可以作为可能的候选人出现在脑海中。我想这个问题也可能是特权和访问权之一。例如，在标准用户列表中可能有某些 NT 权限被拒绝的帐户。所有只是理论，我会去记录日志以获得一些具体的开始。
Installshield Help File:
There are several relevant sections in the Installshield help file. Please study these if you need more tweaking of the installation parameters. All switches are documented here - these links are for the 2018 edition of Installshield:
- Setup.exe and Update.exe Command-Line Parameters (Basic MSI, Installscript MSI)
- Advanced UI and Suite/Advanced UI Setup.exe Command-Line Parameters (Suite Projects)
部分链接:
- Create MSI from extracted setup files