With the release of the next OS from Apple, macOS 11 Big Sur, you may be tempted to upgrade right away and enjoy the newest features and sparkling new look of Apple’s newest OS. With all the new features, it’s tempting to hit that “Upgrade” button right away, but Grove Technologies is recommending that you wait until version 11.0.5 is released, which usually takes a few months. New versions of operating systems can be sluggish and buggy, they can slow down your Mac, and there are always compatibility issues with some apps. Waiting until version 11.05 allows Apple the time to work out the bugs and make sure Big Sur is mature enough for use in business and enterprise. Big Sur also has many “under the hood” changes that could have a big impact on your work.
If you are using an older Mac (older than 6 years) it may be best to skip the update to Big Sur and Catalina all together, or upgrade your hardware. Since Apple’s switch to the APFS File system in 10.14 many clients have been complaining about a sluggish HD or spinning ball when trying to complete menial tasks. This is because the APFS file system was not designed with spindle drives in mind. Spindle drives are the old-fashioned “moving parts” type of HD that, until recently, Apple allowed budget conscious users to install in their Macs. Unfortunately the new file system caused some major performance issues. If you opted for an SSD in your Mac, this issue will not affect you. Before upgrading to Big Sur from older OS’s, be sure to reach out to Grove Technologies about the possibility of upgrading an older spindle drive to an SSD.
Although it’s not a new feature for Big Sur, Apple’s 100% reliance on 64bit applications may have put your favorite app out to pasture. Be sure to check the build of your favorite application to make sure they are running in 64bit. Go to the Apple menu, choose About This Mac, then click the System Report… button. From the system report, scroll down to Software in the sidebar, then select Applications. When you select an individual application, you will see a field titled 64-bit on the right side.
Just in the opening days of the Big Sur release many users have complained about the stability of their system. Kernel Panics, spinning wheels, crashing. This can be avoided by not “upgrading” but doing a clean wipe and reinstall of the OS. Especially if upgrading from more than 2 versions behind. This does however mean a longer upgrade process. If you think you will need a fresh install of Big Sur instead of the upgrade, be sure to mention that during your support call with Grove Tech or ask your support Rep which is right for you.
Got mine bricked while doing a clean install. MBPr 13-inch mid-2014.
— Federick Bon Javier (@Bon_Javier) November 15, 2020
I tried to unplug the I/O board (as suggested in Reddit and Apple Support Community) and it booted fine and resumed installation. It was theorized that the install process somehow damaged the I/O board.
Lastly, users of 2013/2014 Macbook Pros have reported that in some cases the Big Sur update has bricked their Mac completely, making their Mac inaccessible. While other reports cite that some applications on BigSur are allowed to circumvent vpn connections a huge issue for those that rely on those for privacy protections. All efforts to boot into Recovery mode to wipe and reload are futile. The only option has been to take the Mac into the Apple Store. This seems like a worst case scenario, but with Big Sur being so new and untested, issues like this are sure to come to the forefront.
Some Apple apps bypass some network extensions and VPN Apps. Maps for example can directly access the internet bypassing any NEFilterDataProvider or NEAppProxyProviders you have running 😒
— Maxwell (@mxswd) October 19, 2020
Once you have checked all the boxes and you are ready for the upgrade, the main question is: Will my Mac support the upgrade? If you are currently running Catalina and your Mac is manufactured after 2013 its probably a YES. ANY MacPro (black cylinders) and any iMac Pro can upgrade, as well as Macbooks 2015 or later. Macbook Pro’s, Macbook Airs 2013 or later, iMacs and Mac Mini’s 2014 or later. Big Sur has the largest installation file so far with a whopping 12 Gigs! Make sure you have a minimum of 100G of HD space available prior to upgrading.
In Big Sur Apple decided to exempt many of its apps from being routed thru the frameworks they now require 3rd-party firewalls to use (LuLu, Little Snitch, etc.) 🧐
— patrick wardle (@patrickwardle) November 14, 2020
Q: Could this be (ab)used by malware to also bypass such firewalls? 🤔
A: Apparently yes, and trivially so 😬😱😭 pic.twitter.com/CCNcnGPFIB
Grove Technologies wants this upgrade to be as easy and painless as possible when you are READY. Please don’t hesitate to reach out to any of our Mac Experts for questions about how to proceed!
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.04 · Low AI Influence
Summary
Grove Technologies recommends waiting until macOS 11.0.5 is released before upgrading to Big Sur due to potential performance issues and compatibility problems.
Related Posts
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.
Introducing ABM Warranty for macOS
If you manage Apple devices at scale, you already know that **Apple Business Manager (ABM)** provides warranty data — but in practice, it’s extremely limited. It doesn’t provide workflow-friendly insights, it doesn’t surface actionable coverage states, and it doesn’t help you wrangle the ever-growing complexity of **AppleCare+ renewals** across hundreds or thousands of devices. This lack of comprehensive information can lead to missed renewal deadlines, unnecessary costs, and a higher risk of device downtime due to expired warranties.
