Added functionality necessary to support new features in OMNIC Paradigm 2.6.

When upgrading Security Suite on a system that has OMNIC Specta installed and the Thermo Indexer running, you may receive an error message after entering the username and password to use for the Secure Data Storage service. The workaround for this is to exit Thermo Indexer, close the error dialog, and press Next > again.

The Thermo File Change Monitor Service crashes when it receives a notification of a change to a file where the full path is exactly 260 characters long.

When upgrading Security Suite on a system that has OMNIC Specta installed and the Thermo Indexer running, you may receive an error message after entering the username and password to use for the Secure Data Storage service. The workaround for this is to exit Thermo Indexer, close the error dialog, and press Next > again.

Set up the system to automatically create dump files in the %ProgramData%\Thermo Scientific\Security Suite\Dump Files folder if any of the applications crash.

Added top-level error handlers to prevent application crashes from recoverable errors.

The policy name for "Use exclude list for all events, not just directory renames" was blank in Security Administration when run on non-English systems.

Certain multi-file operations (copy, move, etc.) could result in some of the affected files being missed in the audit log.

An intentionally malicious application definition XML file could cause Security Administrator to crash upon trying to read the file in.

When upgrading Security Suite on a system that has OMNIC Specta installed and the Thermo Indexer running, you may receive an error message after entering the username and password to use for the Secure Data Storage service. The workaround for this is to exit Thermo Indexer, close the error dialog, and press Next > again.

The Thermo File Change Monitor Service crashes when it receives a notification of a change to a file where the full path is exactly 260 characters long.

The Admin program already had a policy that allowed a directory rename events to be suppressed from a list of folders. A new policy has been added that will cause all file events to be suppressed from the folders specified in the exclude list. The policy is under the Admin program and is called "Use exclude list for all events, not just directory renames". Checking the policy will make all folders specified under the "List of directories to exclude from File Change Monitor Service for directory rename events" to be suppressed. By default, this policy is turned off.

The Thermo Scientific Secure Data Storage Service could crash if a request was received to rename a file where the source and the destination paths were very long (over 500 characters combined). The buffer size was increased, and checks were added to ensure the combined length of the two paths did not exceed the new limit.

The Thermo Scientific File Change Monitor Service and the Thermo Scientific Secure Data Storage Service was modified to not exit when an internal exception is encountered. The exceptions are logged, and the services continue.

Attempts to log exceptions from the secure file service could fail if the service did not have permission to write to the root of the c: drive. This was fixed by writing the exception log to a folder the service does have permission to write to.

When upgrading Security Suite on a system that has OMNIC Specta installed and the Thermo Indexer running, you may receive an error message after entering the username and password to use for the Secure Data Storage service. The workaround for this is to exit Thermo Indexer, close the error dialog, and press Next > again.

When using a separate server for secure data storage, audit events stop being recorded for changes after the security server is restarted until the file server is also restarted.

The default account used for the file change monitoring service on the file server does not have access rights to the named pipe used by the audit log service.

When using mixed languages between the application and the server, multi-byte characters may not appear correctly. The malformed characters will not be recoverable.

Attempting to run ChangeServer.exe on a Nicolet Summit gave an error message.

Added support for OMNIC Paradigm and the new location the security server name can be stored.

Updated the online help file with the latest content.

Certain installation scenarios would fail to include ChangeServer.exe.

Audit Log entries with more than 259 characters could not be properly transmitted on to the audit log service.

Attempting to run ChangeServer.exe on a Nicolet Summit gave an error message.

Improved handling of error conditions and the messages returned to the user.

The group membership check is no longer necessary and has been removed to avoid requiring additional permissions during installation.

This was found to be an issue with the authentication options specified when communicating with the domain controller.

Documentation incorrectly stated that read-only access was required for the service account when read-write permission is correct.

The default folder permissions for user folders on newer Windows installations could cause the Secure Data Storage service to be unable to place data files in the secure location.

A new application called Audit manager has been added to view events from Thermo Fisher applications. This replaces the use of Windows Event Manager.

Application events will now be stored in a data base instead of the Windows Event Viewer. The data base is defined at installation.

The document called OQ for OMNIC Security Suite software has been modified to align with the new Audit Manger tool.

Version 2.1 installation process now allows the end-user to install just the instrument software or Audit Manager.

Intermittently on a distributed install the file and log service are not set to the account that was specified at install time and are not started.

This was found to be a timing problem and has been resolved for the version 2.1 installation

When installing a distributed configuration, on some networks when you are at the screen where you enter the name of the computer where security administration is installed when you press the Next > button it will not advance and gives the error "Unable to connect - network timeout error". This prevents you from installing the software. The method of verifying the connection has been changed to prevent this problem.

