OpenText Best Practices
Modified on: Wed, 18 Mar, 2026 at 4:01 PM
This article outlines recommended best practices for migrating to or from OpenText (On-Premise) using LinkFixer Advanced.
Note: LinkFixer Advanced is tested to work with OpenText Content Server version 10.5 and above. Compatibility with earlier versions may vary.
1. LinkFixer Advanced Machine / Server
Ensure the system running LinkFixer Advanced meets all minimum requirements.
- Hardware requirements
- Software requirements
- Microsoft SQL database requirements
- System permissions
Permissions Requirement:
For OpenText integration, the user account must have:
- Read
- Write
- Modify access
2. OpenText Content Server Requirements
For optimal performance:
- Use a server with 4–8 CPUs and at least 8 GB RAM
- Configure a thread count greater than 2–3
- Ensure both the LinkFixer Advanced server and OpenText server have the same system time and time zone
3. Connecting OpenText to LinkFixer Advanced
Best Practice:
- Connect directly to the Content Server
- Avoid using load balancers, as they may interfere with processing
4. Enable MIME Type Setting
- Enable the MIME type setting in LinkFixer Advanced
- This ensures proper handling of files with missing or incorrect file types
5. Custom OpenText URLs
- Perform initial scans of your environment
- Contact LinkFixer Support to configure custom OpenText URLs
You can: Submit a support ticket via LinkFixer Advanced
Or email: Support@LinkTek.com
Troubleshooting
1. Process Failures
2. Submitting Logs for Support
When creating a support ticket, include:
- LinkFixer Advanced logs and reports
- OpenText logs