Desktop Authority 8.0 Operating System, Disk Space & RAM Requirements.
Please note that version 8.x support has been discontinued as of May 29, 2014. Please see our Product page for support dates.
Desktop Authority 8.0 Operating System, Disk Space & RAM Requirements
This document summarizes estimated resource requirements and supported operating systems for deployment and use of Desktop Authority 8.0.
The following table summarizes the supported Operating Systems for Desktop Authority 8.0 components.
|DA Software Component||Client OS*||Server OS*|
|Operations Master (DA Manager)||N/A||2000/2003/2008/2008 R2|
|Desktop Agents||2000/XP/Vista/7||2000/2003/2008/2008 R2|
|Distribution/Download Servers||N/A||2000/2003/2008/2008 R2|
|Optional DA Modules:||-||-|
|Patch Management Clients||2000/XP/Vista/7||2000/2003/2008/2008 R2|
|USB/Port Security Clients||2000/XP/Vista/7||N/A|
|ScriptLogic Service||N/A||2000/2003/2008/2008 R2|
*DA is supported on 32- and 64-bit versions of the Windows operating systems.
The following table summarizes the Windows domain types that work with Desktop Authority 8.0.
|Supported Network Types||Domain Types|
|Windows Domains||2000/2003/2008/2008 R2|
The following table summarizes the minimum disk space and RAM requirements for Desktop Authority 8.0 software components.
|DA Software Component||Minimum Disk Space||Minimum RAM|
|Operations Master (DA Manager)||1 GB plus minimum recommended for the operating system and SQL server||2 GB|
|Network Services (SLServer and Update Service)||262 MB2||20 MB3|
|Desktop Agent||636 MB3 for all options||75 MB3,4,5|
The following tables provide detailed resource requirements for each DA sub-component as well as 3rd-party software required by DA. Where the total (minimum) amount exceeds the sum of the sub-component requirements, the total takes into consideration overriding factors such as operating system requirements and temporary space for installations.
|Operations Master Disk Space||Minimum 1 GB (in addition to OS)|
|DA (including ScriptLogic and ScriptLogic Manager folders)||380 MB|
|Components conditionally installed on server:||-|
|MDAC 2.8||5.3 MB|
|SQL Server including Enterprise Tools and Help||360 MB|
|SQL Server Express||70 MB|
|Windows Installer 3.1||2.5 MB|
|.Net Framework||50 MB|
|SQL DMO||5 MB|
|Reporting Cache (One day for 1000 user logons per day)1||256 MB (per deployed SLServer Service)|
|MS Visual C++ 2005 Redistributable||5 MB|
|Operations Master RAM||Minimum 2 GB|
|DA Manager||75 MB|
|SQL Server Express||512 MB to 1 GB|
|Operations Master Service||52 MB|
|Network Services Disk Space||Minimum 262 MB (w/patch 1.4 GB3)|
|SLServer Service||0.6 MB|
|Update Service||5.1 MB|
|Data Collection Cache (One day for 1000 users per day)2||256 MB|
|Patch Files (Assume 50 patch files w/average 20 MB/file)3||1 GB|
|Network Services RAM||Minimum 20 MB (w/patch 100 MB3)|
|SLServer Service||3.2 MB|
|Update Service||16 MB plus 80MB when patching|
|Desktop Disk Space||Minimum 636 MB (all options)|
|Agent Software||100 MB|
|Expert Assist||35 MB|
|Patch Database||60 MB5 (3.5MB compressed)|
|Anti-spyware Binaries||16 MB|
|Anti-spyware Database||200 MB|
|Data Collection Files||1 MB|
|USB/Port Security Software (Embargo)||14 MB|
|USB/Port Security Device Access Logs||10 MB|
|Patch Files (Assume 10 patch files w/average 20 MB/file)3||200 MB|
|Desktop RAM||75 MB 3,4|
|SL CBM Agent4||9 MB|
|SL CBM User Experience4||4 MB|
|DA Update Client||7 MB (when patching)|
|SLAse (Anti-spyware engine)||4 MB|
|SBAMSvc||5-25 MB (greater when scanning)|
|Expert Assist||3.5 MB|
1 This sizing assumes data collection for 1000 computers and 1000 user logons per day for the entire system. In general, the reporting data collection cache managed by the ETL Service on the Operations Master requires approximately 256 KB of disk space for each user per day. By default the ETL Service will clear the cache each day. If ETL processing is not available or it is configured to run less than once per day (the default is 4 times per hour), the reporting cache size (available disk space) will need to be allocated accordingly to store the reporting data files. It is recommended that at least 3 days of storage be allocated to accommodate server or network outages and ensure no loss of data during that period. Note, data collection information is typically compressed when moved across the network. The compressed size is approximately 29 KB.
2 This sizing assumes each instance of SLServer Service services up to 1000 computers and 1000 user logons per day. In general, the reporting data collection cache managed by SLServer Service requires 256 KB of disk space for each user per day. By default the ETL Services on the Operations Master will clear the cache on the network server each day. If ETL processing is not available or it is configured to run less than once per day (the default is 4 times per hour), the reporting cache size (available disk space) on the network server will need to be allocated accordingly to store the reporting data files. It is recommended that at least 3 days of storage be allocated to accommodate server or network outages and ensure no loss of data during that period.
3 This sizing does not include your actual space required to store Microsoft and 3rd-party patches when using PDD. The number and size of Microsoft and 3rd-party patch files will vary. The component break down illustrates patch storage disk space for illustrative purposes.
4 On Terminal Servers one new instance each of SLclient.exe, SLagent.exe and ScriptLogic.CBM.UserExperience.exe are launched in each session, but the underlying Microsoft Windows memory management handles these as shared processes and so they require minimal extra physical memory for each instance. See http://support.microsoft.com/default.aspx?scid=kb;en-us;186572 for more information. The ScriptLogic.CBM.UserExperience.exe process should be disabled if you do not require notifications of patch and software installations to end users. Note, the new CBM Agent in version 8.0 (ScriptLogic.CBM.Agent.exe) is a computer based management service and therefore only a single instance is required in a Terminal Server environment.
5 While every effort is made to minimize the size of the patch database, it will grow over time as new Microsoft and 3rd party patches are released.