Autodesk 18505-011452-9565 Administration Guide - Page 23

Advantages, Create an application distribution share point., Assign the deployment to a computer.

Page 23 highlights

be used by any user of that computer. Generally, you would assign the deployment to a computer that is shared by several users. NOTE Autodesk products are designed to be installed on a computer so that any user who logs on to the computer can run the software. If you assign a deployment to a specific user rather than a computer, you may encounter problems when a second specified user tries to install or uninstall a copy of the program. The following section outlines the advantages and disadvantages of using group policies. Advantages ■ Works well with deployment functionality. ■ Allows you to add custom files to a deployment. ■ Allows deployment to computers rather than to users. Disadvantages ■ Prohibits the passing of command-line parameters to an MSI executable. You must use scripts instead. ■ Prohibits customization of application settings, other than what is set while creating a deployment. Autodesk products typically have software prerequisites that must be installed on a computer to support the Autodesk product. In particular, Microsoft .NET Framework 4.0, Fusion, and the Fusion plug-in must be installed prior to using group policies. Before deploying products, consult the System Requirements for each product, and ensure that these are installed on the computer where the program will being installed. Distributing a program through group policies involves three main steps: 1 Create an application distribution share point. The application distribution share point is created when you create a deployment. See Create an Original Deployment (page 8) to create a deployment. 2 Assign the deployment to a computer. See Use Group Policies to Assign a Deployment to Computers (page 18). 3 Verify the installation. Confirm that the program has been correctly installed. See Verify a Group Policy Deployment (page 20). Alternative Distribution Methods | 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

be used by any user of that computer. Generally, you would assign the
deployment to a computer that is shared by several users.
NOTE
Autodesk products are designed to be installed on a computer so that any
user who logs on to the computer can run the software. If you assign a deployment
to a specific user rather than a computer, you may encounter problems when a
second specified user tries to install or uninstall a copy of the program.
The following section outlines the advantages and disadvantages of using
group policies.
Advantages
Works well with deployment functionality.
Allows you to add custom files to a deployment.
Allows deployment to computers rather than to users.
Disadvantages
Prohibits the passing of command-line parameters to an MSI executable.
You must use scripts instead.
Prohibits customization of application settings, other than what is set
while creating a deployment.
Autodesk products typically have software prerequisites that must be installed
on a computer to support the Autodesk product. In particular, Microsoft .NET
Framework 4.0, Fusion, and the Fusion plug-in must be installed prior to using
group policies. Before deploying products, consult the
System Requirements
for
each product, and ensure that these are installed on the computer where the
program will being installed.
Distributing a program through group policies involves three main steps:
1
Create an application distribution share point.
The application
distribution share point is created when you create a deployment. See
Create an Original Deployment
(page 8) to create a deployment.
2
Assign the deployment to a computer.
See
Use Group Policies to
Assign a Deployment to Computers
(page 18).
3
Verify the installation.
Confirm that the program has been correctly
installed. See
Verify a Group Policy Deployment
(page 20).
Alternative Distribution Methods |
17