| Purpose: | Listed below are the hardware specifications and software requirements for the current version of Lightspeed Systems' Total Traffic Control software products and add-on services. |
| Product(s): | All Lightspeed System's software products. |
Hardware
Each installation requires a dedicated machine with the following resources.
| TTC | Policy Server | Reporting Server | Spam Server | SA Update Server | Lightspeed Rockets | |
|---|---|---|---|---|---|---|
| CPU | > 10Mbps of traffic = Dual P4 2.4ghz+ < 10Mbps of traffic = Single P4 2.4ghz+ |
See Below | ||||
| Ram | 4 GB 1 | |||||
| Hard Disk 2 | Preferred: Single partition with 120 GB available. Minimum: OS partition with 80 GB available. 3 (For performance 10k RPM or higher drives are recommended) | |||||
| RAID | If using RAID, RAID 1+0 or 0+1 is recommended. MS SQL has known performance issues with other RAID configurations. | |||||
| NICs | 3 | 1 | 2 | 3 | 1 | |
| VM Support | No | Yes (See VM tab) | No | No | Yes (See VM tab) | No |
Software
Each installation requires a dedicated machine with the following resources.
| TTC | Policy Server | Reporting Server | Spam Server | SA Update Server | Lightspeed Rockets | |
|---|---|---|---|---|---|---|
| OS | Windows Server 2003 4 (32 bit mode ONLY) 5 | See Below | ||||
| IIS | Version 5 or greater | |||||
| SQL | TTC v8.02+: SQL 2005, 2008, & 2008 R2 - Workgroup, Standard, & Enterprise TTC v7.03 - v8.01: SQL 2005 or 2008 w/SP1 - Workgroup 6 , Standard, & Enterprise NOTE: SQL must be installed locally on the same server as TTC. NOTE: SQL Express is a minimized SQL platform that is not supported. The database size limitations within SQL Express, are not adequate to support either current Content Database tables or future data growth. | .Net Framework | 2.0 | |||
Lightspeed Rockets
| Lightspeed Rockets (LSR-WAM & LSR-EM) | |||
|---|---|---|---|
| Hardware: | Lightspeed Appliance Lightspeed Systems sells a pre-configured appliance, please contact your sales representative for additional details. | ||
| Software: | FreeBSD which is pre-installed on the appliance | ||
| NICs |
|
| Ref | Notes |
|---|---|
| 1 | RAM Considerations Though MS Server 2003, Enterprise Edition will support up to 8GB of RAM, choosing additional processors over additional memory (above 4 GB) typically provides the better performance increases. NOTE: You should check with Microsoft as to how much RAM your version of Server 2003 OS can use. Some versions of Server 2003 can only support a maximum of 4GB, and all 32bit versions of Server 2000 can only support 4GB max. Additionally your server hardware may likely have a max limit also. |
| 2 | TTC Message Journaling Storage When full TTC Message Journaling is going to be employed (journaling Inbound, Outbound and Internal email traffic, as well as Instant Message traffic), it is recommended that a terabyte of disk storage be initially committed to the process. Over the long term, additional storage may be necessary to accommodate network/company growth, but factoring in those futuristic unknowns to reassess extended storage requirements can be performed long before the initial storage allotment reaches full capacity. Additional storage can be easily addressed and added to the journaling storage complex at any time. By default, the message journaling system keeps track of available storage and dispatches repeated alerts once the journaling storage space reaches 80% capacity. |
| 3 | Hard Drive Size: Many Dell servers are shipping with 12 gig OS partitions. This is not large enough to run TTC. |
| 4 | Comparison of Windows Server 2003 Editions please see Microsoft's site. |
| 5 | Unsupported Software Windows Server 2008 is unsupported. There were originally plans to create 64bit version of TTC (to be known as TTC v9.x) however due to hardware incompatibility between our appliance hardware and Windows Server 2008 we have been forced to stop development on TTC for Server 2008. Our ongoing development efforts are focused on delivering the next generation of TTC now known as the Lightspeed Suite. \\ Microsoft 2003 Extended Support End Date has been extended to July of 2015. (Source) |
| 6 | SQL 2005 Workgroup Edition has several limitations: It cannot use more than 3gb of RAM, and is limited to using only 2 CPUs. However on a typical TTC box, SQL does not use more than 3gb. SQL Workgroup is supported but not recommended for larger installations. |
| 7 | LSR-WAM NICs The LSR-WAM appliance ships with a management NIC and a failover (failover functionality can be disabled if so desired) card. This card can either be a 1Gbit copper of 1Gbit fiber configuration. |
| 8 | LSR-EM NICs only has and needs one single NIC as it does not sit in line but rather acts as a Store and Forward |
Virtual Support
Lightspeed supports virtualization of all product installations minus ones designed to be in-line and those that are appliance based 9 . This being said there are a few "standard disclaimers" that apply. If the VM's hosting server is overcommitted on resources (CPU or memory) then it may adversely affect performance of the product. Also (as always) other, non-software related, issues may arise that might make it so a real-physical machine is necessary for this environment.
Hardware and Software requirements for virtual servers are the same as if they were actual real-physical machines unless otherwise noted. All Lightspeed virtual testing performed on VMware ESX v3.5.0 and Xen Server v5.
- Hard disk - Drive must be either a Fibre Channel, iSCSI, or locally attached disk where the underlying disk are in a RAID-10 group. Ensure the LUN is lightly loaded, e.g. there shouldn't be 10 other virtual machines running on this same LUN.
- Resources - Oversubscribing and Over-committing of resources (CPU and memory) will cause issues and shouldn't be done.
| Ref | Notes |
|---|---|
| 9 | There are no plans to ever support any in-line products or appliances due to known issues of stability and throughput. |
Security Agent
| PC (SA) 10 11 | Mac v2.x (MSA) | Mac v1.x (MSA) | |
|---|---|---|---|
| Software | Windows XP x86/x64 |
Mac OS 10.7.x (Lion) Mac OS 10.6.x (Snow Leopard) x86 & x64 Mac OS 10.5.x (Leopard) Mac OS 10.4.x (Tiger) |
Mac OS 10.6.x (Snow Leopard) x86 Mac OS 10.5.x (Leopard) Mac OS 10.4.x (Tiger) |
| Hardware | CPU: 1.4 Ghz or higher Ram: 256 MB + (SA x86) Ram: 2 GB (SA x64) Hard Drive: approx. 150 MB |
Macintosh Intel and Power PC (Universal Binary) | Macintosh Intel and Power PC (Universal Binary) |
 | Minimum Memory Notes
