May 10 2019 09:24 AM
Is this possible? When I googled this, there was a time where logon was part of the scheduling steps when deploying applications.
RunOnce is failing to install because it needs to be run as administrator. RunOnce simulates only double clicking the install .bat.
Any suggestion?
May 10 2019 09:37 AM
Solution@rockypabillore If you're deploying as an Application, on the User Experience tab of the Deployment Tab, make sure "Installation behavior" is "Install for system", then set "Logon requirement" to "Only when a user is logged on". If the installer requires user input, make sure "Allow users to view and interact with the program installation" is checked.
May 20 2019 02:16 PM
Why the requirement for installation at user logon?
May 22 2019 08:53 AM
Hi Ryan,
I finally got a work around. The security tool requires system installation so I added it to RunOnce HKLM key.
May 10 2019 09:37 AM
Solution@rockypabillore If you're deploying as an Application, on the User Experience tab of the Deployment Tab, make sure "Installation behavior" is "Install for system", then set "Logon requirement" to "Only when a user is logged on". If the installer requires user input, make sure "Allow users to view and interact with the program installation" is checked.