I believe the easiest way for now to get a DNN4 site deployed to your local ISP is to create your website/database locally and then backup your database from SSMS and FTP this up to your ISP for them to restore. I have not noticed anything different in how I FTP the website itself, i.e. ftp'ing the site files and modifying the web.config file. The final step always beeing update the PortalAlias database record to www.TheNameOfYourDomain.com - this can be done locally or after you attach to your ISP's SQL Server updating it there. I have read some blogs indicating that SP1 of SQL 2K5 will have features to improve the Import/Export wizard. Perhaps this will include assistance with deploying databases. The mere scripting of the Stored Procedures after the tables/views and data has been exported to your remote site doesn't seem to work as it appears to be missing permissions on dependant objects. I did create a script that I can run that parallels the installation script, but when I run this against my remote database, it is always under my user id, and not dbo. Should I find some way of using SSIS packages, which I've tried but receive a null login error (might be because it doesn't store it and may be an easy fix by modifying the connection string), I will post my findings. Any ideas are welcomed, too! Thanks!