<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>XML on Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/xml/</link>
    <description>Recent content in XML on Robert Terakedis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2020 Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Tue, 09 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.terakedis.dev/tags/xml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Converting Jamf Custom Schema JSON for Workspace ONE UEM</title>
      <link>https://blog.terakedis.dev/post/converting-jamf-custom-schema-json-workspace-one-uem/</link>
      <pubDate>Tue, 09 Mar 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/converting-jamf-custom-schema-json-workspace-one-uem/</guid>
      <description>
        
          
            &lt;p&gt;Periodically, I see app vendors providing custom JSON schema files to help build app-specific configuration profiles for MDM (specifically Jamf).  Workspace ONE UEM supports app-specific configuration, but currently via &lt;a href=&#34;https://github.com/vmware-samples/euc-samples/blob/master/macOS-Samples/CustomXMLProfiles/CustomXMLTemplate.md&#34;&gt;Custom Settings in an XML format&lt;/a&gt;.  While many vendors also suppply a custom mobileconfig file or Custom Settings dictionary that can be used with Workspace ONE UEM, I hope in this post to show how any Workspace ONE admin can manually convert a Custom Schema JSON file to Custom Settings XML.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>