Learning Forum

[Patrick Guerrisi]

Hi

We use SCCM ( now known as MECM) to deploy software to our staff and computer labs. SCCM uses the SYSTEM account when it installs

However when installing as system it throws up the following error :

 

The commandline I am using is:

ansys-rockybundle-bin-22.2.X-win64.exe /SILENT

There is another post about this exact issue but the response given is not the solution:

Rocky installation under the SYSTEM account fails (ansys.com)

When I run the install command with my user account with administrator privileges it installs without error

Can anyone provide a solution why this error is showing when installing as system?

[MangeshANSYS]

 

Hello,

As indicated in the initial response in the post you referenced, please include the target directory with the DIR= flag.

 

Secondly, the error Failed to expand shell folder userdesktop seems to be a generic error seen by many installers.

Please see if any of the suggestions on this webpage are also helpful to you
https://www.reddit.com/r/SCCM/comments/kvsfvr/failed_to_expand_shell_folder_constant/?rdt=34733

 

[Patrick Guerrisi]

Hi

Thanks for the reply

I added the Path switch to the install string and looks like the mapped drive error has stopped popping up but I am still getting the the error Failed to expand shell folder userdesktop

I have added the suggestion from that thread but it hasnt worked

Here is my install string:

ansys-rockybundle-bin-23.1.1-win64.exe" "/DIR=C:\Program Files\ANSYS Inc\v231\Rocky" /VERYSILENT /MERGETASKS="!desktopicon"

Screenshot:

[MangeshANSYS]

as mentioned earlier, it appears that the shell setup runs under is unable to expand userdesktop

perhaps in your install.cmd you can test by adding a line like below beffore the line for silent setup (assuming c:\temp exists)

set userdesktop=C:\temp\

 

if this works, you will need to see if anything got written to the c:\temp folder 

I suspect it is trying to create desktop icons but unable to locate or unable to access whatever userdesktop is pointing to

this is an experiment, hope it helps find the root cause.

 

[Patrick Guerrisi]

 

Hi

Thanks for the reply again

I was able to do a regular manual install with the parameter /saveinfo and unchecked all the desktop icons. This resolved the problem with the "failed to expand Shell Folder Constant "userdesktop" error I was getting

I have been testing this on a VM with Windows 10 on it

I still get the original error even with setting the directory install location which is strange

See below what my install string is and that error that keeps showing at the end of the install ( as system account )

The process exe is named Fluent_coupling.exe 

I could just kill that process at the end. 

Install string used is:

"ansys-rockybundle-bin-23.1.1-win64.exe" "/DIR=C:\Program Files\ANSYS Inc\v231\Rocky" /VERYSILENT /LOADINF="%~dp0Rocky_params.inf"

 

 

 

 

[MangeshANSYS]

Hello,

I used a test machine with Rocky 2023 R1 not installed. downloaded and unzipped the Rocky 2023 R1 update with full package .zip file and extracted to the path you are using

I also used the command line as shown. Rocky installed in minutes without any errors 

I am not sure where the references to K and W drive are coming from. Please check the system's path and other environment variables if it is runnign python from those locations. perhaps try unsetting those portions of the path / environment ?

What else is being done in the .inf file ?Are you also trying to install the Fluent export plugin ?

 

hope this helps

[Patrick Guerrisi]

Did you use psexec to install via the system account?

If not that would be why you get no error

 

I've tried on multiple machines and even with a brand new Frehley imaged window 10 install and when I use the system account I get that error at the end 

[MangeshANSYS]

Hello 

I did not use psexec. what account is psexec running as ? Are W and K drives mapped for other users, but not for the user that psexec runs as ?

also I did not hear on which options are in the .inf file

[JM Derksen]

@Mangesh Bhide

Using "psexec.exe -s -i cmd" (a Sysinternals/Microsoft tool), you can initiate an elevated Command Prompt session under the SYSTEM account to replicate the issue. 
If you are unfamiliar with the procedure, kindly assign this task to another Ansys support employee.

I can confirm that the Rocky 2023r2 installation has the same problem.

Please address this issue promptly, as large companies (as well as small ones) are unable to deploy Rocky using leading Software deployment tools like SCCM/MECM.

 

[MangeshANSYS]

Hello

It worked with psexec as well

I uninstalled the old version



I opened an elevated command prompt and launched cmd under system account and ran the .exe /VERYSILENT with the DIR= flag as seen below




Are there any other issues with your account or administrator rights ? Perhaps have another system administrator run this to verify if this is not an issue with your account ?

I hope this helps

[Roy Padrick]

Has there been a verified solution to this yet? I've tried all the suggestions, but still get the "cx_Freeze: Python error in main script error" when running under system context. My install command is: ansys-rockybundle-bin-23.1.1-win64.exe "/DIR=C:\Program Files\ANSYS Inc\v231\Rocky" /VERYSILENT /LOADINF=E:\rockyinstall.inf

I've tried just the /silent switch and no inf file, still same error.

[MangeshANSYS]

it works as demonstrated in screenshots above. What are the contents of your .inf file ?

[Roy Padrick]

[Setup]
Lang=default
Dir=C:\Program Files\ANSYS Inc\v231\Rocky
Group=Ansys 2023 R1.1
NoIcons=0
SetupType=custom
Components=rocky,fluent,workbench
Tasks=v231,project,start_menu_icons,start_menu_icons_scheduler

 

But it doesn't work, as others have said in this thread. I even followed your commands to the letter, and it still throws the error at the end of the install. When I run it under a regular admin command prompt, it installs fine. So what are you doing differently that we are not? What is different about your VM or process that we can't replicate?

[MangeshANSYS]

It is important that the process be launched from an elevated prompt. could it be possible that your workflow is not running the command as elevated user ?

The machine where i ran the test is a Windows 10 laptop (not a VM) . the test above was to duplicate the other's setup. so I installed approproate utilities from sysinternals (I believe psexec) made sure to launch it elevated. (see output of whoami in screenshot above) 

I hope this information is helpful

[Roy Padrick]

I've been packaging software for deployment for over a decade. Yes, I'm sure it was running elevated. I used PSExec to run under system context. The problem has to be related to the user environment of system. If you want me to submit a video as proof, I can.

[MangeshANSYS]

I absolutely believe you if you are confirming it ran elevated. I will investigate why / how python comes into picture and why you might be seeing that error "cx_Freeze: Python error in main script error"

 

[Roy Padrick]

Any update?

[Roy Padrick]

https://myerauedu-my.sharepoint.com/:v:/g/personal/padrickr_erau_edu/EZThpdzcBYZGkmQ2mkieAH4BwThRWo-SjJE-wizAvBuj0g?e=aPvene

Video of the process and error at the end.