Security Server
Security Enabler for Rockwell Software Products

What's New in Release 2.00.00?
December 2000

Updating Security Server  | Supporting Applications  |  Current Enhancements  |  Product Changes   |  Known Anomalies  |  Notable Items

All Network Edition Users!

• Security Server r2.00.00 requires that you use Windows NT™ 4.0 SP4 or later or Windows 2000.
• DCOM configuration is required for client communication.
• When upgrading to Network Edition from the standalone security:
  1. Using standalone security export your database.
  2. Install the Security Server Network Edition.
  3. Import your standalone database.
  4. Because you are migrating to a network-based system, reconfiguration of user groups and resource/groups ACLs will be required.

All Standalone Edition Users!

• Standalone Security Server r2.00.00 requires that you use Windows 95 (DCOM Service Pack), Windows 98, Windows NT™ 4.0 SP4 or later, Windows Me or Windows 2000.
• DCOM configuration is required for client communication when running on NT or 2000.
• On Windows NT and 2000 workstations, if logged-in domain user name matches that of a private standalone user then authentication is assumed and no additional login is required.

Updating Security Server to Release 2.00.00          [goto Top]
To update to Security Server r2.00.00 simply run the SETUP program located on the CD.  This will install Security Server r2.00.00.   During the installation process the previous release will be removed from your system.  Your network security database will not be affected.  Remember your new r2.00.00 database and older databases, once opened with r2.00.00 cannot be opened in an earlier Security Server release.

Supporting Applications           [goto Top]
The following is a list of products/clients that supported Security Server at the time the Security Server software was shipped to you. 

PLC-5 A.I. Series v8.07 or greater
PLC-3 A.I. Series v6.25 or greater
RSLogix Frameworks v2.50.01 or greater
RSLogix 5 v4.00.00 or greater
RSLogix 500 v4.00.00 or greater  
RSLinx v2.20.01 or greater

Current Enhancements         [goto Top]
The following is a list of enhancements at the time the software was shipped to you.

Security Server r2.00.00

• Roaming security allows workstations to be removed from the network and still remain secure for the supporting applications.  The currently logged-in user has the ability to cache their security information to the local hard drive, remove the computer from the network and still retain their respective security levels for RSI products. 
  • On Windows NT and 2000 workstations, if logged-in local user name matches that of the Roaming Alias user name then authentication is assumed and no additional login is required.
• Standalone security provides local security services for products installed on individual workstations.  Private Security Server users and NT/2000 local users can be given restricted access to actions in specified resources.  This feature is provided within the supporting Rockwell Software products.
• Security Audit Tracking can be written to either the NT Event Viewer Application log or an ASCII file that resides on the server machine.  The security administrator configures the maximum number (1-100) of log files created.  A new log file will be created for each day that an audit event is detected.  The log file is comma separated for easy loading into other software packages, like Microsoft Word or Excel.  Example log file:
  
  7/11/00, 9:26:43 AM, Configuration Explorer: User 'ROCKSOFT\CVANCE' on workstation 'CVANCE-NT4-RSI' changed the 'Audit Configuration Changes' to 'True' for Rockwell Software's Security Server.
  7/11/00, 9:26:43 AM, Configuration Explorer: User 'ROCKSOFT\CVANCE' on workstation 'CVANCE-NT4-RSI' changed the 'Audit Access Permissions' for Rockwell Software's Security Server.
  7/11/00, 9:26:43 AM, Configuration Explorer: User 'ROCKSOFT\CVANCE' on workstation 'CVANCE-NT4-RSI' changed the 'Audit User Access' for Rockwell Software's Security Server.
  
  When running standalone security under Windows 9x, audit events will always be logged to the ASCII file.
• Audit tracking errors are logged when Configuration Changes tracking is selected.  
  

Product Changes          [goto Top]
The following is a list of product changes and repairs at the time the software was shipped to you.

• Configuration Explorer Audit Tracking log Event ID are now numbered 2xx instead of 1xx.  Client and server logs will remain numbered as 1xx.
• Domain and local users that are security administrators with blank passwords are allowed access to Configuration Explorer. 
• Choosing not to save a user group or resource group will not effect the name of the next selected item.
• In Windows 2000, the Event Viewer will no longer report a "Service terminated unexpectedly.." when Security Server is correctly shut down.
• Within the Event Viewer, the Event Source changed from Rockwell Software's Security Server to RSSecSrv.

Known Anomalies          [goto Top]
The following is a list of known anomalies at the time the software was shipped to you.

• AI users needing to specify a processor as a resource must use RSLinx v2.10.118.  If RSLinx 2.20.01 is used, an error will occur when attempting to browse for a processor through the RSWHO function. 

Notable Items        [goto Top]
The following is a list of features and functions that are not fully implemented or non-functional at the time the software was shipped to you.

• The Guest Account in Windows NT (Start > Programs > Administrative Tools > User Manager) must be disabled for User Authentication to work properly.
• If your configuration includes backup servers, those backup servers must have activation installed. If the primary server runs out of activations, the clients go to the backups.
• Database synchronization between the primary Security Server and the backup Security Server can be achieved using NT file replication.
• If you have primary and backup servers, you might consider having activation on a mapped drive accessible by all servers.
• Rockwell Software's Security Server works through Microsoft’s Distributed Component Object Model system, known as DCOM. You must set up DCOM so Rockwell Software's Security Server users can launch and access Rockwell Software's Security Server.  Note that the information provided applies only to DCOM version 4.0.  
• When running Standalone in Windows NT or 2000, a non-configurable refresh cycle runs every 15 minutes.
• If Security Server is run in Windows NT 4 SP4 and SP5 and Microsoft's DCOMCNFG utility is run, Security Service name will change from "Rockwell Software Security Server" to "sentinel.database".  To resolve the problem install SP6.  For a more detailed explanation please refer to the Microsoft Knowledge Base Article, Q184232, "DCOMCNFG Saves Incorrect Display in Services".  This will have no effect on Security Server operation.  To correct the Security Service name, rerun the Security Service Installer.

 

© 2000 Rockwell Software Inc. All Rights Reserved. Printed in the United States of America.
© 1998-2000 Rockwell Software Inc. RSLogix 5, RSLogix 500, RSLogix Frameworks, RSLinx, A.I. Series and the Rockwell Software logo are trademarks of Rockwell Software Inc.  Microsoft, Windows 95, Windows 98, Windows 2000, Windows Me and Windows NT are registered trademarks  of the Microsoft Corporation. Other product names mentioned in this document are trademarks or registered trademarks of their respective companies and are hereby acknowledged.