DDS Deprecation - DDS Deprecation - OnBase - Distributed Disk Services - OnBase/Distributed-Disk-Services/Foundation-26.1/Distributed-Disk-Services/Overview/DDS-Deprecation - Foundation 26.1 - Foundation 26.1

The Distributed Disk Services (DDS) module is being deprecated for eventual removal from the OnBase product suite. DDS is supported in Foundation 26.1 only for existing customers. It will not be available in versions of OnBase released after December 31, 2027

If you are using the DDS module and upgrading to OnBase Foundation 26.1, Hyland Software recommends migrating your OnBase Client users to either Unity Client or the Web Client to fulfill their needs.

• If you expect to perform high volume batch scanning (such as for healthcare), it is recommended that you migrate your OnBase Client users to the Unity Client.
• If you do not expect to perform high volume batch scanning, it is recommended that you migrate your OnBase Client users to the Web Client.

The following are common questions related to moving away from DDS and migrating users from the OnBase Client to either the Unity Client or the Web Client. If you have other questions or concerns about migrating users, contact Hyland Support.

Should I migrate users to the Unity Client or the Web Client?

As stated, the main feature to consider is high volume batch scanning. If you require high volume batch scanning, it is recommended that you migrate OnBase Client users to the Unity Client. Otherwise, it is recommended that you migrate OnBase Client users to the Web Client.

For a more detailed breakdown of the feature differences between the OnBase Client, Unity Client, and Web Client, see the Feature Matrix chapter of the Web Server documentation.

If users are moved to the Unity Client, what would the new configuration look like?

If moved to the Unity Client, disk groups are accessed through the Application Server. This no longer requires the use of DDS because the Application Server communicates directly with the Database/File Servers. This does not require administration of the user rights directly to the file server; access is managed by the OnBase user privileges and authenticated through the Application Server.

If users are moved to the Web Client, what would a standard Web Client configuration look like?

If moved to the Web Client, disk groups are accessed through the Web Server. This no longer requires the use of DDS because the Web Server communicates with the Application Server, which communicates directly with the Database/File Servers. This does not require administration of the user rights directly to the file server; access is managed by the OnBase user privileges and authenticated through the Web Client.

If users are moved to the Web Client, what would a scanning user's configuration look like?

If moved to the Web Client, users would need to set up the OnBase Client to run as a service. The scanning user would scan documents to a scanning-only file location, and then the OnBase Client service would commit batches and move the scanned documents to the respective committed Document Type Disk Group copy locations.

Administrative users would also need to configure communications and scan queues for the OnBase Client service. In particular, the Delay Disk Group Migration Until Batch Commit option needs to be enabled for the scan queue. For more information on scan queue settings, see Configuring Custom Scan Queue Settings in the Document Imaging documentation.

What changes are required for the scanning users with the new configuration?

For both the Unity Client and the Web Client, the biggest change would be the requirement to manage user access rights using NTFS security, Encrypted Disk Groups, or both.

Note: If using both NTFS and Encrypted Disk Groups, managing access rights with NTFS would only be done for users performing scanning. Other users would be managed through OnBase rights/privileges assignment, not NTFS.

For more information on NTFS security and Encrypted Disk Groups, see the Encrypted Disk Groups section of the Platter Management documentation.

Other than the changes to user security, what other differences are there in the new scanning user configuration?

The OnBase Client would now be running as a service to move the scanned documents from the scanned location to the respective committed Document Type Disk Group copy locations.