Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.
  1. Ensure your hardware configuration meets the recommended specs outlined in the On Site System Requirements
  2. Download the FogBugz On Site ISO and ensure it is available at the time of installation. A Fog Creek technician will provide download details when scheduling your installation. The ISO image can be burned to physical media or mounted. ISO image mounting is available in Windows Server 2012 R2 or via separate tooling.
  3. Ensure the Web Server (IIS) Role is enabled on the server where FogBugz On Site will be installed. In Windows Server 2012 R2, this can be installed with Add Roles & Features.
  4. Ensure .NET 3.5 is installed on the server where FogBugz On Site will be installed. In Windows Server 2012 R2, this can be installed with Add Roles & Features.
  5. Ensure the PowerShell execution policy has been set to RemoteSigned or Unrestricted on the server where FogBugz On Site will be installed (Set-ExecutionPolicy RemoteSigned). This is required to run the FogBugz On Site installation PowerShell script and can be reversed once the installation is complete (Get-ExecutionPolicy will return your current policy).
  6. Create a Windows Local Administrator account (e.g. fogbugz-onsite) under which the FogBugz On Site application pools will run. Please have the credentials for this account available at the time of installation. If you plan to use Windows authentication for database access in FogBugz On Site, please create a SQL user for this Windows account on your target SQL Server instance and grant this user the dbcreator role. Account permission can be reduced to db_owner on your FogBugz On Site databases once the installation is complete.
  7. If you plan to use SQL authentication for database access in FogBugz On Site, please create a SQL authentication account (e.g. fogbugz-onsite) on the target SQL Server instance. This account must be granted the dbcreator role. Account permission can be reduced to db_owner on your FogBugz On Site databases once the installation is complete. Please have the credentials for this account available at the time of installation.
  8. If you are a former FogBugz For Your Server Customer, you’ll follow these directions to migrate your data.  We recommend scheduling the install and the migration for separate days to minimize downtime.

If requested by Fog Creek, please send us a bare schema export of your current FogBugz For Your Server database. We require this to prepare a script which will correct any schema drift which may have occurred with your FogBugz For Your Server database over time. This schema export must include index creation. To generate this export from SQL Server Management Studio:

  • Right-click on your FogBugz database and select Tasks > Generate Scripts…
  • Under Choose Objects, select Tables (which will select all Tables) and click the Next > button.
  • Under Set Scripting Options click the Advanced button.
  • Ensure Script Indexes is set to True.
  • Save to a .sql file with Unicode text.
  • Send us this .sql file only if requested.