NetSupportTechSupport

Hi @TIOAOA, The list of new features for NetSupport School 12.50 can be found on the following webpage: New Features - NetSupport School_Classroom management Software You will also receive a Software Release email if you have registered your details on the My Support area on: https://support.netsupportsoftware.com/register.asp and subscribed to the My Alerts section for your selected products. If you would like a full change log from NetSupport School 12.00.0030 to 12.50.0000 please pm your contact details and we will send you an email.

Hi, I wanted to post a quick to this thread to confirm that the above is possible when configuring the NetSupport School Tutor Console and setting the Room name. There are a couple of different ways to achieve this but the most common is to implement the machine based AD template files supplied with NetSupport School. Using the AD Template files you can apply a configuration to your Teacher machines with the Tutor Console installed in order to enforce the same configuration to all Teacher users that are logging on. If anyone would like assistance with this method please feel free to contact the support team at NetSupport and we will be happy to help. Best regards Andy

Hi @dapaulio I have raised an enhancement request internally with our development team for the ability to configure what features of the Notification console each operator has access to. I will attach the existing ticket that you have open with us to this request, we will then contact you should we have any updates on this request in the future. I hope this helps Adam

Hi @dapaulio could you please send us a PM with your contact details and we will then be in contact to advise further on this?

Thanks @SwedishChef, we will also update our own Knowledgebase with this information. If anyone needs any assistance or more information on this please contact us

I work in the support team at NetSupport and I would like to offer our assistance If you would like to contact the NetSupport support team direct on [email protected] or send us a PM with your details and we will be happy to help. Kind Regards, Silvana TechSupport Analyst NetSupport Ldt.

Hi @jgmitchell Apologies for the delay in making this guide available. If you would like to PM me your contact details I will then ensure that one of the techs on the support team here contact you and review the steps for rolling out the DNA Mac Agent with you. Best regards Andy

Hi @gumbygaz, when creating the GPOs for NetSupport School we normally create a high level GPO to cover all machines on the network that contains the Name and Connectivity Server (NCS) settings and any other general Tutor Console or Student settings you wish to apply to all machines. Then, at each room OU level the GPO you create only applies the required Room name. Using this method it is very easy to modify the high level GPO if you wish to change the Tutor and/or Student settings, or change the NCS connection details if you have had to move the NCS to a different server for any reason. Applying the NetSupport School high level GPO to machines that do not have NetSupport School installed will have no adverse effect on any other software or settings on the machine.

Thanks @LRSFC_DanJ, We are also currently completing a document to assist with the roll out of the DNA Agent to Macs, which we will make available shortly. Andy

Hi @LRSFC_DanJ, I work on the support team at NetSupport, if you would like to PM me your contact details I will be happy to also arrange for one of the techs here to contact you to assist with the deployment. Thanks Andy

Hi DavidYoung, Thank you for your post, I work in the support team for NetSupport. We are currently in the process of completing the deployment documentation for the Chrome and iOS DNA Agents. However if you would like to PM me your details I will be happy to ask for one the members of the support team to contact you and then review this with you? Best regards Andy

Hi Support will be contacting you directly, you will get a response from our support database Regards Tech Support

Hi Gongalong, I can confirm that it is possible to enable additional logging on the DNA Agent component that will help us to determine whether the Shutdown is related to NetSupport DNA. If you are still experiencing the issue with the machine shutting down please enable the DNA Agent logging following the instructions below: 1. Open regedit on the DNA Agent machine 2. Navigate to the following location (Note if the Logging key does not exist please create this): HKLM\Software\WOW6432node\NetSupport Ltd\NetSupport DNA\Logging\ 3. Please then create the two below registry values in the above location: Value name : Client Value : 1 Vale type : DWORD Value name : PowerMonitor Value : 1 Vale type : DWORD 4. Next restart the NetSupport DNA Agent service 5. This will then create two log files in the following location : C:\Program Files (x86)\NetSupport\NetSupport DNA\Client\ Client.log and PowerMonitor.log If you could leave the logging on overnight and then when the PC has shutdown please return the log files to us we will be happy to review this and confirm if there is a shutdown being sent from the DNA Server to the Agent? If you would like to contact the NetSupport support team direct on [email protected] or if you want to PM your contact details we will be happy to help. Logging for the Agent can then be disabled by either removing the two keys above or setting the values to 0 for both followed by a restart of the NetSupport DNA Agent Service. Best Regards

Thanks for letting us know @DJ-1701. If you come across anything else you need assistance with don't hesitate to email [email protected] to open a support call.

Hi @DJ-1701, please PM us your contact details and we can open a support call to resolve the issue you are seeing with the Notification Server.

Hi Jam_lane I have started a support call for this issue and a Support technician will be contacting you shortly.

Hi MrKJLS, If you would like to PM your contact details we will be happy to call you and review the 404 page not found message to help set this up with you. Thanks

