Richard, you are a hero. We had missed the fact that the features need physically checked, we just assumed as the the top levels were selected that all was fine. I was able to get things installed thanks to your post.

You should make this a feature in the Wiki as others may also experience this especially if they have never encountered 2012 server before.

 Ahh, just when we thought we were done.
I could only get this working by creating an application (to avoid the common machine key and site not set as an application error). Now this is fine but I needed to create 12 small parent portals off the default (which I have done),  but as an application not a site,  IIS does not let me apply bindings and https certificates.
Is there a work around?.

Each of the portals has a .org.uk domain  so  we parentportal1.org.uk, parentportal2.org.uk, parentportal3.org.uk.
Could I apply a HTTPS certificate the default website and serve them all?

Will the site alias in DNN (without a binding in IIS) be enough to handle site direction

Any advice welcome as this not my strongest area.

for a multisite DNN, you assign all aliases to the IIS website and use appropriate Aliases in DNN > Admin > Site Settings.
If you are using virtual directory, you will have multiple DNN instances, each may use different domain names, but will always include the directory name.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN