Hi, we need to deploy numerous installations of Framemaker 2017 (32bit) on Windows 10 64bit systems. However, the 32bit package created by the Cloud Packager won't successfully install on 64bit systems, as it seems: In all installation tasks FM is missing in the final installation, only the Cloud Software gets installed. This problem does not exist when we install the 64bit version of Framemaker 2017. However, this is currently not an option due to workflow constraints with another software product we use.
The question to get around this bug is: Which reg-Keys must be set to make the installation being "registered" and avoid that the user is presented the EULA form at the first launch? I don't mind that the Software talks "home" since we DO have have the licenses. 🙂