Learning Forum

[andygav]

Hi, I'm coming across a persistent problem with installing Ansys 2024R2 via MDT onto a Win11 23H2 pc.

The command that invokes it is:

setup.exe -silent -licserverinfo 2325:1055:server -aqwa -cfx -spaceclaim -ensight -fluent -forming -forte -motion -optislang -polyflow -reactionwb -sherlock -speos -acis -icepak -autodetect_cads

It proceeds along but on a few machines but then it gets to:

The installation will copy the prerequisite setup files from the media in case you need to reconfigure later or if you need to configure client machines for products installed to a network share.
This may take a while ...
Successfully copied prerequisites from media.

You don't need to install any prerequisites.

  Extraction: \\DC1\DeploymentShare$\Applications\ANSYS ANSYS 2024R2\cads\acispara\WINX64.7z ...
  Extraction: \\DC1\DeploymentShare$\Applications\ANSYS ANSYS 2024R2\cads\spatialiop\WINX64.7z ...
  Extraction: \\DC1\DeploymentShare$\Applications\ANSYS ANSYS 2024R2\cads\cadaisol\WINX64.7z ...
  Extraction: \\DC1\DeploymentShare$\Applications\ANSYS ANSYS 2024R2\cads\cadregistry\WINX64.7z ...

..and then stops. cadregistry is quite small so it shoudn't be an issue. The file extracted OK earlier on.

• Incidentally, I tried putting the product list (minus the -) into a file called "options" and used the -productfile switch but couldn't get it to work. The exact syntax would help here, such as the filename to use (if it matters). Also, it ignores the -forming flag as unknown. 
• I've been installing other software OK, such as Ansys Electromagnetics, Solidworks etc.

 

[MangeshANSYS]

Hello,

Here is a link to the silent installation documentation https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/corp/v242/en/installation/win_silent_op.html which includes syntax and informatino on options

 

for the stalling of the silent installation ...

1.  Does eliminating the space in the folder name yield any different results ? i.e. changing "ANSYS ANSYS 2024R2" to "ANSYS_ANSYS_2024R2" ? Or perhaps map the UNC share as a drive letter and try again ?
2.  the next set of files to be extracted might be one of these zip files (my example uses F:\ as the mount). Do any or all of these files exist in your media ?

  Extraction: F:\cads\cadregistry\WINX64.7z ...
  Extraction: F:\apipsrv\WINX64.7z ...
  Extraction: F:\syscplg\WINX64.7z ...
  Extraction: F:\mechsrvplg\WINX64.7z ...
  Extraction: F:\icemwb\WINX64.7z ...
  Extraction: F:\cads\acispara\WINX64.7z ...
  Extraction: F:\sec\WINX64.7z ...
  Extraction: F:\cads\fusion\WINX64.7z ...
  Extraction: F:\cads\spatialiop\WINX64.7z ...
  Extraction: F:\fluentc\WINX64.7z ...
  Extraction: F:\fluentm\WINX64.7z ...
  Extraction: F:\fluent3ddp\WINX64.7z ...
  Extraction: F:\tp\mpi\WINX64.7z ...
  Extraction: F:\ansys\WINX64.7z ...
  Extraction: F:\data\DATA.GZ ...
  Extraction: F:\aas\WINX64.7z ...
  Extraction: F:\cads\stride\WINX64.7z ...
  Extraction: F:\cads\hoops\WINX64.7z ...
  Extraction: F:\geompara\WINX64.7z ...
  Extraction: F:\artemis\WINX64.7z ...
  Extraction: F:\post\WINX64.7z ...
  Extraction: F:\fluent3d\WINX64.7z ...
  Extraction: F:\ensight_components\WINX64.7z ...
  Extraction: F:\tp\cpprestsdk\WINX64.7z ...
  Extraction: F:\post\WINX64.7z ...
  Extraction: F:\chemkin\WINX64.7z ...
  Extraction: F:\forte\WINX64.7z ...
  Extraction: F:\icemcfd\WINX64.7z ...
  Extraction: F:\turbogrd\WINX64.7z ...
  Extraction: F:\cads\acad\WINX64.7z ...
  Extraction: F:\cads\cat5\WINX64.7z ...
  Extraction: F:\cads\datakit\WINX64.7z ...
  Extraction: F:\cads\osm\WINX64.7z ...
  Extraction: F:\cads\pe\WINX64.7z ...
  Extraction: F:\cads\ai\WINX64.7z ...
  Extraction: F:\geomunig\WINX64.7z ...
  Extraction: F:\cads\nx\WINX64.7z ...
  Extraction: F:\cads\revit\WINX64.7z ...
  Extraction: F:\cads\se\WINX64.7z ...
  Extraction: F:\cads\sw\WINX64.7z ...
  Extraction: F:\speos\WINX64.7z ...
  Extraction: F:\speosnx\SNX2212_WINX64.7z ...
  Extraction: F:\speosnx\COMMON_WINX64.7z ...
  Extraction: F:\speosnx\SNX2306_WINX64.7z ...
  Extraction: F:\speosnx\SNX2312_WINX64.7z ...
  Extraction: F:\speosnx\SNX2406_WINX64.7z ...
  Extraction: F:\additive_cl\WINX64.7z ...
  Extraction: F:\matcal\WINX64.7z ...
  Extraction: F:\motion\WINX64.7z ...
  Extraction: F:\sherlock\WINX64.7z ...
  Extraction: F:\soundsas\WINX64.7z ...

 

3. If not then, which media is being used to install Ansys? Were the .iso images downloaded, then MD5 checksum checked for the .iso and extracted to the share ? Or was a certain zip file or zil files used ? - which one ? if you try to install on a test machine from the GUI then does it work corectly or stalls at the same point ? it is possible that some file may be missing ?

4. Another possibility if if a security software such as an antivitus is causing access issues and hence the lockup ?

 

hope this helps

 

[andygav]

 

 

Thanks for your response. I’ll try your suggestions.

If I abort the task sequence and then re-run it, it will run to almost completion. That is, the software is installed, the license server setup in the client, it all works. The task sequence itself doesn’t terminate however, so you don’t get that nice screen with 0 errors and 0 warnings.

Its as if it saves itself some resource by re-using the files that are already present from the aborted run. It is a large install after all (~64Gb).

Only thing I can find so far is the scratch space but this relates to WinPE. I had upped this to 128Mb just to see if it has an affect though the TS runs in the full o/s rather than in WinPE.

WinPE reserves memory on the X: drive to unpack the WinPE files, plus additional temporary file storage, known as scratch space, that can be used by your applications. By default, this is 512MB for PCs with more than 1GB of RAM, otherwise the default is 32MB. Valid values are 32, 64, 128, 256, or 512.

WinPE: Mount and Customize | Microsoft Learn

I had used the .iso’s and unpacked them into a single folder. I also used the automated installer to download a local copy (as it, usefully, has the service packs applied already).