I’ve used PSADT for a short while now, and have had no issues with it, everything working as intended - I’ve changed the template I build from to log directly to the intunemanagementextension\logs folder, and all has been well.
Now the last week to 10 days, all my new deployments have broken, I’m not getting any logging, and for the most part the script execution completely fails.
Just for testing purpose I downloaded it anew, version 3.10.2, changed the log location and simply had the script create a new file in C:\temp, and logging that.
The logging didn’t work, and neither did the file creation.
I thought it might be related to Win11 24H2, so I’ve tried on 22H2 and 23H2 as well, to no avail.
Apps that was created just 2 weeks ago work fine, on the same devices even.
I’ve tried multiple devices, multiple users, multiple tenants and multiple manufacturers of the devices
Other applications that I create outside of PSADT does work, and even the detection & requirement scripts I’ve tested on the PSADT apps works, even if the PSADT app it self doesn’t
Anyone experiencing something similar, or got any ideas?
I’ve done testing on 6 different networks, including a hotspot, 4 different tenants, 3 different manufacturers/devices.
The networks have been a mix of different corporate networks, my private network as well as a hotspot.
None of these have had any issues until about 10 days ago.
Apps packaged and deployed outside of PSADT works with no issue.
I’m not sure where to even look, as even re-deploying applications that is deployed and working, doesn’t work either! (So reuploading the intunewin file)
It seems like you are having a PowerShell or permission issue. If you think PSADT is the problem, prove it by writing a small PowerShell script that only creates a file in the PSADT log location. Then add more code to make it create another file in C:\temp
I suspect this small script will fall. either way, this will help you focus your efforts. Divide and conquer.
I’ve fallen back to simply packaging my own poweshell scripts directly with transcripting to the same mog location (intuneextensionmanagement\logs\app.log), with no issue.
When I deploy the PSADT package it never even creates any log file.
I can see it in the agentexecutor with an error code of 1, but nothing about what/where it broke
I’ve made sure to test for permissions, and that works with no issue.
I’m able to log, and to modify the system and/or install apps, as long as it’s not through PSADT
I hoped it was due to an issue with 24h2, but that’s not it either
Forget Intune - just run the app install locally and see what happens. If that doesn’t work there’s something drastic wrong. If it does, then the finger of blame moves to the Intunewin file or Intune. You’ve inferred you’re using Intune and not MECM.
Add powershell lines that output text to the console and/or a log file without using the PSADT function. Just use set-content.
To test, use a PowerShell console and dot source the main function: e.g. . .\AppDeployToolkit\AppDeployMain.ps1.
This will let you use the functions direct - so you can run Write-log from the console. Use it with the log path changed and without. I suspect it is a path issue, but that’s just a wild guess.
Thanks for the suggestions, I’ve tried to use on of the example apps (VLC), and running it locally worked fine, I got logging, and the app was installed.
I then tried to deploy the app via Intune once again, as I had it working locally.
It then failed again, no loggin, no installation, only 1 log via the agentexecutor: Poweshell script ran successfully
It seems to be an issue with the combination of PSADT and Intune, though I have no idea where to even start looking for this issue
-Make sure the PS1 files are UTF8 encoded
-Recreate the Win32app in Intune.
-Make sure it doesn’t check if the PS1 files are signed.
-Make sure the files actually make it to the Intune Cache on the targeted PC
