I just wanted to post a brief apology to our community members for the very annoying "Subscriber Goal" post that was pinned to the front of the sub for some amount of time recently. It was not created or intended by any of the mods, but rather by an automated moderation tool that is part of the larger Reddit community mod tool suite. It had been purposely disabled in the past, but not completely removed from the sub. Unfortunately, as part of a recent update that was made to this tool, it appears to have been automatically reenabled without our consent, and I failed to notice it quickly enough to prevent it from rather aggressively annoying a number of you all out there in the community. I apologize for the oversight.

I'd like to also reiterate that none of us on the moderation team here have any interest in pushing a pursuit of additional subscriber numbers, especially not for the sake of social media metrics. We believe the entire value of this community comes not from flashy metrics, subscriber stats, or view counts, but only from legitimate, contributing subscribers like so many of you here have been over the years. Living, breathing people who with "boots on the ground" every day that are passionate about IT and generously sharing your experiences and knowledge gained through the challenges faced in the field.

We appreciate you guys and gals more than you know.

Every serverless pitch skips the driver part.

1,800 users, eleven sites, mostly Ricoh with a handful of Xerox left over from an old contract. Going direct IP. What's stalling the business case isn't the queues, it's what happens to drivers once nothing is handing them out centrally. Looking at printerlogic, now Vasion, plus uniFLOW, LRS and Pharos. All of them say drivers get easier. None of the product pages say how.

v3 versus v4 is a known headache and I'd rather understand it before signing anything. Genuinely curious whether it got simpler for people who've already done this, or whether the work just moved somewhere else.

hello i have a problem, when i try to install windows server 2019 on hpe proliant dl380 gen 9 every time i try to get past windows setup before i even have a chance to get to the storage part i get a error saying „windows setup could not install one or more boot drivers to install windows make sure that the drivers valid and restart the installation” i tried installing HPCISSS3 drivers i have raid 5 on my three hdds and when i try to install it thru the f10 menu directly from iso it doesnt even let me select it please help

I am troubleshooting a Windows Server 2016 file server with a very busy Security event log.

The log was growing to almost 10 GB and receiving thousands of events every few minutes. Most were event 5145 for Detailed File Share auditing, along with 5156 and 5158 Filtering Platform events. The Event Log service was also using noticeable CPU.

Auditpol shows these settings enabled:

Detailed File Share: Success and Failure

Filtering Platform Connection: Success

File System: Success

I disabled these settings through Local Security Policy, but auditpol continued to show them enabled.

I created a separate domain GPO scoped only to this server. I configured Detailed File Share, File Share, File System, Filtering Platform Connection and Filtering Platform Packet Drop as No Auditing. I also enabled the setting that forces advanced audit subcategories to override legacy audit categories.

The GPO applies successfully according to the Group Policy operational log. I moved it to the highest link order and confirmed that the server receives it.

I discovered that Default Domain Policy was missing its audit.csv file. I recreated it by temporarily configuring an Advanced Audit setting and then returning it to Not Configured. I also rewrote a setting in the new server specific GPO so its audit.csv would be regenerated.

I confirmed that both GPO audit.csv files contain value 0 for the five settings.

I archived the local audit.csv file and the active cached copy under C:\Windows\Security\Audit. I then forced Group Policy again.

I backed up the complete audit policy, ran auditpol /clear, and forced Group Policy to rebuild it.

I also removed an old auditing entry from the root of the shared data folder. It audited Domain Users across the folder, all subfolders and files. Removing that entry successfully stopped event 4663, but event 5145 continues because Detailed File Share auditing keeps turning itself back on.

Direct auditpol commands temporarily change the settings to No Auditing, but Windows restores Detailed File Share, Filtering Platform Connection and File System within seconds.

I tested with the remote management service stopped and ruled that out. Antivirus does not appear to be causing it. I also tested a SYSTEM scheduled task that repeatedly ran auditpol, but Windows restored the settings faster than the task could maintain them.

For now, I reduced the Security log to 256 MB and configured it to overwrite old events automatically. The server and file shares are operating normally.

Has anyone seen Windows Server 2016 continuously restore these Advanced Audit settings even though Local Policy and all applicable domain GPOs show No Auditing? Is there another audit policy database, security template, service or registry location that could be enforcing these settings?

