Closed MarcoBuess closed 1 week ago
Thank you for the comment :). I will reconsider it... My design decision was not to tamper in folders that do not belong to other applications (In my opinion this is bad style since you create dependencies that can lead to issues out of my control). The Logfiles under c:\Windows\temp can also be collected through the Collect Logs feature (I made sure to select a folder and naming pattern that is on the list of folders that is supported for collection of logs). But I can fully understand and will rethink it since most other applications also decided to use the IME folder aswell and it is far easier to access on the local machine.
Thanks for the quick response. I do understand what you mean and I think you can now specify which folder you want to collect from within intune. Using the IME is kinda common practice though and you could always fall back to %windir%\temp
if the directory doesn't exist. If you need me to file a PR for that I'll gladly look at the code.
Give me a moment :)... I just want to rethink this in all directions... maybe adding an additional log location as a parameter to the ADMX/ADML.
Would make sense. Also log location seems to be kinda hard coded in these locations:
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
The request
It would be nice if you'd consider putting the log files to the IMEs (Intune Management Extension) log location if applicable (like Romanitho suggests). Problem is, that
C:\Windows\Temp
can not be accessed easily remotely on Entra joined devices. Therefore if a user doesn't have local admin permission (which most shouldn't) there is no way you can get access to the logs. You can collect them remotely through Intune, which will collect everything underC:\ProgramData\Microsoft\IntuneManagementExtension\Logs
.Is your feature request related to a problem?
No response
Additional information
No response