Autodesk 62204-541108-9310 Administration Guide - Page 22

Run Batch Files, Use Group Policies to Run a Deployment

Get Autodesk 62204-541108-9310 - Combustion - Mac PDF manuals and user guides
UPC - 606121703686
View all Autodesk 62204-541108-9310 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

ACADSERIALPREFIX=ACADSERIALNUMBER= ADLM_PRODKEY= ADLM_EULA_COUNTRY= InstallLevel=5 ACADSTANDALONENETWORKTYPE="3" ACADLICENSESERVERTYPE="Redundant Server License" ACADLICENSETYPE="Network License" ACADSERVERPATH=" 000000000000 27005; 000000000000 27005; 000000000000 27005;" Notes thru are valid network license servers with redundant licenses. Run Batch Files After creating a batch file, you move it to a server or use a mapped drive letter or a UNC (universal naming convention) path. If you place it on a server for users to run, create a shared folder on the server, and then add users to the share with the rights they need. Users who just run the batch file can have read-only access to the shared folder. Next, in another server location, create a directory for each product you want to install. Copy the installation files to this directory from the product media. You may also want to create directories for service packs, extensions, and your own customization tools. Use one of the following methods to run an installation batch file: ■ Run the batch file manually at each individual computer. To run the installation, paste the batch file into the Run dialog box or run it from the Windows command prompt. ■ Send an email to each user who should run the batch file, with the UNC path and any required instructions. ■ Email the batch file to each user with instructions for use. ■ Set up the batch file so that it runs on login. Use Group Policies to Run a Deployment With group policies, you can advertise and install a program by assigning a deployment to computers. A deployment that is assigned to a computer can 16 | Chapter 2 Alternative Distribution Methods

  • 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
ACADSERIALPREFIX=<SerialPrefix>ACADSERIALNUMBER=<SerialPostFix>
ADLM_PRODKEY=<ProdKey> ADLM_EULA_COUNTRY=<eula_lang>
InstallLevel=5
ACADSTANDALONENETWORKTYPE="3"
ACADLICENSESERVERTYPE="Redundant Server License"
ACADLICENSETYPE="Network License"
ACADSERVERPATH="<server1> 000000000000 27005;<server2>
000000000000 27005;<server3> 000000000000 27005;"
Notes
<server1> thru <server3> are valid network license servers with redundant
licenses.
Run Batch Files
After creating a batch file, you move it to a server or use a mapped drive letter
or a UNC (universal naming convention) path. If you place it on a server for
users to run, create a shared folder on the server, and then add users to the
share with the rights they need. Users who just run the batch file can have
read-only access to the shared folder.
Next, in another server location, create a directory for each product you want
to install. Copy the installation files to this directory from the product media.
You may also want to create directories for service packs, extensions, and your
own customization tools.
Use one of the following methods to run an installation batch file:
Run the batch file manually at each individual computer. To run the
installation, paste the batch file into the Run dialog box or run it from the
Windows command prompt.
Send an email to each user who should run the batch file, with the UNC
path and any required instructions.
Email the batch file to each user with instructions for use.
Set up the batch file so that it runs on login.
Use Group Policies to Run a Deployment
With group policies, you can advertise and install a program by assigning a
deployment to computers. A deployment that is assigned to a computer can
16
| Chapter 2
Alternative Distribution Methods