[LD42] Gut Reaction Mac OS

While newer versions of dd on Ubuntu or the like come with a new option called status=progress, the one included with macOS sadly does not.

A nice way I found to get progress indication whilst still being able to benefit from the huge speed increase in using /dev/rdiskX is to install a tool called pv, also known as Pipe Viewer.

Nov 20, 2020 Apple Diagnostics shows a progress bar while it's checking your Mac: When testing is complete, Apple Diagnostics shows the results, including one or more reference codes. Learn about Apple Diagnostics reference codes. To repeat the test, click “Run the test again” or press Command-R. To restart your Mac, click Restart or press R. VideoPad works on: 64-bit Windows OS, Mac OS X 10.5 or above, Android 2.3.3 or higher. Best way to learn: the help section on the official website is somewhat confusing, but you’ll be able to find clear step-by-step video instructions on NCH Software YouTube channel.

Now, split up your dd command into two, and pipe everything through pv. If you know the size of the input drive, provide that to pv as-well as it will further improve the output. Take this example, where my input drive is 64GB:

This will result in a familiar looking progress indicator, as-well as an ETA and transfer speeds.

This method also works very well when zeroing out drives, something I had to do quite a lot recently as I was preparing to sell off some older drives. Using the following command for a 500GB drive, for example, worked great:

It's quite useful to finally have some insight into how far along a task like this is, as it's usually quite a time consuming one.

Another way to achieve something similar would be to use brew to install coreutils, which will come with a newer version of dd that supports the status option.

All tools installed with this package are named with g prefixed to them, so you can run gdd to use this packages' version of dd.

Sadly, this version of dd lacks support for macOS' 'raw' disk support (/dev/rdiskX), which means it will be significantly slower to copy a disk over, but there might be certain scenarios where this method is preferred.

I hope this helps!

Thanks.

From what we know about macOS® Big Sur, the upcoming update will have significant implications for IT administrators. The information and OS betas Apple® has already shared mean it’s something that IT teams will need to plan and be prepared for.

First on many admins’ minds: Should they wait to deploy Big Sur? As with all big software updates, we can reasonably expect initial bugs and user experience issues that Apple will need to work out after the first general release.

The decision to deploy on day one or delay the update will ultimately come down to your organization’s needs. But you’re not alone. In fact, Tom Bridge (MacAdmins Podcast Host and Founding Partner at Technolutionary) and Bradley Chambers (9to5Mac Writer and IT Director) recently sat down together to provide expert advice in a recent JumpCloud® recent webinar.

If you missed it, feel free to check out the full recording, or keep reading to learn exactly what you need to know about deploying (or delaying) the Big Sur update.

Need-to-Know Facts about Big Sur

Apple has yet to inform the public the exact day that macOS Big Sur will be released, but they have shared some information about what admins and users can expect. Here’s a high-level overview (with more takeaways here):

Catalina
  • Tom notes that users will notice Big Sur’s “huge visual difference,” such as new icons and a floating bar dock.
  • Both IT admins and end users will have unique changes to adjust to, as Bradley suggests. The user experience will be changing as well as IT-specific concerns, like the new Apple MDM criteria.
  • As with all major OS updates, Big Sur may not be in its final state when it’s initially released. Expect updates to be made after it becomes generally available.

How to Roll out Big Sur

Gut Reaction Darien

The two main options for how IT admins can handle Big Sur are:

  1. Deploy immediately
  2. Delay for testing and bug fixes

Ld42 Gut Reaction Mac Os Download

You might have a gut reaction on which is better, but just based on Tom and Bradley, we know that the IT community is split on this decision. Let’s walk through both perspectives.

Why deploy immediately?

Tom is in favor of immediate deployment for the sake of security for his organization. As he says, “The most secure operating system is the one that Apple releases on day one.”

Why wait to deploy?

Bradley plans to delay updating for three weeks to allow for Apple bug fixes and a better end user experience.His reasoning: “If you do deploy, there are things that could break that aren’t your fault but will be your problem.”

Additionally, while Tom plans to deploy immediately at his organization, he doesn’t think that’s the right course for everyone. He has clients that he expects will need up to 90 days to test Big Sur before deploying across the organization.

How to Decide What’s Right for Your Organization

Admins should only deploy Big Sur when both IT and end users feel ready. Identify the things inside your organization that are “mission critical.” Tom mentions examples like: “Do you have a VPN that’s driven by a kernel extension? Do you have security software driven by a kernel extension?”

Gut

Know your deal breakers and start testing as soon as you can to identify if waiting to deploy is safest. If your end users are able (and willing) to embrace the quirks that might be encountered early on with macOS Big Sur, deploying immediately might be the safest option for your organization.

How to Block Big Sur Upgrades

Should you decide that your organization isn’t ready for immediate deployment of Big Sur, JumpCloud admins can block end users with standard or administrative permissions from upgrading to macOS Big Sur using JumpCloud’s Block macOS Big Sur Policy.

This Policy enables admins to restrict the macOS Big Sur installations, including beta versions. From an user experience standpoint, end users cannot complete launching the installer and do not receive a block message.

Next Steps

Want to learn more about how to manage macOS Big Sur? Check out the latest MDM-centric Office Hours recording where product lead Scott Reed goes into depth on MDM, the software that Big Sur requires, and cross-OS device management with JumpCloud’s directory platform.

If you’re ready to try out the Block Big Sur Policy or MDM, sign up for a JumpCloud Free account. You can add 10 users and 10 devices at no cost — we won’t even ask for a credit card while you evaluate the platform.