Replacing old DNN install

[RFH Customer: bill2clone]

I need a fresh new install of the lastest version
BUT
I want to use the same domain name as before.

I have an old DNN install on www.MyDomain.com, and I want to re-create everything from scratch on a temporary install (new root, new database).
Once my new install is ok, I want that MyDomain.com points to my last DNN install.

I need some ideas on how to do this.
Is there a way to get a temporary URL while I clone the initial portal?
Are there big errors to avoid?
What about the portal aliases?

[Staff: Warren Ashcroft]

The easiest way is to setup a sub domain for the new install, then simply move the files from the subfolder to wwwroot once you are ready to go live with it - I think you would need to manually update the portal aliases to match the new hostname.

[RFH Customer: bill2clone]

Thanks for your reply, Warren.

So, if I understand well...
1) create a sub-domain called MySubDomain.
2) upload DNN 4.9.0 files to wwwroot\MySubDomain
(can't remember if we can upload zip file directly)
3) create database and users
4) launch install
5) configure main portal and child portals as usual
6) backup old DNN portal (just in case)
7) Move MySubDomain files to wwwroot

When exactly do I have to update manually the portal aliases?

[Staff: Warren Ashcroft]

I believe thats correct, yes.

You need to update the aliases when the new install is moved from the subdomain to the live domain (after step 7); I think you need to do it manually in the database table.

[RFH Customer: bill2clone]

I believe thats correct, yes.

You need to update the aliases when the new install is moved from the subdomain to the live domain (after step 7); I think you need to do it manually in the database table.

I'm not particularly keen on updating a database manually.

It is possible to add several HTTP Aliases for each portal.
For instance,
www.MyDomain.com/ChildPortal
and www.AnotherDomainName.com

If I create a new DNN portal on a sub-domain
I will need the following alias
SubDomain.MyDomain.com
to make it work. Right?

If I had an alias www.MyDomain.com in Host Settings (just before moving the files from sub-domain to domain), will I be able to access to the new portal moved to live domain?

In other words, is it possible to run simultaneously the aliases www.MyDomain.com and SubDomain.MyDomain.com ?
(just one or two minutes)

[Tanzy]

If I had an alias www.MyDomain.com in Host Settings (just before moving the files from sub-domain to domain), will I be able to access to the new portal moved to live domain?

In other words, is it possible to run simultaneously the aliases www.MyDomain.com and SubDomain.MyDomain.com ?
(just one or two minutes)

Bill you are correct, just add the alias before you move it mate

[RFH Customer: bill2clone]

Thanks Tanzy.
The main question is...
is there a chance of conflict when having 2 aliases?
(I know it works with one domain name and one child portal URL at the same time)
Have you ever tried to move a DNN portal from a sub-domain to a domain?

No chance of crash at all when trying to run www.MyDomain.com ?