This includes a constant base value of 1 GB for the audit/computer/program/policy databases plus about. For a year, the total estimated data storage requirement comes to about 7 GB. To avoid unlimited growth of the usage database, you may want to discard or split off old records from the database after a fixed time period, perhaps after a year or two. KeyServer's default action of "ignored" is assumed for most program usage, but we assume about 500 products are managed which lead to 30 launches and quits of monitored programs each day (except weekends) for all computers (on average). The audit is assumed to reference about 1,000 programs on each client. The estimates in the table above assume a 1000 client KeyServer with auditing enabled for all. The exact space required for KeyServer data will vary greatly depending on the values assumed: 1,000 computers managed by KeyServer 1,000 computers to be audited 500 managed products 30 daily program launches/quits per computer 12 months of usage data See also Server Requirements, Installation documentation, and Firewall Settings. Processor demands are highly optimized and prioritized so license management services take precedence over admin responsiveness or report generation. There are no database services or other server class OS features required. Standard computer hardware running a desktop OS is all that is required for the KeyServer process. But when a specific report needs to pull down all the data from a large KeyServer supporting tens of thousands of client computers, 1 GB or more may be needed: see the estimates below. This will suffice for many reports even for a large KeyServer since only selected records are fetched. For a 100 client KeyServer, 100 MB is a good estimate. The size of these temp files corresponds to the amount of data being selected for the report, so they will be larger when reporting on a large number of client computers, a large number of programs, and a long time range. When running reports, Ke圜onfigure and KeyReporter will create temporary files to store and sort data. Unlike the Windows or Macintosh client, the Solaris client has not been widely deployed by customers so full function compatibility on all Solaris hardware and software variants has yet to be demonstrated. Some of the various Windows operating system versions that may include these technologies are listed. Windows Remote Desktop Server, RDS (formerly Windows Terminal Server, WTS), and Citrix XenApp (formerly MetaFrame etc.), can be configured to use a single copy of the KeyAccess client software on behalf of all the remote desktop sessions which it serves out to its clients. KeyReporter (Reporter) normally installed as part of KeyServer Note older clients can be used on older OS versions and communicate with 7.8 server Click on the component name to jump to the comments. Installation details, special considerations, exceptional behaviors, or limitations under a specific operating system version are detailed in the comments below the table. The functionality of Sassafras Software components is nearly identical on the various platforms. If you want to check "forward compatibility" of an older component running on a newer OS, consult the Component History document for specific warnings.Ĭonsult the File Locations document for a complete list of files and directory paths which implement each component. Older component versions are "backward compatible". The operating system compatibility notes listed below assume that you are using the latest shipping versions of each component: Client, Admin, Server, and Reporter. Approximate resource requirements for various Sassafras Software components are listed in the following table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |