<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MacOS on Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/macos/</link>
    <description>Recent content in MacOS on Robert Terakedis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2020 Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Fri, 25 Nov 2022 15:40:35 -0500</lastBuildDate><atom:link href="https://blog.terakedis.dev/tags/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apple&#39;s Missing Hardware - A KVM Switch</title>
      <link>https://blog.terakedis.dev/post/apples-missing-hardware-kvm-switch/</link>
      <pubDate>Fri, 25 Nov 2022 15:40:35 -0500</pubDate>
      
      <guid>https://blog.terakedis.dev/post/apples-missing-hardware-kvm-switch/</guid>
      <description>
        
          
            &lt;p&gt;Let me start by saying that I&#39;m assuming many of you out there are in a situation quite similar to my own.  This situation; having a personal Mac &lt;em&gt;and&lt;/em&gt; a work Mac (and maybe an iPad Pro thrown into that mix also). But if you&#39;re also like me, you have limited space on your desk and don&#39;t want to be surrounded by monitors!  This leads me to my most potent complaint about Apple hardware; the lack of a KVM switch.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Mapping Concepts from Munki to WS1 UEM</title>
      <link>https://blog.terakedis.dev/post/mapping-concepts-from-munki-to-workspace-one-uem/</link>
      <pubDate>Mon, 23 Aug 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/mapping-concepts-from-munki-to-workspace-one-uem/</guid>
      <description>
        
          
            &lt;p&gt;Since Workspace ONE UEM version 9.3, VMware has included the open-source &lt;a href=&#34;https://github.com/munki/munki&#34;&gt;munki&lt;/a&gt; binaries in the Workspace ONE Intelligent Hub for macOS.  The intent of this integration was to give macOS admins the ability to distribute 3rd-party non-store macOS apps, without the need to host any backing instrastructure for munki.  Because this integration was meant to give admins some of the commonly used functionality, it was not integrated in such a way to include support for ALL munki&#39;s functionality.   This has left some confusion in the community, particularly with Workspace ONE UEM administrators with extensive munki knowledge/background.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Best Practices for Apple Admins in Workspace ONE UEM</title>
      <link>https://blog.terakedis.dev/post/best-practices-for-apple-admins-in-workspace-one-uem/</link>
      <pubDate>Thu, 15 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/best-practices-for-apple-admins-in-workspace-one-uem/</guid>
      <description>
        
          
            &lt;p&gt;I was recently reading a post about &lt;a href=&#34;https://macostechs.com/2021/05/what-to-do-when-you-have-to-lay-off-your-jamf-administrator/&#34;&gt;What to do when you have to lay off your Jamf administrator&lt;/a&gt;, and it got me thinking.  The &lt;a href=&#34;https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/2102/UEM_Recommended_Architecture/GUID-AWT-RECARCH-INTRO.html&#34;&gt;Workspace ONE UEM documentation&lt;/a&gt; generally specifies what you &lt;strong&gt;need&lt;/strong&gt; from a software and hardware perspective in pre-requisites.  That said, over the years I&#39;ve come to know a few unwritten (or written but obscure) best practices for setting up Workspace ONE UEM to manage Apple devices.  Hopefully you find this post helpful, but I welcome any comments and feedback!&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <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>
    
    <item>
      <title>Troubleshooting macOS Management with Workspace ONE</title>
      <link>https://blog.terakedis.dev/post/troubleshooting-macos-management-with-workspace-one/</link>
      <pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/troubleshooting-macos-management-with-workspace-one/</guid>
      <description>
        
          
            &lt;p&gt;Short post today - just to cover some thoughts on my most recent asset published to &lt;a href=&#34;https://techzone.vmware.com&#34;&gt;TechZone&lt;/a&gt;.   I finally sat down and dug out all my notes on troubleshooting macOS and put them all together into a single, comprehensive &lt;a href=&#34;https://techzone.vmware.com/troubleshooting-macos-management-vmware-workspace-one-operational-tutorial&#34;&gt;macOS Troubleshooting Guide&lt;/a&gt;.  This thing was the result of almost 46 hours of fingers on keys: typing, formatting, and testing.  I truly hope you all get some value out of it, and do feel free to send me feedback if you&#39;d like it extended and/or notice something missing.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Updated GitHub Actions to Publish Hugo Site From Private to Public Repo</title>
      <link>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</link>
      <pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</guid>
      <description>
        
          
            &lt;p&gt;When I restarted my blogging journey last year, I went with Hugo to generate a static website hosted as a GitHub Pages site.  As mentioned, Blogger and WordPress always suffered recurring problems, and maintenance with WordPress still turned into a time suck due to its complexity.  By comparison, GitHub has been a nearly painless hosting provider, and the way I&#39;ve configured it has allowed me to keep drafts hidden by staging in a private repository.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Deploying NoMAD over VMware Per-App Tunnel</title>
      <link>https://blog.terakedis.dev/post/deploying-nomad-over-vmware-per-app-tunnel/</link>
      <pubDate>Fri, 16 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/deploying-nomad-over-vmware-per-app-tunnel/</guid>
      <description>
        
          
            &lt;p&gt;Some folks recently reached out to me asking for help figuring out how to route &lt;a href=&#34;https://nomad.menu/support/&#34;&gt;NoMAD&lt;/a&gt; traffic over VMware Tunnel.   Basically, the ask was to use Per-App Tunneling to give NoMAD the ability to obtain Kerberos Tickets and Sync AD passwords without being directly on the Enterprise network.  If you&#39;re familiar with my previous article about the &lt;a href=&#34;https://blog.terakedis.dev/post/macos-catalina-kerberos-sso-over-vpn-followup/&#34;&gt;macOS Catalina Kerberos SSO Plugin&lt;/a&gt;, you&#39;ll know that Apple&#39;s built-in functionality in Catalina doesn&#39;t work well with Per-App Tunneling.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Modify ZShell Defaults in macOS</title>
      <link>https://blog.terakedis.dev/post/modify-zshell-defaults/</link>
      <pubDate>Mon, 21 Sep 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/modify-zshell-defaults/</guid>
      <description>
        
          
            &lt;p&gt;I&#39;m finding myself using the Terminal quite a bit more in my job. I spent a few minutes over the past few days looking at different ways to make the default terminal layout in macOS better.  While there are many plugins out there for doing this (&lt;a href=&#34;https://github.com/ohmyzsh/ohmyzsh&#34;&gt;Oh-My-Zsh&lt;/a&gt;), I wanted to do something a little more straightforward.&lt;/p&gt;
