It’s always a good idea to be running the latest version of Plesk if possible. As with any software, security loopholes are found and exploited and Plesk are frequently releasing updates to improve the security and other features of the platform.
Usually, Plesk will update automatically within each major version. 10.4.4 for example updated seamlessly from 10.4.3. Updating major versions however requires user action.
The reason I updated Plesk 10 to Plesk 11 was initiated by an alert from our hosts 1and1 about a server vulnerability for ‘ISC BIND 9’ which deals with various DNS functionality within Plesk. The version I was running was ‘BIND DNS Server 9.4.2’. I figured rather than try to address the problem specifically, upgrading Plesk would be the best option as I would have the latest, most secure version of Plesk in addition to the latest Bind DNS server component.
Before I upgraded Plesk, I ran a Windows update via RDP which installed a number of important updates. I don’t think this was necessary, but good practice to keep Windows server updated with latest security patches etc.
Upgrading Plesk 10 to Plesk 11 should be a relatively straightforward process. These are the steps I followed in order to update Plesk 10 (10.4.4) to Plesk 11 (11.0.9) running on a Windows dedicated server 2008 with hosting providers 1&1 internet:
Activating Plesk 11 Backup Manager and Scheduling Backups »
Scheduled Task for PHP scripting in Plesk & Linux »
.htaccess 301 redirect problem for non-www in Plesk »
Scheduling a custom php script URL with plesk »
Setting the www or non-www in Plesk 11 »