d7x is officially updating for all d7II subscribers…
d7II subscribers will notice their copy of d7II v3.6.86 now promotes that an update exists to v3.6.87 (there is no actual code change for this specific .exe version; the version number is incremented to silence d7II update notifications if used after this d7x release.)
d7x (Oct. 24th, 2017) has been rolled out to d7II subscribers!
- INITIAL release; update code tweaked for the official update to d7II.exe
- Download d7II.exe for use as a backup (if missing) using the d7x “Main” menu > “Check for Updates” option. (This should be done automatically when updating from d7II.exe)
- NOTE: Offline tab functionality is NOT fully functional in this release. Please continue to use d7II.exe for all Offline related functionality (including usage from a ‘Tech Bench’ PC and/or WinPE based boot disk.)
[Information may be outdated]
Please see the d7x Manual for ALL current information! The sections below are cloned here if you can’t stand another click!
NOTE: The information below is intended for existing users who already have d7II setup and configured, and have now updated to d7x. First-time users of d7II should see the d7II Quick Start Manual which also applies to d7x for first-time setup and usage.
(Recommended) d7II In-App Method: Update via d7II’s internal update mechanism (d7II should alert you of an update to d7II v3.6.87). Upon relaunch, d7x should show the message box to the right, informing you that this is the update to d7x.
Notes: (d7II In-App Method)
#1 (non-issue) Please be aware that the update may appear to stall, however d7x is downloading updated dependencies silently. Currently the initial UI/splash screen when downloading some dependencies is not displayed, but we plan to correct this issue with a future d7x update.
#2 (d7II update settings) the d7x update process will alter your d7II configuration as necessary, in order to disable the d7II automatic update settings, so that you may use d7II.exe unhindered by forced updates, should a problem with d7x arise.
#3 (d7II.exe v3.6.87) d7x will attempt to update the existing d7II.exe to an actual d7II.exe, which has been altered only to increment the version number to v3.6.87, in order to satisfy update notifications if/when using d7II.exe in the future.
#4 (potential error extracting d7II.exe v3.6.87) Some users have reported an extraction error during the update, which may have left a zero byte d7II.exe file instead of the expected file. If this occurs, please manually delete the zero-byte d7II.exe file if it exists, after which the updated d7II.exe files can be downloaded from within the d7x Main menu > Check for Updates prompt, or manually via this link.
(Alternate) Manual Update Method:
Place d7x v0.0.0.0.exe inside an existing directory with a registered/working copy of d7II.exe, and it will use the existing resources from that copy of d7II including the registration information. This should NOT interfere at all with regular d7II.exe operation or configuration files if it became necessary to use. See the note below on d7II and dCloud Compatibility for more information.
NOTE: This update method does NOT alter the d7II update settings as is done automatically in the recommended method above.
(Alternate) Manual Download Method:
Download the zip file, extract/run d7x v0.0.0.0.exe and register it. It is strongly recommended to register d7x (or any fresh download of a d7x or d7II product) by using the Browse button to find/import your existing d7II\Config\Reg.Settings.dat file, which ensures the exact same “Technician Password” is used; see the note on the Technician Password below for more information.
Notes: (All Methods)
#1 (non-issue, temporary) SSL Certificate Prompt: Currently all methods may receive several certificate warnings during the initial download of certain d7x requirements (see pic.) This is currently expected behavior due to our server’s SSL certificate, which is assigned only by hostname/domain, and not IP address.
The prompt should not be triggered with d7x Platform based server communications (which will perform additional verification on the certificate) after the initial requirements are retrieved, however some exceptions may noted affecting various in-app downloads from our servers for d7II based modules or dependencies. If you notice these prompts after initial d7x setup/update from d7II, then please let us know where the prompt occurs for you.
Background: In current d7x builds, all existing d7II functionality that would communicate with our servers is subject to an automatic IP address substitution for hard-coded hostnames, as well as forced SSL. This was done to resolve issues with some ISPs and UTM configurations that from time to time have been known to accidentally blacklist our hostnames, and it will trigger the prompt in d7II functionality not yet adapted to newer d7x Platform download methods.
We plan to address this soon not only with d7x updates, but with a new SSL certificate for our download servers to cover all the bases, although we do not expect it to affect much more than the update/dependency process.
#2 (d7II.exe v3.6.87 and v3.6.4) The final d7II based .exe files and their dependencies can be downloaded within the d7x Main menu > Check for Updates if missing from the root of the d7x directory, or manually via this link.
100% operational compatibility exists between d7II.exe and d7x v0.0.0.0.exe on the same PC, from any folder, or within the same folder structure as d7II.exe (while sharing the same d7II owner/account/dCloud/Self-Hosted FTP) with two caveats:
1. It is important to remember that d7x.exe (meaning any version, e.g. “d7x v0.0.0.0.exe”) serves as a replacement for d7II.exe, therefore you MUST NOT run them both at the same time, not even from different folders or drives!
2. Also you must ALWAYS “End Session” from d7II if it has run on the system at any time prior to running any d7x.exe version. End Session is normally performed as if you were done with a repair/cleanup/removal/etc. “session” on a client’s PC, and ready to remove your tools.
100% configuration compatibility exists to read and apply config settings from d7II.exe –> within d7x v0.0.0.0.exe
d7x uses all d7II settings appropriately, even where d7II did not (some settings linked to features that were not functional in d7II will now operate properly in d7x, causing some minor but noticeable changes in behavior.)
* For example, the “Pre-Download” setting removed from d7II (due to operational issues) is once again functional in d7x; therefore if the d7II configuration was saved when the feature was available, it will take effect in d7x to download any missing custom apps (including those internally used for the selected functionality) at the beginning of an individual auto mode, or at session startup depending on how it was configured.
Other behavioral changes may be discovered, since the d7x Platform code has resolved a number of unknown or unintended behaviors with d7II code that we just won’t know about until they are found (which isn’t likely to be very soon since d7II is huge with a vast number of different features.)
99% configuration backwards compatibility exists to read and apply config settings from d7x v0.0.0.0.exe –> within d7II.exe
Some config settings have been modified in d7x, therefore changes from the d7x interface may not always be reflected or obeyed in d7II. We expect this to be the case for more in the future, soon moving to 0% backwards compatibility for config settings. Of course any settings related to newer d7x features are already not read by d7II.
Depending on version, running both the d7x and d7II process simultaneously may not be possible, even from different paths. With either d7x or d7II, the second process instance you launched would recognize the existing process, and submit to the primary instance by terminating itself. This behavior is not guaranteed between the differently named apps, so please do not rely on it.
Further, when d7II session data is found in the registry, a new d7x process will run the existing d7II.exe and terminate itself (even when the process isn’t running, but the d7II.exe file exists.) If the d7II.exe file does not exist, d7x would continue but still use the existing set of app/config/report folders already determined by the previous copy of d7II. In this case d7x.exe would use the deleted d7IIx.exe’s session folders, which isn’t desirable (to fix, End Session from d7x before relaunching the same d7x.exe file again to start a new session.)
End Session is NOT a limitation with d7II.exe running after a previous instance of d7x.exe, which presents a major benefit. Because d7x currently operates using active ‘Session’ data in the exact same d7II format and location, therefore if at any point during a session/repair/”Auto Mode” you encounter a bug with d7x, you can shut it down or discontinue usage after a crash (the point being, do not “End Session” from d7x) and simply run d7II.exe instead to finish the job, from the same folder as described here (it should pick up exactly where the d7x.exe left off, even if a stall/crash occurred in the middle of an “Auto Mode” or other customized d7II-based action.)
d7x will not change the way that it handles the existing d7II config settings/definitions system/operational files, and therefore much of the d7II code involving the handling of these files is still in use. All .\Modules\*.* files are still in use and expect everything to be the way it is with d7II. These modules are the smaller programs existing as separate .exe files in the d7II\Modules subdir, which perform specific functionality outside of the main d7II.exe file. Over time all d7II modules will be replaced as they are either integrated into the main d7x.exe, re-written entirely, or retro-fitted with d7x Platform code and moved elsewhere (e.g. inside the “\d7x Resources” subdir) to preserve at least a co-existence with d7II which should remain usable as a backup, until it is replaced entirely by d7x as a stable and official update.
The very first time d7x or d7II.exe is launched without a registration file and registered by the owner, a case sensitive “Technician Password” is created at the registration prompt for use with the product’s various password protected options, which also serves as an encryption key for your customized d7II configurations when stored in the dCloud portal or on your own self-hosted FTP server.
If a different “Technician Password” is accidentally used when registering any new copy of a d7II or d7x product, it will cause data previously encrypted by d7II and/or d7IIx (such as your dCloud/FTP stored d7II configurations and branding customizations) to be unreadable by this and other copies of d7II or d7IIx, including the SFX Mini tool used for remote deployment.
For this reason, it is strongly recommended to register d7x (or any fresh download of any d7II product) by using the Browse button at the registration prompt to find/import your existing d7II\Config\Reg.Settings.dat file, which ensures the exact same “Technician Password” is used.
While you may copy/paste your registration information manually, you must be certain to type in the exact same “Technician Password” (case sensitive) to avoid issues in the future. Although we could decode the password from your unencrypted settings file (if you had one available to send us) we cannot retrieve the password from an encrypted configuration file, either on our servers or in your possession, since that very password was used to perform the encryption!
If at any point during a session/repair/’Auto Mode’ you encounter a bug with d7x, you can shut it down
or discontinue usage after a crash (the point being, do not “End Session” from d7x) and simply run d7II.exe
instead to finish the job, from the same folder as described here.
d7II.exe will resume whatever you were doing with d7x prior to a stall or crash, and even a full auto mode
should resume as if Windows or d7II had only restarted during the process.
But first, please keep these two things in mind:
1. Please try d7x again, it may not have “failed” to perform the task, but only failed to “re-launch”
or “stay active” during the running of a custom app (if those apps are designed for tasks of their own
that interfere with d7x’s operation.)
2. Ensure the d7x process is NOT running, reboot the PC (may not be necessary, but helpful), and run
the older d7II.exe, which will pick up on d7II style session data (written by d7x during it’s operations
for backwards compatibility.)
Note that you can’t switch back to d7x until you End Session in d7II, but in order to properly preserve
session data and reports, you may safely finish your work with d7II.exe entirely on that system.
Newsletter, Blog, and RSS Feeds
Manuals and Information
Additional Subscriber Benefits (dMZ Private Access)
Community & Search