Hi Mike,

Is there any new functionality you're after in 4.6.2 that you don't have in 4.5.4 or are you not just wanting to get to far behind the curve?  I upgraded from 4.5.3 to 4.6.2 and it ws not as smooth as my upgrades from 4.4.1 to 4.5 to 4.5.3.  I'm not seeing any problems as of yet after the upgrade though.  If you're set on upgrading I would do it this way:

Zip up your DNN directory and backup your database.  If you have the luxury, copy these down to a development machine that has a similar development environment as your production server.  Get the site up and running there and try the upgrade. See how things go and then reevaluate.  Once I did this, I went back to the production server and set up a new website in IIS and unzipped the files there, restored the db, did the upgrade, stopped my production site, and then changed the neccessary entries in my portal alias tables and IIS host header records so that the newly upgraded site came up when folks browsed to my domain name.

This might not be everyone's method or even an approved one, but I don't think I'll upgrade in the future without following the same process.

Hope this helps.

Paul

Thanks  for your sugestions.  I think I will make a copy of my dnn directory and sql server, and install a duplicate of my site on a virtual PC.  Then I will try upgrading the site that is on the virtual Pc.  This way I don't mess up my site, and if I like what I see I can upgrade

Thanks for your help

Mike