PDXpert PLM Software
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.
- 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.
- Do not use a compressed, network-mapped, backup or other external (e.g., USB) disk for the application or data.
- If you install on a virtual machine, the virtual disk must appear as a local drive. PDXpert is a disk-intensive application: the virtual disk should use the local disk bus (e.g., SATA) located on the same physical server as the VM, or a SAN-based virtual disk must connect using 1Gbps or better.
Use a hard disk (HDD/SDD) with substantial free space. The "file attachments" library grows much faster than the rate of database (MDF/LDF) growth.
If the PDXpert server is installed on a virtual machine, 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 a practically unlimited number of files in the Library folder, your server's hard disk should be formatted as NTFS.
- To support current versions of SQL Server, install Windows Installer 4.5 (or higher). If needed, download Microsoft Windows Installer 4.5.
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 the workgroup or domain name.
Install Guide Contents
- 001. Installation overview
- 002. Preparing the server computer
- 003. Standard PDXpert System setup
- 004. Standard PDXpert PLM client setup
- 005. Installing LocalDB for PDXpert client ODBC
- 006. Custom installation: SQL Server
- 007. Custom installation: PDXpert server
- 008. Custom installation: Private cloud
- 009. Custom installation: Group Policy
- 010. Upgrading the PDXpert Application Server
- 011. Upgrading the PDXpert PLM client
- 012. PDXpert server post-install checklist
- 013. Moving PDXpert server database and files
- 014. PDXpert Application Server diagnostics
- 015. PDXpert PLM client diagnostics
- 016. Microsoft SQL Server diagnostics
- 017. Microsoft SQL Server log files
- 018. Connecting SQL Server Management Studio
- 019. Upgrading SQL Server
- Installing and upgrading older PDXpert releases
- 023. Service configuration settings
- 024. Application folders and files
- 025. System architectural diagram
Release notes (change history)
- PDXpert 9.0 release notes
- PDXpert 9.1 release notes
- PDXpert 9.2 release notes
- PDXpert 9.3 release notes
- PDXpert 10.0 release notes
- PDXpert 10.1 release notes
- PDXpert 10.2 release notes
- PDXpert 10.3 release notes
- PDXpert 11.0 release notes
- PDXpert 11.1 release notes
- PDXpert 11.2 release notes
- PDXpert 12.0 release notes
- PDXpert 12.1 release notes
- PDXpert 12.2 release notes