&lt;h2 id=&#34;how-you-change-zsh-default-layouts&#34;&gt;How You Change zsh Default Layouts&lt;/h2&gt;
&lt;p&gt;Armin Briegel has a great article about customizing the zsh prompt in his &lt;a href=&#34;https://scriptingosx.com/2019/06/moving-to-zsh/&#34;&gt;moving to zsh&lt;/a&gt; series.  The basics come down to the following - make some changes to the file at &lt;code&gt;~/.zshrc&lt;/code&gt; and then enjoy the fruits of your labor!  This file is also where you can add zsh functions (e.g. reusable pieces of code.)&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>macOS Big Sur and Kerberos SSO via Per-App Tunnel</title>
      <link>https://blog.terakedis.dev/post/macos-bigsur-kerberos-sso-over-vpn/</link>
      <pubDate>Fri, 14 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/macos-bigsur-kerberos-sso-over-vpn/</guid>
      <description>
        
          
            &lt;p&gt;If you&#39;ve read my blogs about &lt;a href=&#34;https://blog.terakedis.dev/2020-02-04-macOS-Catalina-Kerberos-SSO-Over-VPN/&#34;&gt;macOS Catalina Kerberos SSO over Per-App Tunnel&lt;/a&gt; and the &lt;a href=&#34;https://blog.terakedis.dev/post/macos-catalina-kerberos-sso-over-vpn-followup/&#34;&gt;followup&lt;/a&gt;, you&#39;ll know that this has been a use-case I&#39;m interested in solving.  I put a great deal of effort into filing feedback with Apple and providing steps to replicate the issue.  I was quite excited when I saw the per-app Tunnel improvements specifically mentioned in the WWDC videos, and hoped perhaps some changes were made to enable this functionality.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>macOS Catalina Kerberos SSO over VPN Followup</title>
      <link>https://blog.terakedis.dev/post/macos-catalina-kerberos-sso-over-vpn-followup/</link>
      <pubDate>Sun, 22 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/macos-catalina-kerberos-sso-over-vpn-followup/</guid>
      <description>
        
          
            &lt;p&gt;I&#39;ve been going back and forth with Apple about some of the issues I previously found using the &lt;a href=&#34;https://blog.terakedis.dev/2020-02-04-macOS-Catalina-Kerberos-SSO-Over-VPN/&#34;&gt;macOS Catalina Kerberos SSO over Per-App VPN&lt;/a&gt;.  As it turns out, they acknowledged some of the issues I was seeing and are &lt;em&gt;supposedly&lt;/em&gt; working on a fix.  I&#39;ve been watching the past few beta releases for macOS, and I&#39;ve not yet seen anything in the release notes to indicate they&#39;ve implemented any fixes.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>New Key Added to SoftwareUpdate Command in macOS</title>
      <link>https://blog.terakedis.dev/post/new-key-added-softwareupdate-command-macos/</link>
      <pubDate>Thu, 19 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/new-key-added-softwareupdate-command-macos/</guid>
      <description>
        
          
            &lt;p&gt;When Big Sur released, I noticed an issue trying to discover what macOS versions were available in SoftwareUpdate.   I worked around this by using the &lt;a href=&#34;https://github.com/munki/macadmin-scripts/blob/main/installinstallmacos.py&#34;&gt;installinstallmacos.py script&lt;/a&gt; to download full installers from the store.  This script/tool is solid, but I was really hoping to be able to just do the updates using softwareupdate.  Awhile back I filed feedback with Apple to the following:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The --fetch-full-installer parameter for the softwareupdate command line tool is awesome, but there&#39;s currently no way to discover the list of available values for the --full-installer-version parameter.   Can you please add a --list-installer-versions parameter (or something to that effect) that would show the list of available full installer versions that softwareupdate can download?   My understanding is the installer versions relate to the product marketing version (like 11.0, or 10.15.7), but as those versions are added/removed it would be nice easily discover that from the command line.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Deploying Microsoft Defender ATP for macOS using Workspace ONE UEM</title>
      <link>https://blog.terakedis.dev/2020-02-18-Deploying-Microsoft-ATP-Defender-for-Mac-using-Workspace-One/</link>
      <pubDate>Tue, 18 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/2020-02-18-Deploying-Microsoft-ATP-Defender-for-Mac-using-Workspace-One/</guid>
      <description>
        
          
            &lt;p&gt;I had a few folks recently approach me on the MacAdmins slack asking for help with deploying Microsoft Defender ATP for Mac.   We got it working, but it came down to 2 issues:  conflicting documentation and Jamf/inTune specific templates.  Once I was able to parse through the Jamf/InTune documentation, we were able to put together some guidance.  We recently published this guide to the &lt;a href=&#34;https://github.com/vmware-samples/euc-samples/tree/master/macOS-Samples/3rd-Party_Software_Guidance/Microsoft-Defender-ATP&#34;&gt;EUC Samples GitHub Repository&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;conflicting-documentation&#34;&gt;Conflicting Documentation&lt;/h2&gt;
