Preparing the server computer

The server computer does not have to be dedicated exclusively to PDXpert, although sharing hardware resources with other applications and functions may affect system performance.

  • Ensure that your server computer conforms to the server system requirements.

  • Operating system configuration:

    • PDXpert requires Microsoft .NET Framework. If your system's permission profile could block PDXpert setup's installation of .NET, upgrade your computer manually using the Microsoft .NET Framework installer.

    • Ensure your computer has the latest Microsoft Windows, .NET and (if needed) SQL Server service packs and updates. Restart your computer after all updates are installed.

    • Communications between the PDXpert server and client can be encrypted at user log-in by marking the Encrypt my connection to this server option. This perfect forward secrecy protocol uses TCP transport security with Certificate Credentials. Windows Communication Foundation (WCF) determines the encryption level available for PDXpert's communications. The WCF framework automatically chooses the highest protocol available, and can be limited by the Windows and .NET versions on the server machine and on each client machine. The combination of PDXpert 12.2 / Windows Server 2012 / Windows 8 / .NET 4.6 (and all more recent versions of these) use TLS 1.2 or higher, while using an older version for any one of these may use an older protocol. If you require a specific TLS level, both server and client Windows must have the necessary configuration settings. See Microsoft Windows and .NET Support for TLS 1.2

  • Storage device use:

    • Do not use a compressed, network-mapped, backup or other external (e.g., USB) disk for the application or data.

    • To support a practically unlimited number of files in the Library folder, your server's hard disk should be formatted as NTFS.

    • Use a local fixed disk (HDD/SDD) with substantial free space. The "file attachments" library grows much faster than the rate of database (MDF/LDF) growth.

    • Database performance is very sensitive to disk latency and transfer speed; faster is always better.

  • Virtual machine use:

    • The virtual disk must appear as a local drive. SQL Server is disk-intensive: the virtual disk should use the local disk bus located on the same physical server as the VM, or a SAN-based virtual disk must use equivalent performance.

    • Use a fixed-sized disk. Avoid using a dynamically-sized disk — this may cause significant delays when the database or library reaches the disk's limit, and performance degrades because the data is highly fragmented.

  • To support latest versions of SQL Server, install the current Windows Installer release.

  • When using Turkish Windows, avoid using Turkish i/ı characters in the machine name. Microsoft Windows does not fully support these characters in IDNA implementations prior to Windows 8.1.

    To minimize incompatibility between network devices, DNS services, operating systems and local languages, assign only ANSI uppercase alphanumeric and hyphen ("-") characters to a server machine name and workgroup or domain name. If you intend to connect your server computer to an SMTP server, this is a requirement per RFC-1123, Section 2.1: <let>[*[<let-or-digit-or-hyphen>]<let-or-digit>].

Install Guide Contents