|
| Ref | Notes |
|---|---|
| 10 | Language Editions: The SA has only been tested to work on English versions of Windows and may NOT work on foreign language editions. |
| 11 | Windows 2000: SA v8 and above does not and will not support Windows 2000. SA v7.02 was our last release to have this support and may still be found on the downloads page. |
User Agent
This software, with versions for Windows, Macs, and Linux, provides complete user/machine name reporting to the TTC Security Server and should be installed on workstations that cannot or will not use the TTC Security Agent.
| PC (UA) 12 | Mac (MUA) | Linux (LUA) | |
|---|---|---|---|
| Software | Windows 7/Vista/XP/2000 Windows Server 2003 |
Mac OS 10.7.x (Lion) Mac OS 10.6.x (Snow Leopard) Mac OS 10.5.x (Leopard) Mac OS 10.4.x (Tiger) |
Dialog |
| Hardware | CPU: P3 1 Ghz or higher Ram: 256 MB + Hard Drive: Negligible |
Macintosh Intel and Power PC (Universal Binary) | No Hardware requirements |
| Ref | Notes |
|---|---|
| 12 | v2 has two versions x86 and x64 compatible. Please download the appropriate one from [ALLDOCS:Software Downloads - Q10019] |
Power Agent
This software provides power management for computers and monitors.
| PC (PA) 13 | Mac (MPA) | |
|---|---|---|
| Software | Windows 7/Vista/XP/2000 | Mac OS 10.6.x (Snow Leopard) Mac OS 10.5.x (Leopard) Mac OS 10.4.x (Tiger) |
| Hardware | CPU: P3 1 Ghz or higher Ram: 256 MB + Hard Drive: Negligible |
Macintosh Intel and Power PC (Universal Binary) |
| Ref | Notes |
|---|---|
| 13 | x86 and x64 compatible. Please download the appropriate one from [ALLDOCS:Software Downloads - Q10019] |
Mobile Filter & Mobile Filter Browser
| PC 14 | Mac | iPhone, iPod, & iPad | Android | Linux | |
|---|---|---|---|---|---|
| Software | Windows 7/Vista/XP Terminal Server Citrix Server NComputing access terminals |
Mac OS 10.7.x (Lion) | None | 3.0 (Honeycomb) | Ubuntu |
| Hardware | None | None | iPhone iPod Touch iPad |
None | None |
| Ref | Notes |
|---|---|
| 14 | Two versions exists, a 32-bit and a 64-bit version of the Mobile Filter. The 64-bit version is to be installed on 64-bit machines and will filter both 32-bit and 64-bit browser applications. |
TTC Exchange Message Journaling Agent
TTCEMJ-EWSv2 Hardware Requirements:
TTCEMJ-EWSv2 can be integrated into your network in one of three ways:
- Operating as a standalone server, providing real-time email journaling to a remote TTC Security Server. This is the preferred configuration.
- Operating as an add-in utility on a active TTC Security Server that is strictly limited to managing network email scanning, filtering and journaling. Not recommended, but can work.
- Operating as an add-in utility on an active Exchange 2010 Server. Again, workable, but not optimal.
For the first (preferred) option, minimum hardware requirements would be:
- Processor: Minimum 2.0 GHz, Dual Core Recommended
- RAM: 2GB, 4 GB Preferred.
- Storage: 40 GB on primary drive, 80 GB Recommended
- NIC: Server Class 10/100/1000
For the second option, minimum hardware requirements will match those specified for all TTC Security Servers.
For the third option, the selected Exchange Server should not be running with all CPU's above 60% capacity. Also, there should be at least 600 MB of free ram available for TTCEMJ-EWSv2.
 | Virtualization Support TTCEMJ-EWSv2 is developed and tested on Windows Server 2003 / 2008 guests running under a XenServer host. It has also been tested on VMWare's ESX server. Accordingly, it is supported on either of these environments. When creating the guest environments, use the Hardware Requirements noted above as the minimum parameters for the guest O/S. |
