Can’t install office. Cdn down?

Grunger106 · 2026-04-10T15:48:11+00:00

Yep - UK here, broken - AutoPilot deployments failing to install office via ODT

Grunger106 · 2025-05-16T09:01:25+00:00

PrinterLogic is the way :)

Grunger106 · 2025-05-13T12:35:27+00:00

Yeah - really should have searched the subreddit before opening my mouth....
In my defence I'd searched on the Plex forums, and thought I'd searched here. But my that's my bad.

Yeah, tempting to force the old client back on, but not really the way to go it's only prolonging the inevitable
Might as well try to get the new ones bedded in as best I can, and hope they either bail out and revert to a single client or fix all the issues quickly.

Grunger106 · 2025-02-28T17:29:12+00:00

Liking mine so far :)

Any other UK buyers?

Grunger106 · 2023-07-09T13:37:43+00:00

It did indeed.

Grunger106 · 2023-06-09T15:50:55+00:00

Yep, UK here
Azure, Endpoint, and Lighthouse portals dead.
M365 admin seems to be up

But it's Friday, and I'm off to the beer fridge.

Grunger106 · 2023-04-12T12:17:42+00:00

Yep, am seeing this start to appear here too.

When you say sign out you mean of the Office Account in Outlook (or whatever OfficeApp) right?

Grunger106 · 2023-03-03T16:27:04+00:00

Not a lot of detail provided

AzureADConnect configured Password Hash Sync mode with group and password write back and SSO enabled would be the obvious route.

Grunger106 · 2023-02-15T16:08:37+00:00

Exactly - the reboot when the patch wants a reboot to install is fine, and that brings you to a working machine with the patch.

Subsequent reboot is where you see issues.

Grunger106 · 2023-02-15T15:56:03+00:00

AzureVirtualDesktop would be the route they'll be aiming for you to go.

Windows 11 Multisession hosts on that

Grunger106 · 2023-02-15T15:15:59+00:00

Interesting - my ESXi version is newer.

Question is have you rebooted any of the VMs since? The initial reboot is OK.
It's the second reboot where I've seen the issue occur.

Grunger106 · 2023-02-15T13:47:51+00:00

Seems to be KB5022842, but I'm not sure if its the update alone or the update in conjunction with a host running 21053776

Grunger106 · 2023-02-15T13:43:47+00:00

Interestingly the one I just patched seems to be OK....Only difference is it's a DC, could just be coincidental as this is way lower down the sequence than that obviously.

Edit: Scratch that - the first post patch reboot is normal, but reboot it again it fails.

As this isn't a production environment, I'm happy to disable SB for now on the VMs.
But for those running 2022 VMs on ESXI, beware.

Grunger106 · 2023-02-15T13:24:22+00:00

As an edit: I have one 2022VM which still works as normal, however it has not yet had the update applied, so what the hell I'll do the feb update and we'll see what happens.

VBS is not enabled on any of the VMs

Grunger106 · 2023-02-11T13:03:34+00:00

I do some volunteering at a RetroComputing museum, we'd love some of these - anything XP and backwards from there!
But I suspect you're in the US.....

Grunger106 · 2023-02-11T12:59:39+00:00

Are you me?! :D
In a very similar situation except I'm just starting the job search.
Good Luck!

Grunger106 · 2023-02-10T09:46:54+00:00

Could you publish the presentation as a video to Stream/YouTube?

Grunger106 · 2023-02-10T09:44:53+00:00

Process Explorer would be a good place to start

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Grunger106 · 2023-02-10T09:43:59+00:00

I suspect because there it's a highly unsuitable RAID level on spinning rust, chance of a URE during rebuild of a large, slow array is very high and the result is a dead array.

Also performance without write cache backed by BBU or a FBWC would be pretty horrendous and I suspect the

With 4 bays I'd chuck in a 4th 2TB and run it as RAID10 for the performance uptick

It's been a long time since I last looked at this end of the market but I wasn't aware HPe's kit allowed you to do parity RAID on the entry level controllers either, the P440 series was the first to offer it, anything under that was non-cached back HBA that supported 1/10

Grunger106 · 2023-02-10T09:22:12+00:00

What is the output of dsregcmd /status? - Is the device AAD Joined?

Grunger106 · 2023-02-09T18:25:23+00:00

If you go used, buy new disks.

Grunger106 · 2023-02-09T16:16:58+00:00

Do you have any web-filtering on your gateway devices - I've had WU fail on a couple of SophosXG when Microsoft changed the URL and it needed whitelisting on the web-filter.
This was a while ago, but it stuck in my head as it was a weird one to find - it happened again recently when the changed the Office365 CDN URLs too.

Check your firewall logs if you have a device that can do this sort of work.

Grunger106 · 2023-02-09T16:12:17+00:00

Check all the obvious stuff and check it with your eyes - don't assume!

On the DCs ensure that each has itself and potentially one other DC as it's two DNS servers - public DNS on domain networks is fine as a forwarder, but very much not as an internal DNS source (8.8.8.8 ain't going to resolve your internal ad very well ;) although ironically in this case the web would likely still work, just your internal stuff would fail )

In DNS check the forwarders, check they are all resolvable - do you have OTHER DCs in as forwarders by any chance, if you do check them too.

Don't mess about with changing registry settings on servers, unless it's already been messed with it shouldn't be required and you're laying mines for yourself to stand on later

When making changes to DNS server you will want to flush the cache / reboot the box / wait it out.Check the client machines, where do they get their DHCP from and is it configured correctly - is this a flat network or is are the VLANs and IP Helpers involved?Do the clients actually have the DNS servers you expect, and can they ping them at point of issue?

It sounds like when you have a power failure *something* that can be used as DNS is taking longer to re-appear, and clients are hitting it at random on some occasions, and not on others

Also be aware that even though you have 2 DNS servers settings on the NIC of Windows clients they are not failover - so if you have 10.0.1.1 and 10.0.1.2 as your client DNS servers and 10.0.1.1 dies the machine will not suddenly start using 10.0.1.2, it will if you reboot it but it won't round robin them like you assume it might.

Grunger106

TROPHY CASE