Ranger Remote Control - Student Name Display

[BADGER10]

Hi,

 

We've recently installed RRC v10.1 onto our Network.

 

Our network consists of a mixture of Thin Clients (running Server 2003) and actual PC's (running Windows XP).

 

After browsing and midifying the known list, the TS sessions are shown by displaying the name of the user that is logged on. However, on the actual PC's their name is shown as the NetBIOS name of the machine.

 

I've searched the menus and looked through the manuals as best I can but I can not for the life of me find any option to edit it so they all have the same naming method - ideally this would be student log-on name for all.

 

In certain rooms we have a mixture of both Thin Clients and PC's so the teachers are asking for one generic naming method if possible.

 

Is there something obvious I have missed?

 

Thanks in advance

 

Darren

[Great_Scott]

Hi Darren

 

My boss - a bit of a wizard on Ranger - has suggested the following:

Try going to the Ranger Remote Control Panel>Help

This will open Help Topics: NetSupport School

On the Find Tab type "Planning and Installation"

In the resulting page there is a section on naming conventions.

 

Good luck mate, hope you get it sorted.

 

Craig

[Andrew_C]

Run the tutor programme.

 

Then School - Configuration - General tab

 

Insert a * in the "Control Name" field.

 

It then picks up the log-in name.

 

OK, now not sure, but don't have it on this machine! Fairly confident that that is where you need to be.

[john]

We just send a demand out for a register to classes and then once they all register it then changed the workstation name to name of the student.

[deanc]

one thing thats worth considering is that it is much easier from a teachers perspective to be able to select students based upon those that are in your room which is easier if the browse box shows ROOM9- instead of a username. though this will vary with how you have deployed thin client over fat.

 

remembering the names of the 300 students i teach over the course of a fortnight is a challenge let alone thier usernames, something made more difficult if two teachers are teaching the same year group at the same time tends to cause one of us to accidently select the others students.

 

this is one of my biggest complaints about RRCs support of thin client is that it is unable to memorise class lists because even if i create a list of students by selecting thier usernames it actually maps these to Server:port instead of looking for the username.

[Andrew_C]

I don't know how it would work on thin clients - never used them. But, RRC can be set up to only connect with sub-sets of PCs found on the network. Thus teacher in room B1-1...24* or B2-1...24* can be limited to that room, but the HoD or technician can connect to B*.

 

School - Configuration - Start Up and enter room prefix in the top box. B1* or B2*.

 

Security keys could be used to preclude one room controlling another, but this makes an overarching control by a technician more difficult.

[cookie_monster]

We found RRC to be very difficult to manage with thin clients and have stopped using it in favor of ABTutor. Unlike when using 'fat' clients RRC wouldn't pickup groups of thin clients in a room or group as all users appeared as their username, this meant that the teacher had to search out the users in their room and often ended up with users in other rooms by accident.

ABTutor allows you to create room groups even with thin clients and you can preset the group so the teacher doesn't even have to browse for clients.

Edited November 5, 2009 by cookie_monster