Chris Walker's Blog

Note that this will also work in Plesk for *nix as well.

I've been working with a hosting company now for about 6 months. We bought some windows servers with clients on them a few months before I started. Additionally, we have about triple, or more the amount of *nix servers. We use mostly Parallels Plesk software for the user interface, its good, mostly.

I'll be completely honest, moving *nix to *nix is SO much easier than windows to *nix. First, if you do not already know, Plesk's *nix systems have an automated migration script to make a seamless move from one server to another. Unfortunately, because windows does not have ssh, and a plethora of other really useful tools that *nix systems do, this cant be done.

While doing these windows to *nix migrations, usually, if you're just not digging into the system far and want it done. You're going to end up resetting every single password from the client to the db, web user, etc. This, is where I come in.

Follow up:

Before you read on, I should note that you do need to have some knowledge of plesk, a good working knowledge of *nix and windows environments to complete this without either asking me a bunch of questions, or spending a ton of time googling. This is a straight forward how to migrate a client without resetting a single password guide.

The Dilemma

Your client is hosted on a Plesk system that uses Windows. This system is either having problems, or the client makes requests to move to newer software, etc.

The usual solution

When I was first confronted with this, it seemed relatively easy, until I discovered that there is no automatic way to make this happen.

So, you'll move the site, however you see fit, I have gotten in the habit of creating the account on the target *nix system, zipping up the website on the current host, then ftp'ing it to the the target, unzip, fix permissions etc. This is a natural process if you've worked in plesk long enough. When you're creating the account on the target, you'd take down the new passwords and send the user the new information after yeah?

Pages: 1 · 2