Windows Installer Cleanup Instructions for version 6
Introduction
This document describes how to cleanup a machine so that it'll appear to be a clean machine to future 6.x client installs.
This document assumes that you were able to successfully uninstall BOINC via the add/remove control panel applet.
In addition to the information stored via normal MSI operations the BOINC installer makes the following additional changes depending on the options selected during install:
- Creates two additional user accounts
- Creates three local user groups
- Assigns user rights to newly created users
- Stores setup information to the registry
- Migrates existing data from the installation directory to the data directory
Cleanup Users and Groups
To cleanup the newly created users and groups do the following:
- Click on the 'Start' button.
- Right-click on 'My Computer' and select 'Manage'.
- Expand the 'Local Users and Groups' tree node.
- Click on the Groups tree node.
- Delete the 'boinc_admins' group.
- Delete the 'boinc_users' group.
- Delete the 'boinc_projects' group.
- Click on the Users tree node.
- Delete the 'boinc_master' user account.
- Delete the 'boinc_project' user account.
Windows XP Home (and possibly Vista Home?) does not have the Local Users and Groups tree, we need to do it differently here:
- Click on the 'Start' button.
- Click on 'Programs'.
- Click on 'Desktop-Accessories'.
- Click on 'Command Prompt'.
- In the command prompt window that opened, type:
- net localgroup boinc_admins boinc_master /delete (press Enter).
- net localgroup boinc_projects boinc_project /delete (press Enter).
- net localgroup boinc_admins /delete (press Enter).
- net localgroup boinc_users /delete (press Enter).
- net localgroup boinc_projects /delete (press Enter).
Cleanup User Rights Assignments
To cleanup the newly assigned user rights do the following:
- Click on the 'Start' button.
- Click on 'Control Panel'.
- Launch the 'Administrative Tools' control panel applet.
- Launch the 'Local Security Policy' application.
- Expand the 'Local Policies' tree node.
- Click on the 'User Rights Assignment' node.
Open each user right that contains an '*S-' style entry, and remove each entry that begins with '*S-'. Each '*S-' entry represents a user account that has been deleted from the system. Open each user right that (still) contains the boinc_master, boinc_admins, boinc_users or boinc_project rights assignments and remove those.
Windows XP Home (and possibly Vista Home?) does not have the Local Security Policy. It may be possible that you can remove the entries the installer made from the registry, but it's at this point unknown where it puts these entries in the registry.
Cleanup Setup Registry Entries
To cleanup the newly created registry entries do the following:
-
Launch 'regedit.exe' from the Start\Run menu item.
-
Expand the 'HKEY_LOCAL_MACHINE' entry.
-
Expand the 'Software' entry.
-
Expand the 'Space Sciences Laboratory, U.C. Berkeley' entry.
- Delete the 'BOINC Setup' entry.
- Delete the 'Space Sciences Laboratory, U.C. Berkeley' key.
-
Go back to the 'HKEY_LOCAL_MACHINE' entry.
- Expand the 'SYSTEM' entry.
- Expand the 'CurrentControlSet' entry.
- Expand the 'Services' entry.
- Delete the 'BOINC' entry, if it exists.
-
Go back to the 'HKEY_LOCAL_MACHINE' entry.
- Expand the 'Software' entry.
- Expand the 'Microsoft' entry.
- Expand the 'Windows' entry.
- Expand the 'CurrentVersion' entry.
- Expand the 'Run' entry.
- Delete 'boincmgr', if it exists.
- Delete 'boinctray', if it exists.
- Expand the 'Run-' entry.
- Delete 'boincmgr', if it exists.
-
Expand the 'HKEY_CURRENT_USER' entry.
-
Expand the 'Software' entry.
-
Expand the 'Space Sciences Laboratory, U.C. Berkeley' entry.
- Delete the 'BOINC Manager' entry.
- Delete the 'BOINC screensaver' entry.
- Delete the 'Space Sciences Laboratory, U.C. Berkeley' entry.
Exit regedit: File -> Exit.
Cleanup Migration of Data Files
Move all data files back into your installation directory from your newly created data directory.
Conclusion
After performing all the actions your machine should appear to be ready for a clean install to future attempts to execute v6 installers.