Sheridan

I decided to update our SCCM 2503 to the latest supported Dec 2024 ADK. This all seemed to go OK and rebooted and updated the Boot images from the ADK images Now nothing will PXE boot - a PC will get the pxe boot screen and try to load the image and just seems to reboot All I can see in the SMSPXE.log if a few timeout messages: recvfrom() returned 0x8007274c. Waiting for 775. recvfrom() returned 0x8007274c. Waiting for 775. recvfrom() returned 0x8007274c. Waiting for 775. recvfrom() returned 0x8007274c. Waiting for 775. recvfrom() returned 0x8007274c. Waiting for 775. timed-out. Not sure if this is a false flag but it was all working 100% before I did this. Before I rollback to the snapshot has anyone seen this before? Its not a network issue as I'm using the same ports/cables etc that were used before the ADK update!

Its one of the reasons we upped to A3 so cover shared device activation, and home use right etc - basically all the stuff that used to be free and no longer is. Seems to be the way a lot of cloud services will be heading in the coming years

That's exactly what I've been doing today 🙂 - added the core apps and MRU list and will make this the default landing page for everyone!

Thing is I don't want another app to manage simply to access 365 web apps - its another unnecessary complication! I'll probably just redirect everyone to a sharepoint site and they can access their apps via the grid menu

And its back off again...what a POS its been this last couple of days.

Some have come back here but not all, and running very slow. I think I need to find an alternative landing page as this copilot forced mess isn't working too well

Ours has just gone off again, no apps appearing and the meaningless message appearing again Great stuff, makes me long for GSuite a little bit more...

It seemed to be hitting everyone here and had a few calls, some are coming back now when they refresh the page - not a great start to a Tuesday...

Oh dear - most of our users now see no apps on the 365 landing page - only the following message: New to Microsoft 365 CopilotThis is your Microsoft 365 Copilot home page-where you can see and access all of your Microsoft 365 apps. If it's empty, it could be that your user licence was very recently assigned to you. Wait 10 minutes and refresh this page. If you still don't see any apps, contact your IT department. They can help you get up and running. This isn't correct as we have A3 Faculty assigned by default and this isn't a recent addition - anyone else having problems? We use the landing page: https://m365.cloud.microsoft/apps/ Now even as an admin I just get the 'New to copilot message' and all the standard apps are missing. Another day using 365...

We bought a batch of refurb Dell Latitude 7420 2 in 1's recently - 380 each with a 3 year warranty and they're nice laptops. USB C charger as well as one thing I used to hate about Dell is their proprietary chargers!

Managed to fix it by rolling all the way back to V23 of the driver package (current is 25) Seems to be a signal issue between the two devices. Not an issue with Intel GPUs and our AMD's don't have an issue with other screen makes - so only an issue with AMD and Philips!

I tried support with Philips who blamed the AMD driver, the PC vendor blamed Philips....etc Eventually I found that using the Adrenalin control panel to disable hdcp worked...until now! I think I'll try and get a version that's a bit older and see if that still works

Got a really frustrating issue here - some of our desktops all have AMD Radeon integrated graphics and are connected to Philips E Line touchscreens The pause function doesn't work on the screens due to the annoying HDCP - which you can switch off in the Adrenalin control panel (this has worked in the past) However every machine I try to install this on now it simply doesn't work. It installs OK and the drivers are updated, but if you try to open the adrenalin control panel it does nothing - no errors logged, nothing I can't find a registry setting to disable hdcp either so I'm stuck with this turd of a package - unless anyone knows a workaround or how to get the thing to start! Tried the usual things I've found in a search but nothing has worked so far

I was planning rds with mfa but will look into smooth wall vpn - couldn't find much in the way of documentation for this though. Still need to get the new external connection working either way!

We have a vpn on our old cisco box so trying to move away from this, RDS is something I've used before as its cross platform but I've not looked at the smoothwall vpn as an option to be honest. Might have to research that a bit as well

