Basic Maya network deployment

For Windows, deploy Maya from your Autodesk account.

The instructions in this document are for deploying Maya on macOS and Linux across a network.

Extract and copy the installation files

On Linux
  1. Extract the installation files to a network share
  2. Copy install/manifest/basic_deployment_collection_template.xml to the install/ directory, creating install/basic_deployment_collection_template.xml ; this is the copy of basic_deployment_collection_template.xml you will modify for deployment
On macOS
  1. Double click the dmg to mount it
  2. Create a directory on a network share for your deployment documents
  3. Right-click on Install Maya <version>.app and select Show Package Contents
  4. Copy Install Maya <version>.app/Contents/ to the directory on the network share, creating <network_share>/<deployment_documents>/Contents/
  5. Copy Contents/Helper/manifest/basic_deployment_collection_template.xml to the directory on the network share, creating <network_share>/<deployment_documents>/basic_deployment_collection_template.xml; this is the copy of basic_deployment_collection_template.xml you will modify for deployment

Modify the deployment template

Open basic_deployment_collection_template.xml and modify the following sections:

<Eula><Status>
Set this to Accept:
<Eula>
     <Status>Accept</Status>
</Eula>
<LoggingSettings>
Set it to the name and location of the log file. The file must be accessible to the hosts on which Maya is being deployed. For example:
<LoggingSettings>
    <Logging>true</Logging>
    <Path>/my_mnt_pnt/path_to_logs/deployment.log</Path>
</LoggingSettings>
<License>
To configure your license, you will need to make sure your license type is uncommented. By default, the single network license is uncommented. Nested comments are not supported in xml. Be careful not to create nested comments. Deployment will fail if the xml file contains nested comments.

For example, to use a distributed network license, comment out <Single></Single> and uncomment <Distributed></Distributed> and enter the names of license servers:

  
<License>
   <!-- <StandaloneLicense /> -->
   <!-- <UserLicense /> -->
   <NetworkLicense>
      <!-- <Single>
         <Server>Server1</Server>
      </Single> -->
 <!-- <Redundant>
         <Server name="Server1" order="1" />
         <Server name="Server2" order="2" />
         <Server name="Server3" order="3" />
      </Redundant> -->
      <Distributed>
         <Server name="LicenseServer1" order="1" />
         <Server name="LicenseServer2" order="2" />
      </Distributed>
   </NetworkLicense>
</License>
 
If you are using a standalone license, you will need to provide a serial number between the <SerialNumber></SerialNumber> tags within <Bundles><Bundle>. Be careful not to create nested comments when commenting out the <NetworkLicense> section.
  
<License>
     <StandaloneLicense />
<!-- <UserLicense /> -->
<!-- <NetworkLicense> -->
   <!-- <Single>
           <Server>Server1</Server>
        </Single> -->
<!-- <Redundant>
        <Server name="Server1" order="1" />
        <Server name="Server2" order="2" />
        <Server name="Server3" order="3" />
     </Redundant> -->
<!-- <Distributed>
         <Server name="Server1" order="1" />
         <Server name="Server2" order="2" />
      </Distributed> -->
<!--  </NetworkLicense> -->
</License>
[...]
<Bundles>
   <Bundle SeqNo="1">
      [...]
      <SerialNumber>000-00000000</SerialNumber> 
<CustomProperties> <Property name="SelProductKey" [...] />
If you are using an enterprise license, change the value of the SelProductKey property to the enterprise product key, 53501:
<CustomProperties>
   <Property name="SelProductKey" value="535O1" />
   <Property name="EulaLocale" value="US" />
</CustomProperties>
<Applications><!--Name--><Application><UPI2>[...]</UPI2></Application>
Maya components such as Bifrost, USD, and Substance will be installed by default. To prevent a specific component from being installed, comment out the component's <Application> section. The <Application> section of a specific component will be below its name. Be careful to not create nested comments if you are commenting out more than one component. Nested comments are not supported in xml.

For example, if you do not want to install Bifrost, you would comment out the entry below <!--BIFROST-->:

<Applications>
   [...]
   <!--BIFROST-->
   <!-- <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}</UPI2>
   </Application> -->
   <!--MAYAUSD-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   <!--SUBSTANCE-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   [...]
</Applications>

To avoid creating nested comments when commenting out multiple components, comment out each <Application> section individually:

<Applications>
   [...]
   <!--BIFROST-->
   <!-- <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application> -->
   <!--MAYAUSD-->
   <!-- <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application> -->
   <!--SUBSTANCE-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   [...]
</Applications>

If you need to install a component you had previously commented out, you will need to uncomment the component's section:

<Applications>
   [...]
   <!--BIFROST-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   <!--MAYAUSD-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   <!--SUBSTANCE-->
   <Application>
      <UPI2>{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</UPI2>
   </Application>
   [...]
</Applications>

Run the installer

Once you have modified the basic_deployment_collection_template.xml file, install Maya using the silent installation option.

On Linux, open a terminal window, and run the Setup command using absolute paths:
sudo <network_share>/install/Setup -i deploy --noupdate --silent -o <network_share>/install/basic_deployment_collection_template.xml
On macOS, use the Setup command in <network_share>/<deployment_documents>/Contents/Helper/Setup.app/Contents/MacOS/. In a terminal window, run the Setup command using absolute paths:
sudo <network_share>/<deployment_documents>/Contents/Helper/Setup.app/Contents/MacOS/Setup -i deploy --silent -o <network_share>/<deployment_documents>/basic_deployment_collection_template.xml