I have just setup the DNN 4.3.3 on a Windows Server 2003 EE for local domain in the intranet, and I can access the DNN smoothly using localhost.

Now, I need to setup individual portal for the website in this server.

There has already have a website (xxx.home) defined in the server (home directory already created in c:\inetpub\vhosts\xxx.home), it is already running with some HTML pages, and I want to ehance this website to use DNN feature.

I open the localhost/dotnetnuke and login as host, then Host->Portals->Add New Portal

Portal Type:  Parent
Portal Alias: xxx.home

But now, I don't know which Home Directory should be used.

I have try to customize and enter c:\inetpub\vhosts\xxx.home (existing path) for it, and I expecting that it will copy the necessary file to this directory for DNN.  However, when I fill up all other information and press the Create Portal, the following error is prompted,

'/DotNetNuke_2/C:\Inetpub\vhosts\vm2003dnn/' is not a valid virtual path.

It seems that the protals file may be placed under the DotNetNuke directory.

As I don't know how to set the Home Directory, then I press the Customize again to use the default, and press the create protal again, it will then jump to the existing website of http://xxx.home, which is not a DNN portal.

And the url link in DNN Portals also pointing to the existing website, I cannot enable the DNN on it.

It seems that I have missed some step to change the Home Directory for http://xxx.home, isn't it?

May I know which step I have missed if I want to change the existing website to use be a DNN portal?

Thanks in advance!
OJames