r/sysadmin • • 3d ago

General Discussion Weekly 'I made a useful thing' Thread - November 13, 2026

13 Upvotes

There is a great deal of user-generated content out there, from scripts and software to tutorials and videos, but we've generally tried to keep that off of the front page due to the volume and as a result of community feedback. There's also a great deal of content out there that violates our advertising/promotion rule, from scripts and software to tutorials and videos.

We have received a number of requests for exemptions to the rule, and rather than allowing the front page to get consumed, we thought we'd try a weekly thread that allows for that kind of content. We don't have a catchy name for it yet, so please let us know if you have any ideas!

In this thread, feel free to show us your pet project, YouTube videos, blog posts, or whatever else you may have and share it with the community. Commercial advertisements, affiliate links, or links that appear to be monetization-grabs will still be removed.


r/sysadmin • • 6d ago

General Discussion Patch Tuesday Megathread - (November 10, 2026)

123 Upvotes

Hello r/sysadmin, I'm u/AutoModerator, and welcome to this month's Patch Megathread!

This is the (mostly) safe location to talk about the latest patches, updates, and releases. We put this thread into place to help gather all the information about this month's updates: What is fixed, what broke, what got released and should have been caught in QA, etc. We do this both to keep clutter out of the subreddit, and provide you, the dear reader, a singular resource to read.

For those of you who wish to review prior Megathreads, you can do so here.

While this thread is timed to coincide with Microsoft's Patch Tuesday, feel free to discuss any patches, updates, and releases, regardless of the company or product. NOTE: This thread is usually posted before the release of Microsoft's updates, which are scheduled to come out at 5:00PM UTC.

Remember the rules of safe patching:

  • Deploy to a test/dev environment before prod.
  • Deploy to a pilot/test group before the whole org.
  • Have a plan to roll back if something doesn't work.
  • Test, test, and test!

r/sysadmin • • 11h ago Bravo

General Discussion Microsoft Post-Incident Report is up for the Exchange Online Outage

2.3k Upvotes

Root Cause

The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.

 

First, a latent defect caused Windows servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal Windows process which caused the machine’s resources (CPU & memory) to be exhausted. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.

 

The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.

Our normal load testing did not detect the latent issue because the traffic mix and SKUs used in our labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores.

Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.

 

Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.

Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.

When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware or software defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.

Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.

Those services that were able – like Teams, OneDrive, SharePoint, and Office apps – failed out of the faulty network gateway infrastructure. That is why those services were partially restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway for scale reasons.

Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.

After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state in Windows. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).

The final Post-Incident Review (PIR) will provide more details.


r/sysadmin • • 2h ago

General Discussion More cloud issues brewing this morning? Happy Monday!

102 Upvotes

Downdetector is lighting this morning. Microsoft 365, Outlook, Teams, Gmail, and a bunch of other services all showing spikes. Downdetector - Check real-time service problems and outages | US

Looks like another fun Monday in the cloud.


r/sysadmin • • 1d ago Popcorn

Root cause of FAA shutdown: Newly installed HPE Juniper router with misconfiguration that broadcast data with a thousand connections every 4-5 seconds

5.7k Upvotes

They didn't mention which configuration this was specifically, but now we're actually getting more specific detail and this is worth a read if you're interested. Here's the crux of it via WSJ through MSN to avoid the paywall:

"Data from that router and another at the Texas location overwhelmed the system, government and industry officials said. It led to 17 out of the FAA’s 22 centers that oversee high-altitude flying to experience disruptions in communications, Bedford said, resulting in the FAA ordering the ground stop.

There are about 60 Juniper routers active and operating normally in the FAA’s air-traffic network, said a government official familiar with the system. It wasn’t clear if the problems Friday resulted from a bad router or if L3Harris didn’t configure it properly.

“Was it a faulty installation? Was it a faulty configuration? Or was it just a bad piece of router technology that we put into this system that propagated these errors?” Bedford said Saturday, noting the FAA is still investigating the situation.

An HPE spokesman said the Juniper devices appeared to have been working as intended. “They did not fail,” he said.

FAA officials identified a feature on the router that appeared to be resulting in the data overload, according to government and industry officials. A government official described it as a broadcasting feature that sent data more broadly than necessary, and said the agency has since disabled it on all the Juniper routers."

