Hi All

I am currently trying to figure out a way to deploy Ansys 13.0 with MDT

If I run the command
setup.exe -silent -install_dir C:\Applications\Ansys13 -licserverinfo 2325:1055:flexserver
manually from the "Run" command the software installs fine without any issues.

However when the same command line is put into an MDT Application Package the software gets part way through the installation and then appears to stall.

Have any of you succesfully packaged and deployed Ansys?

I have a call logged with the software vendor but they stated "Also please note we don't officially support any of these deployment systems since we don't test them in-house. We will do our best in these cases but cannot promise we will get it to work through it."

Thanks Pete
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
We have deployed Ansys silently via SCCM this year. We did hit one problem with some of the pre-requisites being "blocked", but unlikely to be the same issue if it installs fine from the run command.

The ansys installation log is usually very good, Have you taken a look at it? I believe that the default installation log is put in the installation directory with a .log extension. I spent a while looking at it recently, so feel free to post or PM if needed.
Answered 09/28/2011 by: dbloomfield
Senior Yellow Belt

Please log in to comment
0
please note we don't officially support any of these deployment systems since we don't test them in-house.PMSL...They have *such* a high regard for their clients, they haven't ever been bothered to ask a group of them if they would test-deploy on their behalf. How do these fools stay in business? Priceless.

Anyway, moving on...

I suspect the issue is connected with the fact that MDT uses the local System account to deploy and the package is popping up a dialog box to ask the non-existent user for input. If the EXE extracts and executes an MSI, use that instead (since you can apply a transform to an MSI and either bypass or work around the requirement for user input. If it doesn't, capture it to one.
Answered 09/28/2011 by: VBScab
Red Belt

Please log in to comment
0
The problem we are seeing is the manual install is done and finished in about 4 minutes.

This is approx 10 minutes into the network deployment.....
>>>--------------------------------------->
Start Installation: Wed Sep 28 15:26:40 2011
Revision: 13.0

Platform specifics:
Windows
Username of Installer: dfs/I300364$
User Has Administrator Privileges

You don't need to install any pre-reqs.

Initial mount directory:
\\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical
Installation Directory:
C:\Applications\Ansys13

ANSYS, INC. Products
ANSYS Structural Mechanics
ANSYS Mechanical Products
ANSYS Customization Files
ANSYS PDM Interfaces
TeamCenter Engineering
ANSYS Geometry Interfaces
ACIS
Catia, Version 4
Catia, Version 5
CoCreate Modeling
Inventor
JTOpen
NX
Parasolid
Pro/ENGINEER
Solid Edge
SolidWorks

You don't need to install any prerequisites.

Successfully copied pre-requisites from media.

Reading the installation media contents - please wait.

Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tcl\COMMON.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tcl\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\common\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\configs\common\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\hlptool1\HLPTOOL1.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\hlpfiles\HLPFILES.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\hlpserv\HLPSERV.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instutil\INSTUTIL.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tcl\COMMON.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tcl\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tk\COMMON.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\instcore\tk\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\configs\wb\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\framewrk\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addins\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addinmbu\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addincfg\wb\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addincfg\ekm\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\corewb\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\rsm\RSM.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\icemwb\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\ekm\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addincfg\turbosys\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\cads\acispara\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\tgrid\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\configs\tgrid\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\javajre\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\ansys\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\configs\ansys\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\addincfg\ansys\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\solver\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\data\DATA.GZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\apdl\APDL.GZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\geomacis\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\geompara\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\geomcat4\WINX64.TGZ ...
Extraction: \\dfs\build\Autodesk\Ansys 13.0 SP2\Ansys 13 Mechanical\hpmpi\WINX64.TGZ ...

The log file just appears to stop. 7.zip does not appear to be running so I don't think it is that which is causing the problem.
Answered 09/28/2011 by: petesnow
Yellow Belt

Please log in to comment
0
Equally, by default, the System account has no access to network resources (\\dfs\build). Copy the package locally and execute it from there.
Answered 09/28/2011 by: VBScab
Red Belt

Please log in to comment
0
On our installations there are alot more items to extract. Are you sure its not something simple like disk space?
Also you say that is the log after 10 minutes... our installation takes nearly 25 to complete so you may be worrying prematurely. Whats the status of the log if you leave it for 30?


If not, I would also look into what the "hpmpi\WINX64.TGZ" component is and possible reasons for it to be hanging.
Answered 09/28/2011 by: dbloomfield
Senior Yellow Belt

Please log in to comment
0
Definatley not disk space - we are talking 400+Gb free on these PC's

I tried copying the installation point to the local PC. Ran setup.exe via MDT but get the same result...
I can see 7.zip starting and stopping as the files get extracted but it doesn't appear to be running at the point of failure.

The first time we realised the stall was occuring was after the PC had been trying to build overnight.

I think my next port of call will be to download the software again in case I have a corrupted file.
Answered 09/29/2011 by: petesnow
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity