Windows System Requirements

Before installing FogBugz for Windows, you should run through this checklist to make sure your server has all the required components.

Computer

Any Pentium-class computer will probably be fine for most teams. We've run databases with over 100 users off of a single Pentium II/266 MHz. We recommend at least 512 MB of memory for optimal performance.

Operating System

FogBugz for Windows works on the following operating systems:

Windows 2000
Windows XP Professional
Windows Server 2003

Windows NT 4.0 No Longer Supported

We no longer support Windows NT 4.0. FogBugz 4.x and above have not been tested with Windows NT 4.0.

Windows 2000

FogBugz is compatible with Windows 2000 Professional, Server, Advanced Server, or Datacenter. You should also make sure you have the following components, which Microsoft distributes free:

  • VBScript version 5.6 or later (download here).
  • Internet Information Services (a part of Windows 2000). If it is not installed you may install it from Start | Control Panel | Add or  Remove Programs | Add or Remove Windows Components.

Windows XP

FogBugz is compatible with Windows XP Professional Edition but not Home Edition. You need to install IIS, which is not installed by default. If it is not installed you may install it from Start | Control Panel | Add or  Remove Programs | Add or Remove Windows Components.

Windows XP Professional has a 10 concurrent connection limit.  See the EULA for XP pro, under 1. Grant of License: Installation and Use.

Windows Server 2003

FogBugz is compatible with Windows Server 2003. Using the "Manage Your Server" application, click "Add or remove a role" and insure that the "Application Server" role is turned on.

Data Access Libraries

We recommend installing the latest version of Microsoft's Data Access components ("MDAC"). We test FogBugz extensively with MDAC version 2.6. You can find the latest version of MDAC on Microsoft's web site by going to http://www.microsoft.com and entering MDAC in the search box.

Web Server

FogBugz for Windows runs on the IIS (Internet Information Services) web server, which is a component of Windows. Other web servers in Windows are not supported.

Database

You have three choices:

  1. Microsoft Jet (4.0sp3)
  2. MySQL (more info)
  3. Microsoft SQL Server (7.0, 2000, 2005)

Microsoft Jet is available for free from Microsoft and is good enough for small teams using FogBugz. It works fine for up to about 10 users. It does not support full text search.

Jet is preinstalled on Windows 2000 and later, so you don't have to install Jet. The latest version is available from Microsoft's web site; go to http://www.microsoft.com and enter Jet in the search box.

MySQL is an extremely popular open-source database available for free from MySQL AB. MySQL supports full text search. Download and install from http://www.mysql.com/.  See http://www.fogcreek.com/FogBugz/KB/dbsetup/UsingMySQL-2.html for more information.

Microsoft SQL Server is a commercial, industrial strength database which will scale to virtually any size software team. It requires a license from Microsoft, and makes FogBugz work faster and more reliably on larger teams. SQL Server supports full text search.

Our recommendations: If you can afford it or already have a Microsoft SQL Server license, use Microsoft SQL Server. For very small teams or casual bug tracking, use Jet. Otherwise, use MySQL.

For Email Integration

To send email, you need an SMTP server. If you have the ability to send Internet email, you probably already have one of these somewhere. There is also a free SMTP server included in Microsoft's Internet Information Server (IIS).

For FogBugz to receive incoming mail, you need a POP3 server. FogBugz supports plain POP3 and secure (ssh-based) POP3. Virtually all email servers support POP3.

For Source Code Control Integration

We support Subversion, Perforce, CVS, Visual SourceSafe, and Vault. If you are not already using source code control tools, we recommend Subversion (open source) for small or medium projects, and Perforce (commercial and rather expensive) for extremely large projects.

Other source code control systems can be used if they support some form of triggers and have a web interface, although you will have to write a small script. More info.