If I am doing duplication, I generally just detach the db, then zip up both the files (you can't zip up the files when it's attached) then I attach it again.

I then create a folder in the dnn root called Backup or something like that - and zip to live location - all the files..

If you have terminal services you would then log onto live server, and using the *attach* function in sql - you could attach the file - and if you want to change the name you do so here, and then you have to map to the correct path (common mistake when using the attach method - you manually need to change the path in the options)

The trick is to have your users setup locally as well as livel so your web.config doesn't  need adjusting or you might have to have a local config file and then a commented out live config and adjust when you are on server.

You then use IIS and deploy the site as normal.

A few things you need to know - are

• Virtual Directories - they play havoc with local and live installs
• Set your web url in the portal aliases before uploading or you need to access via sql to rectify
• Make sure your host/host login has been changed before backing up

I know it's not overly lenghty but gives you an idea on how I deploy them. 

Nina Meiers

AAh.. you just create the DB with another name.. you can do that.. I do that when I"m testing.. the trick is to use the attach function - so you can attach as..

Some people use the backup and restore function but for me - the detach and attach works well.

Nina Meiers