wait -passthru is always waiting for the property ".HasExited" to become true. ![]() The powershell commandlet "Start-Process". As soon as that process gets killed, the installation of VS will finish. There is a process named "xgTrayIcon" which gets started during the installation of VS. And i don`t want to use batch instead of PSADTK for the Installation.ĭoes anyone have an idea how to solve this?īy the way i want to apologise for my English. If i call the deployment script from Powershell ISE, everything works fine. If i create a batch file to execute the vs.exe and call the batch file from PSADTK, the cmd window gets closed after the installation and even is giving me a return code, but the powershell script is still staying open. It even doesn´t matter if i use PSADT or a simple PowerShell prompt to enter the command (as Start-Process -wait -passthru). Here´s the Problem: Although all processes started by vs.exe are finished, the powershell script doesn´t end. As soon as the process has finished, the ExitCode is checked. The function Execute-Process is starting the vs.exe and then it´s waiting for the process to finish. ![]() Now when i test the installation of my package on a local virtual machine i call the deployment script from a powershell prompt. This is the command i am using in the PSADTK to install Visual Studio:Įxecute-Process -Path "$dirFiles\VS.exe" -Parameters "-noweb", The package itself is using the (ingenious) AppDeployToolkit, so Visual Studio gets installed via PowerShell. ![]() Each Software package is created as an application in SCCM. We are using Microsoft SCCM to deploy Software. Now i´m facing a strange issue installing Microsoft Visual Studio 2017 Professional (at least it seems being strange to me). ![]() I´m working as a software packager in a german company.
0 Comments
Leave a Reply. |