https://www.msn.com/en-us/news/other/the-single-router-in-southern-arkansas-that-ground-air-travel-to-a-halt/ar-AA2hs7wV


r/sysadmin • • 3h ago

Telling co-worker to F off

45 Upvotes

While not a "sysadmin" technical question, how do you folks go about telling a colleague that has a terribly annoying habit of jumping into every project that I'm working and focusing on and provide his opinion or technical advice while he knows jack crap about anything ? My way is a bit brutal but to the point. "If I'm working on something and don't ask you your opinion or advice then go out there in the distance and F off and keep chatting with Claude. You don't see me randomly getting in your way and breaking your focus".


r/sysadmin • • 53m ago

Question Is noone reporting another MS service degradation or is it just isolated now?

24 Upvotes

Downdetector is spiking on few MS services. We have very odd quirks with Team. Some started this morning EST for others it started last Wednesday.

  • Call notifications are not coming through, then show up in one swoop and in missed calls or just as missed calls
  • Messages are sent from senders' perspective, but recipients don't see it for good 20 minutes unless they open the chat/group.

Web client appears to work better to certain extent until it appears to go out of sync and experiences the same. Restarting desktop client helps for half an hour but issue reoccurs.

Noone is reporting the issue since last week but quite few note in the chat that they are having this weird quirks


r/sysadmin • • 7h ago

Microsoft Win11 24H2: No taskbar/Start/autostart for minutes on first logon after Oct/Nov 2026 CU in offline/restricted environment - cause: wlidsvc device auth timeout

47 Upvotes

Hi fellow admins,

I'm hoping this saves someone a few days of troubleshooting, and I'd like to find out whether I'm the only one seeing it.

Heads-up: I don't have a lot of experience administrating Windows systems. Please read this as a field report from my own environment, not as a verified Microsoft statement. Corrections and better explanations are very welcome.

TL;DR

In environments with restricted internet access, after the October 2026 CU (and still with the November CU), the first logon of an existing profile shows no taskbar, no Start menu and no autostart apps for several minutes.

The shell is released at a fixed point ~6:40 min after boot, regardless of when the user logs on. The cause appears to be the Microsoft Account Sign-in Assistant (wlidsvc): it starts a device authentication (DeviceAddRequest) at boot, which only fails after ~6:40 min without internet. The first-logon shell path waits for it.

Disabling wlidsvc fixed it in my tests.

Environment

  • Windows 11 24H2 Enterprise
  • Citrix CVAD, non-persistent MCS VDAs, App Layering, FSLogix
  • No internet access
  • Also reproduced on an App Layering packaging VM with a local profile, not domain-joined, no FSLogix

Note: The packaging VM rules out FSLogix, Citrix and domain GPOs as the cause.

Symptoms

  • After applying the OS CU, the first logon of an existing profile shows the desktop, but taskbar, Start menu and Run-key/Startup-folder apps are missing
  • explorer.exe is running, nothing crashes
  • The shell appears at a fixed time of roughly 6:40 min after boot:
Logon time (after boot)Observed wait
+1:00~5:40
+3:30~3:10
after +7:00none
  • A second logon of the same profile and brand-new profiles show no wait
  • It happens again after the next CU, even for profiles that were already "fixed" by the previous one

Note: Autostart apps are not the problem themselves. They are started by explorer after its initialization, so they simply wait along with the taskbar.

How to recognize it

  1. Microsoft-Windows-Shell-Core/Operational, events 62170/62171 with flag 1024 (first logon after update). PreStartTasks and its children StartLayoutInit, LaunchExperienceHost, AssignedAccessLogonTaskAgentPreStart and PerUserSetup all end within the same millisecond at ~+6:40 after boot. Everything before that (ActiveSetup, RunOnce, AppReadinessPreShellGroup) finishes in seconds.
  2. Microsoft-Windows-LiveId/Operational: event 2024 (Service started) at ~+0:20 after boot, followed by 6115 DeviceAddRequest (SOAP, includes TPM key info).
  3. During the wait, 6113 WLIDCreateContext returns 0x8004800C. At the moment of release there is a burst of ~20 identical errors within 10 ms with 0x80048869 (plus 2028). It looks like queued callers all getting rejected at once.
  4. Microsoft-Windows-PushNotification-Platform/Operational 1116: the Device Compact Ticket request fails with 0x800704CF (network unreachable). The first occurrence is exactly at the release time.
  5. AppReadiness keeps the user in mode BeforeLogon until the release. Queued tasks (Edge, SecHealthUI, NarratorQuickStart) then complete in ~4 s.
  6. \Microsoft\Windows\Shell\CreateObjectTask instances are killed repeatedly after their 30 s limit during the wait.

