RN200955: Release Notes: Raynet One 2025.3.3663.59 [RTM]

New Features

• Fine-Grained Permission System for User and Resource Access [RCOR-8] [RCOR-17] [RCOR-82]
• User Group Management and Visibility [RCOR-465]
• Sites are Now Scopes [RCOR-345]
• Windows Device Inventarization from Non-Windows Runners [RCP-178]
• Hyper-V Integration and Cluster Membership Visibility [RCOR-567] [RCP-251] [RCOR-842]
• Job Management Overhaul with Unified Wizard and Live Updates [RCOR-464] [RCOR-609] [RCOR-335] [RCOR-468] [RCOR-240]
• Scheduled Task Details Page with Manual Trigger and Edit Options [RCOR-817]
• MSSQL Inventory Reporting with Edition and Cluster Information [RCOR-842]
• Extended Oracle Reporting with Users, Sessions, and RAC Membership [RCOR-23]
• OAuth2 was added as a new credentials type [RCOR-201]
• Improved Organization of Software Data View [RCOR-429]
• Improved Tabular UI Experience [RCOR-535] [RCOR-570] [RCOR-451] [RCOR-361] [RCOR-378]
• Better Schedule Management UI [RCOR-817]
• API Extensions [RCOR-568]
• Re-structured Settings Screen [RCOR-240] [RCOR-345]

Improvements

• Runners can now whitelist or blacklist IP ranges or hostname patterns, define the path to Java, and be assigned to specific scopes for more controlled execution environments. [RCOR-345]
• Logical disks are now supported for Alpine Linux devices. [RCP-63]
• CI icons are now monochrome for a cleaner UI. [RCOR-51]
• IT Visibility screens now provide stable calculated data and better drill-down options. [RCOR-430] [RCOR-38]
• File version information is now returned by Zero-Touch scanner for Windows. [RCP-91] [RCOR-691]
• Improved logic for detection of SQL Server editions. [RCP-250]
• Zero-touch non-Windows scans now correctly handle situations where an interactive prompt is required for SSH login. RCP-25Zero-Touch Windows scans now collect the Update Build Revision (UBR) from the registry, providing more detailed information about the installed Windows build. [RCP-235] [RCOR-620]
• Version numbers for Solaris systems are now derived from the kernel’s major and minor version rather than legacy OS version numbers. This provides accurate reporting of the actual Solaris release, avoiding outdated version values such as 10.5 or 11.5. [RCP-180]
• The application has been migrated to .NET 9, providing improved performance, faster startup times, and better resource management. End users will experience a more responsive interface, smoother operation, and enhanced stability across all supported platforms. [RCOR-382]
• File and registry scan specifications now use a user-friendly expression editor instead of the previous JSON editor, making it easier to create, edit, and understand scan criteria. [RCOR-352]
• Editing Unix credentials now includes validation to ensure correctness and prevent misconfiguration during credential updates. [RCOR-182]
• The installation date of software packages is now collected and reported for Linux systems. [RCP-90]
• Keyboard and pointing device information is now imported from MECM, ensuring these device details are available in Raynet One. [RCP-96]
• Oracle service ports can now be configured directly from the database view, allowing users to adapt port settings to their environment without additional configuration steps. [RCOR-406]
• The edit and remove buttons for RVIA services are now always displayed. When a service is running, the buttons are greyed out but remain visible, making it clear to users that the service can be edited or removed without needing to recreate the runner. [RCOR-208]
• The initial experience in the Self-Service Portal now displays enrollment details, helping users complete manual / advanced scenarios and troubleshooting more easily. [RCOR-392]
• Internal retry logic has been improved, making inventory attempts more robust and reducing the likelihood of failures due to transient issues. [RCOR-745]
• It is now possible to customize the path to java binary on runner basis. [RCOR-345]

Breaking Changes

Migration from any 1.1 version is not supported. A fresh deployment on a clean database is required.

All existing realms must be either:

• Updated using the provided bootstrapper, or
• Recreated if update is not possible.

Example command:

Raynet.One.Server.Keycloak.Bootstrapper.exe update -s http://localhost:8080 

    -u admin -p Start123 -r rnonedev

Deployment Notes

• A Redis instance is now required as an additional container.
• Please ensure Redis is reachable by all Raynet One services.

Raynet One 2025.3 introduces updated appsettings.

"SeedingConfig": {
  "Runner": {
    "Name": "Cloud Runner",
    "SeedCloudRunner": "true",
    "CloudRunnerLocked": false,
    "EnrollmentToken": "qkDwcKxGmDdUwRgwsPWCypiYnTKyno57GmYlIHuXDzIdjmAHYhYJzmQOLhhg9snC2i3in"
  },
  "Scope": {
    "Id": "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF",
    "Name": "Default Scope",
    "DeduplicationKey": "ScopeDeduplicationKey"
  },
  "User": {
    "Id": "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF",
    "Name": "SYSTEM"
  }

}

• These values can be customized to fit the deployment environment.
• Example: For a runner deployed in the cloud that cannot perform local inventory/discovery operations, set:

"CloudRunnerLocked": true

Redis configuration requires the name of the instance, and its connection string.

"DistributedCacheConfig": {
  "ConnectionString": "",
  "InstanceName": ""
}