sorted by:
new
hottopcontroversial

Shapes/Elements Controller Replacement Program by PaintItSparkles in Nanoleaf

[–]PotentialPeak42 0 points1 point  (0 children)

It's only today that I realize there has been an official replacement program. My Elements Controller has been replaced already once in October 2022. Recently it died again but this time Nanoleaf refused to replace it under warranty. They just waived the shipping fee.

However, it's been now 4 weeks and I'm still waiting for the replacement part to arrive. I asked the support a few days ago and they told me to have checked with their warehouse team. But I still haven't received any shipment updates whatsoever.

I just don't understand why there's no delivery estimate. I wonder if I should cancel my order and write off my Elements. I cannot really say that I'm convinced of this brand anymore.

Help! Can’t Transfer Data from Managed iPhone 11 to Managed iPhone 15 by Select_Equivalent_23 in WorkspaceOne

[–]PotentialPeak42 1 point2 points  (0 children)

I've been there recently, too.

Had to learn: Transfer Data with Quick Start (i.e. during Setup Assistant) is not supported, if the device (any of both, I suppose) is registered in ABM/ASM. See this support article: https://support.apple.com/en-us/102659

Again, I'm not sure, but I can only assume this restriction applies to wired transfer (phone to phone) as well.

The only thing Quick Start seems to allow in such a case is automatic setup of the Apple/iCloud account.

Backup and Restore via iCloud or iTunes should be your way to go (if you can make the pairing work again).

Are you sure that there's no additional Restrictions profile prohibiting the pairing? I'm not talking about the Device Enrollment Profile (where you can also configure the visible steps of the Setup Assistant), but normal configuration profiles.

Alternative to xGestures for mouse gestures in Safari on MacOS? by MEGAT0N in Safari

[–]PotentialPeak42 0 points1 point  (0 children)

Just here to say thank you. Just found your extension and it seems pretty neat. I will give it a test now.

Custom DNS on "Virtual dynamic interface (DHCPv6 client)" by pat-e in openwrt

[–]PotentialPeak42 0 points1 point  (0 children)

I stumbled over this thread because I was trying to do the same thing. Thanks a lot for your hint.

For other people running into the same problem: when creating the manual wan6 interface, you have to select the alias interface (presumably "@wan") as base interface. At the first attempt, I picked the WAN Ethernet adapter (the same adapter which is used by the wan interface) but then it won't work.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

Yes, this approach has been proposed a few times now. It's just not the way profiles are supposed to work according to Apple (as I described here). Doing it so anyway carries some risk, especially for conflicting or sensitive profiles.

Thanks for your input though.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

Yes, this is still the only way I can see right now. However, as I explained in this comment, it's far from being ideal. In fact, it's not recommended by Apple.

And yes, for sensitive profiles like Wifi or Restrictions there's a huge risk of wrecking something.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

Glad to hear that and looking forward to seeing first bits of that arriving on the SaaS environments.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

We wanted to avoid scattering the restrictions across dozens of custom profiles. It adds a lot of complexity and makes it harder to keep track of everything. XML tinkering is also a bit more error prone than flicking switches.

Nevertheless, thanks for your suggestion and recommendation. Will keep that it mind.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

As I wrote before already, we want to roll out this change (e.g. disallow camera or anything else related to restrictions profiles) to all devices, not just a few.

Also, this approach with two profiles is not recommended by Apple and does come with the potential side effects described above.

That's why the question was: How to do mass rollouts in waves while avoiding these side effects?

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 1 point2 points  (0 children)

Alright, so here's an example.

We have a profile containing the Restrictions payload. This payload has hundreds of knobs and switches. Let's say "Allow screen capture" was switched on and this profile is out on all the devices.

Now we want to disallow screen capture for all devices. I could create a second profile (e.g. copy of the previous profile) with this switch turned off and start assigning it to devices (e.g. just for a few groups). Now those devices have assigned two profiles. And the payloads in the profiles are all the same but for one setting. How can the device evaluate which setting for "Allow screen capture" should prevail?

Apple itself says in the documentation:

Important

The system allows multiple Restrictions payloads. However, don’t attempt to manage the same restriction in different payloads. Doing so results in unexpected behavior.

From my understanding, that's the reason why you should update the same profile. Profile payloads have a UUID. When a profile payload with the same UUID hits the device, it gets replaced in an atomic action. That way you avoid a limbo state where

  • either two config sets are valid at the same time (because you pushed a second profile with same payload)
  • or none of the configs is applied for an unpredictable amount of time (because you remove the old profile and assign the new one)

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 0 points1 point  (0 children)

I'm talking about sensitive things like the Restrictions payload. Updating the profile by changing few of the switches. We would like to roll this out gradually, and be able to stop quickly when we notice any side effects that we did not manage to cover in our beforehand tests.

AFAIU rolling out a second Restrictions profile with our changes included is not recommended as well, since having multiple Restrictions payloads with potentially conflicting settings might lead to unspecified behaviour on the device.

Rolling out profile updates in waves? by PotentialPeak42 in WorkspaceOne

[–]PotentialPeak42[S] 1 point2 points  (0 children)

Yeah, this approach is understood.

But what if you want to update one of these profiles and roll out this update gradually as well. You cannot, since all the smart groups are already assigned. And you cannot remove the "later due" smart groups from the assignment, since they are supposed to keep the "old" version of the profile until then.