I went through the installation and then tried to log in with the Administrator or the SuperUser admin accounts, but these did not work, and I was told the accounts did not exist. So, I believe this was because there is a separate admin area that I need to go to but I cannot find it. I went into the /admin directory and there was no index page to admin the site, so I can't figure it out.

In addition, how do you install a DNN site that you've developed on top on the installation? I will be developing a site to deploy out to an installation hosted elsewhere.

Thansk!

1. There is no separate admin area - everything is served via default.asxp page in the root directory. You gain access to the admin/host features by logging in as one. During the installation process, depending on the option you've chosen, you would get either default host/admin accounts or woudl specify the username and passwords for such yourself. If you've used an Auto option, login as host/dnnhost and admin/dnnadmin and the system will prompt you to change these passwords right away. However, if you've used any other options and don't remember what you've specified for these accounts, it might just be eaiser to kill this installation and start over. One test might help you - try using a Password Reminder screen to see if host or admin accounts exist. - you can also look in the DB - aspnet_Users table.

2. There are several ways people devise to develop and publish DNN sites. For example, we just use a secondary domain, i.e. myclient.mysite.com for development and, once ready, we just change that domain name to the site's domain name (both in IIS and in DNN, of course) Some other people suggest developing a site on development machine and publishing it out using templates (you find that under Host - Portals -  Export Portal Template, and, then, you run your production site through a Site Wizard (under Admin menu) and choose that template to be used. Yet another way to do it is to simply copy your DB and the whole root directory out to the production. Of course that works only for a complete move or for a single site DNN installation.