![]() This can be quite important for text blocks featuring symbols - like XML. ![]() $obj.Configuration = will try and identify any variables inside of a double-quotes block and swap out the variable name for the localised value, whereas using the single quote preserves the exact format of the text (i.e. This first change is just a tip - it won't change your current XML at all: use the single-quote text block style rather than the double-quote form. But for now, we can rule out the PowerShell side entirely and just look a the XML. I keep saying this as I feel like I'm the blind leading the blind here, but I really know nothing about this MDM stuff - it's way outside my areas of expertise. $obj.Configuration = -CimInstance That really helps us narrow our focus onto the XML. | Cannot bind argument to parameter 'InputObject' because it is null.Ĭan you guys help me with Lain, I understand unfortunately I got another error, I double checked the script on synthax errors, and wrote exactly as in the example stated on this page ( ) Set-CimInstance: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:44:30 Verify that the property exists and can be set. | The property 'Configuration' cannot be found on this object. InvalidOperation: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:5:1ĥ | $obj.Configuration = ::HtmlEncode Get-CimInstance: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:3:8ģ | $obj = Get-CimInstance -Namespace $namespaceName -ClassName $classNam … $obj = Get-CimInstance -Namespace $namespaceName -ClassName $className ![]() To run the stated powershell script with my own configured XML file, as you can see here: So currently as this article states, kiosk multi app mode in Intune for windows 11 is on the roadmap, but there is no ETA, when it comes live.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |