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.
• Be careful when executing an API function for 64-bit-related data (registry, folder, or file) in any of the following operation systems: the 64-bit edition of Windows 8.1, Windows 8, Windows Server 2012, the 64-bit edition of Windows 7, the 64-bit edition of Windows Server 2008, the 64-bit edition of Windows Vista, and Windows Server 2003 (x64). If the target data is specified as an argument in an API function that belongs to one of the following categories, the target data might be changed (redirected) to the corresponding 32-bit-related data:
  
  • Registry operations
  • Directory operations
  • File operations
  • INI file operations