Software Deployment

Sorry only have 2016 complied have not done 2017 yet so using info from that version, but will work same way

You create an Admin install and let that build and run the admin install.  You can customize all the aspects you need in the deployment builder GUI.

Note: build it on a share and do not move it or it will break.

Run the setup.exe  and choose:

the deployment will create a batch file that you can use the command from for the post script.

\\dr-acad\programs\installs\autocad2016x64\Img\Setup.exe /qb /I \\dr-acad\programs\installs\autocad2016x64\Img\autocad2016x64.ini /language en-us

create a post batch file that connects to the share and run that command

What would the PI task do? Much of what AutoCAD needs can be done within the installation package.

You don't need to use Autodesk's set-up executable, you can use the MSI, provided you set some properties with a transform:

Add/edit these:

ADR_DONOTSHOWAGAIN 1
ADR_NEXT_INITIAL_CHECK 1
ADSK_DESKTOPSHORTCUT_1 0
ADSK_SETUP_EXE 1
APPS_TEST 1
DEFAULTDESKTOPSHORTCUT 0
MC3_ENABLED #0
PREFERENCELOCKED 1
ROOTDRIVE C:\

Delete these, according to your preference/standards:

ARPNOMODIFY 1
ARPNOREMOVE 1
ARPSYSTEMCOMPONENT 1

Of course, when all else fails, use ITNinja.COM

Apologies, I took the tag you added - for DWG TrueView - to mean that that was the only Autodesk item you were concerned with. Those properties apply to that product.

AutoCAD itself has a deployment package creation tool. It's documented on Autodesk's site. You add your license details, disable stuff, etc. using it.

From memory, to disable updates, you need to disable the "Autodesk Application Manager Service". If the package creation tool doesn't offer you the option to disable updates, you'll need to track down which MSI performs this function, create a transform for it and disable the service that way. Remember that Autodesk provide a batch/CMD file "shell" that you can use to deploy their products using the MSIs, specifically to allow much more granular deployments than can be achieved using the set-up stub's INI file.