To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2024 (64 Bit)
Build: v5.8.244
OS: Windows 11.0.22631
PS Version(s): 5.1.22621.1, 7.4.2
*** Please add details and screenshots as needed below. ***
I'm working on a project to create remediation scripts for Intune-managed devices. Intune specifically requires any scripts to be encoded as UTF-8. UTF-8 BOM will cause failures. It's possible to set the encoding to UTF-8 in the editor, but on file save the selector changes to Windows-1252.
This appears to be cosmetic, as opening the file in another editor will display UTF-8; however, the potential for error is high.
DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2024 (64 Bit)
Build: v5.8.244
OS: Windows 11.0.22631
PS Version(s): 5.1.22621.1, 7.4.2
*** Please add details and screenshots as needed below. ***
I'm working on a project to create remediation scripts for Intune-managed devices. Intune specifically requires any scripts to be encoded as UTF-8. UTF-8 BOM will cause failures. It's possible to set the encoding to UTF-8 in the editor, but on file save the selector changes to Windows-1252.
This appears to be cosmetic, as opening the file in another editor will display UTF-8; however, the potential for error is high.
DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
Statistics: Posted by reged_robperry — Thu Jun 20, 2024 12:58 pm