Free School Alerting and Notifications offer from NetSupport

[Tesla]

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

 

 

 

Hi Emma

 

Sorry, I was here there and everywhere yesterday, just had one of your support ring me now and sort the issue.

 

Thanks!

 

 

 

For the record it was a port issue as mentioned previouslt, but also an old existing installation from 2015 of Net Support School was causing an issue, and we can't send messages less than 8 characters (they just don't appear at the agent's end), but he's looking into that.

Edited June 9, 2017 by Tesla

[DJ-1701]

...and we can't send messages less than 8 characters (they just don't appear at the agent's end), but he's looking into that.

 

Interesting... thanks for sharing, that might have explained why a couple of my test messages didn't work a few days ago.

[Tesla]

Interesting... thanks for sharing, that might have explained why a couple of my test messages didn't work a few days ago.

 

Apparently they had the same issue with someone else the other day, then today with me. Probably worth giving them details of your setup to see if they can find a link, as they haven't seen this issue before

[beany1]

@Al_NetSupport thanks, it's no problem, I'm really happy we can send all staff a bulletin.

 

The ability to have individual/pick certain people - message would of just been the cherry on top! We're a primary so departments wouldn't really work as most jobs are individual!

 

What I'm confused about is where you have said "once these users logon and also includes their username as well as the PC name." That happens...but not all the time. So i've currently got 27 clients connected, and I know all are logged in, but only 10 are showing username, the others are just computername.

[NetSupportTechSupport]

@Al_NetSupport thanks, it's no problem, I'm really happy we can send all staff a bulletin.

 

The ability to have individual/pick certain people - message would of just been the cherry on top! We're a primary so departments wouldn't really work as most jobs are individual!

 

What I'm confused about is where you have said "once these users logon and also includes their username as well as the PC name." That happens...but not all the time. So i've currently got 27 clients connected, and I know all are logged in, but only 10 are showing username, the others are just computername.

 

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

[drdos256]

"Apparently they had the same issue with someone else the other day, then today with me. Probably worth giving them details of your setup to see if they can find a link, as they haven't seen this issue before"

 

it might have been me - 15 characters is our limit - installed on a 2008r2 server...they hadn't heard of a limit before!

[Tesla]

"Apparently they had the same issue with someone else the other day, then today with me. Probably worth giving them details of your setup to see if they can find a link, as they haven't seen this issue before"

 

it might have been me - 15 characters is our limit - installed on a 2008r2 server...they hadn't heard of a limit before!

 

Possibly....we are also 2008 r2, and they said they'd query with the other school to see if this was the case there....

[Paid_Peanuts]

How long on average is it taking for you to install NetSupport Notify using the MSI?

It is taking upward of 20 mins here on our Windows 7 clients (i5, 8GB, SSD).

Nothing else we deploy via MSI is taking so long. Its the same wether we deploy using PDQ, GPO or simply running the MSI manually. In the same folder is the config.dat and NSN.ini

[mullet_man]

Just installed and tested on a couple of PCs.

 

I've totally not read back through previous messages so am sorry about that, but can we install on over 150 clients but only the first 150 that connect will work? Is that how it will work?

 

We've got more than 150 teacher laptops but doubt 150 teacher laptops will be on at any one time.

[Al_NetSupport]

Just installed and tested on a couple of PCs.

 

I've totally not read back through previous messages so am sorry about that, but can we install on over 150 clients but only the first 150 that connect will work? Is that how it will work?

 

We've got more than 150 teacher laptops but doubt 150 teacher laptops will be on at any one time.

 

Yes that's exactly how it will work.

 

Al

[Al_NetSupport]

How long on average is it taking for you to install NetSupport Notify using the MSI?

It is taking upward of 20 mins here on our Windows 7 clients (i5, 8GB, SSD).

Nothing else we deploy via MSI is taking so long. Its the same wether we deploy using PDQ, GPO or simply running the MSI manually. In the same folder is the config.dat and NSN.ini

 

Hi, I've asked support to jump in and assist.

 

Al

[NetSupportTechSupport]

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

[mullet_man]

Yes that's exactly how it will work.

 

Al

 

Awesome. Thats great.

[MrKJLS]

We are setting up the web console for a bunch of staff to use. Is there a way we can restrict the web console to certain people/ad logins?

[Al_NetSupport]

We are setting up the web console for a bunch of staff to use. Is there a way we can restrict the web console to certain people/ad logins?

 

Hi @MrKJLS thanks for the message. The simple ways are to either limit who has access to the web console page on your intranet or via NetSuport Notify itself, create operators on the gateway, so when someone wants to use the web console to send a message they have to enter their operator name and password to validate them before they send it.

 

I have spoken to the support team @NetSupportTechSupport and they are going to respond shortly with some other suggestions if you want to get a bit more technical with the ASP.

 

Al.

[MrKJLS]

Hi @MrKJLS thanks for the message. The simple ways are to either limit who has access to the web console page on your intranet or via NetSuport Notify itself, create operators on the gateway, so when someone wants to use the web console to send a message they have to enter their operator name and password to validate them before they send it.

 

I have spoken to the support team @NetSupportTechSupport and they are going to respond shortly with some other suggestions if you want to get a bit more technical with the ASP.

 

Al.

 

That's fine, can we pre-fill some of the boxes on the login form like the server box and the encyption key? We are using the ASPX version if thats makes any difference.

Edited June 12, 2017 by MrKJLS

[NetSupportTechSupport]

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.

[MrKJLS]

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.

Thanks, when we change the web console to the asp file the server says 404 page not found.

[NetSupportTechSupport]

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

[MrKJLS]

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

 

Thanks! I've pm'd my details to you

[JimHew]

Hi @Al_NetSupport, today SLT here have said they want to review security policies and this sounds ideal! We've got two Edugeek users here, and since you let a couple of other do it, can we get 300 total too please? We are going to go through with it anyway, but 300 would cover us nicely!

[Al_NetSupport]

Hi @Al_NetSupport, today SLT here have said they want to review security policies and this sounds ideal! We've got two Edugeek users here, and since you let a couple of other do it, can we get 300 total too please? We are going to go through with it anyway, but 300 would cover us nicely!

 

That sounds great timing @JimHew, every little helps in schools at the moment. if you PM me your details, i'll get one of the gang to sort the 300 but don't tell anyone else

 

Hope tesco won't get cross with me using their "every little helps" slogan !

[DJ-1701]

After having the Primary School praise this, I have just gone through the installation for @Boredguy's copy at the Secondary... but for some reason, although the client deployed to the machine (and so did the configuration) the NetSupport Connectivity Server Console is showing 0 Agent(s) connected out of the max 150.

[Tesla]

After having the Primary School praise this, I have just gone through the installation for @Boredguy's copy at the Secondary... but for some reason, although the client deployed to the machine (and so did the configuration) the NetSupport Connectivity Server Console is showing 0 Agent(s) connected out of the max 150.

 

Not the port issue mentioned in the thread beforehand is it? (unsure if you were in that part of convo....feeling too lazy to look!)

[NetSupportTechSupport]

After having the Primary School praise this, I have just gone through the installation for @Boredguy's copy at the Secondary... but for some reason, although the client deployed to the machine (and so did the configuration) the NetSupport Connectivity Server Console is showing 0 Agent(s) connected out of the max 150.

 

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.