OK, Thanks - I've logged a ticket. The way it was originally set up seems overcomplicated to me which is why I want the Smoothwall to be the new firewall - and publish an RDS server through it as well

Definitely - its the only External interface as the previous setup was using the firewall as the gateway.

I'm trying to migrate our old system to use the Smoothwall as the whole UTM - the way the system I inherited was setup was that the Smoothwall is set as the proxy, and then the Smoothwalls internal interface points to our Cisco firewall as its gateway This works - traffic proxied to the Smoothwall goes to the firewall and then out to the internet Now, as I'm planning to remove the old firewall I added an external interface to the smoothwall, gave it an external address (from our ISP range) and set the gateway of the external address to be the ISP provided gateway All good, so I thought all I need to do now is to switch the gateway of the internal address to None as it will use the new External interface, but when I try that it fails with two errors: Gateway: IP is not in use as a gateway Local address: Addresses without a gateway cannot be used in an LLB pool I must be missing something here, as instead of directing the outbound traffic to the firewall it should be able to use the external interface (which is tested and working) to bypass the firewall? This is stage 1 of migrating stuff away from the firewall so I'm using spare external IPs that the ISP allocated

Repair install using Sept 25 ISO and then add Oct Cu worked for me too. MS seemed more concerned about our licensing so I gave up with that route.

Which log file did that appear in? Seems to be a different error to mine but the log file is enormous!

That's my plan - waiting until the next holiday as its used every day

Its on esx - along with all the other ones that worked fine this patch run!

I've tried all the usual windows update fixes but so far this one has me stumped - MS basically sent me the usual fixes and also advised me to try a third party tool (SFCFix) which I thought was a bit odd

I’m only having the issue on one server so far, but I did log with MS who seem to have decided it’s not in their scope of support Going to try a repair install with the latest 2022 iso this week…..

All of our servers are 2022 - same patch level and all bar one have patched (so far) the Oct 2025 CU One stubbornly refuses to install it with the following error: {B38FAB3D-BA8D-4F6E-A0D5-4839E704108C} 2025-10-16 12:17:11:632+0100 1 182 [AGENT_INSTALLING_FAILED] 101 {5026AE86-A668-4D90-9CEE-72AA8EBD09F6} 501 8024200b wusa Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200b: Security Update for Windows (KB5066782). q7C6eQdgGkmj4Nhd.2.1.0.3.0 I've done all of the usual: - delete SoftwareDistribution etc - sfc /scannow - dism /restore health - manual install of the cu downloaded from the catalog When I export the update logs I see entries like this: 2025/10/16 12:17:11.4293726 5404 4292 Deployment *FAILED* [80073701] Deployment job Id 4736DA9F-AC28-4B4A-A71C-1610466EE7A9 : Installing for Top level update id 5026ae86-a668-4d90-9cee-72aa8ebd09f6.501, bundled update id c3b372b6-6bd5-465a-bef9-84df2bd9b7a0.501 [CUpdateDeploymentJob::DeploySingleUpdateInternal:3103] 2025/10/16 12:17:11.4293853 5404 4292 Deployment *FAILED* [8024200B] Deployment job Id 4736DA9F-AC28-4B4A-A71C-1610466EE7A9 : Installing for Top level update id 5026ae86-a668-4d90-9cee-72aa8ebd09f6.501, bundled update id c3b372b6-6bd5-465a-bef9-84df2bd9b7a0.501 [CUpdateDeploymentJob::DeploySingleUpdateInternal:3122] 2025/10/16 12:17:11.4293983 5404 4292 Deployment *FAILED* [8024200B] file = onecore\enduser\windowsupdate\client\updatedeployment\lib\updatedeploymentjob.cpp, line = 3124 Not sure what these are, I've never seem this error before and its only on the one server Short of rebuilding a new server (massive pain due to the apps running on it!) is there another way around this?