I have never seen such a poor migration process. I have had so many issues with this migration listed below. Thing is I have over 40 sites and this is causing me so much time and money to fix this stuff. Clients are unhappy. It is like they just moved the sites over without even testing. They made a fix to the email issue below that I have to update all my sites with because of a PORT number! Then I have to test and make sure it works with a valid username/password for SMTP, something I didnt have to do before. Whoever is in charge of that migration process should be FIRED, period.
- .NET Application not right on site
- Email not working
- Control panel not working
- Access denied errors via FTP
- Sites broken
This should only happen on those set manually, pre asp.net 2.0 supported version of hsphere.
We moved all asp.net 4.0 sites manually as it is able to be tracked and separated unlike 2.0/3.0/3.5
2.
Email is working, will need details, setting of ports has been commonplace for a long time.
CP is working, but there are some times it is down for migrating.
-
It can be fixed by techs, all of them know this if you get files in read only how to resolve. there is one issue on win20 that is in developers hands for creation of subftp failing.
-
Sites aren’t broken unless there is a .net issue with version or directory index not set, these are the most common I’ve seen.
In a mail this week we’ll be detailing what checks should be done on migrated servers, as cluster1 had and has a lot more hand edited items that were done over the years than cluster2. In addition it seems hsphere itself is making some errors in settings due to some legacy code running when it should not.
Whenever you are migrating hundreds of servers there are and will be errors, we’ll work better to communicate now what should be checked then it has been seen more where the problems are. We’ve already migrated one entire cluster and dozens of servers with limited issues, most of these issues are new and being worked on which is one reason for the delays in moving other servers.
There is nothing to do with incompetence here, maybe a bit of expectations too high after the relatively good move on cluster2.
So many more issues. You just can’t make excuses and try to cover up for these. They are still happening. I am not getting emails back with responses to problems that are over 4 days old. Once I get a response they say the site is fixed, but the site is actually down. These guys are not even checking the sites after the migration to see if they are down. It is a total move site and forget mentality, or change setting and say it is fixed mentality. Very unprofessional, and very scary.
When I have 10+ sites down after migration, and I have clients telling me they are down, then yes that has everything to do with incompetence because they didn’t care to check if the sites were up. Email issues maybe different but checking to see if a site is actually up and running is incompetence.
We request you to please open support ticket with domain name, those having issue.