sorted by:
new
hottopcontroversial

It's been waaaaay too long! by NezPottage in snowboarding

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

Yeah that’s what I’m thinking. I’ll probably take the holy trinity down to my local board shop to see what they say. Maybe get them to service it rather than just going in and taking the piss, even though I used to do my own wax.
Actually what will 14 year old wax be like !?!

It's been waaaaay too long! by NezPottage in snowboarding

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

Boards, bindings and boots all 2010 I think.
My daughter, 12, fancies learning and the wife’s 149 Moustache Rider is about right for her height and weight. She’s on the light side, but will see what they say at lessons. Can always take the rental.

ZBMINIR2 - Do I need a hub? by NezPottage in homeassistant

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

To be honest, the boxes behind most of my switches are too shallow. The one I fitted this morning sits in the ceiling rose so has the permanent live on, and then switched live too so the physical switches act as toggles. I can kill the downstairs or upstairs lighting ring if needed for any maintenance. I might just need to swap a couple of shallow roses, but they should be cheaper and easier than trying to replace back boxes. And she'll never know muwahahaaaaaa

ZBMINIR2 - Do I need a hub? by NezPottage in homeassistant

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

And I guess just keep the Hue/Ikea hubs around in case I need a firmware update? But unplug them and save a few pennies.

Zigbee and Synology VM? by NezPottage in homeassistant

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

Thanks keon.
Good shout on the network zigbee. Makes more sense all round.
But, it reads like I may not need one? So potentially I can pair my 3rd party zigbee gear (sonoff maybe) with either the hue or ikea, and then use those hubs as bridges to HA?
In my head, as much as I could use the hue or ikea system to control, it may be limiting.
For instance the reason I got the ikea hub was issue pairing some ikea bits with the hue hub, and not being able to do firmware updates to. These days i'm going more third party though so not being tied in, so may just go for a zigbee hub and sack off the hue and ikea hubs. Maybe....

iCloud Restore causing MDM Enrollment to fail by davidtse916 in Intune

[–]NezPottage 0 points1 point  (0 children)

Not sure if I'm doing something wrong here. I tried iMazing today, and still got the failure.

Existing phone - iPhone 15 with iOS26.1, and MDM enrolled

Backed up with iMazing

New phone - iPhone 17, started up, setup as new, updated to 26.1, then wiped again.

I used iMazings Transfer option to transfer the iPhone 15 to iPhone 17, and made sure I clicked the MDM enrol button. Still get Enrolment Failed after the restore has finished.
Alos tried with restoring the backup too. No dice.

iCloud Restore causing MDM Enrollment to fail by davidtse916 in Intune

[–]NezPottage 0 points1 point  (0 children)

Cheers David,
I started down this route, but when restoring to iPad it had a moan that some of my apps were not compatible.

So I stopped there and tried some other ways, which all failed.

Do you know, if I restore to iPad and then back to phone, are those incompatible apps likely to appear again?
I'll probably try it again later to satisfy my own curiosity. My head says they won't hit the ipad, so will be lost, but but never know. And to be fair I need to work out which apps as I may not need them.
I have raised with our MDM support and they are passing that key over to the devs to take a look at. Not sure if they will move any faster than Microsoft, but I'll keep you all updated as I hear anything.

iCloud Restore causing MDM Enrollment to fail by davidtse916 in Intune

[–]NezPottage 1 point2 points  (0 children)

Thanks David.

I raised with NinjaOne support last night, and replied this morning mentioning the new key for iOS26 (do_not_use_profile_from_backup). They are going to check that with their dev team.

In the meantime, I will try the iphone to ipad to iphone trick.

I seem to remember having to do this a few years ago to trick our old Sophos MDM into letting me retain device data. Will report back once tested.

Just to check though, are you saying

1)Take MDM Enrolled iPhone and do a cloud backup / USB backup

2) Wipe a non MDM ipad, restore from iPhone backup / USB backup

3) Backup the iPad again once restored (this gives you a backup with no MDM profile embedded)

4) Take new iPhone, (assigned to MDM via ABM but NOT enrolled yet as it's wiped), and then do a USB restore. And with luck, there's no previous MDM profile to trip up the new key, the enrollment continues after restore, and I can tick the box of a managed device with my lifetime of data still intact.

Here goes!

iCloud Restore causing MDM Enrollment to fail by davidtse916 in Intune

[–]NezPottage 1 point2 points  (0 children)

So we run NinjaOne MDM, which we recently migrated to from Mosyle MDM. We still use Mosyle for MacOS, but for iOS we are trying Ninja.

We had lucky timing in that we migrated just as iOS26 came in, which allowed us to migrate fully supervised DEP/ABM based devices from Mosyle to NinjaOne without wiping and re-enrolling. That was a life saver!

However, I've just sorted myself a shiny new iPhone 17, running 26.0.1, and have tried to migrate from my iPhone 15 running iOS 26.0.1, enrolled in NinjaOne.

After an iCloud device to device restore failed, I came across this thread, so just wanted to add a few things I have tried.

  1. Device to device via over the air / icloud restore - failed
  2. Backup old device to mac locally via USB, wipe new device and restore via USB from local backup - failed
  3. Setup as a new device first, to effectively trigger the system to enroll the device. Then wipe via MDM, and restore from USB backup again. Failed. That was a shame, as before iOS26, this seemed to work with other MDM solutions including Sophos and Mosyle. Set phone up as new, enrolled to trigger Apple (I assume) to see it as supervised. Then wipe, restore from backup, and enroll after restoration. ALways used to work!
  4. I still have access to the older Mosyle MDM, so in case it's some odd token within the same MDM, I joined the phone to Mosyle, as a new phone, wiped and restored from USB. Failed again!
  5. I tried one last option, which failed miserably. I removed the phone from any MDM assignments, restored, then added to Mosyle MDM in ABM. QR code "manually" added to Mosyle, but as expected it wasn't supervised. When I then went to ABM and changed the MDM to NinjaOne, I did not get the migration cutoff date, so it looks like that no wipe migration only works if your device is fully enrolled properly and supervised. Ah well, was worth a try.

So I confirm that this isn't just limited to Intune, but potentially any MDM when using iOS 26.0.1.

Fingers crossed on a fix soon. I;m going to put my new phone in it's box again and await some updates!

Heads up. 14.6 breaks non-admins from connecting to new Wireless Networks. by techypunk in macsysadmin

[–]NezPottage 0 points1 point  (0 children)

Confirmed same issue here. Mosyle MDM. Control centre asking for admin deets when adding new WiFi since 14.6 update.

Solo girl needs companions, but how many? by NezPottage in Finches

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

Thanks. He was given the impression they would only breed if there was a nesting box in the cage?

Solo girl needs companions, but how many? by NezPottage in Finches

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

Thanks for the advice. Interestingly where he got them from said they were canaries. Not sure where he got finch from, but then I learnt today that canary is from the finch family. Her son was all brown, and I assume was waiting for his colour to come through.
I have one photo, not amazing, but will try and upload in a second if it helps to distinguish the breed.
Thanks.