Micke-K / Micke-K/IntuneManagement
Endpoint Security policies export with different file encoding
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 2.1k
- Forks
- 377
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I pushed v3.7 of the OpenIntuneBaseline yesterday and then got some reports that two different files, ASR rules and BitLocker were failing to import again. I noted a long time ago that IntuneManagement was exporting files using UTF-16LE encoding, and I had to set my .gitattributes file accordingly.
The export I did yesterday seemed to export those two policy types using UTF-8 encoding, leading to them being mangled during upload: Example.
I re-exported them, re-saved the file using UTF-16LE encoding again and pushed a fix.
I was using your Development branch, not sure if that has any bearing on this?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the export from the Development branch for the ASR rules and BitLocker policy types, using the linked BitLocker JSON as the encoding example. Trace the export path and compare the generated files with UTF-16LE versions; done means both policy types import without mangling and use the expected encoding consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100