SUF6NEWBIE
10-04-2004, 07:37 PM
When creating 'Installers' , under most circumstances,
full 'registry' and\or 'system files' access is required.
So this is just a REMINDER that if Target Operation System
includes any NT based system...
It is almost a certanty that if 'must run from an Administrative account'
is Not selected (is enabled by default for new Projects) , then
the odds that your 'setup.exe' will fail are HIGH.
This is a 'common oversight' until it is 'a build habit'.
Classic examples are the terrific 'Run-time' modules that
have been created by IR and 'detection scripts'
Most will FAIL if full system access is not available.
NOTE: when the 'admin account' runtime condition is Set,
if creating 'uninstall ability' ..the 'account permission condition' is
auto-adopted at build time...so keep this 'aspect' in mind.
I have posted this mainly for 'New Developers' , however
can't be stressed enough in my humble opinion.
full 'registry' and\or 'system files' access is required.
So this is just a REMINDER that if Target Operation System
includes any NT based system...
It is almost a certanty that if 'must run from an Administrative account'
is Not selected (is enabled by default for new Projects) , then
the odds that your 'setup.exe' will fail are HIGH.
This is a 'common oversight' until it is 'a build habit'.
Classic examples are the terrific 'Run-time' modules that
have been created by IR and 'detection scripts'
Most will FAIL if full system access is not available.
NOTE: when the 'admin account' runtime condition is Set,
if creating 'uninstall ability' ..the 'account permission condition' is
auto-adopted at build time...so keep this 'aspect' in mind.
I have posted this mainly for 'New Developers' , however
can't be stressed enough in my humble opinion.