Thank you for the efforts - all of you. Much appreciated.
lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS.
Uuuuuhhhhhhhh...
IPP is the future (I think)
https://www.cups.org/blog/2018-06-06-demystifying-cups-development.html
Yeah, as a K-12 whose users still print a ton, that is disconcerting to read. Although, this might provide the excuse we need to cut done on printing overall!
This is incredibly helpful. Thank you for taking on this task for an all in one spot, huge help! Making my catalina bookmark folder much less crowded.
@ClassicII tha k you so much for arranging this. it is really beneficial
We will get through this together guys!
Thanks guys, hopefully the article saves you time! I still can't believe how many changes are in 10.15, I am not even sure where to start! So many how-to articles need to be written. :)
I saw a screenshot showing that the User Template folder is now in Library, not /System/Library/ like it used to be. Which makes sense since /System is totally write protected now.
Kernel Extensions (Kexts) now require a reboot to load – Installing third party kernel extensions now requires that you restart your Mac before they’re permitted to load.
Oh cool, users love forced reboots.
Look at the bright side (I know, LOL), we now have to so it's not up to us, clients or the "boss"...
Will cure the "we never reboot" crowd I s'pose.
I didn't see any mention of Catlina nuking 32bit apps, that buried in there somewhere?
@kevin.v
Yes. Per the 10.15 release notes (available on the public site without login):
"Deprecations
macOS frameworks are now thinned for the x86-64 architecture. Apps that execute i386 code now fail with the EBADARCH error code. The remaining stub frameworks are nonfunctional and exist only for compatibility purposes. (51236070)"
So question?
With Catalina does this mean that we have to change all our scripts shebangs from
#!/bin/sh
to
#!/bin/zsh
For them to work properly?
I know it's a silly question but I am very new to JAMF and the only sole Admin at my location been working day and nice trying to get something working just right for our current user base and now am beginning to feel that it was all in vain. Will all the scripts written be broken?
@CorpIT_eB Not at present, all of your bash scripts will still work, it's just the default shell is being changed to zshell. At some point in the future they may remove bash support though, at which point yes, your existing scripts will all have to be updated and tested.
@allanp81 thank you, for the reply.
Catalina has me a bit worried about all the hard work I have done here since getting JAMF for the Org.
@CorpIT_eB As @allanp81 indicates, your existing scripts don't require re-working yet. As with any major update to macOS, you're going to find it necessary to adapt things to Catalina. What you've learned so far will (mostly) still be applicable. And unless you're suddenly blessed with only needing to support one version of macOS that knowledge will be required for at least some part of your installed base.
@sdagley Yes, we went JAMF Pro about six months ago, being a 100% Windows System Administrator all my life took on this challenge with 0 Knowledge in #!/bin/sh scripting. Thought I knew my Mac environments and for the last couple of months have been banging my head on my desk. If it wasn't for all of you guys here on JAMF Nation I don't know where I would be.
I finally have a decent, Enrollment processes and because of some poorly made decisions on my end for our mac users have had to physically (manual process) migrate all our machines in our environment from HS to Mojave.
I picked up a book on scripting with bash in hopes I can start to learn but man what a difference this is compared to PowerShell and having to try and understand .plists has been rough.
Now Catalina is dropping and I am like.....GREAAAAAT! lol.
To @CorpIT_eB (and anyone else concerned) I have already switched my default shell to zsh on my Mac after seeing the news and am running it daily in Terminal. So far I can't say I really see the difference, but of course that's not accounting for some of my mammoth scripts with thousands of lines of code in them. I will at some point start testing those as zsh scripts to see if they fail anywhere. My guess is they may only need some minor reworking. I would not be terribly concerned about. Initially I kind of freaked out at the news, but after diving into the Z Shell a bit, I think most of us will make the switch without too much difficulty.
At least that's my hope :)
@CorpIT_eB You'll find a lot of script examples on Jamf Nation. If you can arrange it, the Jamf Pro certification courses Jamf offers are well worth it. There's a new site with a collection of links to Mac Admin related resources you might also find useful: Mac Admin Info
I think every admin that has zero-touch setup and FileVault should be worried!
I think FileVault is going to require user approval to enable. There are some Rich Trouton WWDC notes in the developer forum and this WWDC video @ 29:26.
https://developer.apple.com/videos/play/wwdc2019/303
C
@gachowski fdesetup is being deprecated in Catalina, at least the part where you pass it usernames and passwords. I have a feeling it'll only be able to be managed with config profiles going forward.
@wmehilos
The profile uses fdesetup so I don't think it's deprecated.
Because of the Apple NDA... I am not sure we can talk about the details of the full security changes in Catalina the effect FV and zero-touch.
C
Regarding fdesetup and using username/password, it sure seems like this is deprecated and not blocked as @gachowski referred to in https://developer.apple.com/videos/play/wwdc2019/303
I would be careful with this as it's still possible for this rule to be enabled during future betas.
I also added 2 great articles by ScriptingOSX's Armin Briegel to the Link List.
One talks about imaging and the other talks about the move to zsh.
http://scriptingosx.com/2019/06/moving-to-zsh/
https://scriptingosx.com/2019/06/imaging-is-still-dead/
For folks worried about moving from bash, as has been stated it’s still available for now. The sh shell isn’t going anywhere either. Take the next year to work on converting your scripts. I’ll be using http://shellcheck.net/ by pasting in my old script, change the shebang to !#/bin/sh or !#/bin/zsh and see what changes it says I need to make. Then test, test, test...