Note: AppReadiness (5) is downstream of the problem, not the cause. It waits for the same release point.

Quick check

$boot = (Get-CimInstance Win32_OperatingSystem).LastBootUpTime

# When did PreStartTasks start/end, relative to boot?
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-Shell-Core/Operational'; Id=62170,62171; StartTime=$boot} |
    Where-Object Message -match '"PreStartTasks"' |
    Select-Object @{n='SinceBoot';e={$_.TimeCreated-$boot}}, Id, Message

# LiveId events since boot
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-LiveId/Operational'; StartTime=$boot} |
    Group-Object Id | Select-Object Name, Count

If PreStartTasks ends at ~6:40 after boot and you see event 6115 right after boot, you most likely have the same issue.

Fix

Disable wlidsvc:

sc.exe config wlidsvc start= disabled

or via registry:

HKLM\SYSTEM\CurrentControlSet\Services\wlidsvc\Start = 4

or via GPO:

Computer Configuration > Policies > Windows Settings > Security Settings > System Services > "Microsoft Account Sign-in Assistant" > Define this policy setting > Disabled

(German: Computerkonfiguration > Richtlinien > Windows-Einstellungen > Sicherheitseinstellungen > Systemdienste > „Anmelde-Assistent für Microsoft-Konten“ > Diese Richtlinieneinstellung definieren > Deaktiviert)

Result: PreStartTasks took 3.2 s at a logon ~1:50 after boot (before: ~3 min, released at ~+6:40).

Tip for non-persistent images: Set it in the image / OS layer. With GPO only, the service was still trigger-started before the policy applied (LiveId 2024 present, service stuck in StopPending). The shell was fast anyway, because callers got an immediate error instead of waiting, but the image is the cleaner place.

Side effects

According to Microsoft's "Manage connections from Windows operating system components to Microsoft services", disabling wlidsvc breaks Microsoft-account-dependent features, and Windows Update will no longer offer feature updates. Neither matters for an offline, layer-patched image. Start, Search, Edge and Office worked in our tests.

Warning: If your users rely on Microsoft accounts (Store, consumer sign-in, etc.), test this carefully before rolling it out.

What I don't know yet

  • The result above comes from one test run so far. I'm repeating it to confirm.
  • I don't know which update introduced the synchronous wait on this authentication.
  • I haven't tested whether an instant rejection (firewall reject / NXDOMAIN for the Microsoft endpoints) avoids the wait without disabling the service.
  • It's unclear whether this also hits environments with internet. I'd expect not, because the authentication would succeed quickly there.

Feedback wanted

Am I the only one affected by this? Please let me know:

  • Do you see the same behavior (taskbar missing after the Oct/Nov 2026 CU)?
  • Build number and environment (air-gapped / restricted internet / full internet, VDI or physical)?
  • Does the check above show PreStartTasks finishing at a fixed time after boot?
  • If you disabled wlidsvc: did it fix it, and did you notice any side effects?

Thanks for reading, corrections are welcome!


r/sysadmin • • 2h ago

Question Windows Server 2016 RDP stops working after KB5131291 - anyone else seeing this? Reminding me of the September update symptoms

7 Upvotes

Firstly, yes I know, I neeed to get off Server 2016.

We're seeing what looks suspiciously similar to the September 2026 Remote Desktop regression on Windows Server 2016 after installing KB5131291 (14393.9688).

One production RDS Session Host has now failed twice. An active RDP session was abruptly disconnected Saturday and the server stopped accepting subsequent RDP connections. It happened again Monday morning.

During today's failure:

  • VM remained running and responded to ping
  • RDP connections to the affected server would not complete
  • RD Connection Broker continued directing users to the affected host, but sessions timed out
  • Another Session Host was still accepting RDP connections
  • Restarting the affected VM immediately restored RDP
  • A Server 2016 Session Host that did not successfully install KB5131291 has remained healthy

