EPDR and Autodesk desktop licensing service stop working

SiSmaSiSma
in WatchGuard EPDR/EDR/EPP

Using Autocad on a client with EDPR, Autodesk desktop service stop working with this message "Unable to connect with Autodesk desktop licensing service. Quit and restart Autocad 2025 to try to connect".
This issue are shown after 8.0.23.001 version was installed. As suggest from Autodesk, each path was excluded from EDPR scan and also EXE files but nothing change. Uninstalling EDPR solved the problem and Autocad back to run. Any suggestion to keep protection on?

Comments

  • David_CarroDavid_Carro WatchGuard Representative

    Hello, @SiSma

    Please open a case to support@watchguard.com with your customer name and ID, so we can provide troubleshooting for your query.

    Kind regards,

    David

    David Carro | Technical support
    WatchGuard Technologies, Inc. | www.watchguard.com

  • SiSmaSiSma
    edited October 18

    Hi, @David_Carro
    I did it two days ago and this is the hint that solved my problem (probably yes, I have no issue for the moment :# ):

    Please enter the following exceptions under the Code Injection exceptions in EPDR
    Here is where to add these exceptions:
    1. Navigate to "Settings" > "Workstations and servers".
    2. Select the profile that is being used.
    3. Expand "Advanced Protection".
    4. Scroll down to "Code Injection". These will need to be added under "Excluded processes" below "Code injection exclusions".
    5. After adding these you can save the changes

    Exceptions:
    • wscommcntr4.exe
    • acad.exe
    • revit.exe
    • adsso.exe
    • adsklicensingservice.exe
    • adpsdkutil.exe
    • adpclientservice.exe
    • adsklicensingagent.exe
    • adsklicensinginsthelper.exe
    • adskaccesscore.exe
    • adskidentitymanager.exe
    • adpclientservice.exe
    • adskaccessuihost.exe
    • adskupdatecheck.exe
    • adskaccessservicehost.exe
    • adskexecutorproxy.exe
    • lmgrd.exe

    Many thanks

  • David_CarroDavid_Carro WatchGuard Representative

    Hello,

    Exactly, that is the temp solution, but we have opened an RFE.
    Please provide your case number so I can add your case to the list of clients to be contacted after we find the definite solution.

    Thank you for your patience!
    David

    David Carro | Technical support
    WatchGuard Technologies, Inc. | www.watchguard.com

  • Daniel_MeyerDaniel_Meyer

    Same problem here at our customers. Please send a feedback here in this thread if the behavior is fixed. Thanks!

  • Angelo_Cabral_COBAAngelo_Cabral_COBA

    Hi, Same problem here. Please update. Thanks

  • David_CarroDavid_Carro WatchGuard Representative

    the workaround at this moment is to exclude the following processes from the Code Injection analysis:
    • wscommcntr4.exe
    • acad.exe
    • revit.exe
    • adsso.exe
    • adsklicensingservice.exe
    • adpsdkutil.exe
    • adpclientservice.exe
    • adsklicensingagent.exe
    • adsklicensinginsthelper.exe
    • adskaccesscore.exe
    • adskidentitymanager.exe
    • adpclientservice.exe
    • adskaccessuihost.exe
    • adskupdatecheck.exe
    • adskaccessservicehost.exe
    • adskexecutorproxy.exe
    • lmgrd.exe

    For updates on teh subject, please open a case with technical support, and you will be added to a list where all will be informed when solved.

    Kind regards,

    David

    David Carro | Technical support
    WatchGuard Technologies, Inc. | www.watchguard.com

Sign In to comment.