OP can be deployed and accessed within a remote desktop (terminal) services scenario. Office Practicum is coded to allow each user session of an RDP server to have the his/her own user profile with the his/her own custom peripheral and form placement settings. When building out an RDP server for an office it is important to not only take into account the resources that will be consumed by OP but to also assess the resource needs for any third-party applications users might access when logged into an RDP session (Internet Explorer, Office Apps, Adobe PDF, etc.).
Typical memory consumption for an instance of OP is on average 60-90 MB. However, in some situations (which relate to billing and scanning) an Office Practicum instance running on an RDP server can consume as much as 250-350 MB of memory. While this is a rarity it is important to size the respective RDP server to allow for these infrequent jumps in memory consumption.
A general baseline that can be used when sizing an RDP server would be to allocate a minimum 256 MB of memory per RDP session, with 512-1024 MB per session being preferable. An example deployment for 30 end users would be to configure a Windows 08/12 RDP server configured with at least a quad-core based processor (with hyperthreading preferred and 18 GB of RAM). This assumes that 2 GB is being used for the operating system, with the remaining 16 GB reserved for RDP based services and application needs. This roughly works out to be just over 512 MB per user session.
It should be noted that these recommendations and specifications are for an RDP server built for the sole purpose of OP usage and access. If end users need to use other third party applications, it would be advisable to configure an RDP server with roughly twice the processing and memory capacity. This will ensure a positive and productive user experience.