Five Golden Rules for a Successful Ubuntu Desktop Migration

Canonical

on 21 November 2011

This article is more than 14 years old.


So, you like the idea of deploying an Ubuntu desktop to all or some of your users. You like the way Ubuntu’s light-client model can give  your older desktop machines a new lease of life. You like the fact that Ubuntu is secure, portable, and easy to manage. Best of all, you like that it costs nothing to license, and comes with a host of enterprise-grade apps that cost nothing to license either.

Now it’s time to see how it works for you in the real world. To help you plan your migration, we’ve compiled our five golden rules for success. These are things we’ve learned from the hundreds of Ubuntu desktop migrations we’ve conducted for clients around the world – from the French National Police Force to the Supreme Court of India.

 

Download today and discover how to:

  • Plan effectively for maximum effect
  • Target the users ripe for migration
  • Identify the apps that save you money and hassle
  • Create the right management flows
  • Pilot your project to get it just right

Talk to us today

Interested in running Ubuntu in your organisation?

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

The foundations of software: open source libraries and their maintainers

Open source libraries are repositories of code that developers can use and, depending on the license, contribute to, modify, and redistribute. Open source...

From inspiration to impact: design students from Regent’s University London explore open design for their dissertation projects

Last year, we had the opportunity to speak at Regent’s UX Conference (Regent’s University London’s conference to showcase UX work by staff, students, and...

When an upstream change broke smartcard FIPS authentication – and how we fixed it

This is the story of how Canonical’s Support team provided bug-fix support: we tracked down an upstream change in OpenSC that inadvertently broke FIPS...