##osx-server

You could still `defaults read com.apple.mail`

boot air already

And look for the LogFoo keys

fish balloon next

so we actually get to check before the update as well

apparently haven't turned it on since

macmule: really wish every time I went to add something to AutoCasperNBI, it remembered the last folder I was in, rather than my user folder.

3 accounts configured but not enabled there defaults read com.apple.mail | grep -c -i log == 0

evening peoples

hey bruienne

hey bruienne

heya macgirl84 dknuth

hiya bruienne

my brain is mush from these god awful meetings today

enabled gmail imap account and still no entries for log*

bruienne: scheduled 45mins, actual 3hrs?

mosen: salutations

doing update now

mosen: scheduled 2 hours, went short, still fried my brain

felt like 10

hah

rhammen: ok.. As I forget things.. Can you raise that on GH? I've an update in the works & will figure it out.

bruienne: too much newspeak?

Sure, I'll find the time to post there. Because I do this on a machine with multiple partitions, it was more logical for me to put all of the apps/packages/graphics into a single partition, rather than all over.

macgirl84: SLA speak, services, metrics, data points

KPI

bruienne: by the dogcow, that's worse

rhammen: cool. If you don't & I forget.. Maybe 1 of us remembers the conversation here.. Haha.

msblake_: I like Kitzy.. But wtf?

I know it just comes down to spare time.

sad clarus

macmule: funny i was just reading that twitter thread

gneagle I did only the sec update and still have no logFoo in com.apple.mail

rhammen: well in my arse for a few weeks.. Just got to remember.

macmule: lol, I know, right?

I think there's a few important points about AD binding

rmanly: Ok. I had thousands of archived logs from the past few days

it actually proves a point gneagle had yesterday.. But don't tell him.

http://mywiki.wooledge.org/ShellHallOfShame/Page3 These are all good.

macmule: first 10.10.2 NBI en route.

rhammen: thanks.

I wish he hadn't said that right as my class was starting though, lol

My phone is blowing up. Luckily it's a WebEx based class and no one else needs to know.

msblake_: class with him?

macmule: No, it's a grad school class

gneagle: https://twitter.com/johnkitzmiller/status/56094... re: JAMF dogfooding. (Convo yesterday).

gneagle just to be sure I did itunes, ard client, and ard with reboots and no change so far. Also deleted a message from inbox.

msblake_: well 2nd Twitter storm with a JAMFer for me today. Haha.

macmule: Not getting the connection

gneagle: well AD does seem a pita if your not working in a fully integrated AD environment. Then it becomes desirable & more AD connectivity wanted.

macmule: https://jamfnation.jamfsoftware.com/discussion.... seems tedious to manage

gneagle: that or ASUS? I'd rather block the odd few then worry about ASUS/reposado

Like today.. I'd not block any apple updates.

Not so much about "blocking" as about testing/release workflows

does ignoring an update with --ignore hade it in app store as well? Never tried.

rmanly: Pretty sure yes

& our JSS is globally accessible.. It's one line..

gneagle: I'm going to have something like 18 caching servers soon.. For iOS & OSX. So going to make the jump to them fully.

Also, peers will give me some redundancy without me working at it.. (Less to set via the JSS too.. Even though it's easy via network segments).. We're also load balancing NetBoot & Casper DP's on each site.. Again, automatically.

So more robust infrastructure, less work. :)

So gneagle, it's less tedious to manage.

Have you actually done it, though?

managed the ignore list for softwareupdate, that is?

gneagle: tested on a few macs with one update. Yep.

We replicate apples catalogs on our ASUS anyways.

just a week behind, & if a "BAD" update comes out.. We'd turn off ASUS on the server we were cascading from.

I think the last one was blocked was maybe 10.9.5? Was that reissued??

I'll post it up when done anyways.

macmule: Seems it would get difficult to manage if Apple, say, dumped 5-10 updates in a single day (like maybe 27 Jan 2015) and you wanted to only let your testing group get them for the first week

rhammen: now people are saying that there may be an ASR change in 10.10.2?

I dunno

gneagle: yea, we don't have a testing group..

macmule: Then how are you sure there won't be issues?

(all this may be fine for you)

But often I want to promote good practices for most

macmule: no asr change that I can see. What's up?

I still use/recommend SUS

Even if you don't fit in the "most" group

deploy manually-downloaded updates to the test groups for a week or two

before they're enabled.

gneagle: never sure. Never 100% certain. We had 1 weeks grace & would look out for reports on MacE & JN.

in before @gneagle brings up Reposado

rhammen: But that's why I wrote reposado; to get rid of the manually-downloading part

I think NetSUS has clouded my opinion, need to set it up on its own some year.

gneagle: completely understand and I'll get there.

rhammen; Why's that?

reposado is trivial to set up

gneagle: But when we have found issues that haven't been reported.. It's normally us painting ourselves in a corner.

macmule" ?

chilcote: people are having issues using Casper imaging to block copy OS.dmg's on 10.10.2 NBI's.

gneagle: like safari toolbar change

Where's the corner?

Ah.... well I wish them the best of luck.

gneagle: turn of phrase

What were you trying to convey?

chilcote: well, people started blaming AutoCasperNBI.. So immediately went (bollox).

macmule: FWIW AutoCasperNBI seems to be taking a hell of a long time to build my OS DMG

copy it ot NetBoot.dmg that is

to. FFS

macmule ha ha.... if only there were an elephant in the room...

gneagle: the only issues we have seen affecting our environment over 4 years due to "bad" Apple updates have been due to something odd that we've done.

macmule fwiw, I just updated my nbi to 10.10.2 and am not seeing any slowdowns. I'll throw it in debug mode and check the logs.

I keep forgetting that Reposado is such a good idea

macmule: 36 minutes seems a bit long.

chilcote: thanks. It seems to be a JAMF casper imaging issue. So bullet dodged my end.

shocker

gneagle: that's not the Full OS's though. They are tested.

macmule: You've been a bit lucky, then

gneagle: same for before. What breaks most are the app updates. Things like CS6 & plugins.

Yes, that's also true

Which is why a testing/release workflow is important

And why Casper should support one natively

gneagle: so generally Apple updates have been a non-issue.

So yea, Apple updates are going to go via caching server & we block the bad.

macmule: But once you know "the bad" isn't it too late?

"crap, five barns are on fire! Well close the barn door on barn #6"

gneagle: if it's an instant brick of the Mac.. Yes.. But we can reimage without losing user data & it's within the SLA's agreed with the business.

With testing/release, barn one gets burned down a few times

But 2-6 much less often

But wouldn't you want to detect the issue before you get to the "need to reimage a bunch of user's machines" stage?