Android devices contain a highly secure store of root certificates to help them verify if a server can be trusted, checking its certificate against these root certificates stored locally on the device.
If your CAC enabled web sites aren’t working as expected or you receive a security alert, the InstallRoot program (32-bit or 64-bit) can install certificates automatically for you.
InstallRoot is a Windows program that helps install DoD Certificates necessary for CAC enabled websites and DCMA. InstallRoot should be used by anyone having difficulty accessing DoD websites or who receive an error message saying their security certificate cannot be verified.
Advanced Uninstaller PRO can ensure that no traces are left after uninstalling InstallRoot by scanning your PC and deleting all associated files and folders related to InstallRoot. Furthermore, Advanced Uninstaller PRO offers to perform a cleanup to ensure all registry entries associated with InstallRoot have been completely eliminated from your computer system.
ROOT is available for Linux, Mac (beta release), and Windows platforms. If you would like to provide feedback to its maintainers please post to this discussion thread.
Installroot is a tool designed to create a certificate store with DoD certificates needed for PKI authentication with CAC enabled DoD websites. In order to use it effectively you must possess administrator access on your computer.
To install certificates manually, launch a Command Prompt window and navigate to where your download file resides (for instance ‘CD C:UsersJimDownloads’). Launch the installer, answering yes when asked for permission by Windows for changes on your computer. Depending on your system requirements you can download either 32-bit or 64-bit versions – 32-bit for older computers while 64-bit for modern systems.
Once a product is installed, an entry for it is added to INSTALLROOT’s software list – the top level installation path for all products and components – which you can view with the commpkg info command. Each of the entries in the software list also have unique mnemonics associated with them that you can see using commpkg info –listpackages command.
In this mnemonic, the first letter indicates whether or not a product is an operating system patch or in-place package upgrade; second letter denotes whether or not installation occurs in an alternate root; last two letters represent whether shared components that were installed along with this product reside in an alternate root (if applicable); this information helps in deciding what to verify using commpkg verify command with its various options.
The /etc/rc_install script runs before sulogin to provide job control to rc_install and keep the system read-only. Furthermore, this script runs before running /usr/bin/env LCFG (with no password set), so that any changes made in /etc won’t affect processes that are already running or user accounts that already exist.
The rc_install script invokes the start method of logserver component, initiating an HTTP daemon that serves log files and information about LCFG components for analysis and debugging of system. This feature provides insight into which components are running as well as any issues they’re experiencing – its importance being reported back to central reporting service for problems within system.
If you are having issues with installroot such as not being able to uninstall it or its files or it no longer running, troubleshooting it may be necessary. There are various techniques you could try such as reinstalling it or using System Restore; both could potentially help.
System Restore, included with Windows operating systems, allows users to easily restore their computer back to its previous state and uninstall programs which interfere with its proper workings. Before performing a System Restore operation, however, you should backup any personal files to protect against unexpected disaster.
If you cannot uninstall installroot manually or it does not appear in your list of programs and features in Control Panel, then it could be that the file used to create this entry has become damaged or missing due to malware infection, incorrect settings of file or virus that has changed file extensions. If this problem cannot be rectified manually then professional services may need to be hired in order to diagnose and recover corrupted registry entries as soon as possible and resolve them effectively.