In addition to moving all files in the wwwroot folder you may also need to backup the existing MS SQL server database, restore it into MS SQL Server on the new server, and make any necessary changes to the two database connection strings found in the site's web.config. I say "may" because it is possible that your site's existing database is located on a separate database server which may be accessible from the new web server. You will likely need to contact your hosting provider for help in this area.

You will want to start with an "empty" directory on the new server rather than first installing DNN on the new server. Make sure that the following requirements are met on the new server application:

1. It's application pool is running the appropriate version of ASP.Net - for example, DNN 5.2.0 and above require ASP.Net 3.5 SP 1. DNN 5.4.4 and above can also run in an ASP.Net 4.0 application pool. If moving to a different MS SQL Server, note that DNN 5.2.0 and above requires MS SQL Server 2005 or 2008. To avoid the "orphaned SQL user" issue it is best to create a new SQL Server user (in dbowner role) with a different userid than the old one and update the two connection strings in web.config.

2. Full filesystem permissions (including modify) have been granted to the ASP.Net worker process account on the directory into which DNN will be installed and that this permission propagates to all child directories as they are created.

3. Appropriate DNS changes will be necessary to repoint the site to the new IP address. I am assuming that the site's url will not be changing so you should not have to add a new portal alias.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner