When updating DyKnow to a later version, it is important to be mindful of the initial DyKnow installation. To avoid complications, please exercise consistency when performing installations and updates. Installations using the executable file found on the DyKnow Download page should only be updated using newer versions of the executable. Similarly, Installations using the DyKnow MSI Package should only be updated using newer versions of the DyKnow MSI Package. Attempting a combination of installation types may result in unanticipated consequences.
Common Installation/Update Pitfalls
Installation: MSI Using Group Policy Objects
Update: DyKnow Executable
An institution uses GPO to install DyKnow version 5.1.x1 on student computers. After a time, the institution decides to update DyKnow to version 5.1.x2. The institution visits the DyKnow Download webpage and downloads the 5.1.x2 executable. The 5.1.x2 executable is then used to update DyKnow on all student computers. When student computers are restarted, GPO detects a change in the DyKnow version and the Windows Installer automatically attempts to reinstall version 5.1.x1. This installation will exit without completing, but “advertises” 5.1.x1 as the registered provider for the .dyz file type. When a .dyz file is double clicked, the MSI will trigger an auto repair, which will necessitate a reboot. After the reboot 5.1.x2 will still be installed. This issue is a known issue when manually performing a major upgrade a managed MSI package.
Installation: DyKnow Executable
An institution uses the DyKnow Executable to install DyKnow version 5.1.x1 on student computers. After a time, the institution decides to update DyKnow to version 5.1.x2. The institution contacts their CRM to obtain the MSI Package for 5.1.x2. The 5.1.x2 MSI Package is then used to update DyKnow on all student computers. The unintended result is multiple installations of DyKnow will appear to be installed on the student computer. Only one installation, however, will actually function as an installed program. This is a known issue with InstallShield. DyKnow will update this article as necessary when a solution is made available.