Part of the Autodesk software registration process, it allows you to run a product in compliance with the product's end-user license agreement.
A directory service from Microsoft that is part of Windows 2000 and Windows 2003 Server.
A collection of shared file resources created by the Deployment wizard and used by deployments to install the program to network workstations. Service packs (patches) can be applied to an administrative image using the Deployment wizard.
A pull technology that notifies users of an updated software product that is available for installation. Users typically double-click a shortcut (or do a similar operation) to complete the installation of the advertised product.
A runtime process that can accelerate the initial startup of AutoCAD.
The process of installing an Autodesk product to one or more computers on a network.
A link to a unique MST (Microsoft Transform) file that serves as a basis for an installation. Using the Deployment wizard, administrators can create multiple deployments that result in different types of installations for users.
A network service that identifies all resources on a network and makes them accessible to users and applications. Resources include email addresses, computers, and peripheral devices such as printers. Ideally, the directory service should make the physical network topology and protocols transparent so that a user on a network can access any resource without knowing where or how it is physically connected. Virtually all directory services are based on the X.500 ITU standard.
License management technology from Macrovision Software, Inc. FLEXlm provides administrative tools that help to simplify management of network licenses. FLEXlm can be used to monitor network license status, reset licenses lost to a system failure, troubleshoot license servers, and update existing license files.
Microsoft server technology that provides a way to do push installations and advertising-based installations using standard Microsoft 2000 Server administration components.
A deployment that consists of an MSI file, any associated transforms, additional user-specified custom files, and profile and registry settings.
Microsoft installer that supports a variety of parameters that can be scripted.
Microsoft patch file (see patch).
Microsoft transform file. Modifies the components installed by the MSI file. For example, the Deployment wizard creates an MST file with the settings that you specify. The deployment created by the Deployment wizard uses the MST file in conjunction with the MSI file and MSIEXEC to install the program on local workstations.
A type of installation where multiple stand-alone seats of the program are installed using a single serial number.
A profile that contains partial registry information corresponding to a subset of the options available from the Files tab of the Options dialog box.
A software update to an application.
A user with rights to access and write to the Program Files folder and the HKEY_Local_Machine folder of the registry.
An installation technology that requires user interaction to complete the installation.
An installation technology that installs files to a remote desktop without any user interaction.
The process of using scripting languages such as VB Script to facilitate the deployment of software packages.
Autodesk terminology for an application patch.
An installation that proceeds without any explicit user input. No dialog boxes are presented that require interaction from the user.
Microsoft Systems Management Server. A tool that helps administer networked machines by allowing remote configuration, push deployments, and user administration. SMS is an expensive technology that must be purchased as an additional server.
See MST.
