Issuetrak System Requirements

This article provides the system requirements for the Issuetrak application. 

Upgrade Notes

• Issuetrak is not supported on in-place OS upgrades of any kind.
• Issuetrak is not supported on SQL Server in-place upgrades.
• Issuetrak requires that your current instance is on version 10.3.7 or higher before proceeding. If your environment is currently running an earlier version, please contact Issuetrak Support for assistance.

Database Server

• Processor – Dual Core 1.8 GHz Processor
• Memory – 4 GB available RAM
• Disk Space – 4 GB available hard disk space
• Operating System – Windows Server 2019, 2022, or 2025 (32/64-bit; Standard, Datacenter)

• Applications and Settings – Microsoft SQL Server 2017, 2019, or 2022 (32/64-bit; Standard, Web, Enterprise or Business Intelligence Edition)
  • Full-Text Search feature must be installed
  • SQL_Latin1_General_CP1_CI_AS collation enabled
  • SQL Server and Windows Authentication mode enabled
  • TCP/IP and/or Named Pipes protocols enabled in SQL Server
  • Database compatibility level for any given Issuetrak database to be upgraded must be set to a minimum level of 130

• Additional Requirements:
  • Microsoft .NET Framework 4.7.2 or greater
  • Region and Language Settings should have the current locale set to “English (United States)”

Web Server

• Processor – Dual Core 1.8 GHz Processor
• Memory – 4 GB available RAM
• Disk Space – 4 GB available hard disk space
• Operating System – Windows Server 2019, 2022, or 2025 (32/64-bit; Standard, Datacenter)

• IIS Version and Server Roles – Microsoft Internet Information Services (IIS) 7.5, 8.0, 8.5, or 10.0
  • Web Server (IIS) installed as a Role in Windows Server Manager with the following Role Services installed:
    • Common HTTP Features: Static Content
    • Application Development: ASP, ASP.NET 4.5 or higher, and ISAPI Extensions
    • Security: Request Filtering
    • Performance: Static Content Compression
  • If deploying API v2:
    • .NET 6.0 Hosting Bundle - which can be obtained here.
      • Newer versions of the .NET Hosting Bundle will not currently work with API v2.
      • This must be installed after IIS. If it is installed before IIS, then deployments will fail.
    • API v2 needs to be in its own IIS Application Pool, which must be set to "No Managed Code"

• Additional Settings:
  • Microsoft OLE DB Driver 18 for SQL Server
    • MS OLE DB Driver 19 for SQL Server is also supported, so long as your environment is already configured to use it.
  • Microsoft .NET Framework 4.7.2 or greater
  • PowerShell 5.0 or greater
  • Issuetrak requires that its classic and MVC application pools are running .NET Framework v4.0.
  • Issuetrak recommends securing each installation with SSL.
  • IIS must have the URL Rewrite Module installed.
  • IIS must have the HTTP Module installed.
  • Soft requirement:  IIS needs to have the HTTP Redirection module installed in order to allow the deployment tools to redirect web requests to a user-friendly "Please wait while your site is being upgraded" screen. 

Incoming Email

• Applications – POP3, Secure POP3, IMAP, or Microsoft Exchange 2013 or newer

Outgoing Email / Notifications

• Applications – SMTP-based outgoing email server

DPAPI Encryption

• Microsoft .NET Framework 4.7.2 or greater

Lightweight Directory Access Protocol (LDAP)

• AD-based Public Key Infrastructure (PKI), if enabling CAC/Smart Card Authentication
• Microsoft Cryptographic API-compatible revocation provider on web server, if enabling Smart Card Authentication

• AD Single Sign-On requires:
  • Windows Authentication Role Services enabled in the Web Server (IIS) Role
  • Integrated Windows Authentication enabled within IIS

• AD SSL Encryption requires an LDAPS certificate to be installed on the Domain Controller
• For Cloud customers: AD SSL encryption also requires that your Domain Controller supports TLS 1.2.