TTCEMJ-EWSv2 Software Requirements:
- If running TTCEMJ-EWSv2 on an Exchange 2010 Server:
- Microsoft Exchange 2010 Server MUST be running.
- If running TTCEMJ-EWSv2 on its own server (this is the recommended configuration):
- Windows Server 2003 - both Enterprise and Standard editions are supported, as well as either the x86 or x64 platform.
- Windows Server 2008 - Enterprise and Standard editions are supported, as well as either the x86 or the x64 platform. Also, the newly released R2 edition of Server 2008 is fully supported. As the R2 edition comes with Powershell 2.0 installed, this is one less prerequisite that must be manually installed.
- Management Tools for Exchange 2010 are optional and not required. Due to the remote management capability of Powershell 2.0, TTCEMJ-EWSv2 is able to communicate with the Exchange CAS and Mailbox Role machines without requiring the presence of the Management Tools.
- Microsoft Powershell v2. Note that Windows Server 2008 R2 comes with Powershell 2.0 already installed. If you're not running on this environment, you can download Powershell here: Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)
- Microsoft .Net Framework 3.5 or greater.
- If operating on a TTC Security Server, their should be at least 40% CPU and 600 MB of free ram available. As a TTC Security Server is usually very busy, we do not recommend you install TTCEMJ-EWSv2 on a TTC Security Server. However, it will work. IT will work better if the TTC Server is functioning as a Journaling server only. Additionally, you will need to have Microsoft's Powershell v2.0 or greater installed on the TTC Server.
TTCEMJ-EWS Hardware Requirements:
TTCEMJ-EWS can be integrated into your network in one of three ways:
- Operating as a standalone server, providing real-time email journaling to a remote TTC Security Server. This is the preferred configuration.
- Operating as an add-in utility on a active TTC Security Server that is strictly limited to managing network email scanning, filtering and journaling. Not recommended, but can work.
- Operating as an add-in utility on an active Exchange 2007 Server. Again, workable, but not optimal.
For the first (preferred) option, minimum hardware requirements would be:
- Processor: Minimum 1.6 GHz, Dual Core Recommended
- RAM: 1GB, 2 GB Preferred.
- Storage: 40 GB on primary drive, 80 GB Recommended
- NIC: Server Class 10/100/1000
For the second option, minimum hardware requirements will match those specified for all TTC Security Servers.
For the third option, the selected Exchange Server should not be running with all CPU's above 60% capacity. Also, there should be at least 600 MB of free ram available for TTCEMJ-EWS.
| Virtualization Support TTCEMJ-EWS is developed and tested on Windows Server 2003 / 2008 guests running under a XenServer host. It has also been tested on VMWare's ESX server. Accordingly, it is supported on either of these environments. When creating the guest environments, use the Hardware Requirements noted above as the minimum parameters for the guest O/S. |
TTCEMJ-EWS Software Requirements:
- If running TTCEMJ-EWS on an Exchange 2007 Server:
- Microsoft Exchange 2007 Server with Service Pack 1 or greater MUST be running. The RTM version of Exchange 2007 is not supported.
- If running TTCEMJ-EWS on its own server (this is the recommended configuration):
- Windows Server 2003 - both Enterprise and Standard editions are supported, as well as either the x86 or x64 platform.
- Windows Server 2008 - Enterprise and Standard editions are supported, as well as either the x86 or the x64 platform.
- Management Tools for Exchange 2007 are optional and not required. If you attempt to install TTCEMJ-EWS without the Exchange Management Tools present, the Initial Configuration Wizard will not be able to create the Journaling Mailbox, but will provide you with instructions on how to perform this step using a tool included with TTCEMJ-EWS. Should you desire to install the Exchange Management Tools, this Microsoft TechNet article provides more info on installing / running the Management Tools: http://technet.microsoft.com/en-us/library/bb232090(EXCHG.80).aspx
Exchange Management Tools for x86 Systems
Microsoft has made available a 32-bit version of the Exchange 2007 Management Tools. If you want to install TTCEMJ-EWS on a 32-bit platform and have EMJ be able to create the required Journaling Mailbox automatically, you should install the 32-bit version of the Exchange 2007 Management Tools. They are available for download here: Exchange Management Tools for x86 Platforms - Microsoft Powershell 1.0. To download Powershell, see this page: How to Download Windows Powershell
- Microsoft .Net Framework 2.0 (with at least SP2) or greater.
- If operating on a TTC Security Server, their should be at least 40% CPU and 600 MB of free ram available. As a TTC Security Server is usually very busy, we do not recommend you install TTCEMJ-EWS on a TTC Security Server. However, it will work. Additionally, you will need to have Microsoft's Powershell v1.0 or greater installed on the TTC Server.
 | EMJ should not be installed on a server that is currently or ever was an active Domain Controller (DC). There are known issues with the functionality of EMJ when installed in this environment. These issues relate to the fact that when a server is promoted to the state of DC the permissions are modified. Even when the box is demoted Microsoft does not fully reset these permissions to their prior state. It is recommended not to use a DC for EMJ installation. |
