which could not be accessed in post setup procedure. The silent setup script modified for diagnostics had a variable containing a mounted network drive. We saw this by testing with the domain admin group members account (intended for a silent setup via SSMS or Matrix42) by doing a login to the target machine. Why does the membership in "domain users" does behave differently from usage of the Administrator account itself?Īll related GPO policies concerning the user account control were set to allow an installation at administrator level wihtout prompting / "elevate without prompting", but it seems the elevation happens anyway and the elevation event breaks Then I had the idea to add this parameter to the script (that finally passes ALLUSERS=1 to the msiexec.exe) and the setup succeeds, software works fine for all users. But it works only for the Administrator himself. This exists both in the logfile created with the "domain admins" member account but also with the Administrator account.
found in the installation logfile this entry here: Then I did some research and it turns out that there is one optional parameter called ALLUSERS for script based setup.exe or msi file based setups. If I use the account called "Administrator" the result of the "silent setup" was ok. The result of the "silent setup" was defect and the behavior matches the "per user" installation. After a reboot this is gone and the application doesn't work for other domain users. In case the domain admin group member starts the applicatoin Windows 10 keeps the file registered (comdlg32.ocx) even ifĪnother user (member of domain users) logs on at the same machine.
other users can't use the software because some OCX are registered on a per-user base which leads to very very strange side effects. other users don't see the software in the list of installed programs However the installation doesn't finish correctly, two things happen on Windows 10 Enterprise from the DVD image 2016: The setup.exe passes some parameters to msiexec.exe including a log file location and it is called by a user who is member of the group "domain administrators". I am observing a strange behavior - we deploy an application which can be distributed with a silent setup.
0 kommentar(er)