Active Directory Federation Services (AD FS)

• AD FS 2016 or higher - See Microsoft's article for AD FS server requirements.
  • OpenID Connect / OAuth connections via Application Groups
• Multifactor authentication (MFA) requires at least one other authentication method, and is dependent entirely on the implementation of AD FS in your environment.  See this article for more details.

Asset Management

• Remote Asset Auditing
  • The machine TrakAsset is executed from must have WinRM installed
  • The machine TrakAsset is executed from must have Active Directory Module for Windows PowerShell installed
  • The machine TrakAsset is executed from must allow ICMP in order for its connection test function
  • Both the local machine and the remote machine must be on the same domain
  • The account that executes TrakAsset must be a domain administrator and must not have a blank password
     
• TrakMac on Macs with M1 processor
  • The Mac must have Rosetta installed in order for the software to function

Windows Integrated Security

• The Integrated Security user that you designate needs to be a Domain-authenticated service account with:
  • "Access this computer from the network" rights for BOTH Web and SQL servers
  • "Log on as a service" rights on the SQL server
  • "Log on as a batch job" on the Web server

Web Browser

• Firefox, Chrome, Microsoft Edge Chromium

SSL Configuration

Implementing this recommendation will require the installation of an SSL certificate on the hosting web server. There are two typical scenarios for installing an SSL certificate within IIS. The first scenario involves creating a self-hosted certificate, a certificate type that is submitted to a Certificate Authority (CA) that is a server under the control of the hosting organization. The second scenario involves requesting a third-party certificate, a certificate issued by an external CA. Examples of certificate vendors that issue third-party certificates include (but are not limited to):

• VeriSign (https://www.verisign.com)
• GeoTrust (https://www.geotrust.com)
• Thawte (https://www.thawte.com)

The following Microsoft knowledgebase articles provide step-by-step instructions for requesting a certificate, installing the certificate within IIS, and setting the HTTPS binding for a site so that only SSL connections are permitted.

• “How to Set Up SSL on IIS 7”: Provides steps for configuring SSL for IIS 7.0 and above.
• “Configuring SSL in IIS Manager”: Provides a video on enabling SSL security with self-signed certificates for IIS 7.0 and above.
• “IIS 8 – Certificate Management and Deployment”: Provides a video overview of certificate management within IIS 8.

In addition, if the API is deployed, then the application pool identity that is assigned to the Issuetrak API application pool must have read and write permissions on the folder used to store Issuetrak attachments. The following Microsoft IIS article provides detailed information on not only configuring IIS Application Pool Identities but also configuring the security for resources such as files and folders.

Application Pool Identities

Additional Notes

• Your Issuetrak database and web server can reside on the same or separate machines, dedicated or shared machines, or physical or virtual machines that meet the minimum requirements.
• Issuetrak cannot reside on the same server as Microsoft Exchange, SharePoint, or Windows Server Update Services (WSUS).
• We recommend additional processing power, RAM, and disk space for optimal performance and long-term scalability. When using a shared machine, we also recommend keeping the overall size and number of applications running on that machine to a minimum.
• Issuetrak cannot reside on Windows Server Essentials, Windows Nano Server, Server Core, or a Domain Controller.
• SQL Server Express is not a supported edition of Microsoft SQL Server.
• Safari is not a supported browser for use with Issuetrak.
• FIPS (Federal Information Processing Standards) is supported.
• Microsoft Azure SQL is not a supported database platform.
• As of December 31, 2020, all versions of Microsoft Internet Explorer are no longer supported and may result in unexpected behavior with Issuetrak.  
• Please note that certain IIS modules such as URLScan may interfere with HTTP request distribution to the API site endpoints. In particular, any modules that restrict or deny requests with the HTTP verbs GET, POST, PUT, and DELETE must be reconfigured to permit access for HTTP requests using those HTTP verbs for the API site.