TTC Security Agent Anti-Virus for Exchange
TTC Security Agent Antivirus for Microsoft Exchange (SAAVEx) is an add-on product for your Exchange 2003 servers. Utilizing the anti-virus capabilities of TTC's Security Agent, SAAVEx has the ability to provide anti-virus scanning capabilities to all items (public and private) in an Exchange store. Utilizing Microsoft's VSAPI (Virus Scanning API), SAAVEx will perform an anti-virus scan on all items currently residing in an Exchange store as well as all new items that arrive.
Hardware Requirements
Since SAAVEx must be installed directly on the Exchange server it is going to protect, its hardware requirements are the same as Exchange's - if Exchange is performing ok, SAAVEx will also perform satisfactorily.
Software Requirements
SAAVEx requires that the following software be installed:
- Microsoft Exchange 2003 - any edition (SAAVEx might work with Exchange 2000, but it has not been tested against this version.)
- TTC Security Agent v6.02.05 - or above (if the Security Agent (SA) is not present on the Exchange Server, SAAVEx's setup program will automatically download and install the correct version of Security Agent).
As you can see, the hardware and software requirements for SAAVEx are simple.
| SAAVEx should not be installed on a server that is currently or ever was an active Domain Controller (DC). There are known issues with the functionality of SAAVEx when installed in this environment. These issues relate to the fact that when a server is promoted to the state of DC the permissions are modified. Even when the box is demoted Microsoft does not fully reset these permissions to their prior state. It is recommended not to use a DC for SAAVEx installation. |
TTC GroupWise Journaling and Anti-Virus
GWJAV Hardware Requirements:
GWJAV can be integrated into your network in one of three ways:
- Operating as an add-in utility on a active TTC Security Server that is strictly limited to managing network email scanning, filtering and journaling, or
- Operating as a standalone server, providing off-line email anti-virus scanning, distribution list parsing and message queuing to a remote message journaling server, or
- Operating as an add-in utility on a active TTC Security Server that is performing all primary TTC network functions of Content Filtering, Spam Mail Blocking, Message Journaling and Traffic Reporting.
For the first and third options, minimum hardware requirements will match those specified for all TTC Security Servers - please reference TTC Hardware and Software Requirements - Q10006.
For the second option, minimum hardware requirements would be:
- Processor: Minimum 1.6 GHz, Dual Core Recommended
- RAM: 1GB, 2 GB Preferred.
- Storage: 40 GB on primary drive, 80 GB Recommended
- NIC: Server Class 10/100/1000
GWJAV Software Requirements:
GroupWise Server
GroupWise v7.03 or v8.0x is required for operations with the GWJAV agent. GW 8.0x support requires GWJAV version 1.05 or higher.
There are known compatibility issues with Groupwise v7.04 which we are currently attempting to address. GWJAV TTC Server
If operating on a TTC Security Server, it's minimal software requirements will support the GWJAV agent.GWJAV Standalone
If operating as a standalone server, the GWJAV Server should be installed with:
- Operating System: Windows Server 2003
- Novell Client (needed to create a Trusted Key)
- .Net Framework 2.0+
| GWJAV should not be installed on a server that is currently or ever was an active Domain Controller (DC). There are known issues with the functionality of GWJAV when installed in this environment. These issues relate to the fact that when a server is promoted to the state of DC the permissions are modified. Even when the box is demoted Microsoft does not fully reset these permissions to their prior state. It is recommended not to use a DC for GWJAV installation. |
Related Articles:
|
Return to Parent Page: Public Info -- Index |
|
Pages with common labels/tags (Click to show, if any) |
Comments (2)
May 23, 2011
Rich Fielding says:
"We recognize that Microsoft will be ending support for Server 2003 in June of 2..."We recognize that Microsoft will be ending support for Server 2003 in June of 2011 and we will either have everything migrated to the Rocket or have Server 2008 support prior to that."
June of 2011 is one week away...is support of 2008 as well? Incidentally, Microsoft stopped Mainstream Support of 2003 in July of 2010: http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+Server+2003+R2
May 25, 2011
Jeff Wilbert says:
Rich, please see the updated footnote 5.Rich, please see the updated footnote 5.