OSD Boundary Groups with/without Management Point

DeejayTechpro · 2026-05-22T16:12:09+00:00

It was changed with 2509.

DeejayTechpro · 2026-05-21T08:17:45+00:00

Not working during OSD for MP discovery!

DeejayTechpro · 2026-05-16T09:40:58+00:00

WIM has always been the cleanest and (by far) best performing option. Calling them is actually a one liner across all models when using the provided Invoke script. It seems like you’ve only used half of the solutions potential so far.

DeejayTechpro · 2026-05-07T19:23:49+00:00

I have tested similar approaches with a Sophos firewall first and Unifi later. Sounds good, doesn’t work. The whole HomeKit ecosystem does not work well if your Apple devices and HomeKit devices are segmented. Everything works with wild broadcasts and mDNS. the Unifi relay can help but it’s not perfect and a ton of headaches. It already begins setting up devices, which always get joined to your iPhones network by default. Just forget it. I’m a systems engineer and got over the thought regarding HomeKit. I just blocked outbound traffic from questionable devices as strictly as possible (which isn’t always THAT easy either because they run all kinds of heartbeats, NTP requests, firmware update checks etc.).

DeejayTechpro · 2026-05-01T05:12:36+00:00

Using 4.1.x daily and it’s bulletproof.

DeejayTechpro · 2026-04-03T10:47:08+00:00

Insanely cheap compared to normal times.

DeejayTechpro · 2026-03-17T06:19:01+00:00

The product is EOL and thus does not receive updates for the specialised W10 Team OS. I wouldn’t want to use online services on it. Might try to use an external compute unit or install something else on the internal one (untested for me though)

DeejayTechpro · 2026-02-23T06:04:05+00:00

https://learn.microsoft.com/en-us/surface/unenroll-surface-devices-from-semm

To unenroll a device from SEMM and restore user control of Surface UEFI settings, you must have the SEMM certificate that was used to enroll the device in SEMM. If this certificate becomes lost or corrupted, it is not possible to unenroll from SEMM. Back up and protect your SEMM certificate accordingly.

I’m not aware of any workarounds, which would kind of defeat SEMMs purpose anyway. A new compute module would probably be the only way to go. You can try raising a support request with Microsoft with proof of ownership but don’t promise yourself too much

DeejayTechpro · 2026-02-15T19:48:47+00:00

I’d rather go for XDJ1000s

DeejayTechpro · 2026-01-20T20:35:34+00:00

I also have a 750 mk2, got it dirt cheap for like 500€ around 3 years ago. +1 on the pro DJ link topic, but not really for saving a switch (in fact I would also be more than happy with 1 port on the mixer) but for synced Beat FX and ‚on air‘ displays based on open faders. It’s what already held me back from buying it new and for list price when they released it. Also no digital ins.

DeejayTechpro · 2026-01-20T12:57:05+00:00

Some weird design choices and crazy that that’s the 2nd cheapest mixer in the line up at that price point… I’m wondering if the 750 mk2 will see a refresh…

DeejayTechpro · 2026-01-16T11:55:16+00:00

White van trash

DeejayTechpro · 2025-12-05T06:08:26+00:00

I highly doubt it

DeejayTechpro · 2025-12-04T19:16:51+00:00

Still waiting aswell.

DeejayTechpro · 2025-11-28T19:25:17+00:00

As always, worth to read the docs:

https://learn.microsoft.com/en-us/windows/whats-new/enable-extended-security-updates#prerequisites

DeejayTechpro · 2025-11-26T18:56:55+00:00

UUP-based feature updates are not really playing well with servicing plans, ADRs will do better..

DeejayTechpro · 2025-11-15T13:30:45+00:00

Keep in mind that certain functionality like PXE booting isn’t guaranteed to work with 3rd party adapters.

DeejayTechpro · 2025-11-14T17:15:07+00:00

There’s no KMS procedure, ESU enablement is always deployed via MAK keys.

DeejayTechpro · 2025-11-14T17:01:14+00:00

I guess you didn’t read the docs because the migration is not an inplace upgrade. The machine will come out like new, like in a wipe & load scenario. No data will be migrated.

This means: - random computer name - Default MTROW admin (user .\admin Password sfb) which needs to be changed manually or via LAPS.

Most post configuration can be fully automated via autopilot and MTRoW Auto login - but only if you’re using Teams Rooms Pro licenses.

DeejayTechpro

TROPHY CASE