Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInPin on PinterestShare on Reddit

social-media-the-10-best-practicies-for-upgrading-universal-type-server_extensis-blog-600x420

Because software upgrades can be disruptive to a Production environment I’m frequently asked which best practices a company should employ when upgrading Universal Type Server.

Here are ten basic ideas to help guide you through the upgrade process.  Please feel free to share your own tips with us or any others I may have forgotten to mention.

  1. Forward with a Backup – starting your upgrade out with a way to quickly restore your environment in the event of unforeseen problems is always the best way to lower your stress level. Backup first, always.
  2. Keeping up with the Joneses – Often customers jump into the latest operating systems or other application updates before ensuring their software and plugins are compatible. Compatibility information is generally available on the Extensis website so be sure to look before taking the update plunge.
  3. Testing, is this thing on? – Whenever possible, we recommend you review upgrades in a “testing” environment before upgrading your Production environment. This helps you identify and deal with unexpected issues without bringing your business to a halt.
    Did you know? The Extensis software agreement enables you to use your licenses on a separate testing environment at no additional cost. So setup a test environment to ensure everything works as expected.
  4. Keeping up with the times – We realize that it’s very challenging to stay on top of the latest versions of all your software. But just like the rest of the technology world, critical changes occur every day so if you don’t stick to a regular upgrade schedule you’ll fall behind.
    If you want to be certain Universal Type Server upgrades go smoothly, we recommend you lag no more than one full version behind.
    For example, Universal Type Server is currently at version 6.x so if you are running Universal Type Server 4 or older it’s time to get updated. When it comes to databases, upgrading from two (or more) versions back to the current version may not be directly compatible. Upgrading may require extra steps to to ensure you’re current. Staying updated will save you time and energy in the long run.
  5. One step at a time – Remember it’s much easier to ensure a successful upgrade when you use a stepped approach. Complete one installation at a time then validate its results.
    For example, if you need to upgrade systems to Mac OS X, Adobe Creative Cloud and Universal Type Client all at the same time take it slow and implement one change at a time. If you don’t, how will you know where a problem lies when things don’t go as expected? I can assert you will not know and neither will our technical support team.
  6. Server upgrades first – In the Universal Type Server world, client versions are often optimized for their intended servers. Therefore, it’s best practice to upgrade your Server before the clients. This ensures any new database schema updates get handled before connecting new client versions.
  7. In-Place upgrades (over a restore) – Universal Type Server offers two upgrade options. We recommend performing an in-place upgrade over a backup restoration (whenever possible).
    In-place upgrades ensure your current server data is updated quickly and users have the least disruptive experience. Remember as a safety net, run best practice step #1 before doing an in-place upgrade.
  8. Stagger client upgrades – It’s often recommended larger organizations upgrade their client versions in smaller chunks. Doing so minimizes the first-time work Universal Type Server is required to perform when syncing newly connected clients. Many of our customers will schedule client updates by office location, floor, department, or publication so their users have advance notice. Also if an unexpected issue occurs, the number of affected users is manageable.
  9. Contact us, really – Many customers don’t think to reach out to us before they upgrade until something goes haywire. Next time, email or call us first. You’d be surprised how much useful information we can share before you begin.
  10. Finally, do not contaminate the crime scene – In the rare event you encounter an issue, requiring support assistance, please do not make additional changes until we can gather the information needed. Often times we are unable to resolve the issue quickly because important application files, databases and logs are no longer available.

I hope this article was helpful for you. On behalf of the Universal Type Server Team, thanks for being our customer and good luck with your next upgrade.

Feel free to reach out and let me know which other topics you’d like for us to write about.

FREE Guide: Server-Based Font Management Best Practices Guide

Tags: , , , , , ,

No Comments »

Leave a Reply

Your email address will not be published. Required fields are marked *