{"id":388867,"date":"2024-10-09T21:05:38","date_gmt":"2024-10-09T21:05:38","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/388867\/"},"modified":"2024-10-09T21:05:38","modified_gmt":"2024-10-09T21:05:38","slug":"388867","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/388867\/","title":{"rendered":"Reply To: Unexpected issues with SCCM deployment of Ansys Fluids and Structures 2024 R1"},"content":{"rendered":"

<p>When the initial process for the script is started as admin (which for installs from the SCCM client is always the case), then every subsequent process that it starts also runs as admin. Like I said, clicking on the install button in SCCM or running the script in an administrator powershell window works exactly as expected and installs Ansys fluids and structures. Where there’s a problem is when SCCM is having to do a mandatory deployment where there is no input from the end user. SCCM does all the same things and with the same account as it would for a self service install, it’s just the trigger that’s different: a mandatory install is triggered on a evaluation cycle that runs periodically, while a self service install is triggered on a mouse click. In this one specific case, setup.exe starts to run, but then unexpectedly stops after 10-15 seconds and somehow still gives return code 0 (detailed information in my initial post). This isn’t an permissions problem, if it were then the self service installation wouldn’t be working either. <\/p><\/p>\n","protected":false},"template":"","class_list":["post-388867","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t