No matter how talented your team is or how knowledgeable the consultant who installed your Perceptive Content (what we old timers called ImageNow back in the day) system was, there are probably some gaps in your content management game that need to be filled. Sure, you could spend hour upon hour experimenting or maybe corner a few fellow system administrators at an annual users’ group (or the online equivalent). Maybe you’d prefer trawling Google day after day to find that elusive tip or trick? No? To help you out a bit, we’ve collated a few of the most effective best practices that I’ve seen work for hundreds of Perceptive Content users/admins like you.
If you have any requests for something you don’t see here, don’t hesitate to post your question or query in the comments below! Ok, let’s get going…
A service account for Perceptive Content services and associated scheduled tasks.
Creating an active directory user outside of any password policies and assigning to the above-mentioned items.
This account can be used on all Perceptive Content servers and aids in maintenance and future upgrades.
Disabling TCP Offload
Using a server’s NIC card properties and a command line, this setting can be disabled.
This setting can be enabled on all Perceptive Content Servers and will help prevent possible networking issues.
All documents and all folders views
Disabling these and creating individual views with assigned users is recommended.
This setting helps with document retrieval times and less overall strain on the server.
A database maintenance plan
Using SQL management studio with the right permissions, you can set up a general maintenance plan and/or add to an existing one. Hyland provides some general guidelines to ensure optimal performance.
Access security considerations
NTFS permissions should be limited to a single service account with Modify permissions. This aids in securing the critical storage element behind Perceptive Content.