However, as long as you are an administrative user on the Windows server, we have a way around it. If you fail to use this specific account, you get the above error.Īs you can imagine, it’s not always good practice to give out these account details especially for external staff. The JSS installer (downloaded from the “My Assets” section of Jamf Nation) needs to be run by the full local administrator account, rather than a domain administrator or a network user given local administrator privileges. So, what am I talking about? Well, if you try to run a JSS installer on Windows with the wrong user you get this error message: This is another thing that I occasionally come across as an eternal consultant and keep forgetting the exact command needed to work around it, so externally accessible blog it is! Background In the first custom action i tried to set this value but that doesn't work and in the same function i am checking for admin privilege.Aka “It is recommended that you use an account that is a local administrator and run the JSS Installer with elevated permissions” But i didn't get when, where and how to set this property value to one. I have gone through some threads which tell to set MSIDEPLOYMENTCOMPLIANT=1. If i create a batch file and then right click and run as admin then installation is successful. Now as per my knowledge setup.exe launches the msi with admin privileged but on directly trying to install with msi the msi get launched with non elevated access.
When i run setup.msi by double click on WindowsXP, 64 bit machine with non admin user than it prompt that user need admin access and doesn't even goes to script. When i run setup.msi by double click on WindowsXP machine with admin user than installation success When i run setup.msi by double click on Windows7, 64 bit machine with admin user than i am not able to create the registry and installation fails. When i run setup.exe by double click on Windows7, 64 bit machine with admin user than installation success, if key get created successfully then i assume that installation is running in admin mode else i aborted the installation. To check the administrative access i create a key in HKEY_LOCAL_MACHINE. The package required administrator privilege to install. We used to create Single MSI and single EXE for installtion.
0 kommentar(er)
