Ranger remote control screen flickers on connect

[cookie_monster]

I'm sure that students can tell when a teacher connects as they will often suddenly close I.E or whatever when you double click to get a llook at the screen.

 

Has anyone else seen this and is there a setting to stop it?

 

RRC 9.1 with XP SP2.

 

Cheers.

[john]

Is ranger NetSupport School Rebranded or is that another one (I get confused over who buys whos and rebrands it!) But if its NetSupport based, there is a config file you can modify to stop the screen refresh on connect.

[cookie_monster]

It's just a rebadge. I thought i'd seen an option like that but i can't find it now, any chance you can point me in the right direction.

 

Cheers.

[AndyG]

There is a setting to stop the screen flicker on connect this is called silent mode. However this setting not in the user interface of the configurator.

 

To set silent mode, you will have to manually edit the client32.ini file and add the following to the [client] section

 

silent=1

 

after you save the client32.ini file you will have to checksum the file, to do this see Manually editing the Client32.ini file

[cookie_monster]

silent=1 is set in the client32.ini file and i can see that's the one that has been sent to the stations but i'm sure the students get some kind of tip off that a teacher has connected.

[boomam]

Does the student toolbar pop up on connect?

I found that that was a new 'feature' of NSS v9.

[cookie_monster]

Nope i've got that turned off.

 

I've tried this again in a few rooms and i think it's only on the older PC's and it's not every time, i think what happens is of you catch the PC while it's busy it gets bogged down.

[boomam]

How do you deploy NSS?

We do it via GPO here and find on our older workstations that used to run 8.5x that it'd install 9.0 along side it, and it caused nothing but problems.

 

Might be worth checking out?

[cookie_monster]

We had 8 in a couple of rooms but when we upgraded to 9 (deployed via GPO) it seemed to delete all of the version 8 files and replace them.

 

How did you solve your issues?

 

Cheers.

[boomam]

My issues wernt the same as yours, i was thinking that the cause could be the same though?

 

Manual uninstall of both versions of NSS and then manual install of v9 + manual copy of client32.ini & the licence file.

 

After that the problems i was having went away.

[Lithium]

How do you deploy NSS?

We do it via GPO here and find on our older workstations that used to run 8.5x that it'd install 9.0 along side it, and it caused nothing but problems.

 

Might be worth checking out?

 

Why not install the full Tutor client and use the NSS Deploy tool?

 

That's how I've been doing it.

 

From that tool I can deploy to computers I want from a list, remove it, send out a new license file and modify the client configuration when I like.

 

It even can do it while students are logged on

[cookie_monster]

I can do all that using the deploy tool the only problem with that is that it gets forgotten when stations are rebuilt and then you have missing clients and no one reports it untill they're in the middle of a class and trying to use it.

 

I like the station build process to be as automated as possible.

[cookie_monster]

Anyone know if there is a quick way to view a client? I'm looking for a way like Dameware which instantly brings up the browse list and allows you to connect straight away as long as the client is installed. It's a pain having to open the console and sit watching it browsing for clients for ages.

[boomam]

How do you deploy NSS?

We do it via GPO here and find on our older workstations that used to run 8.5x that it'd install 9.0 along side it, and it caused nothing but problems.

 

Might be worth checking out?

 

Why not install the full Tutor client and use the NSS Deploy tool?

 

That's how I've been doing it.

 

From that tool I can deploy to computers I want from a list, remove it, send out a new license file and modify the client configuration when I like.

 

It even can do it while students are logged on

The deploy app is nice when i started using it.

But trying to keep settings constant throughout the network without having to use the deploy app each time is a pain, along with a multitude of other problems i was having with it.

So GPOs to to deploy the software, along with a licence/client32 file and it all goes so much more smoother for me.

[boomam]

Anyone know if there is a quick way to view a client? I'm looking for a way like Dameware which instantly brings up the browse list and allows you to connect straight away as long as the client is installed. It's a pain having to open the console and sit watching it browsing for clients for ages.

Cancel the browse, it should have remembered the clients from before, but they do appear offline. Just click on them to connect.

 

Or setup a known list, that way it knows the clients already and only connects to them rarther than doing a network client scan.

 

.

[cookie_monster]

We have nearly 300 PC's so i can't have them all in the console and a known list won't really work when i'm just trying to quickly connect to one random PC quickly.

[boomam]

Seperate them into groups then?

Thats what i do. Works well enough for me. .

[cookie_monster]

I tried that but maybe i'm doing it wrong.

 

If i do that they all still have to be listed in the default 'All' group so when i click refresh it still browses for all 300 clients.

[boomam]

If you have a known list it doesnt have to browse, just connect to the computers it already knows are there, which is FAR quicker.

Does about 5-6 computers per second for me like that.