JC360 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Jc client installation and uninstallation guide =====
==== JC client installation ====
The description applies to the HCKU client. During installation, the installer creates files for JC in the directory of the user on whose behalf it runs. Administrator rights are not required for this, in Windows all files of the software are stored in AppData/Local folder, you do not need to have administrator rights to be able to overwrite this. It follows that if a user installs JC, it is only installed for that user, other users do not even see that it is installed (because it is not there). Addons/registry keys for browsers and other programs are not yet installed in this step. The installer automatically launches the client after installation, which normally pops up the login window, but still doesn't install the addons. (Here in parentheses, I note that there can be 2 exceptions, one case, which we just did for the Brazilian company, is that the installer automatically logs in the client, and the other case is that if JC was already installed and the personal files were not removed, then it might automatically log you in. In these cases, it might appear as if the extensions appear after installation, but it's actually only installed by the client.)

==== Running the JC client ====
After installation, the client is started by the installer and the login window pops up. As soon as the user logs in, the plugins are activated based on the rules and these plugins "install" the extensions they need. In the case of browsers, if there is a DOMCapture rule, the extension is installed, in the case of Outlook the addon. For this, the client first checks whether the user on whose behalf it is running is included in the administrators group and if it is included, then it tries to request a UAC prompt and restart with elevated rights, and then it can continue in two ways: \\
\\
•	**It has received admin privileges, so it runs in elevated mode** \\
In this case, you can write the HKLM branch of the Windows registry, which allows you to install plugins for browsers in such a way that the user cannot remove them (for this reason, no other program running in non elevated mode can remove them either). \\
\\
•	**The user has not received admin privileges/is not an admin** \\
In this case, the HKLM branch can be read at most, but not written into (or delete from there). However, you can do it with the HKCU branch, so you can enter the appropriate keys there so that the browser/Outlook automatically installs the plugin. I have to note here that browsers and Outlook work completely differently, in this description things are simplified from this point of view. (For example, we don't even write the HKLM branch for the Outlook add-in, but that's a matter of detail.)



==== Client uninstallation ====
Let's start with the non-obvious case first, then come the more special cases:
  * The user is not a local admin or does not allow UAC for either JC or the installer, installations (install/uninstall) and JC are run on the user’s behalf. There is nothing extra, the client only writes the HKCU registry branch, the installer can overwrite this, so it removes the extensions after the app uninstalation is succesful.
  * The user local admin, on his behalf, runs JC in elevated mode, but during uninstallation, the installer is also started in elevated mode. In this case, there is no problem either, the client also writes to the HKLM branch, but the installer also knows, so it removes it nicely - the extensions disappear.
Now comes the problematic cases:
  *  The user local admin starts JC in elevated mode, which modifies the keys under HKLM, but when uninstalling, the installer is no longer started with elevated mode. This is especially common and problematic, because the uninstall does not start automatically in elevated mode even when started from the control panel or the computer cases, so we notify the user with the following picture;
 
{{:use_cases:windows:picture1.png?400|}} \\
**The solution is in the text, the uninstallation should be run with elevated rights.**

  * The user is not a local admin, but JC was already started by another admin user in elevated mode. In this case, the user cannot do anything, since he is not a local admin, so he cannot remove the HKLM keys in any way (even with the removal tool). The local admin on the machine must uninstall JC in the appropriate way (2. method), only then will the HKLM keys disappear.

==== JC browser extension uninstallation with Reg edit ====

**Google Chrome;** \\
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist /v 7500 /f

**Microsoft Edge;** \\
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist \\
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\Extensions\obmlbfkihnobgbokahopnbaehffncfoe