Ranger for Networks: Release Information

Ranger 5.0.5

LAN Ranger:

• Graphs are now accessible from LAN Ranger Client.
• User tracking is now configurable from LAN Ranger Client
• LAN Ranger Client security enhancement – LAN Ranger Client main form will not accept user input until the password has been validated.

New fields under computer/user properties:

• OS version (LR Server only)
• Ranger version (LR Server only)
• Switched on duration
• IP address

Computer/user properties form now updates intelligently – no more flickering.

Added a feature that allows closure of a program running on multiple machines by selecting the program in the tree view, and then multi-selecting the users/computers you want to shut it down on, right clicking and selecting “Close Application”.

If a screen shot should fail to capture for some reason, an error will be logged in the status log, with an additional message dialog being displayed if the user manually initiated the screen capture.

Fixed a bug which would sometimes incorrectly enable the “Close Application” menu item, causing a “List Index out of Bounds” error if selected.

Fixed a bug in Ranger REACT that (for log off triggered events only) would fail to apply exclusions based on group name or user name.

Fixed a bug in Ranger Rollout that can cause an access violation if a computer that had active or historical package jobs was deleted from LAN Ranger’s memory.

Graphs:

• Various graph bug fixes
• Higher colour icons
• Custom range date controls have integrated calendar, time controls are more intelligent when accepting user input
• Time-based graph colours made more suitable

Screen viewer:

• Optimisation, now much better at dealing with a large number of screen shots.
• LAN Ranger no longer locks up if Screen Viewer does and LAN Ranger doesn't close Screen Viewer if LAN Ranger is closed itself.

RangerAdmin:

- Fixed a bug in Ranger Administrator that would throw an unhandled exception on shutdown if it couldn't write to dirhashes.ini

- Removed references to sshots share.

Miscellaneous policy additions:

• Added the policy option to restrict the Search feature in XP and Windows 2000.
• Added support for My Pictures and other special My Documents folders.
• Added support in Preshell to set Frontpage default open save location.
• Added support for Jpeg and other active desktop wallpapers in XP and 2k.
• Added the ability to disable the Control Panel via policies in XP/2000 (this is disabled by a title check but has been added here for additional security)
• Added the ability to set the display resolution per group on 9x workstations.
• Added additional default title checks for new installations.

Ranger Rollout:

Package Builder now knows about the latest versions of Internet Explorer so it can report them correctly as installation conditions.

Ranger Server:

Improved layout of the Ranger Server user interface.

Stopped Ranger Server shutdown causing a crash under certain circumstances. This fix has also been applied the other Ranger services, although none of these exhibited the symptoms.

Secmon

:

Removed the default restriction removing "Search" for users with Ranger security applied. (For Windows XP and Windows 2000 post IE 5 workstations only).

Secmon no longer leaks resources when capturing screens.

Ranger Environment Variables are now correctly integrated into Secmon environment space, allowing any program spawned by Secmon (e.g. via LAN Ranger) to use these environment variables.

Ranger Account Manager:

Added the option to give alternative permissions to additional groups when creating user home directories.

By default, home directories are configured with the following permissions:

• User - Modify
• Domain Admins - Full Control
• System - Full Control

Additional groups can now be added with either Read/Execute or Modify permissions.

Support now added for Solo workstations without network cards. Accounts created in local mode (Solo) will now reference absolute paths to their home directory instead of UNC paths.

Setup and Installation:

• All application executable files are now created with a build package version number.
• Main setup executables are automatically suffixed with the full build package version number.
• Version Info.txt is now Ranger product specific.
• BuildVersionInfo.txt file no longer used.
• Clupdate directories are automatically named during package installation and are based on the build date.
• Removed the security permission issue that occurred when trying to extend Ranger on to another Domain, hosted by a Windows 2003 server.
• Added many more checks in to Ranger Manager's “Check Installation” option that should detect major errors before they cause Ranger to fail on that workstation. Ranger Manager also now uses the client stored copy of ec.dat
• when validating installation.
• ECM will no longer display the unavailability of “Web Client Network” as an error.
• ECM now reports progress during the applying settings phase.