Hi MrKJLS, Thank you for your post, in order to restrict access to who can send notifications for Notify you can setup Operators on your Notify Server. In order to perform this please logon to the machine hosting the Notification Server, here you will see the Notification Server icon in the system tray please right click and select Configure Connectivity Server. The Configure Connectivity Server utility will then appear select the Operators tab. Enable the second option "Specify operators permitted to send notifications". The click the add button and enter the Operator accounts. Then click Apply and OK to savet the changes. When you then next access the Web Console the operator details would then need to be included in order to connect to the Notification Server to send a notification. With regards to your second question concerning whether it is possible populate the Notify fields for when you open the Web Console, there are two methods to access the web console via a default.asp file or default.aspx file. When using the default.aspx file to access the Notify Web Console you can follow the below steps to populate the fields. 1. Select the Notify entry in the IIS Manager hierarchy 2. Double click on the Application Settings icon in the ASP.NET section 3. Double click each of the entries listed under the Application Settings and add the relevant information in the Value fields Gateway Address, Gateway Key, Gateway Port and Operator Note when using the .ASPX method to access the web console if you want to populate the Gateway Connection details you also have to include the Operator values to be predefined within the Application settings. However if you use the default.asp file to access the Web Console you can choose to Edit this file to populate the Notification Server connections details only without specifing the Operator details. When you access this page the Server details would be populated but the user would still need to enter their Operator details. If you would like any assistance with setting up the above please contact our support team on [email protected] and we will be happy to help.

Hi Paid_Peanuts, In response to the delayed installation time with Notify we would like to review this with you to help determine why this delay has occurred with the installation. If you would like to contact the NetSupport support team direct on [email protected], alternatively if you want to PM your contact details we will be happy to help. Best Regards

Hi @beany1. Please PM us with your contact details and we investigate the username issue you have seen when using the Notify Console.

Hi Fiza, To change the port used by the Notification Server, please follow the steps below: 1. Right click on the Notification Server icon in the system tray (globe icon) 2. Choose Configure Connectivity Server 3. The Configurator will then appear, ensure the General tab is selected 4. Here you will find a Port(s) field (should default to 443) 5. Enter the new port e.g. 3085 6. Click Apply and then OK I would then recommend to restart the Gateway32 service. Note once you have changed this on the Server you will need to update this on your notification Consoles and Agents. If you would like further assistance with this please contact our support team on [email protected] and we will be happy to help.

Further to our telephone conversation I am pleased to say that we were able to resolve the issue you were experiencing. To summarize: we discovered that the TCP port configured for the Notification Server to use was already in use by another program on the server. Changing the Notification Server port to 3085 (port is registered to NetSupport) and restarting the Gateway32 service allowed the Notification Server to bind to the port. This was confirmed by viewing the GW001.log file in the C:\Program Files (x86)\Common Files\NSL\Connectivity Server folder. Modifying the Notify Agent configuration using the AgentConfig.exe file enabled the Agent machine to connect to the Notification Server on port 3085.

Thank you DJ-1701, couldn't have said it better ourselves

Further to Al's comments regarding the Notify Web Console that you can add into your IIS Server, please find below the full instructions on using the default.asp or ASP.NET methods for configuring the Notify Web Console: There are two ways to configure the Notify Web Console depending on your security requirements. 1. default.asp When using the default.asp page you are required to enter all of the Notify Server details along with the username and password before you can send a message. This is not ideal as anyone that wishes to send a message needs to remember all of the information for all of the required fields. There is however a workaround when using the default.asp page that will enable you to store the Notification Servers IP address, port number and Gateway Key, so the user will only need to enter the username and password when they want to send a message. This workaround involves editing the default.asp page used for the ASP web interface so the Notification Server details are pre-configured on the page. If you wish to try this method please follow the steps below on the Notification Server machine: 1. Navigate to the NetSupport\NetSupport Notify\Web folder and locate the default.asp file 2. Make a copy of the default.asp file in case you need to restore it 3. Open the default.asp file in Notepad 4. Select Edit | Find and enter formfields then press Enter. This will take to the section of the code that we need to edit 5. Change the value="<%=Request("GWAddress") %>" to be value="[NotifyServerIPaddress]" i.e. value="192.168.1.1" 6. Change the value="<%=Request("GWPort") %>" to be value="[PortNo]" i.e. value="443" 7. Change the value="<%=Request("GWKey") %>" to be value="[GatewayKey]" i.e. value="testing123" 8. Do not change the entries for the Operator or Password fields 9. Save the changes to the default.asp file Now when you open the Notify web interface page you should see that the Gateway Address, Gateway Port and Gateway Key fields are already populated with the correct information. The user can now just enter the required information in the User Name and Password field to gain access to the Notify Web Console. 2. ASP.NET Using the ASP.NET component of the Notify Web Console will allow you to configure both the Notification Server connection details, and the username and password of the Operator to connect to the Notification Server. This is done using the following method in the IIS Manager on the server: 1. Select the Notify entry in the IIS Manager hierarchy 2. Double click on the Application Settings icon in the ASP.NET section 3. Double click each of the entries listed under the Application Settings and add the relevant information in the Value field 4. Double click the Default Document icon in the IIS section, select the default.ascx entry and use the Move Up option to move the default.ascx entry to the top of the list To use the ASP.NET method you will also need to have created an Operator entry on the Operators tab of the NetSupport Connectivity Server Configuration Utility window on the server. Ensure you click the Apply button after adding the Operator account to enforce its use on the Notification Server. You can access the window by right clicking on the NetSupport Connectivity Server icon in the System Tray and selecting Configure Connectivity Server. If you have any problems or questions please do not hesitate to contact us on [email protected]

Running the AgentConfig.exe file that you will find in the Notify installation directory will allow you to enter in the plain text value used when you created the Gateway Key during the Notification Server installation. The encrypted value for the Gateway Key will then be written into the Config.dat file located in the same folder as the AgentConfig.exe file. This encrypted value can then be copied and used in the Notify Agent GPO to apply the required Gateway Key value to the Notify Agent machines. Alternatively, you can contact us on [email protected] and we can provide our Encryption Utility to you to create the encrypted value.