ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Comparing MeshCentral 2 to ScreenConnect

    IT Discussion
    remote access screenconnect meshcentral meshcentral 2 connectwise control connectwise
    39
    980
    216.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Scott Banned
      last edited by Scott

      How does the Power State graph work?

      I have several clients that show "Device is powered from 12:00:00 AM to 3:50:00 PM" for today May, 22; however, the agent is not connected and the machine icon shows "Last seen: 5/22/2019, 12:57:30 PM" or "Last seen: 5/21/2019, 7:59:00 PM"

      Looking at the graph, the machine has been connected all day, however elsewhere it indicates the machine was last seen last night.

      Edit: To follow up, another computer has full bars on the 7 Day Power State: "Device is powered from 12:00:00 AM to 12:00:00 AM" For 5/16, 17, 18, 19, 20, 21 and for today 5/22, it says, "Device is powered from 12:00:00 AM to 9:26:43 AM." yet the device icon says last seen 5/17/2019, 11:12:22 AM.

      S 1 Reply Last reply Reply Quote 0
      • S
        smartkid808 @Scott
        last edited by

        @Scott said in Comparing MeshCentral 2 to ScreenConnect:

        How does the Power State graph work?

        I have several clients that show "Device is powered from 12:00:00 AM to 3:50:00 PM" for today May, 22; however, the agent is not connected and the machine icon shows "Last seen: 5/22/2019, 12:57:30 PM" or "Last seen: 5/21/2019, 7:59:00 PM"

        Looking at the graph, the machine has been connected all day, however elsewhere it indicates the machine was last seen last night.

        Edit: To follow up, another computer has full bars on the 7 Day Power State: "Device is powered from 12:00:00 AM to 12:00:00 AM" For 5/16, 17, 18, 19, 20, 21 and for today 5/22, it says, "Device is powered from 12:00:00 AM to 9:26:43 AM." yet the device icon says last seen 5/17/2019, 11:12:22 AM.

        I have the same issue. Been meaning to ask but kept forgetting.

        1 Reply Last reply Reply Quote 0
        • YlianY
          Ylian
          last edited by

          On the power timeline... yes yes... I need to fix this. One thing that would help is to download the power timeline raw data (The "Download Power Events" button on the top right of the power lines display) and make sure the raw data is correct. If it is, it's just me drawing it wrong. If it's not, I need to go fix something deeper in the server. Feedback on this would be appreciated.

          S 1 Reply Last reply Reply Quote 1
          • S
            smartkid808 @Ylian
            last edited by smartkid808

            @Ylian said in Comparing MeshCentral 2 to ScreenConnect:

            On the power timeline... yes yes... I need to fix this. One thing that would help is to download the power timeline raw data (The "Download Power Events" button on the top right of the power lines display) and make sure the raw data is correct. If it is, it's just me drawing it wrong. If it's not, I need to go fix something deeper in the server. Feedback on this would be appreciated.

            Hi Ylian

            Not a big issue for me, but please let me know what I can do to help you out!. Here is a screenshot. Its been off since the 17th, but showing on 24/7. I can email you or whatever you need. Any additional files/exports/logs.

            a400ec98-7a2a-460f-b7f3-a8e289db840c-image.png

            Time	 State	 Previous State
