OLD installation of Adaxes

Question

Hello,

Where i'm actually working, it seems there is an "old dev" Adaxes environnement which was linked to the AD.

The server has been deleted now, but it seems the Windows Integration (for Password Self-Service) is still linked to that old server. Even if i install a fresh client.

Where those parameters came from a GPO i guess ?

Comments

I found a parameters in the Windows integration menu which allow me to set a priority. This worked fine and now i can see the parameters of my "new" Adaxes.

I don't have any notification in my tray about the enrollment (setted in Windows intégration) and the user get a policy associated.

any idea ?

---

Hello Alexandre,

Did you install Adaxes Self-Service Client on the computer that you are testing from? The notification will only appear on computers that have the Self-Service Client installed. Also, have you already enrolled for password self-service? The notification will appear only for users who haven't yet enrolled.

---

Yes the computer have the client installed and no i don't have enrolled for password yet.

---

Alexandre,

To help us troubleshooting the issue, can you enable Self-Service Client trace logging and send us the log file? To do this:

1. Launch Windows Registry Editor. Click Start, Run, type regedit, then click OK.
2. Locate the following registry key:
   [HKEY_LOCAL_MACHINE\Software\Softerra\Adaxes Self-Service Client]
3. Right-click the LogLevel entry and select Modify (create the entry if it does not exist).
4. In the Value data box, type 2 and click OK.
5. After logging is enabled, Adaxes Self-Service Client will log all events to file adaxeswinlogonextlog.txt located in the System32 subfolder of your Windows folder. Send the file to our support email (support[at]adaxes.com).

---

I edited the registry then reboot my computer, the popup finnaly appeared (i had previously reboot the computer after client install).

I will try on another computer to check if it's working correctly.

---

hello Alexandre,

If everything works fine after reboot, do not forget to disable the logging. For this purpose, set the LogLevel entry to 0.

---

What changes did you make in between the reboot and the registry to get it to work? I am still having the same issue.