And create mine below, but it seems not working. Setup.exe is running but hangging there for a very long time. Let me know if i did it wrong in anyway.
Note the incorrect quotation types around your commands â & â rather than ", and â & â rather than '
Iâd also suggest your two commands are slightly different, the PSADT (PowerShell) command is missing the quiet parameter (so âmayâ be launching a GUI hidden (in the System context?)), so I think you command should be:
@Adrian_Scott, As Moderator Iâm able to fix posts and it turns out the curly double quotes are a side effect of Hyan not using the <\> Preformated Text tool on code in his post.
I have fixed Hyanâs post by adding back-ticks on his lines of code so that Discourse site shows them properly.
I used the PowerShell App Deploy Toolkit a few years ago to create a packaged install for SAS Enterprise Guide. One thing I can recommend is to remove the â-quietâ and â-windowstyle âhiddenââ parameters until youâre certain the install works as intended.
Initially the install wasnât working for me, and once I removed those parameters and watched the install on one of my test devices, I was able to see the dialog that SAS displayed showing the various steps of the install (think there were 20+ individual steps it detailed in the dialog), and I was able to see an error that I hadnât been aware of. Think it was with a prerequisite needed for the installâI either hadnât included it or had a wrong version.
Once I was consistently getting a succesfull install, I then added back in the parameters to make the install quiet, etc.
The command that eventually worked for me:
Execute-Process -Path â$InstallPath\setup.exeâ -Parameters â-wait -quiet -responsefile "$InstallPath\SAS_EG.propertiesâ -quietstatus -allselectable -defaultproductset -skiplocaleprompt -dotnetdetect" -IgnoreExitCodes â-1â
During testing, I didnât include the parameters â-quietâ or â-quietstatusâ so that I could see the progress dialog the install displayed, which eventually led me to being able to detect the thing that was broken (think it was a missing prerequisite or wrong version or some similar thing).
Once I was able to get a working install with all the install dialogs visible, I added those two parameters back in and then the package was production-ready.
May i know if anyone experienced before, the script work during testing, with exit code 0 but failed deployment in intune?
The size of the intunewim file closely to 10GB The status is error downloading content. Installation status in company portal is 100%. Seems the files in IMECache folder is not sync completely.
[Installation] :: Execution failed with exit code [-1].