Also check the documentation for an /SMS switch or similar. Installers that spawn other installations and close themselves frequently have a switch that will force the originating EXE to stay active until the entire package has installed.
Isaac Holmes IT Support Engineer Distributed Engineering Support University of Notre Dame ________________________________________ From: [email protected] [[email protected]] On Behalf Of Jeffrey Hunt [[email protected]] Sent: Thursday, December 05, 2013 3:19 PM To: [email protected] Subject: Re: [MDT-OSD] Autodesk IDSU 2014 via MDT 2012 u1 Have you tried installing the .Net framework separately so that the app does not try to install it? It could be as simple as that. Have you tried extracting the prereqs from the installer? The installer probably launches a separate installer for the app than what it starts with. On 06/12/2013 12:58 AM, "Matt Wilkinson" <[email protected]<mailto:[email protected]>> wrote: > > Anybody deployed this using MDT 2012 u1 or sccm 2012? Whenever I kick off a > deployment mdt thinks the setup has quit but it hasn’t it just installs .net > 4.5. The heartbeat thinks setup has closed. > > The command line is this. My client is Windows 7 x64 SP1 > > "Img\setup.exe" /W /QB /I Img\IDSU 2014 (CAD) x64.ini > > > > Thanks. > > > > Matt Wilkinson > > ICT Technican > > Leeds College of Building > > > _____________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System on behalf > of Leeds College of Building. > For more information please visit http://www.symanteccloud.com > _____________________________________________________________________
