• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Transfering DNN sites with MSSQL databases in Plesk

L

LeaUK

Guest
For those of you stumbling over here looking for help when you move DNN sites from dev to production aka mydomain/TestSite to customerdomain.com here's my-way:


Database management

• Login to development DNN site as ‘host’
• Add the new domain as an additional http alias (no 'http' prefix) to the current portal - DO NOT create a new portal alias!
• Using Plesk create a new db in the client’s domain (different db name and different db user name to the development DNN db)
• Using MSSQL Management Studio > Select DNN development db > Tasks > Backup (this will fail if the db wasn’t created by Plesk!)
• Highlight databases > Restore > ‘From database’ choose DNN dev db’. ’To database’ choose new db created in Plesk.
• Options > ‘Restore as’ ensure points to the new files. And ‘Overwrite the existing db’ is enabled.
• Select new db > Properties > files > change Logical name to new db name
• Recreate a new user in the new db which replicates the one Plesk originally created – otherwise Plesk won’t be able to delete it or backup


Connection string

• Copy the complete mydomain/TestSite root IIS folder from the dev domain to the new domain
• Change the connection string in web.config file in the root to new db name and new username. Best thing is to simply search for old db name and replace.
• Restart domain – this triggers the read of the new web.config settings


Update image links

If your original DNS test site was beneath a virtual directory i.e. mydomain/test and you move it to newdomain.com root, all pictures will fail. So update all image links by in the DNN site using the 'Engage F3' module.


Took me many hours to resolve this lot...
So hope it helps others.

Lea
 
Back
Top