Changes between Initial Version and Version 1 of ClientSetupWinSix


Ignore:
Timestamp:
Jan 4, 2008, 10:12:21 AM (13 years ago)
Author:
romw
Comment:

Seperate Spec and Design Doc.

Legend:

Unmodified
Added
Removed
Modified
  • ClientSetupWinSix

    v1 v1  
     1= Windows Installer Specification v6 =
     2
     3[[T(VersionSix)]]
     4
     5[[PageOutline]]
     6
     7== Introduction ==
     8
     9BOINC version 6 for Windows is a big improvement in security. In order to take advantage of the increased security though, there needs to be some major changes to the installer.
     10
     11== Goals ==
     12
     13The goals of the installer for v6 are:
     14
     15 * Account-based sandboxing
     16 * Separate the data files from the executable files
     17 * Simplify installer experience
     18
     19== Account-based Sandboxing ==
     20
     21BOINC will now utilize the Windows users’ and groups’ functionality to control specifically who can execute and manage BOINC.
     22
     23Two user accounts will be created one for executing BOINC itself and one for executing the BOINC applications. Three local user groups will be created to handle to manage BOINC.
     24
     25== Executable/Data Separation ==
     26
     27Previous versions of BOINC on Windows stored the data files and executable files in the same directory structure which made managing permissions difficult.
     28
     29The installer will now need to create a new directory that will serve as the data directory.  The installer will migrate data files to the new data directory if they exist.
     30
     31== Simplify installer experience ==
     32
     33=== Welcome Screen ===
     34
     35Same as before.
     36
     37=== License Screen ===
     38
     39Same as before.
     40
     41=== Configuration Screen ===
     42
     43{{{
     44title: Installation options
     45subtitle: These are the current installation options
     46
     47Program directory:  [...]
     48Data directory:  [...]
     49
     50Use BOINC screensaver
     51Protected application execution
     52Allow all users on this computer to control BOINC
     53
     54
     55Click Next to use these options.
     56Click Advanced to customize options.
     57[Advanced] [Next]
     58}}}
     59
     60Advanced goes to the advanced configuration page.
     61Next goes to the Confirmation screen.
     62
     63=== Advanced Configuration ===
     64
     65{{{
     66title: Customize installation options
     67subtitle: Customize how BOINC is installed on your computer
     68
     69Program directory: [...] [Browse]
     70Data directory: [...] [Browse]
     71
     72[ ] Use BOINC Screensaver
     73[X] Protected application execution.
     74    This provides increased protection against faulty project applications.
     75    However, it may cause screensaver graphics to not work with older applications.
     76[X] Allow all users on this computer to control BOINC
     77[Next]
     78}}}
     79
     80Checkboxes labeled as [X] are enabled by default, otherwise they are disabled.
     81If any values are present from previous install, use them.
     82The "Allow users" checkbox is disabled unless the "Protected" checkbox is set.
     83
     84'Next' goes to 'Confirmation' screen.
     85
     86=== Confirmation Screen ===
     87
     88Same as before.
     89
     90== Discussion Topics ==
     91
     92* Why was the 'Launch BOINC on startup' option removed from the installer?
     93
     94The 'Launch BOINC on startup' option actually started the BOINC Manager, so on systems where BOINC was being installed as a service it was being ignored. Most people do not understand the difference between BOINC and the BOINC Manager. Most people who install BOINC want it to run whenever they are not around.
     95
     96To keep things simple we decided to remove the option and setup the system so that both BOINC and the BOINC Manager are started at system startup or logon, if the users want to change this behavior they can delete the BOINC Manager shortcut and/or change the service properties via the service control manager administrative tool.