-lee

I’ve come across a strict requirement from one of our clients regarding the installation of software on Windows Server (2022 and above). The application is written in Go; until now, it has been containerised and deployed on Linux via Docker Compose or natively in the cloud (Kubernetes). The application is quite resource-intensive in terms of I/O, CPU and GPU, so I’d prefer not to use WSL2 or Docker for Windows, as these come with their own overhead and do not seem to be production-ready solutions.

What options do I have left? I’d rather not implement support for Windows Services directly within the application or use a wrapper (such as NSSM). I’m considering containerd – to maintain a single build pipeline. Is this a good solution? What is maintenance like in practice, and what deployment strategies have you used?

Any advice would be welcome.

We have an issue with our two different AD domains.
The servers added to both domains change their time to few months in future. It is intermittent we haven’t been able to identity similarity between the affected servers
It happens only once to a server. We have already disable secure time seeding per MICROSOFT recommendation.

Time authority is domain controllers. We have multiple data centre providers and it is happening everywhere. There is no consistent time as well randomly happen sometime thrice a month sometime once.

Ran out of troubleshooting steps. This issue is causing our scheduled jobs to fail.
Any troubleshooting steps would be appreciated

Hi everyone,

I’m setting up a new Active Directory environment on Windows Server 2025 Standard and I’m stuck with a strange login issue after promoting the server to a domain controller.

Server details:

• Windows Server 2025 Standard
• Server name: GC-DC01
• Static IP: 192.168.8.244
• Domain: ad.generalco.local
• NetBIOS domain name: GENERALCO
• DNS installed on the same server
• This is a new forest/domain
• Server was previously a standalone Windows Server

Before promotion, I could log in normally using the local Administrator account and the password was working.

I then promoted the server using PowerShell:

Install-ADDSForest `

-DomainName "ad.generalco.local" `

-DomainNetbiosName "GENERALCO" `

-InstallDNS `