Fri May 17 2019 17:53:28 GMT+0000 (UTC)	1	
Sun May 19 2019 04:53:31 GMT+0000 (UTC)	0
            YlianY 1 Reply Last reply Reply Quote 1
            • YlianY
              Ylian @smartkid808
              last edited by

              @smartkid808 Wow, yes, you got it just right. The saw data and the graph don't match at all. I will work on this...

              1 Reply Last reply Reply Quote 3
              • S
                Scott Banned
                last edited by

                Is anyone else running into an issue whereby running the installer on Windows causes two entries to be made in list of machines? One shows agent is connected, other does not.

                Identically named machines show up in nodes listing: Owner-HP, or User-Laptop, etc.

                This does not happen with all installs, but has on last several.

                JaredBuschJ S 2 Replies Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @Scott
                  last edited by JaredBusch

                  @Scott said in Comparing MeshCentral 2 to ScreenConnect:

                  Is anyone else running into an issue whereby running the installer on Windows causes two entries to be made in list of machines? One shows agent is connected, other does not.

                  Identically named machines show up in nodes listing: Owner-HP, or User-Laptop, etc.

                  This does not happen with all installs, but has on last several.

                  Never seen that. But I have seen a second connection show up later a few times.

                  1 Reply Last reply Reply Quote 0
                  • S
                    smartkid808 @Scott
                    last edited by smartkid808

                    @Scott said in Comparing MeshCentral 2 to ScreenConnect:

                    Is anyone else running into an issue whereby running the installer on Windows causes two entries to be made in list of machines? One shows agent is connected, other does not.
                    Identically named machines show up in nodes listing: Owner-HP, or User-Laptop, etc.
                    This does not happen with all installs, but has on last several.

                    I have never seen it, but I did see that when I installed it (unattended) and also ran it (ad-hoc connection). I was just curious what would happen if I did that. Hopefully Ylian has some insight.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      Scott Banned @smartkid808
                      last edited by

                      @smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:

                      @Scott said in Comparing MeshCentral 2 to ScreenConnect:

                      Is anyone else running into an issue whereby running the installer on Windows causes two entries to be made in list of machines? One shows agent is connected, other does not.
                      Identically named machines show up in nodes listing: Owner-HP, or User-Laptop, etc.
                      This does not happen with all installs, but has on last several.

                      I have never seen it, but I did see that when I installed it (unattended) and also ran it (ad-hoc connection). I was just curious what would happen if I did that. Hopefully Ylian has some insight.

                      Did one show up as connected and the other not?

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        smartkid808 @Scott
                        last edited by

                        @Scott said in Comparing MeshCentral 2 to ScreenConnect:

                        @smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:

                        @Scott said in Comparing MeshCentral 2 to ScreenConnect:

                        Is anyone else running into an issue whereby running the installer on Windows causes two entries to be made in list of machines? One shows agent is connected, other does not.
                        Identically named machines show up in nodes listing: Owner-HP, or User-Laptop, etc.
                        This does not happen with all installs, but has on last several.

                        I have never seen it, but I did see that when I installed it (unattended) and also ran it (ad-hoc connection). I was just curious what would happen if I did that. Hopefully Ylian has some insight.

                        Did one show up as connected and the other not?

                        Both showed as online

                        1 Reply Last reply Reply Quote 0
                        • dafyreD
                          dafyre
                          last edited by

                          I had my first chance to really use the remote control bits. I was helping someone out, and my system kept dropping the desktop connection, and the client would disappear from the group.

                          A few seconds later, it would show back up and I could connect again. The disconnection seemed random. One time I'd work 5 minutes, and the next, I'd lose the connection after 30 seconds.

                          Has anybody else seen anything like that?

                          scottalanmillerS 1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @dafyre
                            last edited by

                            @dafyre said in Comparing MeshCentral 2 to ScreenConnect:

                            I was helping someone out, and my system kept dropping the desktop connection, and the client would disappear from the group.

                            No, not seen that.

                            1 Reply Last reply Reply Quote 0
                            • YlianY
                              Ylian
                              last edited by Ylian

                              If you see random drops, you may have a router/proxy/firewall with short idle connection timeouts. Add this to the "settings" section of config.json and restart your MeshCentral server.

                              "AgentPing": 60

                              This will cause the server to "ping" (within the TCP/TLS control channel) the agent every 60 seconds and have the agent replay. That may fix it. If it does, try "AgentPong": 60 instead, that will cause the server to send a pong every 60 seconds and the agent will not reply, so cuts idle traffic by half. Then, you can also try longer time between ping/pong commands.

                              It's also possible your agent is on a wireless network and the network keeps dropping.

                              Let me know if that works.
                              Ylian

                              dafyreD 1 Reply Last reply Reply Quote 2
                              • dafyreD
                                dafyre @Ylian
                                last edited by

                                @Ylian said in Comparing MeshCentral 2 to ScreenConnect:

                                If you see random drops, you may have a router/proxy/firewall with short idle connection timeouts. Add this to the "settings" section of config.json and restart your MeshCentral server.

                                "AgentPing": 60

                                This will cause the server to "ping" (within the TCP/TLS control channel) the agent every 60 seconds and have the agent replay. That may fix it. If it does, try "AgentPong": 60 instead, that will cause the server to send a pong every 60 seconds and the agent will not reply, so cuts idle traffic by half. Then, you can also try longer time between ping/pong commands.

                                It's also possible your agent is on a wireless network and the network keeps dropping.

                                Let me know if that works.
                                Ylian

                                I have this setting in place. I'll let you know if it works the next time I use it.

                                1 Reply Last reply Reply Quote 0
                                • YlianY
                                  Ylian
                                  last edited by

                                  Perfect thanks. By the way, I have been doing a bunch of updates to MeshCentral, much of it is community driven from GitHub, latest updates on Twitter: https://twitter.com/meshcentral. Just added optional User Session Idle Timeout an hour ago.

                                  MC2-IdleTimeout.png

                                  1 Reply Last reply Reply Quote 3
                                  • S
                                    smartkid808
                                    last edited by

                                    One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.

                                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                                    • JaredBuschJ
                                      JaredBusch @smartkid808
                                      last edited by

                                      @smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:

                                      One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.

                                      Per machine is a horrible idea for anything with a tool like this.
                                      Per group is where this type of setting should be.

                                      As for your thought. Make an issue. I don't see one for this feature request.
                                      https://github.com/Ylianst/MeshCentral/issues

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        smartkid808 @JaredBusch
                                        last edited by

                                        @JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:

                                        @smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:

                                        One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.

                                        Per machine is a horrible idea for anything with a tool like this.
                                        Per group is where this type of setting should be.

                                        As for your thought. Make an issue. I don't see one for this feature request.
                                        https://github.com/Ylianst/MeshCentral/issues

                                        Yea, group sounds better.. Will do.. tnx

                                        1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller
                                          last edited by

                                          If things like that are going to be by group, I think we need way more powerful group management. Right now, we heavily limit the use of groups because it is a pain to have any number of users and groups because you have to add and remove people from every group.

                                          JaredBuschJ 1 Reply Last reply Reply Quote 0
                                          • JaredBuschJ
                                            JaredBusch @scottalanmiller
                                            last edited by JaredBusch

                                            @scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

                                            If things like that are going to be by group, I think we need way more powerful group management. Right now, we heavily limit the use of groups because it is a pain to have any number of users and groups because you have to add and remove people from every group.

                                            That means MC is useless. No tool like this should be lacking group controls. I group by Client because not all techs need access to all clients. Some clients have different settings than others. One client requires consent on connect, one wants only the pop up, one doesn't care, etc.

                                            Adding users to groups is actually a problem I made an issue for a while back.
                                            https://github.com/Ylianst/MeshCentral/issues/185

                                            Since then, two more related issues for controlling things with groups and users.
                                            https://github.com/Ylianst/MeshCentral/issues/210
                                            https://github.com/Ylianst/MeshCentral/issues/256

                                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 37
                                            • 38
                                            • 39
                                            • 40
                                            • 41
                                            • 48
                                            • 49
                                            • 39 / 49
                                            • First post
                                              Last post