Application Object Templates

You use the Application object template file to create the Application object in Novell eDirectory^TM. Both Application object template (.aot and .axt) files contain the same information, which is used to populate the Application object property fields during creation of the object:

• The eDirectory name and workstation shortcut name to be given the Application object.
• The modifications that need to be made to the workstation's configuration settings (registry settings, INI settings, text file modifications, and so forth) during installation of the application.
• The macro definitions to use during installation.
• The list of application files to copy to the workstation during installation, including the source location to copy the files from and the target location to copy the files to.

The .aot file is a binary file that cannot be edited; the .axt file is a text file that can be modified with a text editor. If you need to modify the Application object template after snAppShot has created it, you should modify the .axt file and use it to create the Application object. Otherwise, you should use the .aot file because data from the .aot file is imported more quickly.

Application Source Files

SnAppShot also tracks all of the application files that are copied to the workstation. These files, which become the application source files, are copied to a network source location, renamed numerically starting with 1, and given a .fil file extension (for example, 1.fil). Novell Application Launcher^TM uses these source files when installing the application to the workstation.

Application File Definition File

To map the .fil files to their original files, snAppShot creates a file definition (filedef.txt) file. This text file not only maps the .fil files to the original files, but also specifies the target location and name to be used when installing the files to the workstation. For example:

1.fil=c:\dmi\win32\_deisl1.isu 
2.fil=c:\dmi\win32\bin\wdmiutil.dll

SnAppShot Limitations

Please be aware of the following before using snAppShot:

• SnAppShot does not work with MSI applications installed by Microsoft Windows Installer. This includes applications such as Microsoft Office 2000 and Microsoft Office XP.

  MSI applications often install portions of the application "on-demand," which means that a snapshot of an MSI application's installation could possibly not include all features and functionality available in the application. For this reason, MSI applications must be distributed as MSI applications rather than as AOT/AXT (snAppShot) applications. For more information, see Distribution: Complex Applications.

• SnAppShot does not support some of the new Windows XP registry types, such as hex(800000007). Care should be taken when using snAppShot on Windows XP to ensure that the generated .axt/.aot file (or Registry page in the resulting Application object) does not include changes that could adversely affect the operation of Windows XP workstations to which the application is distributed.
• SnAppShot fails when the Windows registry is larger than 30 MB. The following message displays:

  A critical 'out of memory' error has occurred. snAppShot must close.

  The recommended solution is to use AdminStudio ZENworks Edition instead. For information, see the AdminStudio ZENworks Edition Installation Guide.

• SnAppShot does not support Windows terminal servers. Do not use snAppShot on a terminal server to create an AOT/AXT application you want to deliver to other terminal servers.
• The Application object template changed from version 4.0.1 to 6.5 to accommodate several functionality changes, including the change from system requirements to distribution rules. If you have a pre-ZENworks 6.5 environment, you must select the Create Pre 6.5 Application Object Template File option while creating the .aot file in order to use the file in your environment. If you use the default option, Create 6.5 Application Object Template File, the resulting .aot file is not usable in a pre-ZENworks 6.5 environment.