Pre-Installation Checklist and Configuration Steps for FogBugz On-Premises Installation


Follow

Overview

Before installing FogBugz On-Premises, you will need to do additional configurations to your server(s) and users to ensure all prerequisite server features are enabled and configured, and required service users have been created, enabled, and configured.

 


Prerequisites

 


Information

 

Parameters Required During Install

During the install process, the install script will require some parameters. Please have them prepared beforehand.

  • Installation Directory: The location on the disk where FogBugz On-Premises will be installed.
  • Service Username: The username for the user under which your FogBugz On-Premises application pools will run. This user needs to be a Local Administrator. This is the same user that will be used to connect to the SQL Server if Windows Authentication is used.
  • Service Password: The password for the user under which your FogBugz On-Premises application pools will run.
  • SQL Server Instance: The SQL Server instance where your FogBugz On-Premises databases will be hosted.
  • SQL Server Username: (Optional) If using SQL authentication, the username for the SQL authentication account which will be used to create and access your FogBugz On-Premises databases.
  • SQL Server Password: (Optional) If using SQL authentication, the password for the SQL authentication account which will be used to create and access your FogBugz On-Premises databases.
  • Fully Qualified Domain Name (FQDN): The FQDN where you plan to access FogBugz (e.g. fogbugz.yourdomain.com).
  • Administrator Email: The email address for the initial site administrator account created during your FogBugz On-Premises installation.
  • SMTP Server: (Optional) The host for the SMTP server where FogBugz will use to send emails.
  • SMTP Port: (Optional) The port over which FogBugz will connect to your SMTP server.
  • SMTP User: (Optional) The SMTP user FogBugz will use to access your SMTP server.
  • SMTP Password: (Optional) The password for the SMTP user.
  • SMTP SSL: (Optional) Whether or not FogBugz should use SSL when connecting to your SMTP server.

 

Back to the top


Environment Settings

The following server features need to be enabled and configured

  1. Ensure the Web Server (IIS) Role is enabled on the server where the FogBugz On-Premises will be installed.
    • In Windows Server 2012/2016, this can be installed with Add Roles & Features.
  2. Ensure .NET 3.5 is installed on the server where the FogBugz On-Premises will be installed.
    • In Windows Server 2012/2016, this can be installed with Add Roles & Features.
  3. Ensure the PowerShell execution policy has been set to RemoteSigned or Unrestricted on the server where the FogBugz On-Premises will be installed.
    • Command Get-ExecutionPolicy returns your current policy.
    • The policy can be changed using the following command (case sensitive):
      Set-ExecutionPolicy RemoteSigned
    • This is required to run the FogBugz On-Premises installation PowerShell script and can be reversed once the installation is complete.
  4. Configure FQDN for Fogbugz On-Premises
    • Your FogBugz On-Premises FQDN consists of a Site Identifier and a Host in the form of http://{site identifier}.{host}
    • This FQDN must be configured on your DNS server to resolve to your FogBugz On Premises web server. Example FQDNs that fit this pattern are:
      • fogbugz.yourdomain.com
      • fogbugz.yourserver

    • Additionally:
      • localhost:80 must be bound to your FogBugz On-Premises web site in IIS on your FogBugz On Premises web server.

    • For development environments or environments where the production DNS server is not accessible, you can use the Windows hosts file C:\Windows\System32\Drivers\etc\hosts to override the default DNS settings, by adding a new entry at the end of the file. For example: 127.0.0.1 fogbugz.yourdomain.com to configure it on a local development environment.

 

Back to the top


Service and User Accounts

  1. The Windows account executing the install script needs to be Local Administrator on the given server (start the PowerShell prompt with Run as Administrator).
  2. IMPORTANT! Create a Windows Local Administrator account (e.g., fogbugz-onprem) under which the FogBugz On-Premises application pools will run.
    • Please have the credentials for this account available at the time of installation.
  3. Authentication for the database access in FogBugz On-Premise
    • If you plan to use Windows Authentication, please grant access to this Windows account on your target SQL server instance.
    • If you plan to use SQL Authentication, please create a SQL user (e.g., fogbugz-onprem) on the target SQL Server instance.
    • In both cases, the account must be granted the dbcreator role. Account permission can be reduced to db_owner on your FogBugz On-Premises databases once the installation is complete.
    • If, after the installation, you need to reduce the role of the database user from db_ownerto even lesser access levels like db_datareader and db_datawriter roles (for ex. due to security policy), it should not have any negative impact as long as it is ensured that the FogBugz application (user account) has the right to INSERTUPDATE and DELETE records in the database.
      NOTE: Both db_datareader and db_datawriter roles are must-haves.
    • Please have the credentials for this account available at the time of installation.

 

Back to the top


FogBugz For Your Server (FBYS) Customers

Migrate your data

If you are a FogBugz For Your Server (FBYS) customer, follow these directions to migrate your data.  We recommend scheduling the installation and the migration for separate days to minimize downtime.

 

Exporting Database Schema

When you are upgrading from a previous version like FogBugz For Your Server (FBYS) with the help of the FogBugz team, you might be requested to send us a bare schema export of your current FBYS database.

  • It is needed to prepare a script that 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:

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

 

Back to the top