Hi everyone.

My new DNN intranet goes like in 3 days and I was looking for tips or suggestions to make the launch as smooth as possible.

One thing that I need to do and wanted to ask was my current alias.  In order to test the site before launch, I had a new host entry called "IntranetTest" added and it points to the new DNN site.  Everything works great but my the live host entry is "Intranet" and that will be updated by my network group to point to the new site.  However, I will need to add the new alias to the site for "Intranet" or rename "IntranetTest" to "Intranet".  I think I'd rather add the new alias so that I can continue to use "IntranetTest".  Any suggestion if that's the best appraoch? 

Also, if I take this route, do I have to add the new alias on each portal or is there a way to change it once in the parent portal and it changes for all child portals?

Thanks,
Mark

Sebastion,

I just added "Intranet" under aliases. The day I go live, if I make that my default alias, clear my cache and recycle the app pool, will that make it work correctly with my child portals?

For example, I have a child portal called "Markerting". This is the link while I'm testing:

http://IntanetTest/Marketing

Would it automatically change to this when I set "Intranet" as my default alias?

http://Intranet/Marketing.

My guess is yes but I want to be sure all URL's will change based on the new default alias of "Intranet".

Thanks,
Mark

you need to provide proper aliases for child sites as well, afair they are stored using full path (check PortalAlias table in the database).

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN