Forum Widgets
Latest Discussions
Servers not rebooting following update (WSUS)
Has anyone else encountered an issue with servers sometimes not rebooting straight away following an update installed via WSUS? It sits at restart pending for 24 hours, until the next update check is due, then reboots. This is particularly an issue with terminal servers because (for reasons best known to Microsoft), these offer ordinary users the option to update and restart (under normal circumstances, only an admin has the restart option visible). so there is a whole day where one person could inadverteltly reboot a terminal server, thereby potentially causing others logged in to lose what they are working on. I've trawled through the event log on an affected server, and I can't see any clear reason why it doesn't reboot immediately on all occasions (with some updates it does reboot - this behaviour is not consistent). The affected updates seem to be .NET monthly cumulative ones, but I can't say for sure whether it's only them affected, nor is it clear whether only terminal servers do this (I hope to clarify this with testing over the next few weeks). However, either way it's the terminal servers which are the problem - the other servers are only accessible by admins, who know not to reboot them during working hours unless really necessary). Thanks
Activate Server 2025 with 2022 retail key
I have a retail key for Windows Server 2022 standard edition. I'm rebuilding from scratch on new hardware and have installed Windows Server 2025 standard edition evaluation on the new hardware. If I try to activate Server 2025 with my 2022 license key, I get the error 'The product key you entered didn't work. (0x80041014)' Shouldn't this work? ThanksNew server 2022 not connecting properly
I have a 2012r2 DC to which I added a new 2022 server. The server manager on the DC reports That the RPC server is unavailable, and that the target server name can not be resolved. The firewall has incoming ports 5985 and 5986 enabled. I have not installed AD yet on the new server DC1 I have been going down rabbit trails for longer than expected, what should I be looking for?Windows Server 2025 Terminal Servers - start menu pinned icons
I'm designing the config for some terminal servers running Server 2025. I want to pin specific icons to the start menu. In Server 2022 (or Windows 10), this was simply a process of setting up the reference machine how I wanted it, then Export-StartLayout -Path "C:\Export\MStartMenuLayout.xml" to generate the config file, whcih was then applied using the GPO Computer Configuration\Policies\Administrative Templates\Start Menu and Taskbar\Start Layout - this worked fine. On Server 2025 (and Windows 11), however, it appears that this doesn't work the same any more. Although the export command works, it generates a JSON file now rather than an XML. OK, so I saved the file with the JSON extension, and copied the old GPO, amending the name of the config file to point to the new one. However, it still doesn't work and this documentation: https://learn.microsoft.com/en-us/windows/configuration/start/layout?tabs=intune-10%2Cintune-11&pivots=windows-11 Would appear to indicate that it can only be done using Intune. If it was Windows 11 I could do that, but as this is Server 2025 it isn't an option - Intune cannot manage server OSs even if I wanted to do that. Can anyone suggest any alternative methods of doing this? All I want to do is configure a common set of pinned apps for all users - I'm not bothered about configuring any other aspects of the start menu as the defaults are OK. Thanks
Error trying to demote via dcpromo legacy 2012 R2 DCs
Hi, I am in the process of trying to assist a customer upgrade their 2 x DCs from 2012 R2 to 2022. I have built the 2 x new 2022 servers and they are domain joined so I am at the point where I am about to demote the first 2012 R2 DC. At this point, I have Made sure that AD is healthy and there are no issues with replication Moved all FSMO roles to the other DC in this environment meaning that the DC I am working on is hosting nothing DNS is synching fine At a high level, everything looks like it should so proceeding to demote the first DC and got the following error during demote process through dcpromo.exe Error - The Active Directory Domain Services Installation Wizard (Dcpromo.exe) could not configure the computer account DC2$ on the remote Active Directory Domain Controller DC1.REC.LAN. Verify that the user running Dcpromo.exe is granted the "Enable computer and user accounts to be trusted for delegation" user right in the Default Domain Controllers Policy. For more information, see the resolution section of http://go.microsoft.com/fwlink/?LinkId=178406." Now I have looked at the MS KB and I can see from this in this environment, it could be exactly what is stated and / or the fact that the DC computer objects are protected from accidental deletion. The second option is easy to fix but given the error specifically calls out the "Enable computer and user accounts to be trusted for delegation" I wanted to look at this. The user account that was running dcpromo.exe at this time has Domain Admin membership and when I checked this right through whoami /all, it stated this right was disabled. Looking at the Default Domain Controller Policy (which is applying to the Domain Controller OU) BUILTIN\Administrators (which Domain Admin are a part of) should be getting this right assigned to them. Does anyone know what is going on here or can provide assistance? I can't raise a partner support case for the customer as it is affecting 2012 R2. From DCPROMO.LOG " 2/17/2024 13:12:36 [INFO] Removing Active Directory Domain Services objects that refer to the local Active Directory Domain Controller from the remote Active Directory Domain Controller DC1.REC.LAN... 12/17/2024 13:12:36 [INFO] Error - The Active Directory Domain Services Installation Wizard (Dcpromo.exe) could not configure the computer account DC2$ on the remote Active Directory Domain Controller DC1.REC.LAN. Verify that the user running Dcpromo.exe is granted the "Enable computer and user accounts to be trusted for delegation" user right in the Default Domain Controllers Policy. For more information, see the resolution section of http://go.microsoft.com/fwlink/?LinkId=178406. The error was: (5) 12/17/2024 13:12:36 [INFO] NtdsDemote returned 5 12/17/2024 13:12:36 [INFO] DsRolepDemoteDs returned 5 12/17/2024 13:12:36 [ERROR] Failed to demote the directory service (5)" Any help would be much appreciated.
window server 2025 ping problème
Bonjour, j'ai configurer mon serveur dns sous window server et quand je fais le nslookup de mon domaine j'ai des réponses mais le ping du domaine ne passe pas. que faire ? merci pour votre aide. Hello, I configured my DNS server under Windows Server and when I do the nslookup of my domain I have responses but the ping of the domain does not go through. what to do? thank you for your help.
