Narnian
February 2nd, 2007, 02:01
Hello!
I am having issues with how NetInstall handles security during installations. My users are just that, users, not admins or power users.
Many of the installations fail because they spin off processes that run under the local user context, not the NI service accounts, even though I check each line in the script (and the overall package properties) to use the service accounts during the installation. Even if I use the runas script option some processes manage to run under the local user account.
My workaround is to create a VBScript to run the silent setups and compile it in PrimalScript to an EXE with an embeded local admin (usually I use the NI Service or SIS account). Then it works file if I call my compiled EXE - the same processes stay running under the NI Service accounts.
The worst offenders are InstallShield based setups.
And thoughts/pointer/clues?
Running NetInstall 5.8, NI Service accounts are in the local administrators group.
Pax,
Richard
I am having issues with how NetInstall handles security during installations. My users are just that, users, not admins or power users.
Many of the installations fail because they spin off processes that run under the local user context, not the NI service accounts, even though I check each line in the script (and the overall package properties) to use the service accounts during the installation. Even if I use the runas script option some processes manage to run under the local user account.
My workaround is to create a VBScript to run the silent setups and compile it in PrimalScript to an EXE with an embeded local admin (usually I use the NI Service or SIS account). Then it works file if I call my compiled EXE - the same processes stay running under the NI Service accounts.
The worst offenders are InstallShield based setups.
And thoughts/pointer/clues?
Running NetInstall 5.8, NI Service accounts are in the local administrators group.
Pax,
Richard