I took a parent portal and created a portal template.

I created a child portal

Ok, granted the template reproduction is not quite there yet, but that is a whole new topic.

I read through the asp.net  dotnetnuke forum and found how to create a sub-domain against this new child portal.

I went to WebHost4Life and created the sub-domain http://wheelerspoint.justnorthresorts.com

I then added the alias to the new child portal and removed the existing portal alias.

The template brought over the security role - Content Administrator

My problem is the new portal won't recognize the security role of Content Administrator. I configure pages, modules and (example NewsArticles Admin) to allow a user in this role to edit. No go.

I have the exact roles and users on the parent portal and it works just fine.

Any Ideas??????

As a rule of thumb........

Never create anything but a child portal 1st.

So to start out create www.mysite.com/newsite

Once created your logged in as the admin, log out and back in as host  to the newly created site adding the new alis of newsite.mysite.com, then make your changes in IIS adding the newsite.mysite.com. Access the site with the new domain and log in as admin.

I know this is an extra step, but I have deployed enough sites using single installations with multiple sites now that I have found it to be the most reliable way to get it done.

Thanks for the advice.

I just created a child portal that seems to be holding. The only way I could get it to not fail on the FTB was to not customize the home directory. Before I make a decision on have isolated instance of DNN for each site or attempt a multiple portal install, can you look at my post "Syndicate and a second parent portal " in the NewsArticle forum and tell me what you think.

TIA
Robb

I've responded to the other thread.

The method described by jack to create child portals is the exact steps I ussually take.