Ranger Solo
Extending the reach of Ranger to laptops and standalone machines.
Ranger Solo works on Laptops and PCs and supports Microsoft Windows 95 through to Windows XP.
Ranger Solo supports working on and off the network. In order for users to work off the network they must have a local user account created with a home folder for the logical network drive to map to.
Windows 9x legacy support
Ranger Solo supports Windows 9X environments by including;
Ranger Solo works in conjunction with Ranger for Networks. Ranger Solo supports three modes of operation, two of which determine the level of integration that occurs with Ranger for Networks.
The three modes are:
1) Local only
Ranger Solo only supports local login. Security and environment is based on local configuration settings.
2) Local and network
Ranger Solo supports local and network logins. When connected to a Ranger for Networks network, Ranger Solo acts as a standard Ranger for Networks Client. In this case the security and environment settings are applied from the server; the computer is visible within LAN Ranger and is subject to centralised control including remote commands, activity logging , react rules and software deployment.
3) Local, network and updates (centralised management)
Ranger Solo performs as 'local and network' but in addition the local configuration and program files are updated from the Ranger for Networks server.
Program files denote all settings in Ranger Administrator including start menu and desktop icons and group and common group resources.
If mode 3 is selected, configuration of the local security and environment settings should be performed from Ranger Administrator on the Ranger for Networks server .
This functionality simplifies management of multiple installations of Ranger Solo. Without a Ranger for Networks installation, a policy change would have to be replicated on every Ranger Solo installation.
Configure for Network (setting a mode)
Configuring Ranger Solo's mode of operation is performed locally on each Ranger Solo installation. To gain access to the program 'Configure for Network' you must logon to the local computer as the administrator or manager.
Select 'Configure for Network' from the Ranger program start menu. When selecting option 2 or 3 you will need to authenticate to the network first, in order for Ranger Solo to find the Ranger for Networks installation. When asked, specify the name of your Ranger for Networks server. This 'homes' Ranger Solo into the specific Ranger for Networks installation.
Homing to a network prevents the Ranger Solo installation from accidentally joining another Ranger for Networks network and potentially logging user actions to another LAN Ranger server or having the local security or environment settings overwritten.
Ranger Solo requires local user accounts to be created on the machine for authentication and group selection purposes.
Each user account must have a local home folder created. Local profiles are optional. The local home folder is required as a storage location for the user's work.
To ensure local users are restricted to those that are authorised to have local access, Ranger only supports users logging on against accounts in the local user manager or accounts SAM database. Ranger Solo does not support logging on against cached user profiles.
It is important to note, therefore, that users on the local computer may have two accounts; one for local access and one for network access. The two accounts are unique even if the usernames are the same. Both accounts have their own passwords which require setting and, if changed, there is no synchronisation between accounts.
Solo sync is configured to 'always run' when a user logs on or off. The program will only be displaced if the network user has a local user account.
The program has a simple three step process to help users synchronise the local and network home areas. Files on the local and network folder are scanned and those found to be new or modified are pre-selected for synchronisation.
Solo Sync will then transfer the files from the local or network home area and will finish by displaying a transfer summary including the number of files transferred, the total size in bytes and any errors.
If the same file (based on file name) is found, Solo sync will present a dialog to assist the user to determine which to keep. Three options are available; copy local, copy from network or copy to both with creating two unique files.
In an environment where Solo is used on laptop or stand-alone computer, a number of different usage scenarios can be configured. Each of these is explained below
Shared laptops
Generally a pool laptop is owned by the school and is allocated to a department. The laptop is available for general use by students or teachers and usually used for the duration of a lesson. As the school owns the laptop or computer, the security and usage restrictions can be at the discretion of the school.
Ranger Solo can help configure and reduce potential support problems caused by accidental or deliberate configuration changes. As standard, software cannot be installed from a CD, although programs such as Microsoft Encarta that simply require the CD to be inserted will operate normally. The floppy disk is available for file transfer and any Internet services will work normally.
The manager must install new software and/or make configuration changes. Installed software can then be made available to other users the next time they log in.
Shared laptop with one account
Ranger Solo is installed and only one local user account is created, typically the name of the laptop or computer. Each user issued with the pooled laptop logs on with the same username and password.
In this situation, the user should not save their work to the local computer otherwise it will be accessible by subsequent users and will be unavailable and potentially lost when the computer is given back. In this situation users should save their work to memory sticks.
No customisations will be allowed as this affects all subsequent users.
Shared laptop with multiple accounts
Ranger is installed and for each user who will or potentially be issued the pooled laptop a local account is created. The usernames are typically set the same as the user's network account username.
In this situation each user can log in using their own name and have access to only their own files. Work can be saved locally (virtual network drive), but before returning the laptop they should logon to the network so that their work can be synchronised to their network home area.
Each user may be allowed to customise their individual desktop, wallpaper, sounds
Individually allocated laptops
Generally a laptop is given to the student or teacher for the duration of the laptop or the user's time at the school. The laptop ownership is mixed, it maybe the sole property of the school, shared with the end user, or on lease purchase.
In this situation, control and configuration can become unclear. The user who is given the device on long-term period will bring the laptop in and out of school and will potentially want to enjoy all the benefits computers can bring, including games, internet, music etc.
In this situation restrictions and use policy becomes contentious. The user may not be given 'full' administrative control of the laptop but will be given far more access to the system with the ability to install and configure software. Ranger Solo can support this configuration, providing a finer level of control over the access to the system than Windows alone. The user can be made a member of local security groups to support the privileges they need to perform certain tasks, but Ranger's independent security settings can enforce policy control separately.
The laptop will be configured with a single logon account. The local user account will be given the same name as the user's network login