Updating from d7II or an older d7x

Pre-Requisites:  (Both Methods)

If you have any copies of d7x on the same PC, ensure that you have used the END SESSION to close one of them before the upgrade.

Next, be sure to delete the following Registry key if it exists:  HKLM\Software\Foolish IT\d7II.

To keep/update an existing configuration.

Download the “d7x (Blank Config)” zip file, and extract the included d7x vX.X.X.X.exe file and d7x Resources directory to your existing directory with a registered/working copy of d7II.exe or a previous d7x vX.X.X.X.exe file.  Be sure to delete the original exe file before running the new d7x vX.X.X.X.exe file.

Run the d7x vX.X.X.X.exe file, and it will startup after converting the d7II configuration and removing the .\Config folder in the process.  Once d7x starts, you should verify your configuration, paying attention to email/FTP settings.  ** Email settings that are configured for GMail can now be reconfigured using Google OAuth2 (meaning you can enable 2FA without needing to use insecure ‘App Passwords’ with d7x) so we highly recommend reconfiguring with that setting vs. using the traditional password based authentication provided by earlier versions of d7x and d7II.

Optional/Recommended:  Now you may want to cleanup d7II config files no longer in use, so that your configuration is as slim as possible for transfers to and from the Config Mgmt Portal.  So go into the .\d7x Resources\Config_Legacy folder, and delete EVERYTHING EXCEPT the “Profiles” and “SortOrder” folders, and the “AppOverrides.ini” and “AltText.ini” files.  Absolutely everything else is unused by d7x even the logos, so they are just taking up space and unnecessary.

Optional/Recommended:  Next you should cleanup the rest of the unnecessary files by deleting everything (files and directories) from the root of your d7II-now-d7x folder EXCEPT for the d7x vX.X.X.X.exe file, the d7x Resources directory which now houses all of d7x’s various dependencies and components, and your Scripts directory (if you have one.)  Everything else is d7II and should be deleted.  Note that the 3rd Party Tools directory should be deleted because many d7x custom apps will download/extract to different locations than the d7II custom app of the same or similar name, leaving you with duplicates in that directory, so we recommend just deleting it entirely, and letting d7x recreate it.  If you prefer to have these files in the folder before you begin work on a system, then you can pre-download every app used by d7x and your custom apps in your auto mode profiles by going to the “Auto Mode Options” button on the top right corner of the app and select “Download/Update All Apps Now” from the drop down menu.

FINAL STEP (DO NOT SKIP):  Once your new d7x folder is cleaned up of unnecessary files, you need to visit the Config Mgmt Portal where you can save your config but most importantly test to see if the Technician Password was imported.  Launch d7x and go to the Servers drop down menu on the top left, and select Config Mgmt Portal.  At this point you may be prompted to enter a “Technician Password” which is why you should not skip this step, and if so do this now, and please see the info below about the Technician Password!  If you were not prompted to enter a Technician Password, that means it imported from your d7II configuration, but you should be sure that you know it.  If not, you can reset it in d7x Config > Admin tab.

Once that is done, and this is optional but a recommended part of your last step, you can now save/upload your config through the Config Mgmt Portal, and create a d7xRDT (Remote Deployment Tool) based on that config.  (The d7xRDT is a replacement for the d7II_SFX_Mini.)  More info and a video on the d7xRDT is available further down in the manual.

To start with a new/blank config or starter config.

Download your choice of the “d7x (Starter Config)” or the “d7x (Blank Config)” zip file, and extract to a new folder, launch d7x vX.X.X.X.exe and enter your account credentials (and license data for earlier license types.)  The difference between them is that the Starter Config contains a pre-built configuration that you can look at and modify easily (the default auto mode profile is populated with apps, and “Your Company Name Here” text and generic logos are setup instead of no logos, so you have templates to work with and can see what and where modifications need to take place.)

Note that you may register d7x by using the Browse button (when prompted for your account credentials and license information) so that you may find and import an existing d7II\Config\Reg.Settings.dat file.  The only issue with this is that it ensures the exact same “Technician Password” is used; see the note on The “Technician Password” below for more information on the Technician Password, but you should know the password in use so if you aren’t sure of what that password is, then after importing a d7II license file you should go to the d7x Config > Admin tab and reset your Technician Password from there.  Once reset, ensure to delete or overwrite any configs you have in Config Mgmt Portal as they will be encrypted using your previous Technician Password.

Notes:  (Both Methods)

#1  The “Technician Password”  (IMPORTANT!)

#2  For remote usage, please see d7xRDT, the “d7II SFX Mini” replacement (Video)

#3  If for some reason you are updating from d7II v2.x (which was not forced to update to d7II 3.x) then you may want to see this article:  Recreate the d7II v2.x Look and Feel