Previously when software applications started they altered the folder permissions on the secure folder every time the program started. Now they only alter the permissions the first time when the folder is created or filled with files. This allows IT departments to alter the configuration from the recommended default permissions.

Now that folder permissions can be altered, the software tests writing to the secure folder using the current account and the specified secure file service account. If the current account is allowed to write to the secure folder a warning message appears stating this is not expected. Also if the secure file service account cannot write to the secure folder an error message occurs as well.

Previously if you had an active directory domain that had no organizational units defined an error message "The specified domain does not exist or could not be contacted" popped up when starting the Administration program. After closing the message the software works properly but would not list users and groups on the domain, and required you to type the user or group name. Now the software hides the list of organizational units if none are defined and lists the users and groups when the domain is selected. Normal active directory domains let you choose the domain, followed by the organizational unit, which then lists the users/groups in that organization.

When this occurs the Instrument application will display a dialog box stating "Thermo File Service: The service is installed but is not running." If the services are not running and set to the account specified at installation, the instrument application will not be able to save data files to a secure folder.

In Security Administration, open one of the Access Control items, change the permission from Deny to Allow or Allow to Deny, immediately click on the Save button. The change was not saved.

In certain circumstances, the Thermo Log Service would generate extraneous file events in the log when a file was being saved by an application.

If the default data directory was chosen as the Secure Data Folder, the user would be unable to install newer versions of OMNIC, qPro, INSIGHT, etc. The user is now prohibited from selecting one of these well-known directories as the Secure Data Folder.

During distributed installations, going back to the service account selection screen would leave the user unable to go forward again and would state that the username or password was incorrect every time.

Upgrading to Security Suite 2.0 would not properly retain the previous settings.

The automatic loading of applications into Security Administration during installation on non-English locales would not load any application that did not have a configuration file for the current locale.

In Security Administration, open one of the Access Control items, change the permission from Deny to Allow or Allow to Deny, immediately click on the Save button. The change won’t be saved. Workaround: File-Save does work. It also works if the user places the focus (Clicks) on any other object before selecting the Save button.

After selection of a domain, it tests if the domain supports Active Directory. If it does, a dropdown is displayed with Organizational Units. This allows you to list just the users and groups associated with an Organizational Unit instead of an entire domain.

Changed the access rights selection to have a dropdown with 2 choices "Allow" or "Deny" to clarify the use of access rights. Previously it used a checkbox for the allow/deny choice.

Add audit events when logging on or exiting the security administration program

Added menu item to automatically call up the Windows event viewer to view the audit events for Thermo Fisher products.

Changes to automatically load the Application XML files after installation when you run the Security Administration program after installation. This simplifies setup and insures that new capabilities are merged into existing installations.

Change the Thermo Log Service to have directory rename events be a different event type to allow filtering these items out.

Add a new policy which lets you edit a list of directories that the Thermo Log Service ignores. This list will allow the asterisk to be used as a wildcard character and will default to the directories already rejected.

The Security Admin program will not allow you to close until all secure directories have been defined for applications that support secure directories.

Add a new menu item that allows you to replace a user/group with another user/group for all access control items. This allows built-in groups like "Administrators" to be easily replaced with a custom group appropriate for your network.

Changed to set a common folder location for all subfolders for application data using an environment variable and show that path after it is set. When the instrument software is started for the first time, it will create this common secure folder location, copy the files from the local installation (C: drive) to the secure location, and finally it will set the correct permissions for that folder. Afterwards, the folders will be set to read only for all users except for the one account specified at installation time to have read/write permission.

Display the name of the Security server so customers know what to type when running the ChangeServer program or installing the instrument software.

Improved the logging service to ignore renames of Google chrome temporary directories.

Changed the ChangeServer program so that the dialog for specifying the server name is a topmost window that cannot go behind another window.

Display an error message if the event log is set to overwrite old events rather than archive them. Also provide a menu and toolbar item to perform configuration tests.

Made various controls wider and taller to allow more text to be displayed without being cut off.

Improved the printing of application settings so that items are not cut off and when printing data folders it, displays the root path separately from the folder path.

Fixed issue where the date format was not displayed properly in printouts if the date format is configured to use text names for months and not numbers.

Changed event logging to always use the security server to ensure that events generated by non-admin users are recorded properly.

Changed the ThermoFileService.exe and ThermoClient.dll to support the INSIGHT software using secure folders to store data on networks.

Previously most of the files were version 1.6 and only the file watcher was version 1.7, this was confusing for some customers and has been resolved.

On some Win 10 systems an error message stating "The API return buffer is too small" appears on some domains. After you close the error message the software appears to operate properly. This has been resolved.

The changes to the file watcher process sometimes prevented the service from starting when the computer was rebooted. This has been resolved.

OMNICxi map files, *.mapx, are now supported in the file watcher process.

OMNICxi map files, *.mapx, are now supported in the file watcher process.

