msi install as system context error
Hi!
there is no problem installing msi with local administrator privileges. when installing as system context, the installation fails. help me please
Answers (3)
the error code 1603 can be caused by multiple issues, see here:
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-1603-during-installation-of-Autodesk-software.html
in addition some software (and Autocad is also known in some versions to be affected) needs admin rights for the install then SYSTEM is not sufficient.
Comments:
-
recommendations didn't help - alyam 3 years ago
The MSI is referencing a LOT of file system locations which don't normally exist for the "SYSTEM" profile and is possibly failing when trying to access/update something which doesn't naturally exist in the system profile context.
Without reading too deeply into the log, I see a lot of peculiar actions such as this,
MSI (c) (C8:F4) [23:32:35:703]: PROPERTY CHANGE: Adding USERPROFILE property. Its value is 'C:\WINDOWS\system32\config\systemprofile'.
MSI (c) (C8:F4) [23:32:35:711]: Dir (source): Key: payload.8.0.50727.193.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E , Object: c:\users\33229126\desktop\Windows\winsxs\5z1v718o.6n8\ , LongSubPath: Windows\winsxs\5z1v718o.6n8\ , ShortSubPath:
MSI (s) (FC:7C) [23:32:41:820]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
Does the MSI Transforms refer the environmental variable %USERPROFILE% somewhere?
Does the same behavior occur if you specify allusers=2 ? msiexec.exe /i "MSIPATH" /qn /norestart ALLUSERS=2
P.S.
I highly recommend CMTrace from the SCCM 2012 toolkit for reading through MSI log file data in a somewhat friendly manner.
Comments:
-
installation fails with allusers = 2
i didn't find variable %userprofile%. could you help?
msi+log uploaded https://drive.google.com/drive/folders/1wEke7UEf_tZrxuz1j7CKwdinvvrFQnGG?usp=sharing - alyam 3 years ago-
Unfortunately I can't offer a whole lot of insight as this point forward it gets very product specific and might not even be possible to do.
I looked at the admin guide for SKF @ptitude Analyst 2013, but it wasn't particularly useful and while it references the .MSI it doesn't make any references that would suggest they support any deployment methods.
I'd recommend reaching out the the application vendor to get advice.
When you install it as a named user, does it work for user accounts other then the one you installed it as? You may potentially have to run the install using a service account that has local admin rights on the workstations.
You can also try installing Orca and peeking at the MSI properties but that will be a fairly intensive and time involved task depending upon your experience level (not exactly a fun chore either) - Kiyolaka 3 years ago-
the developer gave the answer: install under the local admin entry
i need to create a deployment in sccm. system account context required - alyam 3 years ago
Are these machines domain joined? The best solution would be to provision a service account that has local administrator rights on the machine. Additionally unfiltering the admin token for it so its not subject to UAC prompts, would then use that specific service account for the deployment when I was learning sccm with 2012r2 you could make a package run as a specific user.
You could alternatively provision the account locally via script if a lot of your machines aren't going to have a LOS with a DC most of the time.
