(Windows Vista+, Server 2008+)
- Microsoft SQL Server 2005, 2008 (including R2), or 2012, including Express Editions.
- Windows Server 2008 (including R2), Windows Server 2012, Windows 7, Windows 8, Microsoft Windows Vista Ultimate, or Windows Vista Business.
- Microsoft Internet Information Services (IIS) (Internal Part of Operating System)
- Microsoft .NET Framework 3.5 with Service Pack 1. Both 32-bit and 64-bit editions are supported.
Small Installation (<1K Secrets, 1-10 Users):
- Dual-Core 1.6Ghz or higher
- 2 gig ram
- 500MB of disk space + 10 MB of disk space per user per year.
Medium Installation (1K-10K Secrets; 10-100 Users):
- Dual-Core 2Ghz or higher
- 2 gig ram
- 1 GB of disk space + 10 MB of disk space per user per year.
Large Installation (10K+ Secrets, 100+ Users):
Instructions on setting up
Database Mirroring and Disaster Recovery - recommended for Medium and Large installations.
- Quad-Core 2.0Ghz or higher
- 4 gig ram
- 2 GB of disk space + 10 MB of disk space per user per year.
- Secret Server will operate in a virtualized environment (VMWare or Hyper-V).
- DO NOT install Secret Server on a domain controller (Microsoft ASP.NET does not operate reliably when installed on a Domain Controller).
- You can also run Secret Server on the same machine as other applications (Secret Server will need sufficient RAM and CPU to operate normally) but see the next point first.
- However for maximum security, you should install the application on dedicated systems or at least systems with applications with the same level of security/sensitivity. Access to these systems should then be restricted. While all sensitive data in Secret Server is either securely hashed or encrypted, it is a security best practice to limit any opportunities for foul play.
- If you intend to use Session Recording, then additional disk space will be needed for the database to store the recorded videos. See http://support.thycotic.com/KB/a162/configuring-session-recording.aspx for more information.
- The following example is based off of a test instance with 120,000 Secrets.
- The database was 1.6 GB.
- The machine was a Windows 7 instance with an Intel i7 2.67 GHz processor and 6GB of RAM.
- Searching performance is primarily driven by the number of Secrets a user has access to, so in the above example a user searching all Folders with View access to all Secrets could see search times of 4-6 seconds. Meanwhile a user with access to 6000 Secrets in the same instance will see search queries return in 1-2 seconds. Search times can vary based on data, the fastest search will be for a distinct value in a smaller set of Secrets, the longer searches will be for a generic value in a larger set of Secrets. For example the search for a Secret named "PRODSRV03\LocalAdmin" will return much faster if the search value is "PRODSRV03" and done in a specific Folder, than if the search is "Admin" and done at the root level.
- To increase performance consider putting the database and web application on a separate servers, this will reduce resource contention. Another option is to set up front end clustering behind a load balancer using the Enterprise Plus edition, which will help scale out the work done on the web server.
Article ID: 51, Created On: 9/11/2009, Modified: 3/11/2013