• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The new installer always asks for Administrator permissions even if the user chooses to install in a location to which they have full permissions. This is despite the fact that in Advanced Installer I picked the option 'Admin level install if user in admin, user-level install otherwise'.

      I checked this with the Advanced Installer team, and it turns out that the option is somewhat badly named. What it actually does is perform an Admin-level 'All Users' install if it's possible to escalate to Admin, not just if the user is already Admin - this means that on Vista upwards you always get a request to escalate to Admin.

      In order to truly perform a user-level install we have to add an extra dialog to the installer to let the user choose whether to install for all users, or just for themselves.

            [SRCTREEWIN-599] Add installer option to perform user-level install

            Resolved as we now use Squirrel for the installer

            Mike Corsaro (Inactive) added a comment - Resolved as we now use Squirrel for the installer

            I know that some software asks the same question as your 1.5.2 installer does ('Do you want to allow the following program to make changes to this computer?' and show the fields to enter administrator name&password). If 'Yes', an administrator install is done (for all users); if 'No', a per-user install is done (if a folder was chosen for which the user has permissions).

            The SourceTree 1.5.2 installer unfortunately chooses to abort the install when 'No' was chosen.

            Granted, a per-user install is also 'making changes to this computer', but maybe the construct taken from other programs could be used as a work-around. Otherwise, the question is rather pointless: after all, why would anybody choose to start an installer if he/she does not want to make changes to the computer...

            looking-out-for-1.5.3-ishly yours,

            Roger

            Roger Erens added a comment - I know that some software asks the same question as your 1.5.2 installer does ('Do you want to allow the following program to make changes to this computer?' and show the fields to enter administrator name&password). If 'Yes', an administrator install is done (for all users); if 'No', a per-user install is done (if a folder was chosen for which the user has permissions). The SourceTree 1.5.2 installer unfortunately chooses to abort the install when 'No' was chosen. Granted, a per-user install is also 'making changes to this computer', but maybe the construct taken from other programs could be used as a work-around. Otherwise, the question is rather pointless: after all, why would anybody choose to start an installer if he/she does not want to make changes to the computer... looking-out-for-1.5.3-ishly yours, Roger

            Permission issue on Check For Updates also reported at SRCTREEWIN-639. As pointed out there another option would be to add a manifest for the Check For Updates program to require administrator permissions, if we can't get the per-user install working properly. Forum thread at Advanced Installer indicates that it's not quite as simple as first thought because of the download locations.

            Steve Streeting (Inactive) added a comment - Permission issue on Check For Updates also reported at SRCTREEWIN-639 . As pointed out there another option would be to add a manifest for the Check For Updates program to require administrator permissions, if we can't get the per-user install working properly. Forum thread at Advanced Installer indicates that it's not quite as simple as first thought because of the download locations.

            Another factor here is that if a user escalates to admin to install, the auto-update will not auto-escalate to admin to update, leading to 'Access Denied' errors. Raised with Advanced Installer here: http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=25994

            Steve Streeting (Inactive) added a comment - Another factor here is that if a user escalates to admin to install, the auto-update will not auto-escalate to admin to update, leading to 'Access Denied' errors. Raised with Advanced Installer here: http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=25994

              mminns minnsey
              sstreeting Steve Streeting (Inactive)
              Votes:
              23 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: