16.3 Notes on creating and using AIT files
This section gives notes on creating and using AIT files.
-
AIT files do not support Web pages and software created in Java or ActiveX.
-
If API functions that manipulate the registry key HKEY_CURRENT_USER are defined in an AIT file, the user of each computer on which remote installation is to be performed must have logged on as a member of the Administrators group.
Such a user only can access HKEY_CURRENT_USER. If the client user is not a member of the Administrators group, the target registry key of the API functions is automatically changed to HKEY_USERS\.DEFAULT. This change may cause installation to fail.
However, if the change of the target registry key does not affect any operations of the software being installed, the installation will continue.
-
You might want to use an AIT file to remotely install a package that requires restarting the target computer after installation. In this case, use an AIT file that is set to terminate the installer without restarting the target computer. For remote installation to end successfully, the target computer must be restarted by the package settings.
-
If you specify 64-bit-related data (registries, folders, or files) in the following categories of API arguments and perform operations in the following operating systems, the target data for APIs might be changed (redirected) to the corresponding 32-bit-related data: the 64-bit edition of Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2.
-
Registry operations
-
Directory operations
-
File operations
-
INI file operations
-
-
When you perform a remote installation by AIT, the API of AIT for window operation might not be able to set a focus on the application. To work around this symptom, execute either of AIT_Exec() and AIT_ExecCommand() first and then use AIT_PlayKey(), which is a recorder operation API, to simulate the pressing of the Alt + Tab keys to move the focus from the desktop.