For the benefit of anyone else having this problem, I can confirm a fresh install from the server corrected the issue, one thing to note that caught me out however...

I couldn't figure out how to get http://localhost to resolve on the server I was installing DNN and when visiting the the DNN site via it's full url or IP address I kept getting a message about the site not being ready yet i.e. I didn't get the normal "new DNN install wizard" you would see when running a fresh install of DNN on a development machine. To correct this you need to edit the web.config and set "UsePortNumber" to false, this allows you to access the "new DNN install wizard" via the full url or IP address.

Hi Sebastian, I did read that somewhere else (can't remember where), but adding the alias before moving didn't make any difference.

Oddly enough when I was trailing a number of CMS's (DNN included) a few months ago one of my tests was "how easy is the CMS to publish to a server" and my early test DNN publication works just fine, I don't remember doing anything special other than a website publish from VS 2010, it just seemed to work!