Announcement

Collapse
No announcement yet.

New RMM Issue with Jobs Gone

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • New RMM Issue with Jobs Gone

    Ok, I know these are changes that were made. Here is the issue with taking the jobs away. When you run a procedure you have NO update or status of the procedure itself. I can't tell if it is running or finished or stuck.

    This is a MAJOR issue when you are working 'blind' and running it against multiple computers. I think the last update took the product back to the start again. I was almost at 100% going to Comodo until this update. I am back to the testing phase again and now starting to look at other options that are starting up in the next month or two.

    Please let me know your solution to this issue or if Job / Procedure status will be coming back.

  • #2
    Hello doveroh

    I have forwarded this as a feature request/feedback in regards to the Jobs/Procedures.
    We will get back to you with am answer to your question.

    Comment


    • #3
      Ethan I noticed that when I run a procedure that nothing is even happening on my end points. I did a test with just a file transfer as a procedure and it still hasn't transfered 3 hours later. I did a manual transfer with no issue.

      This last update is causing major headaches for me, I don't know about anyone else, but if it is an issue for other people, please speak up or let me know how you are handling procedures and cleanups.

      Comment


      • #4
        Hello doveroh ,

        We have just tested this on our environment and the issue did not reproduce. What we did:
        - Created a new Procedure from scratch > File Transfer > "Type source file path here..." we tested with C:\log.txt then "Optional - Type destination file path here..." we input E:\
        Run procedure > a pop-up with a session came up, connecting to that endpoint > the file appeared on the E:\ drive in a couple of seconds. Closed the session after this finished "END".

        If the issue still persists for you then please email c1-support@comodo.com with the logs from both the machine on which the RMM Console is installed and also the Agent logs from the affected machine.

        For the console logs:
        1. Navigate to: C\Program Files (x86)\COMODO\RMM Administration Console or to C\Program Files\COMODO\RMM Administration Console
        2. Edit dbg_config.ini: change Level=7 to Level=15
        3. Wait for the issue to reproduce and then collect Logs from:
        C:\Program Files (x86)\COMODO\RMM Administration Console\logs or C:\Program Files\COMODO\RMM Administration Console\logs

        For the agent logs:
        1. Navigate to:
        C\Program Files (x86)\COMODO\Rmm Agent Service or to C\Program Files\COMODO\Rmm Agent Service
        2. Edit dbg_config.ini: change Level=7 to Level=15
        3. Wait for the issue to reproduce and then collect Logs from: C:\Program Files (x86)\COMODO\Rmm Agent Service\logs or C:\Program Files\COMODO\Rmm Agent Service\logs

        Comment


        • #5
          John I ran it from within a session itself. It just disappears and there is no status update for me that says if it completed or anything.

          Comment


          • #6
            John doveroh I can confirm the same. Running a procedure from outside a session does not work, it opens up a session but does not run procedure Running the procedure from manually from within in a session works but you don't get any confirmation that it has.

            Another issue I am seeing within the session windows is that the default System Inventory tool never deploys it just sits at "Loading - Waiting for client to deploy tool"

            Comment


            • #7
              Hello doveroh snoopwoody ,

              If the issue still persists for you then please email c1-support@comodo.com with the logs from both the machine on which the RMM Console is installed and also the Agent logs from the affected machine.

              For the console logs:
              1. Navigate to: C\Program Files (x86)\COMODO\RMM Administration Console or to C\Program Files\COMODO\RMM Administration Console
              2. Edit dbg_config.ini: change Level=7 to Level=15
              3. Wait for the issue to reproduce and then collect Logs from:
              C:\Program Files (x86)\COMODO\RMM Administration Console\logs or C:\Program Files\COMODO\RMM Administration Console\logs

              For the agent logs:
              1. Navigate to:
              C\Program Files (x86)\COMODO\Rmm Agent Service or to C\Program Files\COMODO\Rmm Agent Service
              2. Edit dbg_config.ini: change Level=7 to Level=15
              3. Wait for the issue to reproduce and then collect Logs from: C:\Program Files (x86)\COMODO\Rmm Agent Service\logs or C:\Program Files\COMODO\Rmm Agent Service\logs

              Comment


              • #8
                John doveroh

                An update from me. I've restarted the workstation I'm running the Administration Console on and procedures now run ok. Maybe the restart force an update of the console?

                Comment


                • #9
                  Hello snoopwoody

                  Thank you for the update. Did you try to restart the console as well prior to the computer restart to see if that helps?

                  Comment


                  • #10
                    Hi Ethan yes I did but it was only when I restarted the workstation that it started working

                    Comment


                    • #11
                      Any ideas on how to get the status of a procedure your ran to see if it completed or not?

                      Comment


                      • #12
                        Hello doveroh

                        Unfortunately for the moment there is no way you can see the status of a procedure.
                        However this case has already been escalated, and we will get back to you as soon as we have a resolution.

                        Comment

                        Working...
                        X