This week marks my fourth week at Amazon Care. I am on an incredibly great team of Systems Engineers. I try to keep my enthusiasm measured when around them but it’s so nice not being a one person show.
I’ve also found most of the onboarding training to be deeply thoughtful and not as “canned” as I’m used to. Might be the new job feel but I can’t help but feeling this was the right move.
I am happy to report I will be starting a new role on a team at Amazon Care. Years of keeping my head down, working hard, and taking every Udemy class imaginable with hopes of progressing my career has paid off.
If you’ve ever tried using Time Machine with a NAS pre-APFS days you’ll know the experience left a lot to be desired. I was encouraged by a colleague to give this another shot and am happy to report a huge improvement in speed and performance.
The initial backup of my machine, which was roughly 80GB of data took about 70 minutes to complete. I am also happy to report that Time Machine remembers the location of the NAS and will auto-mount it as needed.
If you’re using an UnRAID NAS, you will find this guide helpful:
Yesterday a friend shared an interesting story. They decided to take advantage of Apple’s zero percent financing option for a new MacBook. To their dismay, having an Apple Card that was half utilized caused (in their opinion) a THIRTY point drop in their credit score.
Upon trying to pay it off entirely he informed me that there was no way to do so. While there is a “Make Additional Payment” option, it only allows you to pay off a finite amount, which seemed really strange.
It turns out there isn’t a way to do this through the Wallet app, but if you use the online portal (https://card.apple.com) you can pay off as much as you’d like.
If you have the pleasure of binding your macOS fleet to Active Directory some of you may have noticed issues using the sudo command for administrative users.
Chatter on the MacAdmins slack channel suggests that Apple has acknowledged the issue and will resolve it in a future update. Here’s how we’re temporarily working around this:
# Collects the logged in user
loggedInUser="$(stat -f%Su /dev/console)"
# Checks to ensure logged in user isn't already in sudoers
if grep -Rq "$loggedInUser" /etc/sudoers
echo "User ID already exists in sudoers file...Exiting"
echo "$loggedInUser ALL = (ALL) ALL" >> /etc/sudoers
iCloud Keychain got a nice update with iOS15 that enables you use it as your MFA provider. Not only does it make the likes of Google Authenticator/Authy unnecessary, it also makes for a much more seamless experience for the end user in Safari. If you have MFA enable for a service (Gmail, Reddit, etc.) you will first need to disable it. Next, locate the entry for that service in iCloud Keychain and select Setup Verification Code.
I ran into an interesting issue attempting to purchase AppleCare for a set of headphones I picked up at Best Buy. I was within the sixty day window but when I tried making the purchase online I was presented an ominous message:
“It looks like your device isn’t eligible for an AppleCare agreement.”
The AppleCare rep was stumped. After a bit of googling I discovered the headphones didn’t have a purchase date associated with them—presumably because they came from a third party retailer.
The fix is to visit https://checkcoverage.apple.com, enter your details, and you’ll more than likely be prompted to provide a purchase date. I was then able to complete my purchase.