&lt;p&gt;The initial problem I found was some confusion generated by Microsoft&#39;s documentation.  The first article, &lt;a href=&#34;https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/mac-preferences&#34;&gt;Set Preferences for Microsoft Defender ATP&lt;/a&gt; referenced a payloadType of &lt;code&gt;com.microsoft.wdav&lt;/code&gt;.   These preferences seem related to the UI and various configuration settings.  In other words, it controls what changes can be made in the UI if opened by the end-user.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Testing macOS Catalina Kerberos SSO Extension Over VPN</title>
      <link>https://blog.terakedis.dev/2020-02-04-macOS-Catalina-Kerberos-SSO-Over-VPN/</link>
      <pubDate>Tue, 04 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/2020-02-04-macOS-Catalina-Kerberos-SSO-Over-VPN/</guid>
      <description>
        
          
            &lt;p&gt;Working at VMware, I&#39;m surrounded by great technology and super-smart folks!  In our portfolio of technologies, the folks in our R&amp;amp;D have recently been putting quite a bit of effort into building out macOS capabilities for our Workspace ONE Tunnel client for macOS.  Workspace ONE admins can leverage the same VMware technology they used to enable per-app VPN for iOS and Android, but now on macOS!  There&#39;s a bit of nuance to configuring the VPN client if you&#39;re previously familiar with iOS (look for my Operational Tutorial soon to hit &lt;a href=&#34;https://techzone.vmware.com&#34;&gt;TechZone&lt;/a&gt;).  That said, the premise is the same -- by configuring the appropriate rules, the Tunnel app redirects traffic from whitelisted applications back into your network through the Unified Access Gateway.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>