[AccessD] Inno Scripts

[John Colby]

As luck would have it:
1) ATM we are selling into a single company.  However this will change soon
we hope.
2) The company likes us and the product, and we have communication paths
into the company.  We really need their cooperation anyway because we need
to install in specific paths etc, and we do need to write to the registry.
3) We have about 10 Beta users, one of whom was an ex IT / networking guy.



On Mon, Nov 1, 2021 at 7:20 AM Bill Benson <bensonforums at gmail.com> wrote:

> I can check with our IT group but from what I have been led to believe,
> none of our computers can have software installed other than through SCCM
> unless the users are an admin on their machine, and HKLM is off limits.
>
> I would be quite surprised to find out otherwise. For sure they would want
> to know if they don’t already so nothing lost by asking I guess.
>
> Being dead wrong twice in a single morning before 7 AM is unusual for me
> but not completely unheard of.
> :)
>
>
> On Mon, Nov 1, 2021 at 4:57 AM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
>
> > On 1 Nov 2021 at 3:58, Bill Benson wrote:
> >
> > > Running that script without elevated rights will be interesting to see
> > > how it goes. Testing on your own machine, where you more than likely
> > > do have such rights could lead to mistaken impression it will run for
> > > your customers when possibly it will not. So hopefully you have some
> > > beta testers on hand who can be your eyes on the ground before you get
> > > too far into making it all perfect. We generally require powershell
> > > and it has to be set up by IT to get most registry things to happen.
> > >
> >
> > That's all handled by one line in the script :)
> >
> > [Setup]: PrivilegesRequired
> > Valid values:
> >  admin, or lowest
> > Default value:
> >  admin
> >
> > Description:
> > This directive affects whether elevated rights are requested (via a User
> > Account Control
> > dialog) when the installation is started.
> >
> > When set to admin (the default), Setup will always run with
> administrative
> > privileges and in
> > administrative install mode. If Setup was started by an unprivileged
> user,
> > Windows will ask
> > for the password to an account that has administrative privileges, and
> > Setup will then run
> > under that account.
> >
> > When set to lowest, Setup will not request to be run with administrative
> > privileges even if it
> > was started by a member of the Administrators group and will always run
> in
> > non
> > administrative install mode. Do not use this setting unless you are sure
> > your installation will
> > run successfully on unprivileged accounts.
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting