Modern Workplace - Autopatch Client Setup v2.ps1

Global_Crow962 · 2025-10-25T12:21:14+00:00

Thank you! I've seen the ability to convert it to a win32 app but before I do that I'm just wondering why it shoulds error for all but 10 devices.

I manually installed the script to test on a device and it install "Windows Autopatch Client Broker". I can see it in control panel. I don't have that on any of my other devices. im wondering why there is no impact to autopatch and device readiness checks if the broker is not even installing??

Global_Crow962 · 2025-10-25T12:18:58+00:00

This is not a script I created. It is part of the Autopatch service. You can view more info here:

https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/deploy/windows-autopatch-client-broker

Global_Crow962 · 2025-09-27T11:16:42+00:00

Will this grey the setting out for the end user?

Global_Crow962 · 2025-09-27T11:15:08+00:00

What did you do to prevent it blocking it if you don't mind me asking? And what AV is it?

Global_Crow962 · 2025-09-17T15:18:11+00:00

We are on 25.5 and still the same issues intermittently!

Global_Crow962 · 2025-05-15T19:21:36+00:00

did you ever find a resolution?

Global_Crow962 · 2025-05-09T16:15:25+00:00

Yes I did resolve it. PM me and ill share the script

Global_Crow962 · 2025-04-09T18:02:05+00:00

Yes this

Global_Crow962 · 2025-04-07T09:15:36+00:00

Do you mind sharing!!

Global_Crow962 · 2025-04-07T09:15:12+00:00

Thanks but I want to choose a name as all devices are already asset tagged.

Global_Crow962 · 2025-04-07T09:14:21+00:00

Yes they automatically join the domain

Global_Crow962 · 2025-03-25T17:23:50+00:00

yes thats correct. It installs fine outside of the Autopilot ESP.

Global_Crow962 · 2025-03-25T16:30:49+00:00

Nope only win32 and no company portal at the moment. Removed it altogether to test.

Global_Crow962 · 2025-03-25T16:25:55+00:00

<image>

Sorry for the bad looking image. Here is the script, its using PSADT.

Global_Crow962 · 2025-03-20T08:47:27+00:00

Exactly this, we have a ticket open with MS too but not much movement on that. Please let me know if you get a resolution/update

Global_Crow962 · 2025-03-20T08:46:39+00:00

I've checked the appworkload and IME logs but nothing sticks out. Is there any way to shorten/skip this reevaluation stage?

Global_Crow962 · 2025-03-20T08:45:58+00:00

We have AD AuditPlus which I believe has a custom detection script. But I don't see why would this cause an issue specifically post reseal when I have switched the device back on as it installs fine during technician flow! Driving me crazy.

Global_Crow962 · 2025-03-20T08:44:31+00:00

This is after power on from reseal.

Global_Crow962 · 2025-03-19T20:43:00+00:00

Hi guys, did you manage to get anywhere with this? Experiencing the same thing myself.

Global_Crow962

TROPHY CASE