All - Many of you may be experiencing or have experienced issues with Expert Launcher. Please see fix and workaround options below until your firm can apply the Expert Launcher Update in mass.
--
Expert Launcher may have issues opening Expert Applications and error with InvalidCertificateException.
This specifically addresses firms running 8.2 EX0005-0007 or firms that upgraded to EX 0008+ but did not update the Expert launcher to the newer version.
Solution:
Have your IT team push out Expert Launcher from EX0009+
PLEASE NOTE:
We have made Expert Launcher available as a standalone download and is available from the myAderant Portal | Product Downloads | Aderant EXPERT - General | Expert 8.2.2.0 Update EX0009+ Launcher Only
it can be used by firms on 8220.EX0005, 8220.EX0006, EX0007, EX0008 or EX0009 who cannot launch applications from the Launcher and get an error message mentioning InvalidCertificateException
OR
Expert On-Prem Workaround(s):
Run applications directly
End users can run the applications directly (not using Launcher) or from Expert Assistant (not EA Pro as this uses Launcher). There are two places they can run applications directly:
- ExpertShare
- Local machine – i.e. C:\AderantExpert\<env>\Applications
OR
Registry key change on end-user machines
Users will be able to use the Launcher as normal if firms implement a registry key change that will ignore the fact the certificate is expired.
The key is:
- HKey_Local_Machine\Software\Aderant\Security\LauncherAllowUnsignedExecutables with a string value of "true"
Note: this change typically needs to be executed on a user’s local machine by IT staff.
Expert Sierra Workaround(s):
Registry key change on end-user machines
Users will be able to use the Launcher as normal if you implement a registry key change that will ignore the fact the certificate is expired.
The keys are:
- HKey_Local_Machine\Software\Aderant\Security\LauncherAllowUnsignedExecutables with a string value of "true"
- HKey_Local_Machine\Software\Aderant\Security\LauncherAllowDownloadFromPotentiallyUntrustedZones with a string value of "true"
Note: this change typically needs to be executed on a user’s local machine by IT staff.
Future action:
Firms that have implemented the registry key change will need to remove it when they upgrade to the latest available version of Launcher installs to prevent any possible security issues.