DJ-1701 Posted June 8, 2017 Posted June 8, 2017 Have to say, I've just shown this to the Office Staff and they are very impressed. Again, thanks very much for this! 1
DJ-1701 Posted June 8, 2017 Posted June 8, 2017 i'm being dense here but where can I find the MSI file? Go to NetSupport Notify - Download a free 30 day trial and fill out the form stating your an existing customer and it will give you all the downloads you need. 2
Al_NetSupport Posted June 8, 2017 Author Posted June 8, 2017 Have to say, I've just shown this to the Office Staff and they are very impressed. Again, thanks very much for this! Always nice to hear positive feedback from the end users. Hope it's useful and saves everyone time. We're biased but it's a really handy tool. (Perhaps not a budget priority, but useful nonetheless). Al 1
fiza Posted June 8, 2017 Posted June 8, 2017 Go to NetSupport Notify - Download a free 30 day trial and fill out the form stating your an existing customer and it will give you all the downloads you need. Ahhh thanks. I was looking in the installation folder.
Tesla Posted June 8, 2017 Posted June 8, 2017 I have deployed the agent to a machine, but if i go to send a message, I cant see it, I can only see the server, anyone else seeing this? (I still cant get the server tool to work on our actual server here so it's just on my pc as a test...)
JordanT91 Posted June 8, 2017 Posted June 8, 2017 I still can't get this to work properly. I've installed the Server component on a server with key X (gets converted to Y) on port 443. I've installed the Agent and Console on my own PC but when I start the console and enter the IP address of the server, port and key (both X and Y) it says 'Incorrect server key'. Any ideas?
Matt_NetSupport Posted June 8, 2017 Posted June 8, 2017 I still can't get this to work properly. I've installed the Server component on a server with key X (gets converted to Y) on port 443. I've installed the Agent and Console on my own PC but when I start the console and enter the IP address of the server, port and key (both X and Y) it says 'Incorrect server key'. Any ideas? Hi JordanT91, I am sure it will be something simple but I will ask our support team to call you (If that is convenient) - we have you contact details. Matt
MkII Posted June 8, 2017 Posted June 8, 2017 I have deployed the agent to a machine, but if i go to send a message, I cant see it, I can only see the server, anyone else seeing this? (I still cant get the server tool to work on our actual server here so it's just on my pc as a test...) Same. Did you install via rdp? I did but then re-installed using mstsc /admin - still the same
Matt_NetSupport Posted June 8, 2017 Posted June 8, 2017 Hi Mark, I will ask Support to contact you as well. Matt
Emma_NetSupport Posted June 8, 2017 Posted June 8, 2017 I have deployed the agent to a machine, but if i go to send a message, I cant see it, I can only see the server, anyone else seeing this? (I still cant get the server tool to work on our actual server here so it's just on my pc as a test...) Hi Tesla, Support just tried calling but there was no answer. Is there a better time for us to try again, or if its easier please PM me a direct dial and I will pass it on Thanks, Emma
NetSupportTechSupport Posted June 8, 2017 Posted June 8, 2017 (edited) I still can't get this to work properly. I've installed the Server component on a server with key X (gets converted to Y) on port 443. I've installed the Agent and Console on my own PC but when I start the console and enter the IP address of the server, port and key (both X and Y) it says 'Incorrect server key'. Any ideas? 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. Edited June 8, 2017 by NetSupportTechSupport 1
MkII Posted June 8, 2017 Posted June 8, 2017 Wow - impressive support! (My problem was blocked activation on our LA upstream proxy - needed a manual key supplied by NetSupport) 1
fiza Posted June 8, 2017 Posted June 8, 2017 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. I've got the same issue. How do I change the port being used on the server?
NetSupportTechSupport Posted June 8, 2017 Posted June 8, 2017 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.
fiza Posted June 8, 2017 Posted June 8, 2017 (edited) 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. Thats sorted but where do I change the port on the Notify Consoles? Don't worry I found it. Edited June 8, 2017 by fiza
round2it Posted June 8, 2017 Posted June 8, 2017 Just want to say thankyou to netsupport for this great product. I plan to use it for a message of the day task along side the emergency notifications. Nice to see a company supporting schools The slt are impressed and this will be good for when we are looking for a new classroom support tool. Well done.. 3
Al_NetSupport Posted June 8, 2017 Author Posted June 8, 2017 Just want to say thankyou to netsupport for this great product. I plan to use it for a message of the day task along side the emergency notifications. Nice to see a company supporting schools The slt are impressed and this will be good for when we are looking for a new classroom support tool. Well done.. Really good to hear, and thank you taking time out to share the feedback, it's really appreciated. Al.
beany1 Posted June 9, 2017 Posted June 9, 2017 Thanks @Al_NetSupport for this, fantastic bit of software, it's going to be great for all staff bulletins. Just one thing, I'm noticing that when I send a message, quite a few of our users aren't shown, just the computer name. I did a test message to a computer name and on the message acknowledgement the username was filled in with the correct user, but when I went to send another message, even after refreshing it still only shows the computer name. Is this a limitation of the software, or is something wrong here?
round2it Posted June 9, 2017 Posted June 9, 2017 I have found a small delay in new installs being picked up but after a little while they show correctly
Al_NetSupport Posted June 9, 2017 Author Posted June 9, 2017 Thanks @Al_NetSupport for this, fantastic bit of software, it's going to be great for all staff bulletins. Just one thing, I'm noticing that when I send a message, quite a few of our users aren't shown, just the computer name. I did a test message to a computer name and on the message acknowledgement the username was filled in with the correct user, but when I went to send another message, even after refreshing it still only shows the computer name. Is this a limitation of the software, or is something wrong here? Morning @beany1 , thanks for the message and glad you like the software. In terms of use, NetSupport Notify is designed to be a device based alerting solution, so pulling up all your depts you can send messages to groups ( or all) devices across your network. When an alert is acknowledged at that point we record who the logged on user was. The product is not aimed to be an alert to users x, y & z. We do include an option for sending to a specific user ( singluar) where you are prompted to enter their User ID, but for normal use it's alerts to departments or groups rather than people. Hope that clarifies? Al. 1
fiza Posted June 9, 2017 Posted June 9, 2017 That's a shame. It would be good if you could target users ie all members of SLT no matter where they are logged on.
Al_NetSupport Posted June 9, 2017 Author Posted June 9, 2017 (edited) That's a shame. It would be good if you could target users ie all members of SLT no matter where they are logged on. Keep the faith @fiza Just playing with a couple of options. We can assign a device to a dept when a user logs in and can work with containers, so I reckon you could have your SLT staff when they sign into any PC, have the dept ID on that PC set to SLT - then when you send a message to dept SLT you know it's going to the devices wherever they are. Anyway, just testing before i confirm. Sometimes i get carried away. Give me 10 Al. Edited June 9, 2017 by Al_NetSupport 1
Al_NetSupport Posted June 9, 2017 Author Posted June 9, 2017 Just playing with a couple of options. We can assign a device to a dept when a user logs in and can work with containers, so I reckon you could have your SLT staff when they sign into any PC, have the dept ID on that PC set to SLT - then when you send a message to dept SLT you know it's going to the devices wherever they are. Anyway, just testing before i confirm. Sometimes i get carried away. Give me 10 Al. So the good news is I wasn't imagining things, due to the flexible way we interact with AD it is perfectly possible to achieve the behaviour you want @fiza and @beny1 - although i did get one of our much smarter than me techies to double check. It is possible using the User ADM or ADMX Template files supplied with NetSupport Notify to apply the Department name to a AD Security group. When importing the User ADM template file you will find a policy to define the Department name in the following location : User Configuration\Administrative Templates\NetSupport Notify\Agent Configuration\General\Department Details After enabling this policy to define the dept name you will need to ensure that this is just applied to your required AD Group ( i.e SLT Users), once you have performed this, whenever users from this group logon to a machine with the Notify Agent installed the policy will apply your department name to them and this will appear in the Notify Console. The below example shown was applied to a SLT User AD Group we setup as a test here: For the above example we applied a department name of SLT Users to the SLT AD group of users in our test domain. The Console then shows the Department name once these users logon and also includes their username as well as the PC name. Hope that Helps? Al. P.S thanks @NetSupportTechSupport for your help. 2
fiza Posted June 9, 2017 Posted June 9, 2017 @Al_NetSupport - Just tried it, works like you said. Thanks 1
Recommended Posts