You would like information about Symantec Endpoint Encryption database, installation, and hardware sizing requirements.
SEE Installation Specifications
Symantec Endpoint Encryption on a client requires 2-3 installation packages depending on the configuration: Framework, Full Disk and Removable Storage. The Framework is always required. Full Disk (SEE-FD) and Removable Storage (SEE-RS) are available options.
The installation package sizes are as follows:
SEE-FD 14 MB
SEE-RS 20 MB
The SEE agent footprint once deployed can range between approximately 54-84MB, again depending on if SEE-FD, SEE-RS or both were installed.
With SEE-FD encrypted volumes are created on the disk in addition to the software install sizes. The volume size is approximately 30M. If Pre Boot Authentication is enabled within SEE-FD, the bootloader disk space footprint is approximately 30MB.
The following processes/services (and their memory footprint) will be present on the deployed client.
*(SEE-RS specific services)
In terms of performance, the Rated I/O impact has been observed to be 5-10% during initial encryption and 5% (or less) after encryption when the encryption driver performs on the fly encrypt/decrypt operations.
Symantec Endpoint Encryption has relatively modest bandwidth requirements. Policy updates are typically around 50k. Updates are only conducted to change client configurations. The Client check in interval is configurable; the default is 60 minutes.
There are two ways to implement the database in SEE: on the server itself (via SQL Express w/Advanced Services) and “off box” using a database server. One Symantec Endpoint Encryption management server can support 100,000 clients, but this is also dependant on the database being used. If you are using SQL Express (w/Advanced Services) running on the server itself, that number goes down to about 10,000.
Database sizing depends on a number of factors: configuration of the database, number of installed clients, number of computer objects in the AD forest, the number of registered users, etc. With the way the schema is created, the data file has an initial size of 800MB and can grow up to 10 GB in increments of 25MB. The log file is created with an initial size of 80MB and can grow up to 2 GB in increments of 20MB.
10240 MB (10 GB)
2048 MB (2 GB)