<?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 Matt Thornton</title>
    <link>https://matt-thornton.net/tags/macos/</link>
    <description>Recent content in Macos on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 05 Dec 2020 20:15:59 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMWare Fusion / Big Sur / Ubuntu / Black screen</title>
      <link>https://matt-thornton.net/tech/vmware-fusion-big-sur-ubuntu-black-screen/</link>
      <pubDate>Sat, 05 Dec 2020 20:15:59 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/vmware-fusion-big-sur-ubuntu-black-screen/</guid>
      
        <description>&lt;p&gt;Recently updated to macOS Big Sur. I&amp;rsquo;m not sure why I do this sort of thing quite so freely&amp;hellip; I always naively assume everything will be OK. And so far, Big Sur vs Catalina is just a bit nightmare.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m sure there&amp;rsquo;s a huge amount of “don&amp;rsquo;t like change” in there but there are many things that are annoying the crap out of me with Big Sur. Calendar notifications for one. Gah.&lt;/p&gt;
&lt;p&gt;But anyway, one real issue I have had was with VMware Fusion. I was previously on v11.something and when trying to launch a VM got greeted with “Host OS does not have enough physical memory to launch this VM” which was a complete load of bollocks. After a quick Google, it was evident it was a VMware incompatibility issue - Fusion 11 will not run on Big Sur and you must upgrade to VMWare 12. Yay. $100 later and I have Fusion 12 and&amp;hellip; things are still broken. Main issue is that trying to start a VM results in a bunch of error messages&amp;hellip; these seem to get resolved by changing the compatibility level of the VM&amp;hellip;. but even then, starting the VM ends up in a black screen.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Eugh. Configuring Powershell for remote Exchange management</title>
      <link>https://matt-thornton.net/tech/powershell-tech/eugh-configuring-powershell-for-remote-exchange-management/</link>
      <pubDate>Tue, 19 May 2020 10:03:37 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/powershell-tech/eugh-configuring-powershell-for-remote-exchange-management/</guid>
      
        <description>&lt;p&gt;I use a mixture of Mac and Linux for most of my needs. I&amp;rsquo;ve run Windows virtual machines of same flavour or another but since .NET core 3 landed I&amp;rsquo;ve barely had to do even fire it up. There&amp;rsquo;s nowadays very little you can&amp;rsquo;t do in a non-Windows environment.&lt;/p&gt;
&lt;p&gt;That doesn&amp;rsquo;t really extend (yet?) to remote administration of your Office365 tenant using Powershell.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m trying to configure some DNS bits for one of our domains that needs the &lt;a href=&#34;https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2?view=exchange-ps#install-and-maintain-the-exchange-online-powershell-v2-module&#34;&gt;Exchange Online V2 Powershell&lt;/a&gt; module. Come with me as I disappear down a rabbit hole of getting this working.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Migrate VMWare Fusion virtual machines to VMWare ESXi</title>
      <link>https://matt-thornton.net/tech/vmware/migrate-vmware-fusion-virtual-machines-to-vmware-esxi/</link>
      <pubDate>Tue, 27 Nov 2018 12:21:23 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/vmware/migrate-vmware-fusion-virtual-machines-to-vmware-esxi/</guid>
      
        <description>&lt;p&gt;Way back in 2012, &lt;a href=&#34;https://matt-thornton.net/tech/my-vmware-esxi-5-1-build-part-1-the-hardware&#34;&gt;I dabbled with ESXi&lt;/a&gt;. In fact, I faced then, moreorless the same problem I was facing a few days ago.&lt;/p&gt;
&lt;p&gt;That particular ESXi server didn&amp;rsquo;t last particularly long - no technical issues, it just didn&amp;rsquo;t turn out to be the thing I wanted.&lt;/p&gt;
&lt;p&gt;Fast forward 6 years, and I found myself in a new situation where having an ESXi host would be useful. We use Azure a lot nowadays, but there are still some scenarios where we&amp;rsquo;d like some on-premise kit such as developing against Sharepoint. (Although in fairness, I&amp;rsquo;m not sure anyone really ever *wants* to do that.) I digress.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>