Moving deployment to an new server

[Cammie Watson]

Does anyone know of any good articles or resource on moving our cms 2002
website from one server to another

[George Leithead]

On Dec 14, 4:27 pm, Cammie Watson <cwat...@pkc.gov.uk.(donotspam)>
wrote:

> Does anyone know of any good articles or resource on moving our cms 2002
> website from one server to another

Not off hand. However it is quite easy really. In summary (assuming
that both servers are in the same AD domain!):
- Build new MCMS server and when specifying the database name, make
sure it is the same as the original
- Take a back-up of the original MCMS database
- Restore to new server
- Deploy code (you have made this a repeatble deployment, haven't
you!) to new server
- Make any necessary web.config changes
- Hay presto, done!

[stevekgoodwin]

We've done this a couple of times, and we take the lazy option: back
up the web server and restore it to new hardware, resolve any driver
conflicts, test, test, test and swap over. Our installation would fail
spectacularly if we took George's suggestions, unfortunately.

IIS config can be complex -- our site is made up of multiple
applications, application pools, webservices, 3 versions of .Net,
about 8 databases on 3 database servers and so on all running on the
same server. Don't forget Firewall config, that can burn you if you're
in a hurry. Filesystem permissions. Special user accounts. Any
hotfixes you may have applied to MCMS. Telerik editor configuration
files.

If you've got a very simple setup, maybe it'll work. Best advice I can
offer is "plan and test".