Before installing FogBugz for Windows, you should run through this checklist to make sure your server has all the required components.
Computer
Most modern Intel servers will be fine for most teams. We recommend 2 GB of memory for optimal performance.
Do not run FogBugz on a server which is also running large enterprise applications such as Microsoft Exchange or Microsoft Sharepoint.
Operating System
FogBugz for Windows works on the following operating systems:
Windows XP Professional
Windows Server 2003 (SP2 or later)
Windows Vista
Windows 2008Windows 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.
Windows Server 2003 (SP2 or later)
FogBugz is compatible with Windows Server 2003 SP2 or later. Using the "Manage Your Server" application, click "Add or remove a role" and insure that the "Application Server" role is turned on.
Windows Vista
Windows Vista and 2008 is now officially supported. Below are notes on what you may need to get FogBugz to work on Vista and 2008.
By default, IIS 7.0 is not installed on Windows Vista Business or Ultimate, or 2008. You can install IIS by opening Programs and Features under Programs in Control Panel, and clicking the link to Turn Windows Feature on or off on the sidebar. Make sure to install the ASP components, which are not installed by default, prior to starting the installation. This can be found under IIS->WWW Services->Application Development Features->ASP. Vista is not designed as a server, and will limit you to about 10 connections.
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.
.NET Framework 2.0
The .NET Framework is now required. It may not be installed by default. You can download the installer from Microsoft.
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:
Microsoft Jet (4.0sp3) MySQL (5.0 or later, more info) Microsoft SQL Server (7.0, 2000, 2005, 2008)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.
Jet is preinstalled on Windows XP 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. 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. There is also now a free version called SQL Server Express, which also works with FogBugz.
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. SQL Server Express will work for most other situations, unless you already have MySQL running.
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 Mercurial (open source).
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.