SeriouslyUser59

Probably a weird question but do I need the original band -- or any band for that matter when I trade in an Apple Watch to Verizon? I'm kind of hoping I can just send the watch and the band is treated more like a charger but I'm probably being hopeful.

I had a PA220 that was off being shipped around the world for a few months. Long enough that the device cert expired. When it was powered back on it didn't reconnect to Panorama by itself. I went ahead and renewed the cert on the device directly, that didn't seem to make a difference. Then I followed the process to recover managed device connectivity (sc3 reset, clear the status on the panorama, new authkey), that connects it back to Panorama for a bit but then it gets disconnected again after a few hours.

In configd.log on the Panorama side I see this:

2022-07-07 08:14:45.248 -0500 SC3: did:'<serial>', ser:'<serial>', ver:'10.1.6-h3', mod:'PA-220'
2022-07-07 08:14:45.2

Just a heads up for anybody else fighting this. On any M1 macs I couldn't get the MDM profile to load after I signed it and pushed it through JAMF with the fun error 'The operation couldn't be completed. (SPErrorDomain error 1.)'.

The solution seems to be editing the mobileconfig file a bit:

• drop the <dict> section containing the old kernel extension stuff (be sure to leave everything else)
• on line 6 & 8 replace the UUID with a new one
• change line 14 to something like 'Falcon Profile M1'.

(Those last changes are due to the fact JAMF won't import the 'same' profile twice.)

Once you do that, resign the profile and upload it, then scope it to your M1 Macs (excluding them fr

Has anybody else ran across this yet? The gist of the issue is ADR rules are downloading patches to c:\windows\temp as they're being processed, which is normal. The problem is it's leaving behind a lot of 0 byte temp files eventually causing errors in patchdownloader.log since it couldn't create a new temp file. This morning when I noticed it there were over 65500 said temp files. After clearing those out ADR rules ran correctly but then left another 700 empty temp files.

I think it cropped up with 5.00.9040.1000.

Update looks like this might've finally been patched in KB4600089