Backup Critical Data
Despite DNP Configuration Studio (former DNP Installer) does backups itself before each application update, we strongly recommend you to make backups of the following data before continue with DNP 2.0 update:
- Files for all DNP components (DNP Portal, DNP Enterprise Server, DNP Server) usually installed in "c:\DotNetPanel" folder.
- DNP Portal SQL database (its default name is "DotNetPanelPortal")
- DNP Enterprise Server SQL database (its default name is "DotNetPanelEnterpriseServer")
You may do database backups from SQL Server Management Studio (Express or full edition).
Updating DNP 1.x to DNP 1.5.3
You can upgrade to DNP 2.0 only from the previous DNP 1.5.3. If you already have DNP 1.5.3 you may skip this section.
If you currently have DNP older than 1.5.3 you must upgrade to 1.5.3 first using old DNP Installer.
Old DNP Installer 1.0.8 can be found here: http://www2.dotnetpanel.com/Portals/0/DotNetPanel%20Installer.exe
If you already have DNP Installer 1.0.8 installed on the server, please upgrade it anyway with the installer above, because it was setup to read installation information from the old DNP web site, located here http://www2.dotnetpanel.com/
Using DNP Installer upgrade your DNP installation to DNP 1.5.3.
Preparing for 2.0 Update
Reviewing Your Converted Account and Licenses
All customers accounts and licenses have been moved to new http://www.dotnetpanel.com/.
Please note, DNP 2.0 does work only with new converted licenses. Do not try to apply licenses from old web site to DNP 2.0 installation.
Some customers had several accounts on the old web site with the same e-mail. New DNP web site does not duplicate e-mails, so some accounts have been merged by e-mail. Username for merged accounts was chosen randomly.
If you can't login on the new web site with old username, or can't remember the password, please do not try to guess this info and use password reminder instead. After 5 wrong login attempts your account will be locked and you will need to write a request to our support.
New password reminder allows to reset password by either username or e-mail.
If you see that you have wrong number of licenses under your account, please contact us by e-mail and specify your username(s) or e-mail(s) on the old web site. Do not proceed with upgrade to 2.0 until you are sure that your new account and converted licenses are OK.
If you want to change your username to some other, more friendly, please contact us by e-mail and specify your current username and desired new one.
Current DNP 1.5.x licensing service has been replaced by a stub. This means that DNP 1.5.3 can be used for free until the stub is disabled. We plan to disable this stub after 2-3 months when all our existing customers will migrate to new DNP 2.0.
Reviewing New Mail Templates
Before doing 2.0 update, please review and customize updated 2.0 templates for Account, Space Summary Information and Password reminder. Updated templates can be found in the attachments section at the bottom of this page or at DNP demo site http://demo.dotnetpanel.com/
Updating DNP 1.5.3 to 2.0.1
In order to update DNP 1.5.3 to 2.0.1 you should use DNP Configuration Studio. The latest DNP Configuration Studio can be downloaded from this location:
http://www.dotnetpanel.com/DotNetPanel/Downloads.aspx
In general, DNP 1.5.3 to 2.0.1 upgrade algorythm is the following:
-
You have DNP 1.5.3 installed.
-
You download DNP Configuration Studio (DNP CS).
-
First, using DNP CS you upgrade all DNP 1.5.3 applications (DNP Portal, DNP Enterprise Server, DNP Server) to 2.0.0 one-by-one.
-
Second, you upgrade all DNP 2.0.0 applications to 2.0.1 one-by-one.
-
Finally, you upgrade all DNP 2.0.1 applications to 2.0.2 one-by-one.
-
Repeat the procedure for all servers where DNP applications are installed.
If it is allowed, please run "iisreset" command before doing DNP 2.0 update or restart DNP application pools. This step prevents some files from being locked during the update process.
Note to those customers who have already downloaded and run DNP Configuration Studio on the server where DNP 1.5.3 installed: Before starting the upgrade to 2.0.0 please delete "C:\Program Files\DotNetPanel Software\DotNetPanel Configuration Studio\Data" folder.
For detailed steps how to upgrade existing DNP installations using DNP Configuration Studio, please refer Updating DotNetPanel Applications page.
Verifying 2.0.1 Installation
After successful update to DNP 2.0.1 you should verify that all configuration settings have been migrated properly.
Server
Open DNP Server's URL in the browser. If everything is OK with DNP Server installation you should see the following picture:
(DNP Server URL would be different for your installation)
Enterprise Server
Open DNP Enterprise Server's URL in the browser. If everything is OK with DNP Enterprise Server installation you should see the following picture:
(DNP Enterprise Server URL would be different for your installation)
Portal
Open "App_Data\SiteSettings.config" file and make sure that "EnterpriseServer" configuration element contains correct URL to Enterprise Server.
Also, in this file you can change the value of "PortalName" element. This is the name of Portal that will be shown in titles of all DNP pages.
Open Portal URL in the browser. If DNP Portal was correctly updated you'll see "Sign In" page:
Sign in under "serveradmin" account.
Please note, that both "host" and "admin" accounts are not applicable for DNP 2.0 anymore as DNP 2.0 WebPortal is not based on DotNetNuke engine.
Open "Configuration -> System Settings" page and make sure you have correct SMTP settings specified:
Update "SMTP Server Settings" if required and click "Save Settings" button to save your changes.
Setting Up 2.0 Licenses
DNP 2.0 requires that both DNP Enterprise Server and DNP Server should have licenses installed (previous versions required only DNP Server to be licensed).
If you are upgrading from DNP 1.5.3 then you are probably an existing customer and all your licenses have been convrted to 2.0 Gold licenses. Gold license can be applied for both ES and Server applications.
Please, do not try to install old licenses as they are not compatible with DNP 2.X and will be rejected).
Please, watch carefully that the same license is not installed on several servers. Such licenses will be automatically blocked by licensing engine.
In DNP 2.0 both Enterprise Server and Server licenses can be installed from DNP web interface without a need to open configuration files.
Enterprise Server
To install the license to DNP Enterprise Server sign in under "serveradmin" account and open "Configuration -> Licenses" page:
Enter license serial number and click "Add License" button. If the license is accepted you'll see it in the list of installed licenses.
Server
To install the license to DNP Server(s) sign in under "serveradmin" account and open "Configuration -> Servers" page:
Open "Server Details" page for the server you want to install the license to.
Expand "Licenses" section:
Enter license serial number and click "Add License" button. If the license is accepted you'll see it in the list of installed licenses.
Repeat this procedure for each registered remote server.
Updating Mail Templates and Parking Page
Review, customize and update new DNP 2.0 templates for Account Summary Information, Space Summary Information, Password reminder and Parking Page. Updated templates can be found in the attachments section at the bottom of this page or at DNP demo site http://demo.dotnetpanel.com/ (when signed in under "demo_admin").
How to change templates for given DNP account, please refer to these page: