NetSupportTechSupport

Hello, from your provided steps it looks like it should be correctly setup, but the extension should only be deployed to the User OU. We do also have a full guide on getting this configured that can be accessed here: Centrally configuring and deploying the NetSupport DNA Agent extension for Google Chrome (TD).pdf However, if the steps in the guide match up to your current environment, then please send us an email with all the information on [email protected] and we can investigate this further with you and setup a remote session for review. Or you could always start a live chat with us here: https://netsupportsoftware.com/chat

Hi Daniel, I have emailed you from the ticket I raised in the Support database.

Good Morning @Space_Munkey, It does appear that your AV is the root cause. If you can DM me your details (name, contact email), I will be happy to assist in resolving this with you. Alternatively, please feel free to reach out to [email protected] or join our chat system on www.netsupportsoftware.com/chat and we will be happy to assist.

Hello vandos, I'm from the NetSupport Technical Support Team, if you can PM me your contact details or send your issue to [email protected] , we will be happy to assist. Daniel

Hi, I'm from the NetSupport Technical Team, if you can PM me your details or pop on our chat at: https://www.netsupportsoftware.com/chat , we will be happy to assist. we can talk you through this process and go through the options. We look forward to hearing from you and assisting further.

Hi, I'm from the NetSupport Technical Team, if you can PM me your details or pop on our chat at: https://www.netsupportsoftware.com/chat , we will be happy to assist. It may be a case that you require a Gateway Server, but we can talk you through this process and go through the options. We look forward to hearing from you and assisting further.

We received a report of this detection by Sophos at the end of last week and following this we have sent a false positive submission to Sophos for the NetSupport files that they had quarantined, and we hope that this will be resolved with them shortly. If anyone is continuing to experience any issues, please contact our support team and we will be happy to assist. Adam

Hi @allw If you could send us a PM with your contact details, we will be happy to contact you and troubleshoot this with you. Adam

Thank you for your reply. If you do see any issues when trying to install the DNA 4.70 software on the Windows Server 2019 please contact us on 01778 382272, https://www.netsupportsoftware.com/chat or email [email protected]

@AJWhite1970 Thank you for your message. We can confirm that NetSupport DNA 4.70 is supported on Windows Server 2019, we are sorry to hear that you are having a problem on your server. Would it be possible for you to PM us with your contact details so that we can arrange a remote session to assist you?

Hi @fera_lj , Windows 10 support was introduced in version 12.00 of NetSupport School so we would recommend using version 12.00 or above of NetSupport School on your Windows 10 machines, however, if you could send us a PM with your contact details, we will look into this further with you and investigate what's causing the issue. Adam

The NetSupport Notify Agent configuration can be applied using either the local Config.dat file (C:\Program Files (x86)\NetSupport\NetSupport Notify) or via a machine or user based GPO. Any Notify Server connection settings applied via the GPO will take precedence over the settings contained within the local Config.dat file. The Policy locations to check on the Notify Agent machine are: HKEY_CURRENT_USER\Software\Polices\NetSupport HKEY_LOCAL_MACHINE\SOFTWARE\Policies\NetSupport If you have any questions regarding the NetSupport Notify software please do not hesitate to contact us on [email protected]

Hi @zwilson50 Please could you send us a PM with your contact details? We will then be in contact to review this further with you. Thanks, Adam

Thought I would just post a quick reply to this thread in case anyone else is having similar issues. The issue with the installation above was caused by an incorrect install parameter being used for the installation. Once this was modified with the correct parameters, the installations then started going through as expected. If anybody else is experiencing similar issues, then please do not hesitate to contact us at [email protected] or send us a PM on Edugeek and we will be in touch. Adam

Hi @Fazza , Please could you send us a PM with your contact details and we will be in contact to review this further with you? Adam

Hi @Bev , @whartomt01 The DNA iOS/Chrome agent connects to the DNA Server on port 1743 via a Web Socket. The DNA Server listens on port 1743. The only filtering exception that we are aware of that will need adding is for port 1743 for the DNA server's local IP Address. It does appear as though there is filtering in place which is restricitng this traffic from reaching the DNA Server, however, we will need to confirm what this is. We have recently been reviewing some additional wireshark tracing which captures all packets on port 1743 from a specific IP address. As such, we would like to apply this to your DNA Server and one of the iOS/Chrome devices so we can determine at which point the the connection is failing at. I can see that you both have existing tickets with us regarding this so we will be in contact shorlty to advise on the steps that we would like to take. Adam

Hi @whartomt01 Please could you PM us your contact details and I will check the status of your ongoing support call? Thanks Adam

Hi all, Just wanted to clarify on this post for anybody else who may be looking and wanting to know the same question. It is possible to target machines that specific users are logged onto with the scheduled messages by configuring the Notify Agents to report their Active Directory OU as their department name. With this applied, when creating your scheduled message, you can then target the OU containing the desired users. When the scheduled time is then reached, the notification will be sent to any users that are a member of the specified OU and logged onto their machine. I hope this helps Adam

Thank you for getting in touch @disk I am pleased we were able to resolve the issue by configuring the tutor to use a direct TCP connection method rather than the default UDP browse, which appeared to be suppressed on the network. Adam

Hi @RiffRaff Thank you for providing the Support Tool files to us from the Tutor Console machine in question, and for letting us know that you have resolved the issue by locating the GPO in your AD that was applying the unnecessary settings on the Tutor machine. If you have other problems or questions please do not hesitate to contact us.

Hi @disk Please could you send us a PM with your contact details and we'll look into this for you? Thank you.

Hi @JordanT91 Please could you send us a PM with your contact details and we'll look into this for you? Thanks Adam

Hi nottsure Have PM you

Hi @dapaulio The licenses in NetSupport Notify are calculated on the Notification Server. It sounds as though the evaluation licence that is built into the Notify installer file that you are trying to run may have expired. Please could you send us a PM with your contact details and we will contact you and get this resolved. Thanks Adam

Hi @deano3693, I can confirm that we do have an enhancement request raised with our development team to be able to increase the number or combination of keys required to send the Emergency Response from the Notify Agent machine. This will help to eliminate any false triggers from the machines. I am unable to confirm a time-scale as to when the feature will be in the Notify software; however, we will keep you updated with any developments in this area.