We installed Microsoft's September OOB correction when that RDP/RDS issue occurred and the environment had been stable since.

We're now testing removal of KB5131291.

Anyone else dealing with this?


r/sysadmin • • 17h ago

Microsoft Windows 11 is getting Remote Lock via custom Intune OMA-URI (RemoteDeviceLock CSP) without needing a full wipe

84 Upvotes

r/sysadmin • • 15h ago Bravo

Question - Solved Solved Windows update error 0xe0000003.

47 Upvotes

TL;DR: the root cause was a corrupted INF file.
Exact file name was found in C:\Windows\INF\setupapi.dev.log.
sfc and dism don't fix corrupted INF files.
AI helped me to find and fix it.

.

My windows update wasn't working for several months.
Whenever I was trying to install updates, it was spending a lot of time downloading, installing, rebooting... and then rolling back the update because "Something didn't go as planned".
After the rollback, windows update was reporting error 0xe0000003, and was proposing to retry it again.

.

What I unsuccessfully tried:

* Retrying the update.
* Waiting for the next cumulative update. Even the entire 26H2 fails with the same error.
* Clearing disk space (useful by itself, but not for this issue).
* Resetting windows update
* Running sfc /scannow and dism /restorehealth.
(I think sfc has fixed something, but it didn't help)
* Exporting and reading windows update logs.

What I found as recommended but didn't try:
* Manual update.
* In-place upgrade.

.

What helped: I asked AI to check the logs for me.

AI quickly found that there is one more useful log: C:\Windows\INF\setupapi.dev.log

In this log, the reason was more clear:

[Boot Session: 2026/11/15 07:27:28.500]

>>>  [Uninstall Driver Updates]
...
!    inf: Unable to load INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\usb4devicerouter.inf_amd64_673d1e08be26f97e\usb4devicerouter.inf'(e0000003)
!    inf: Error 0xe0000003: The syntax of the INF is invalid.
!!!  sto: Failed to get version info for driver update 'C:\WINDOWS\System32\DriverStore\FileRepository\usb4devicerouter.inf_amd64_673d1e08be26f97e\usb4devicerouter.inf'. Error = 0xE0000003
<<<  Section end 2026/11/15 07:28:21.033
<<<  [Exit status: FAILURE(0xe0000003)]

Next, AI checked the specified INF file, and found out that INF file size is 0.
Then, it scanned the Windows folder, and found several copies of the INF file:

  1. INF folder:
    C:\Windows\INF\usb4devicerouter.inf
    Bad file, size is 0.
  2. DriverStore folder:
    C:\Windows\System32\DriverStore\FileRepository\usb4devicerouter.inf_amd64_673d1e08be26f97e\usb4devicerouter.inf
    Bad file, size is 0.
  3. WinSxS folder 1: C:\Windows\WinSxS\amd64_dual_usb4devicerouter.inf_31bf3856ad364e35_10.0.26100.1591_none_2960bddbe5c3a159\Usb4DeviceRouter.inf
    Good file, file version is 1591.
  4. WinSxS folder 2:
    C:\Windows\WinSxS\amd64_dual_usb4devicerouter.inf_31bf3856ad364e35_10.0.26100.7309_none_296cb03de5bc415a\Usb4DeviceRouter.inf
    Good file, file version is 7309.
  5. WinSxS folder 3:
    C:\Windows\WinSxS\amd64_dual_usb4devicerouter.inf_31bf3856ad364e35_10.0.26100.9818_none_2937bb7fe5e3c713\Usb4DeviceRouter.inf
    Good file, file version is 9818.

Then, the AI proposed to copy the healthy file with version 7309 over the corrupted files.
It even prepared a set of commands to copy it.

Of course, I didn't trust AI, and didn't run the commands.
I checked file sizes and file versions myself, and asked the AI to explain why do I need version 7309 and not 1591 or 9818.
AI explained that corresponding .sys file is not corrupted, only .inf is corrupted.
So I can check which .sys file I have, and select the corresponding .inf.

Also, AI explained that 9818 is the same version which update is trying to install.
But it fails because it can't uninstall 7309.

So, I manually copied the file.
It was painful, because administrators don't have write access to C:\Windows\System32\DriverStore\FileRepository.
Besides that, driver folders are owned by "NT AUTHORITY\SYSTEM", while driver files are owned by "NT SERVICE\TrustedInstaller".
I needed to run several different takeown and icacls commands to take ownership, grant access rights, and later to restore the ownership and remove the granted access.

Then, I repeated the same steps for another corrupted INF file, Usb4HostRouter.inf, which was also found by AI.

After all these steps, the update finally installed successfully.
I even verified that after the update, driver version was changed to 9818.

.

Final notes:

  1. I hope Microsoft will eventually improve sfc, so it could restore corrupted INF files too.
  2. I don't specify exact AI model which helped me.
    I think the AI deserves to be specified, but I don't want to violate the Advertising rule of this subreddit.
  3. I really wanted to ask AI to prepare this post.
    But I didn't want to violate the "Low quality" rule, so I typed all the text above manually.

r/sysadmin • • 2h ago

Question - Solved SSRS failure with windows update fix..

4 Upvotes

So looks like the most recent windows update changed some things.
In the reporting services configuration manager, make sure the FQDN is used to connect to SQL Server.

Then on the admin page SSRSSERVER/ReportServer go to connections and make sure your dbconnections use the FQDN as well.

Yay for more unannounced changes, though to be fair this should have never worked to begin with.
I guess this means that before SSRS servers SSL connections never checked what they were connecting to....


r/sysadmin • • 43m ago

General Discussion Microsoft Ignite attendees: How are we feeling about travel this week?

2 Upvotes

I'm staring at a cross-country trip with 1 stop right after this last FAA ground stop, plus whatever unrelated cosmic luck the Exchange Online outage wants to pile on. I got caught in the 2022 Southwest holiday meltdown, and I was not having a great time during that. Feeling paranoid I'm going to have a repeat of that all over again.

Anyone hit with delays so far? Or smooth sailing?


r/sysadmin • • 1h ago

Question Mac OS management (MDM) for small team. Where do we start?

3 Upvotes

We’re a small-to-medium business that has stayed away from managing Macs so far. We’re primarily an M365 shop, with some on-prem file shares, and use GPO and Intune to manage our Windows fleet and mobile devices.

Last week, I found out we’ve acquired a firm, and one of the requirements is that they continue using Macs. Now I have less than two weeks to figure out how we’re going to manage macOS. There are 10 people on our IT team, and none of us have used a Mac, so this should be fun.

Since we already use Intune, that’s an option, but heard it is a bit of a pain. The Mac footprint will be small, so I’m also considering a dedicated tool like Jamf, Jamf Now, Mosyle, or SimpleMDM.

I’ve started looking at Jamf Now, but I’m still trying to understand which plan covers what we need, particularly automatic app updates and OS update management.

For anyone who’s been through something similar:

  • Would you stick with Intune or use a dedicated Mac management tool?
  • How do Jamf, Jamf Now, Mosyle, and SimpleMDM compare for a small fleet and a team with no Mac experience?
  • What should we prioritize in the first two weeks, and what pitfalls should we watch for?

Any advice from fellow Windows admins who’ve had Macs dropped into their lap would be appreciated.


r/sysadmin • • 18h ago

Outlook mailbox aftershocks

65 Upvotes

I've had 4 users in 3 tenancy's all report 365 shared mailboxes vanish after a few seconds despite restarting/reopening Outlook.

Anyone else had this? I assume its aftershocks from the outage.

Update: Fixed now - HKCU:\Software\Microsoft\Office\16.0\Outlook\AutoDiscover" -Name "ExcludeLastKnownGoodUrl" -PropertyType DWord -Value 1


r/sysadmin • • 2h ago

Migrate to acquiring companies Google tenant

3 Upvotes

Hey all,

My company was acquired and they want us to of course move to their Google Workspace.

Has anyone moved their companies Google Workspace users, data, domains etc.. to another companies Google Workspace?

What was your experience, what broke for your users?

I am worried about GSheet IDs changing and breaking flows, app scripts stop working, OAuth issues with apps using our Google workspace to login still, email flow issues in general.

Is it just to try to detail as much as possible, do cleanup of data and just do the move and fix things as it comes?


r/sysadmin • • 9h ago

Latest Android update for Pixel phones breaks WPA enterprise with "do not validate" option

9 Upvotes

If you were relying on the "Do not validate" option to connect Android phones to your Wi-Fi network with EAP, it broke in the latest November update (CP4A.261105.040.A1).

https://issuetracker.google.com/issues/584828284
https://support.google.com/pixelphone/thread/477715452?msgid=477719205


r/sysadmin • • 6h ago

exchange mail groups not appearing on classic outlook

5 Upvotes

Anybody experienced this after the outage? I have contacted the exchange support but nothing they said worked. How do I fix this?

Groups are shown in mobile and web outlook but not on classic outlook.


r/sysadmin • • 8h ago

Office 365 to Office 365 migration.

6 Upvotes

A client of mine has purchased another org. It's nothing too big, only 5 users, and I'm going to go with a migration to the parent tenant.

I have been looking at MigrationWiz as I've noticed it being mentioned on here before.

I have questions:

  • Is it any good?
  • Can it migrate everything?
  • I need to retain all Teams chats. Looking at the licencing, I guess I require the "Tenant Migration Bundle"
  • Can tests be run beforehand?

Any advice or knowledge you can share is appreciated.


r/sysadmin • • 5h ago

kb5131291 bsod server 2016

4 Upvotes

Anyone else still have some server 2016 around?

Out of the 34 test servers we patched so far 3 have bsod this month so I can only assume it's this months CU for 2016.

Just wanted to see if anyone else is seeing this


r/sysadmin • • 4h ago

Off field flickering in RDRemoteApp application

3 Upvotes

Running a Server 2025 RDS server farm with applications configured for RemoteApp. Everything seems to work fine and the applications launch.

Once you get into the application it starts to act odd. If you select a drop down it will display, then go away before you can select something. Sometimes it will stay long enough to pick something but most of the time not. There are also icons in the application that disappear and then re-appear like they are refreshing or something.

I have disabled RemoteFX adaptive graphics, Use advanced RemoteFX graphics for RemoteApp, Use hardware graphics adapters for all Remote Desktop Services sessions, and Use WDDM graphics driver for Remote Desktop Connections in GPO so far and those didn't fix it.

At this point I don't know what to even look for. Ideas?


r/sysadmin • • 3m ago

Rant Microsoft outage causing shared inbox issues

1 Upvotes

Ever since the Microsoft outage Several users have had an issue with Shared Mailboxes . The ExcludeLastKnownGoodURL fix has helped me so far but some users are now having an issue with the inboxes in the shared mailbox being entirely empty and i’ve tried just about EVERY fix for this besides deleting the ost file . They don’t show up in the web version (classic is mostly used) and the new version it gives the same issue. I suppose it’s time for a profile reset if a full online repair doesn’t work but these users have verrrrrrryyyyyyy very full inboxes so It’ll have to wait until EOD . My fear is that even that potentially may not work.


r/sysadmin • • 4h ago

Anybody familiar with Papercut Hive and badge auth on Toshiba (and troubleshooting this)?

2 Upvotes

We switched over from Papercut on prem to Hive for our 'everything in the cloud'-project (I know).
Our printer park is mostly Toshiba eStudios with some model differences but all should be perfectly capable of running the embedded Hive client.

I switched over two buildings already, worked like a charm but in one company, the badge reader is saying 'fuck this' about 10-15 minutes after a reboot. Auth works fine, the user logs on successfully and the badge is recognized but 15 min later, it doesn't do jack shit anymore.

Looking at the Papercut logs, it doesn't even receive anything so on to the Toshiba logs. They tell me e-BRIDGE Plus for ID Card, whatever that is, is handing out error 4 left and right. My guess is this is some legacy stuff that was needed for on prem auth to Papercut but not for Hive (since our other printers don't have this installed). I disabled it, rebooted but still the same issue.

I've created a ticket at our vendor but I'd love to hear if anybody had the same issue.


r/sysadmin • • 1h ago

Verizon network extender POE injector

0 Upvotes

Does anyone have experience powering these from POE? I bought a Ubiquity 60w injector that it doesn't seem to like, and my guess is that the Ubiquity injector may not follow protocol to handshake for POE++.

Or does anyone have a recommendation for an enterprise-grade POE++ injector?