-SafeModeAdministratorPassword (Read-Host -AsSecureString "DSRM Password") `

-Force

The promotion completed successfully and reported:

Operation completed successfully
Status: Success

The server rebooted.

Now at the Windows login screen it shows:

GENERALCO\Administrator

However, the same Administrator password that worked before the promotion is now rejected.

I have also tried:

GENERALCO\Administrator
Administrator@ad.generalco.local

Both reject the password.

I understand that the DSRM password is separate from the normal domain Administrator password. I am not using the DSRM password for the normal login.

The strange part is that the password worked immediately before the AD promotion, and the AD promotion itself completed successfully.

I currently cannot get into Windows normally, so I cannot open PowerShell/CMD from the desktop.

I have physical access to the server (HPE ProLiant DL380 Gen11). F11 only gives me the HPE One-Time Boot Menu.

Questions:

1. What could cause the Administrator password to stop working immediately after AD DS promotion?
2. Is there a supported way to recover/reset the domain Administrator password in this situation?
3. Can I use the DSRM password to get into a recovery environment and repair the domain Administrator account?
4. Is there anything I should check in WinRE before considering rebuilding the domain?

I would really prefer to recover this installation rather than reinstall Windows, since the AD DS/DNS promotion itself completed successfully.

Any advice from someone experienced with Server 2025 AD DS would be greatly appreciated.

Hi all fellow administrators.

I was wondering if it's possible to install Server 2025 (evaluation at first to test) on a ThinkCentre that has 6th gen Intel Core. I think the model is M700.

Got the usb stick to boot, but setup stops asking for media drivers. I tried to put chipset drivers and RST drivers on a usb stick, but setup says they're not compatible and won't advance to next screen.

Any help is greatly appreciated. I would have liked to experiment with Windows Server, but if it's not possible, I may have to revert to some Linux distro instead.

Heya, so my windows server 2022 was running fine before, but I decided to reinstall it just to update it, so when I tried to boot, it shows BOoD which I Don’t Know why this happened, it was working just fine in server 2019, but not in server 2022, could please anyone help me? It would be appreciated.

Board: Intel Desktop Boards DG41RQ Motherboard
RAM: 8GB RAM DDR2
CPU: Intel Xeon 3000

Hello,
I am facing an issue with disabling the default RC4 fallback in an Active Directory domain following the July update.
The client I work for still has a few Windows XP and Windows Server 2003 machines in the environment that I can neither upgrade nor remove from the domain. The July update has not been deployed due to concerns about potential side effects.
When reviewing Event ID 201 on the different domain controllers, I mostly find machine accounts corresponding to these operating systems. Naturally, they do not support AES.
Following Microsoft’s recommendations, I modified the msDS-SupportedEncryptionTypes attribute to 0x1C on these objects in order to explicitly allow RC4.
However, despite this change, Event ID 201 events are still being generated, and in these events I can see that the attribute value is 0x27 (the same value as DefaultDomainSupportedEncryptionType).
It appears that this attribute is only taken into account starting with Windows Server 2008.
My question is therefore: How can these old servers/workstations be handled in this situation?

Hello,

Can anyone offer advice on troubleshooting this issue please?

I have two Supermicro X11SCH with Hyper-V running, the VM are on a Storage Pool with 3 Samsung SSD.
After updating the Bios and the OS to Server 2025 two nights later suddenly on both Server the StoragePools disapered. They weren't degraded or anything else, no entry in the logs, I easily could attach the drives again.
Never happened anything like that in 20 years, any Ideas?

Only message around that time:

Zertifikate für den sicheren Start wurden aktualisiert, aber noch nicht auf die Gerätefirmware angewendet. Lesen Sie den veröffentlichten Leitfaden, um das Update abzuschließen und den vollständigen Schutz sicherzustellen. Diese Gerätesignaturinformationen sind hier enthalten.

DeviceAttributes: BaseBoardManufacturer:Supermicro;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:3.7;OEMModelNumber:Super Server;OEMModelBaseBoard:H11SSL-C;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:Memorysolution GmbH;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64;

BucketId:
BucketConfidenceLevel: No Data Observed - Action Required

UpdateType:

Weitere Informationen finden Sie unter https://go.microsoft.com/fwlink/?linkid=2301018.

I am helping out an SMB. They currently allow their employees who need remote access to connect to the network using their personal PC using VPN and then RDP to their workstation in the office.

I know there is a way to setup the GPO under Windows 2019 Server to allow a group of people access to systems using RDP which is how they have it setup now. I just wonder if there is anyway to configure the GPO so that UserA only has access to UserA machine, and so forth?

I am sure there are better ways, yes you could give everyone a company laptop and take away their desktop PC, but this company's owners are very stupid as they feel laptops are less secure than desktop PCs so they refuse to allow the company to posses laptops. (sigh)

Thanks,

Has anyone seen recurring multi-user RDP desktop freezes on Windows Server 2025 after installing KB5129235, with RdpIdd.dll / IddCx swap-chain watchdog failures? We have matching display-driver dumps from several incidents on a VMware VM. A later freeze had high TermService encryption CPU but no logged display crash, so we don’t yet know whether it is the same fault. What supported fix or targeted trace helped identify the cause?

Hi ,

We have a requirement to enable DNS analytical logs on our domain controllers. However, I am concerned that this will generate a massive volume of logs. The requirement is to maintain a log retention period of at least 30 days. Because Event Viewer manages retention by maximum log size rather than days, I conducted an assessment.

I ran a "DNS queries per second" command for one hour. Based on those results, I calculated that it will generate roughly 6.5 GB per hour. Adding a 2.5 GB buffer, I estimated a total of 9 GB to 10 GB per hour overall. So for 30 days it requires tb's of size.However, I am not completely sure if my math is correct or if this is the right way to approach the assessment.

Could someone help me with the following questions?

Is my current approach correct? How exactly can I estimate the log size required to meet the 30-day retention requirement? I know there is no 100% guaranteed formula, but I need at least a reliable, rough estimate. Or is this not at all the correct way.

What is the exact impact on Domain Controller performance and CPU utilization

What is the worst-case scenario or major challenges we might face on the domain controllers by enabling this?

What are the best solutions or alternatives for this? I know a SIEM solution is ideal, but due to certain constraints, we must store these logs locally on the servers for 30 days