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

<p>The UAC slider is set to the highest setting via policy. Installs that come through the SCCM client do not trigger a UAC prompt window. <\/p><p>The account doing the install for the SCCM client doesn’t need direct access to the server file share because all of the install files get downloaded to a local folder (C:\\Windows\\ccmcache).<\/p><p>As a test, I checked the %TEMP% location for the account and it’s the C:\\Windows\\Temp directory. I can check others, but I don’t know which ones are relevant to troubleshooting this. There functionally shouldn’t be any difference between a mandatory SCCM install and a self service one, with the sole exception of what actually starts the install script. The account doing the install is the same, the permissions are the same, and the environment variables are the same. <\/p><p>Adding the “-verb runAs” argument to the start-Process line of the script actually caused more problems, to the point that even clicking on the install button manually would fail to install. As it is, the script itself is launching in an administrator session, so any subprocesses would also launch with the same access. <\/p><\/p>\n","protected":false},"template":"","class_list":["post-390457","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