The installer for the software now properly uninstalls the previous version before it installs the current version. The software being installed has not changed.

Unsuccessful login attempts now match that of the Windows Security policy.

This only occurs in this version

When using Security Administration to configure policy items, if you configure a policy item to be accessible only to members of the Windows built-in Administrators group, the policy item may not be accessible to users who are members of that group.

This happens because starting in Windows Vista administrators no longer start with administrator privileges.

For those who encounter this problem, there are two workarounds:

Using either of these workarounds the software will behave as it did in Windows XP, and the software will start with administrative privileges.

Changed the splash screen, icon, and about box to display Thermo Scientific. The about box now displays information about the installed version, not the file version.

The administration application did not add application information properly if you added an optional software package before you added the package it depended upon. Now if you attempt to add an optional feature for an application before you add the main application you will receive the message, "You must add the (application name) application before you can add this file to security administration."

Security Administration 1.5 did not install over previous installations because the installer said, "A later version of Security Administration is already installed on this machine." The installer on the CD was not the correct version. This has been changed.

When using the German version of Windows and the computers are connected to a domain network, the built-in groups (such as Users and Administrators) cannot be added or removed from the access rights list. This problem only occurred on the German version of Windows when networked. The 1.5 release fixes this issue.

The Security Administration software has been changed to fix issues noted during operation using the Vista operating system. This includes changing the help system from .HLP files to .CHM files.

If you install Security Administration on a computer with the Windows Vista operating system and are using a network, audit events are different from in previous versions. In this circumstance, audit events will correctly have the name of the remote user of the computer that generated the event, but will list the name of the Security Administration computer rather than the name of the remote computer. This change is required because Windows Vista does not allow remote computers to write to the event log.

When adding applications to Security Administration, if you add an optional software package, such as OMNIC for Raman or OMNIC Series, before you add the OMNIC application, the system policies will not be installed.

If guest user accounts were enabled (they are disabled by default and it is recommended that they remain disabled), those accounts could have access rights even though Guest accounts were denied access. This issue was caused by a mistake in the default XML files for OMNIC software products. However, the 1.4 version of Security Administration corrects XML files that have grant and deny items in the wrong order.

The Security Administration software has added the ability to store application-specific passwords as policy items. Several new types of audit events for the TEVA software were also added.

Chinese and Russian translations of Security Administration have been added to the CD, bringing the number of translated languages to seven.

Under some conditions, after a local user account has been added to a policy group, attempts to add a domain user account will fail. This has been fixed.

If you add the "Power Users" group to Access rights or policy groups when you save, the "Power Users" group will not be saved.

If you load a translation of an application XML file after already loading a different language, multiple entries will occur for the same items. Now you can load the English XML file of an application, followed by a foreign language, and it will switch the display to that foreign language without changing any settings. You can also load the English XML file after this and it will switch back to English.

If you add a new signature reason, it does not show up by default in the application. The default for new signature reasons was no access rights; you needed to add users or groups who could access the signature reason. In 1.3 this behavior was changed to add the "Users" group to a new signature reason as the default. If you do not wish to allow all users to access the signature reason, simply delete the "Users" group.

When the Security Administration program starts, it prompts for a user name and password. However, it accepts any valid user name and password account on the Administration computer rather than just the name and password for the currently logged-on user. This has been changed so that only the person currently logged on to the computer can log into Security Administration.

The Security Administration software has added the ability to add several new types of policy items, such as items from a drop-down list. Several new types of audit events for RESULT software were also added. The Security Administration program has a new menu item to remove applications from administration.

Some Japanese characters are not displayed properly in the list of available users and groups. The Microsoft default list only partially supports Japanese characters and needed a fix to work with the full character set.

The Security Administration program now requires user authentication when the program starts to verify the user identity of the Security Administration software.

The Security Administration program will switch to initiating the accounts on the local computer, rather than the accounts on the login domain if the enumeration takes a long time. An edit control has been added that allows user names to be entered manually so enumeration can be avoided. Accounts are not re-enumerated when switching from the access control portion of the tree to the policy portion. These changes make using the software faster on large global networks that take minutes to enumerate the available users and groups.

The Security Administration program has two new menu items: The Add to All Access Control Items command will add an Allow or Deny entry for the specified user to every function in the Access Control section of the current application. The Remove From All Access Control Items command will remove the entry for a specified user or group from all functions in the Access Control section of the current application.

The Security Administration program now supports choices such as French (Canadian) instead of only the direct foreign language choices of French, German, etc.

Text would print much larger on some inkjet printers than it did on laser printers. Now correctly calculates font sizes.

Some capabilities were added to get the date/time of the server.

In some circumstances the full name of the user account was not retrieved and the logon name was used instead. Now it properly gets the full name of the account if specified for use in audit events.

Added support for foreign language translations.