SRV 2022 WDS - Can't import Realtek NIC Drivers
hello, i'm using windows deployment services (WDS) on my windows server 2022. many clients (windows 10 and windows 11) have a "Realtek PCIe GbE Family Controller" as onboard NIC. if i get the required driver from ex. HP or DELL i can't import it into my WDS server (error code:0xC10408A6). even the driver from the microsoft catalog won't import. normally i would get it from realtek homepage, but this driver won't import either. a friend of mine has a WDS on a windows server 2019. he can import the driver from the realtek homepage an it works fine. what can i do? the error description says that the cause for failed packages includes unsigned x64 driver-package (it's signed), network connectivity (it's fine) and package corruption (but it works on server 2019). my 2022 server has the latest windows updates.
Windows Server 2022 Unable to Simultaneously Collect and Forward Events
We have a scenario where we are using a single Windows Server 2022 OS as a WEC, collecting events from multiple devices across the network. The same server then acts as a client, forwarding these events onto a SIEM tool that acts as a WEC. Essentially the Windows Server is an aggregator that funnels logs to the SIEM. This setup works fine with a Server 2019 OS. However in Server 2022 the upstream forwarding will fail intermittently with Event ID 103 "Subscription was unsubscribed" messages. This has been tested across 3 different environments (completely different ADs and infrastructures). Please note we have followed the steps in: https://learn.microsoft.com/en-us/troubleshoot/windows-server/admin-development/events-not-forwarded-by-windows-server-collector for the 2019 server. The SDDL matches these recommendations already in 2022, but we have repeated the steps on the 2022 server to test the effect and it has made no difference. I have also checked https://learn.microsoft.com/en-us/windows/application-management/svchost-service-refactoring However neither article acknowledges Server 2022. The SACL permissions for WinRM and the Event Collector service match those specified in the first article and I can see no further reason for this behaviour. Has anyone else come across this problem, or can provide guidance on the recommended WinRM SDDL/Service split configuration to support this setup on Server 2022?
HP ProLiant DL120 Gen9 - installation Windows Server 2022
Hello everyone! Im sure the answer is yes, but I want to be safe about the answer. We have a HP ProLiant DL120 Gen9 with a Intel Xeon CPU E5-2620 v4 and 32GB RAM. I'm 99,9% sure that I can install there without problems and use Windows Server 2022. I can't think of anything why server 2022 should not run on this machine, but as I said, I want to be 100% sure. Now - Can I install and use without doubts? 😄 Thank you for answers! Kind regards, Goodfred
Unable to restore 2022 Domain Controller from Windows Backup System State
I am trying to test restoring a Windows 2022 DC and can't get it to work. I have backed a test DC using Windows Backup and selected 'System State' (I have also tried using a full backup with the same outcome). I am trying to restore to a isolated system (as this is just for DR validation). On the isolated system I boot into AD recovery mode, run the windows backup, select restore (trying both authoritative and non-authoritiative) and let it run. It completed with no issues and once it reboots it takes me to the logon screen. This is where the issue is. I can't log in. Any account I try it give me a “We can't sign you with this credential because your domain isn't available”. Any suggestions are appreciated.Server 2022 boot loops after Hyper-V role installation
After enabling the Hyper-V role on Windows Server 2022 on a Intel NUC6CAYH with Celeron Processor J3455 the unit goes in a bootloop (recovery). This unit previously had Windows Server 2019 installed and before that even Windows Server 2016 and both worked without issues with Hyper-V role installed When using the en-us_windows_server_2022_x64_dvd_620d7eac.iso (RTM release) iso I am able to install Hyper-V role, but when installing any cumulative updates afterwards it goes into this boot loop as described above, only solution is to start in safe mode and the Hyper-V role installation is rolled back. (or in revovery set hypervisorlaunchtype=off) I have found out this seem to be related/similar to be able to enable the Core isolation toggle (which is partly based on virtualization as well) on NUC6CAYH (Apollolake) Steps i tried: 10.0.20348.169 (RTM) (Clean install) Install Hyper-V Role Successful Core isolation toggle Successful 10.0.20348.230 (September ISO) (Clean install) Install Hyper-V Role Unsuccessful Core isolation toggle Unsuccessful ----------------------------------------------------------------------------------------------- 10.0.20348.169 (RTM) (Clean install) Install Hyper-V Role Successful Core isolation toggle Successful 10.0.20348.230 (KB5005575) (Update) We couldn't complete the updates Undoing changes Don't turn off you computer As far as i read the processor meets the minimum requirements, eg: 1,4 GHz 64-bit processor Compatible with x64 instruction set Supports NX and DEP Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW Supports Second Level Address Translation (EPT or NPT) CoreInfo excerpt Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Intel64 Family 6 Model 92 Stepping 9, GenuineIntel Microcode signature: 00000046 VMX * Supports Intel hardware-assisted virtualization X64 * Supports 64-bit mode NX * Supports no-execute page protection CX16 * Supports CMPXCHG16B instruction LAHF-SAHF * Supports LAHF/SAHF instructions in 64-bit mode PREFETCHW * Supports PREFETCHW instruction CoreInfo -V excerpt Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Intel64 Family 6 Model 92 Stepping 9, GenuineIntel Microcode signature: 00000046 VMX * Supports Intel hardware-assisted virtualization EPT * Supports Intel extended page tables (SLAT) Anyone can explain why this works fine on RTM, but won't work after installing any cumulative updates as that makes no sense to me?