Search the Community

Server info: OS Name: Microsoft Windows Server2019 Standard OS Version: 10.0.17763 N/A Build 17763 Original InstallDate: 1/17/2020, 12:25:18 PM Having issuesinstalling cumulative updates. It seems to have installed defender and .NETupdates fine. But can't get the current (Win 10 (1809) and Server 2019 -Cumulative Update (64-bit) January 10 2023) or previous December update toinstalled. If I try it manuallyit fails with MSI failed with error code -2146498304. When I try it fromWSUS or Microsoft it fails with 2023-01 Cumulative Update for Windows Server2019 for x64-based Systems (KB5022286) - Error 0x800f0900 I have tried toreset windows updates according to the below KB. https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/additional-resources-for-windows-update Ran the SFC /Scannowand the DISM restore health commands The restore health command fails withError: 0x800f0954 In Googling allthese error codes I'm basically chasing my tail. Everything keepscircling around to the same thing over and over and nothing seems to work, andeverything fails The below is from the windows update log. [font=Calibri]2023/01/1311:00:13.1374595 7128 8128 Handler CBS called Error with 0x800f0900, [/font] [font=Calibri]2023/01/1311:00:13.1402237 7128 8128 Handler CBS called Terminate[/font] [font=Calibri]2023/01/1311:00:53.9164837 7128 7556 Handler Completed install of CBS update withtype=0, requiresReboot=0, installerError=1, hr=0x800f0900[/font] [font=Calibri]2023/01/1311:00:54.0648649 7128 7556 Handler * END * CBS Install[/font] [font=Calibri]2023/01/1311:00:54.6929704 3664 5204 Agent *FAILED* [8024200B] Method failed[CAgentUpdateManager::InstallUpdate:11739][/font] [font=Calibri]2023/01/1311:00:54.8788666 3664 5204 Handler Loaded state: cCompleteIterations: 1,pt: SelfContainedNoExpressPayload, nNextRequestID: 1.[/font] [font=Calibri]2023/01/1311:00:54.9012256 3664 5204 Agent LogHistory called.idUpdate={447FF6C5-74A0-4DFD-A497-9039E898E010}.200, resultMapped=800F0900,resultUnMapped=800F0900[/font] [font=Calibri]2023/01/1311:00:54.9131342 3664 5204 Agent Install updates CallerId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9132320 2116 4776 ComApi Install ClientId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9140489 2116 4776 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font] [font=Calibri]2023/01/1311:00:54.9143000 2116 4776 ComApi Reboot required = False[/font] [font=Calibri]2023/01/1311:00:54.9143085 2116 4776 ComApi Exit code = 0x00000000; Call errorcode = 0x80240022[/font] [font=Calibri]2023/01/1311:00:54.9143100 2116 4776 ComApi * END * Install ClientId = UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9146923 3664 1652 Agent WU client calls back to install call{36B49B40-ED6B-4C7D-A74A-D2CC913B7D67} with code Call complete and error 0 [/font] [font=Calibri]2023/01/1311:00:54.9149632 2116 6932 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font]

Hi All, Recently setup RD Web access and associated roles (Connection broker, session host, gateway, licensing) on a server 2019 x64 standard VM running on Hyper-V. Locally web access works fine with published apps launching and working perfectly. Onto the issue... can't see the web page externally through out smoothwall. I have included screenshots of our smoothwall port forward config and gateway settings. Any help will be much appreciated as we're under a lot of pressure to get this operational.

Good morning, I have a print server running on server 2019. The print spooler is not stable. It keeps restarting, the only way i have gotten it working is to set Subsequent Failures to restart the service. The service will restart between 3-5 minutes. during this time one can print no issues. I think its a corrupted or outdated print driver. The drivers that are in use range from 2018 - 2006. So yea i would say their are some really old drivers on their. I know the print spooler is crashing but i cannot find what exactly the cause it. the event viewer has not been much help i have posted the errors i see below. Is their a process to track down the driver? Everything i read online just said to update all the drivers but nothing about tracking the down the exact one that is causing it. Aside from having Techs do a Clean up on the server, Update Currently used drivers, Remove unused/old Drivers and delete old queues. If that does not work the only other thing i can thing od is to build a new server and install everything fresh and manually move printers over. Their are 78 drivers Their are 81 Printers Thoughts?? I see the below but those files don't exist, which is why i says "The print spooler failed to delete the file" The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms003.inf_amd64_9bf7e0c26ba91f8b.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms002.inf_amd64_4d944e2fb3bcc43c.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\ntprint.inf_amd64_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\prnms003.inf_x86_dd2fd5b05c3d8604.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_x86_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. I see this from time to time but it does not tell what the print driver is.... Document failed to print and was deleted because of corruption in the spooled file. The associated driver is: . Try printing the document again. Not much i could find out but about the below The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-636618257-2613738635-33974680-1377919\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable. I see this every 3-5 minutes... The Print Spooler service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. And yes i know about Cleaning out C:\Windows\System32\spool\PRINTERS but this is the not the case as it will stop while that is empty/ no jobs coming in. Thanks

We have recently promoted a 2019 Server to be a domain controller but it won't authenticate access to our EMC VNX datastore which we believe only supports RC4 Kerberos - is there anyway to enable RC4 Kerberos in Server 2019 as it appears to have been removed? (Using the IIS Crypto tool we can see the 2019 server does not have any RC4 ciphers) Access to the EMC VNX datastore works from 2012 and 2016 DC's. Access from the 2019 server to all other devices on the network also work (we can see these using AES encryption via the klist utility) I can see no documentation suggesting any changes around Kerberos in server 2019

I have eight new Windows 2019 servers to provide desktop virtualization for students, upgraded from 2012. My AD/DC is 2012r2 and the group policies that had help me lock down my previous RDS servers no longer work. Is there a GP update i can put on my 2012 server? I'm pressed for time and not sure if I can get the AD/DC upgraded to 2019 in time. Any suggestions

I'm trying to add a 2019 DC to my existing 2012r2 DCs, they've done the DRFS migration "eliminated" (and are all in the same state, dfs is happy with no errors) and now have sysvol_DRFS as the sysvol share on the 2012r2s When I go to add a new 2019 DC and promote it, it creates a sysvol NOT sysvol_DRFS and DFS will not sync correctly the new server. (dfs has a timeout error with new server, possible error) I've tried with a second (new) DC and I'm getting the same result... (it want to make a sysvol not sysvol_DRFS) what gives? The new server does create a sysvol folder with files in it, so it is syncing... so it is doing something. is sysvol_DRFS only for migrated servers? and it is the share name that is important not the location on a given server? Then why does dfs get upset?