![]() To create an installation package, click Add, click Download from the web, and download the desired package.Īfter downloading, specific command line parameters can be added. Open the ESET Remote Administrator Console (ERAC) by clicking Start → All Programs → ESET → ESET Remote Administrator Console → ESET Remote Administrator Console.Ĭlick the Remote Install tab, and then click Actions → Manage Packages. bat file, specific parameters can be added to the installation package using ESET Remote Administrator. Instead of using the Windows command line or a. Using ESET Remote Administrator to add command line parameters bat file with the special command line parameters – just add the command line (e.g., step 3) to the. xml configuration file must be named cfg.xml. msi package, installation destination and. Because this was for an SCCM application, I utilize the current directory environment variable ?% to ensure it will always add the file location properly regardless of where the EXE exists in the CCM cache.Please do not use the directory paths shown above, which serve as examples only. I added this single command to my batch script right before I run WorkstationInstaller.EXE. …but it requires two commands be ran: one to create the appropriate registry value and another to run the file after the registry value has been made.Īfter learning this it was easy to create the following command that calls REG.EXE to create the registry value which forces my WorkstationInstaller.EXE file to run in Windows 7 compatibility mode: REG ADD "HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /V ?%\WorkstationInstaller.exe /T REG_SZ /D WIN7RTM /F Therefore, it is possible to run a file in compatibility mode from command line… ![]() The following tables show the data values that I found: Compatibility Modes: Descriptionĭisable Display Scaling on High DPI Settings If multiple settings are to be used, separate the data with a single space ( like in the pskill.exe example pictured above: 256COLOR WIN95). Modify the registry value to run the file as desired. There are three types of settings that can be applied to each application: compatibility mode, display settings, and privilege level. The name of the string is the path to the file and the data is specific to the desired compatibility setting(s): Note that if settings are written to the HKLM (all users) location, users cannot change the affected settings in the file properties GUI unless they are an administrator.įor each item that has custom compatibility settings, a string is made. The registry key differs depending on if the setting applies to an individual user or to all users.įor an individual user: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layersįor all users: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers It is actually the same location used to store application-level display and privilege level settings too ( more on that in a moment). I learned that these compatibility entries are written in a straightforward fashion to the Windows Registry. I needed to find a way to do this from the command line. Ironically the installed application itself ran fine in Win 10 without being in compatibility mode, but the installer wouldn’t. While recently designing an SCCM application, I ran into an issue where an EXE installer had to be executed in Windows 7 compatibility mode while running on Windows 10. Successfully Tested On: Windows 7 Enterprise SP1, Windows 8 Enterprise, Windows 8.1 Enterprise, Windows 10 Enterprise versions 1507 - 2004, Windows 10 Long-Term Servicing Branch (LTSB) versions 1507
0 Comments
Leave a Reply. |