Deploying AutoCAD 2010

Posted: December 3rd, 2009 | Author: admin | Filed under: Uncategorized | Tags: , , , | No Comments »

Installing AutoCAD 2010 with scripts is fairly painless. First use the setup utility to create a new “Deployment,” saving the deployment to a network path. Once you have created a new deployment browse to the network path you saved it to. In this folder you should have three items, a folder called “AdminImage”, a folder called “Tools”, and a shortcut with the name of your deployment. View the properties of the shortcut and copy the “Target” field.

The target field should be simular to the following (One Line):

\\server\share\AutoCAD_2010\AdminImage\setup.exe /qb /I \\server\share\AutoCAD_2010\AdminImage\AutoCAD_2010_x86.ini /language en-us

Append this line with /wait to acheive a result simular to the following (one line):

\\server\share\AutoCAD_2010\AdminImage\setup.exe /qb /I \\server\share\AutoCAD_2010\AdminImage\AutoCAD_2010_x86.ini /language en-us /wait

Now just execute the command above from your scripts!

The AutoDesk Documentation is available here (pdf), but the document only provides an example in visual basic script.

Bonus:

If you wish to deploy the Visual C Runtime, DirectX, .NET 3.5 SP1, etc separately you can edit the .ini file referenced in the command above to remove this functionality (”\AdminImage\AutoCAD_2010_x86.ini” in this example). Simply open the file in a plain text editor and remove the references to the components you do not wish to have the setup install on the “PREREQUISITE” lines in the “[ACAD]” and “[ADR]” sections.


Deploying Maya 2010

Posted: November 20th, 2009 | Author: admin | Filed under: Unattended Installations | Tags: , , , | 1 Comment »

Below is a sample script for installing Maya 2010 Silently. Keep in mind many of the lines are long, and are likely to wrap in a web browser.

SET MAYA2010INSTALLPATH=<Insert Your Path to the folder containing the MSI Files below>

SET MAYA2010SERIALNUMBER=<Insert Your S/N>

SET MAYA2010PRODUCTKEY=<Insert Your Product Key>

SET MAYA2010LICSERVER=<Insert Name of your License Server (i.e. DNS Name)>

msiexec /i “%MAYA2010INSTALLPATH%\Maya_Docs_en_US2010.msi” /qb REBOOT=REALLYSUPPRESS

msiexec /i “%MAYA2010INSTALLPATH%\isscript.msi” /qb REBOOT=REALLYSUPPRESS

msiexec /i “%MAYA2010INSTALLPATH%\Maya2010.msi” /qb ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS

msiexec /i “%MAYA2010INSTALLPATH%\MatchMover2010.msi” /qb ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS

msiexec /i “%MAYA2010INSTALLPATH%\AutodeskDirectConnect4.0.msi” /qb  ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS

Source: Deployment of Maya 2010


Unattended installation of Windows Installer (.MSI Files)

Posted: October 11th, 2009 | Author: admin | Filed under: Unattended Installations | Tags: , , , | No Comments »

If your installer has a .msi file extension, it uses the Windows Installer. Typically all that is needed is to execute the file with one of the following switches.

example.msi /QB

example.msi /QN

The /QB switch will run the installer and display a progress box while installing the software. The /QN switch will run the installer and display no nothing at all.

Some installers reboot automatically after the installation has run. To suppress the reboot you can run the installer with the switch “REBOOT=Suppress.” For example:

example.msi /QB REBOOT=Suppress

example.msi /QN REBOOT=Suppress

The following are all of the switches available for MSI files:

Windows ® Installer. V 5.0.7100.0

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install – Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product – m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode – progress bar only
/q[n|b|r|f]
Sets user interface level
n – No UI
b – Basic UI
r – Reduced UI
f – Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i – Status messages
w – Nonfatal warnings
e – All error messages
a – Start up of actions
r – Action-specific records
u – User requests
c – Initial UI parameters
m – Out-of-memory or fatal exit information
o – Out-of-disk-space messages
p – Terminal properties
v – Verbose output
x – Extra debugging information
+ – Append to existing log file
! – Flush each line to the log
* – Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p – only if file is missing
o – if file is missing or an older version is installed (default)
e – if file is missing or an equal or older version is installed
d – if file is missing or a different version is installed
c – if file is missing or checksum does not match the calculated value
a – forces all files to be reinstalled
u – all required user-specific registry entries (default)
m – all required computer-specific registry entries (default)
s – all existing shortcuts (default)
v – runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.

Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.