The OpDesk console server is used to manage and push opk packages to the distribution points that are hosted on windows distributed filesystem shares (DFS). DFS will handle the load balancing and replication between the DFS nodes for OpDesk clients to stream OpDesk virtualization packages (.OPK)
OpDesk Console: This server is tasked to manage applications and associations to end
users and/or endpoints.
Database Server: The OpDesk database is used to store information pertaining to applications, associations, application usage and inventory of endpoints.
Distribution Points: The distribution points handle store the OpDesk packages from the OpDesk Console server and store agent configurations and inventory.
Distribution Point on DFS: DFS handles load balancing and replication for fault tolerance setups for high availability with the distribution points.
NOTE: All servers can be either virtual or physical, when running any of the services on virtual there will be a performance hit due to the limitations of virtual hardware.
Installation Methods
Single Tier Installation:
Single tier installation includes the OpDesk Console, distribution point, and database to be installed on the same server. Having all functions installed on the same server will require higher system resources to
handle all the agent connections.
Table 1-1: Single
Tier Installation
CPU | Memory | Disk (distribution point) |
8 | 16 GB | 500 GB |
Two Tier Installation:
Two Tier
installation requires running the OpDesk Console and database server
on the same server while running the distribution point on another
server or DFS environment
Table 1-2: Two
Tier Installation (OpDesk Console and database server)
CPU | Memory | Disk (distribution point) |
4 | 8GB | 500 GB |
Table 1-3: Distribution Point (per node if using DFS)
CPU | Memory | Disk (distribution point) |
4 | 8GB | 500 GB |
Multi-Tier Installation:
Multi-Tier
Installation is defined by the OpDesk console, database servers and
distribution point is each on its own server. The distribution point
can be hosted on a DFS environment. See DFS deployments section:
Table 1-4: OpDesk
Console
CPU | Memory | Disk |
4 | 8GB | 500 GB |
Table 1-5:
Database Server (MSSQL)
CPU | Memory | Disk |
4 | 8GB | 100 GB |
Table 1-6:
Distribution Point. If using DFS these are the requirements per node.
Please review Microsoft system requirements for DFS
https://docs.microsoft.com/en-us/windows-server/storage/dfs-namespaces/dfs-overview
CPU | Memory | Disk (distribution point) |
4 | 8GB | 500 GB |
DFS System requirements:
The distribution point can be installed on Microsoft distributed file system (DFS) or a simple NTFS share. DFS will allow for high availability. OpDesk is unique in leveraging DFS to handle load balancing between DFS nodes and also replication for high availability.
System Requirements:
OpDesk recommends
the following for DFS environment for hosting the distribution point
for OpDesk.
Table 1-7: table
below is minimum requirements per DFS node.
Number of Nodes | CPU | Memory | Disk |
3 (minimal) | 4 | 8 GB | 500 GB |
NOTE: We require
3 DFS nodes to handle replication and fault tolerance
Calculating
number of DFS nodes: OpDesk recommends using 3,000 endpoints and up
to 1,000 applications per DFS node.