This is the process for adding a new portal when we work in a development Virtual PC. The order below isn’t too important as long as each stage in the process is done completely. This also assumes you already have a DotNetNuke site set up and working on Windows Server 2003.
First decide on an address (lets call it www.dnn4.com), then open your hosts file and add it to the end of the 127.0.0.1 line. The hosts file is located at c:windowssystem32driversetc
This means that every time your point your browser on the local virtual pc at www.dnn4.com it will redirect to 127.0.0.1, which is where we will be hosting our DotNetNuke portal.
Next open up your DotNetNuke install and log in as your host account. Navigate to “Host” then “Portals” in the DotNetNuke menu.
On the page that comes up you should see a list of portals (probably only 1 as you only have a single portal with a default DotNetNuke install). Click on the drop down menu at the top and then “Add New Portal”.
You want this to be a parent portal with the alias “www.dnn4.com” if we are following this example. Fill in the other details including the “Security Settings” section, which is the details of an admin account you are going to add to this new portal. Click “Create Portal”.
Your portal is now created but unfortunately you can’t get to it externally as there is no way of resolving that alias.
Open up your Internet Information Services (IIS) manager. Right click on “Web Sites” and then click “New” then “New Website”. This will pop up a wizard to create a new website.
Type in your description, I always use the alias here (www.dnn4.com in this case), click next. On the next page leave everything the same and put your alias in the box under “Host header for this Web site (Default: None):” and click next. On the next page but in the path to your DotNetNuke install and click next. Finally make sure you click “Run scripts (such as ASP) and click next to end the wizard.
Now your new portal is set up you can wonder why you didn’t always do this instead of installing DotNetNuke all over the place.
Be warned: If something goes really wrong with your DotNetNuke database (it can happen, especially with dodgy modules) you run the risk of breaking all the portals associated with it. Always make a backup of your data before you add new modules / change DotNetNuke.