Import the administrative image into Configuration Manager

Instructions for using the Application and Package model workflows

After you've created a deployment in Autodesk Account, you import the entire administrative image as one package into Configuration Manager using either the Application or Package model. Add a command line that points to Installer.exe and Deployment.xml with the correct switches. The installation sequence is handled by Installer.exe, which reads the XML files.

Using the Application model

This method deploys by device and users.

1. Open Configuration Manager and navigate to

   Software Library\Overview\Application Management\Applications\<customer path to application folder>

2. Either create a folder or open an existing folder in which to create the application.
3. Click Create Application in the upper-left corner of the window. You can also right-click the background and select Create Application from the menu.
4. Select Manually Specify The Application Information.
5. Enter name, publisher, and version information. Recommended: Choose Date Published to help you keep track of the application.
6. Click Next to view the Application Catalog screen. This workflow deploys to the Software Center (instead of the catalog), and so the information in this screen does not apply. Click Next.
7. Click Add (beneath Deployment Types).
8. Select Manually Specify The Deployment Type Information.
9. Select the application you created, add administrator comments as needed, and then click Next.
10. To specify Content Location, browse to the network folder containing the administrative image and the batch file (for example, install.bat ).
11. To locate the Installation Program, browse to the batch file.
    Tip: Type *.* to see a list of all the files or type the file name.
12. Add a detection method to notify Configuration Manager when the application is installed. There are several detections methods to choose from, but Autodesk recommends using one or several MSI product codes. When adding detection, specify these setting values:
    • Setting type. Windows Installer
    • Product code. {28B89EEF-1001-3102-CF3F3A09B77D}
    To add more MSI codes, select Add Clause again.
    Tip: For detection, don't select MSI codes from components that can be installed on the same machine, such as Material Libraries.
13. Consider the following user experience options:
    • Select Install For System if your resource is a device. Otherwise select Install For User from the Installation Behavior drop-down. This option installs the product with administrative rights.
    • To install the application without requiring the user to be signed in, deselect Logon Requirement.
    • To install silently, select Hidden under Installation Program Visibility.
14. (Optional) In the Requirements screen, enter requirements for the application to run.
15. (Optional) In the Dependencies screen, enter application dependencies.
16. Review the information in the Summary screen. Click Previous to edit details. Otherwise, click Next to create the application.
17. Click Close when the application has been created to return to the wizard. Click Next until the wizard finishes.

Using the Package model

This method deploys by device, not by user.

In the Configuration Manager console, follow these steps:

1. Click Software Library, and then expand Application Management.
2. Expand Packages, and then right-click to create a new folder or navigate to an existing folder.
3. Right-click the selected folder and choose Create Package in the selected folder to start the Configuration Manager package creation wizard.
4. Enter the package information.
5. Select This package Contains Source Files and then browse to the network location for the downloaded administrative image created by the image creation tool.
6. Select the Standard Program type and enter the program information:
   • Name. The name that appears on client machines when the product is deployed.
   • Command line. Add the install<Deploymentname>.bat file from the administrative image. The following example is for 3ds Max 2021:
     
     
   • Run. Select Hidden to install the product silently without user input.
   • Program can run. Select Whether Or Not A User Is Logged On so that the product can install on the device at any time.
7. Click Next and enter Requirements:
   • Name. The name that will appear on client machines when the product is deployed.
   • Command line. Add the same information as in step 6.
   • Run. Select Hidden to install the product silently without any user input.
   • Run another program first. Autodesk recommends deselecting this option. If you do select it, you can specify the package to run before installing this package.
   • Platform requirements. Either select This Program Can Run On Any Platform or select the operating systems supported by the product.
   • Estimated disk space. If you know the cache space the product requires, add it here. Otherwise, select Unknown.