• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

How Safe is Upgrade to Plesk 10

P

pkonstan

Guest
I have Plesk control panel 9.5.4 and am interested in upgrading to the new 10.1 version.

But as I look over this forum and elsewhere on the Web, I get a little concerned in light of all of the problems that people are having. Is it just that I'm only seeing the voice of a small minority who have problems?

Are there success stories of people for whom the upgrade has gone great.

I'm running RHEL 5 and php 5.16 on an Apache Server.

Thanks for any insight that can be given.

Also, is there a recommended checklist of things you should do prior to an upgrade?
 
In my experience it is not the upgrade process necessarily that's the problem. My upgrade as such went without a hitch. It is the result afterwards that seems to be causing extreme heart-burn with many users.

The issue is that Plesk 10 seems to be an entirely different product compared to Plesk 9, with some "features" added (but mostly badly or illogically implemented), and other features entirely removed making life VERY difficult afterwards. I have still to see how I would get my job done with Plesk 10. You see all the postings from people noting that the "new Plesk" simply does not do the job anymore.

My advice would be to hang on to Plesk 9.x and wait and see if Plesk 10 finds a way to restore real functionality again.

I surely wish I had not upgraded. If I had a downgrade path that did not require me to totally reprovision the server and re-migrate all data, like Igor proposed in another posting, I'd take in a flash.
 
test it! there is a 14day trial. test it on a testserver make a test-migration. decide if the new features and new structure is something you can deal with or not.
 
To be honest my biggest concern is the fact that Plesk 10 has so clearly removed old functionality.
An update is supposed to be adding features (or fixing issues). Not taking away what is already there, or transform itself into a totally different product, unexpectedly.

Good suggestion to acquire an extra server, just to test Plesk 10 functionality. Would make sense if it was a bug-testing session, but bug-testing is what I expect Parallels to do.. But one should not have to "test" for existing functionality having been thrown out.

What would you say if you had been using Microsoft's Office Outlook for many years, upgraded to get a new pretty interface and found out that it suddenly only supported connections to Exchange servers; that it no longer could download mail from your IMAP or POP accounts. You would call it insanity. Why remove features that are in use and are working fine. (Actually a good example, because Microsoft made that mistake in Office 2003, if you remember. They added new security that made it impossible to open many types of attachments. And was forced to make "fixes" that restored the old functionality, after their users revolted.)

With new Plesk, there seems to more of a existing functionality removal and functionality shift from Plesk 9 to Plesk 10, than there would be to port domains over to another product. At least one would know up front that this other product would be different and would expect it.

Plus as a many year developer I do not understand how someone can create a new structure, where I am forced to move from being able to control all my domains from one root screen to suddenly needing to jump in and out of a whole stack of separate "Control Panel" windows to see the same information old plesk could could show in a simple overview. Add to that longer sequences of clicks to open windows, and more clicks to open hosting/domain panels in those windows, plus cutting/pasting to put the information together. Thats really bad usability. I don't understand who approved that level of usability. Independent of it being a totally different functionality from older versions.

Its OK if Plesk wants to add more functionality to support people selling Hosting. Thats their business decision. But that can be done by adding features. (Plus, from what I have seen of comments from people using it as a Hosting controller, they lost out and are even losing their own customers as well.)

You don't have to alienate and destroy your old customers on the way to acquiring new ones. That is bad business. Acquiring new customers is nice, but repeat business and existing customers renewing their licenses is what pays the bills.
 
Last edited by a moderator:
1. why order a server? setup a virtual maschine install an os and the free 14 day plesk trial. done in 1h. whats the problem? i dont say do it in case of bugtesting. do it to see the new structure and features in live environment and learn to handle them!

2. you are right with outlook but there are many new outlook features i cant use with an old exchange server and windows do many things different in newer versions too for example old apps are sometimes not working.
yes backward compatiblity is necessary but sometimes you have to change things to get something new implemeted and get ready for the future! you cant always let things work the same way as ever or you are zero innovative and your product will die. i agree with you plesk do some strange business decisions but in my oppinion not all decisions they made in plesk10 are wrong only because its different
 
I agree with you that Plesk 10 is not all wrong. I see some features that makes sense to add for future functionality (even though I personally have little to no use for them). Its the bad usability decisions that confuses me. Why make things that used to be simple more difficult to do in a new product. The goal should be the opposite.
 
i agree with Ou there are some strange UI decisions in this release
 
Back
Top