search

Micke-K / IntuneManagement

Copy, export, import, delete, document and compare policies and profiles in Intune and Azure with PowerShell script and WPF UI. Import ADMX files and registry settings with ADMX ingestion. View and edit PowerShell script.
MIT License
1.07k stars 195 forks source link

No support for unicode encoding #195

Open timoukon opened 7 months ago

timoukon commented 7 months ago

I noticed that if my policy has for example Japanese characters in the name and description, Intune Management export doesn't handle it properly. When exporting the policy to Intune, Japanese characters will are not encoded.

If I use Powershell 7, then it works. However, there are other issues with Powershell 7.

7h59RvlaId
Micke-K commented 7 months ago

Hello!

I'll see if I can figure this out.

And it might be time to see if I can get this to work in PowerShell 7. It's been a while since I last tried.

Cheers!

timoukon commented 7 months ago

Thanks, that would be great! I also noticed this problem when I was trying to translate some of IntuneManager's menus in Japanese.

Micke-K commented 6 months ago

Hello,

I did a test where I named a policy with special characters and exported it.

That worked for me. Exported the policy to a file with special characters.

Not sure if my test is 100%. I copied some Chinese characters from a web page and pasted it in the Name field when creating a test policy. I also added them to the description field. All worked as expected.

Cheers!

timoukon commented 6 months ago

Now that I tested this again, it seems to be working fine. I am not sure what caused the issue last time. If I bump into this again, I will document the situation more precisely. I am working with Japanese and English systems so maybe the OS language might have affected this.