Forum Widgets
Latest Discussions
Certificate authentication with SID not working
When trying to login to Windows (against AD) using a certificate with the SID extension present in the certificate, it will not work if the SAN UPN is missing in the certificate. The error message "Your credentials could not be verified" will be displayed. Changing the certificate template to include SAN UPN will make the login work as expected. Is it by design?SolvedJan LiikamaaOct 28, 2025Copper Contributor77Views0likes2Comments
Replacing our Server 2016 RDS with Server 2022 RDS
Hi All, I have a Server 2016 terminal server. I set it up a while ago obviously, and I have 10 2016 RDS CALS installed in the RD license manager. We are part of a domain, and I have a group policy assigned to our current RDS server with lots of user options like session limit, printer redirection, max profile size, etc. I created a new Server 2022 VM and installed the RDS role and all it's features. But for some reason, it doesn't appear to be configuring the services. I add the roles via Server Manager once installed, the computer reboots when the server comes back up, Server Manager starts and says the install is complete. But when I go to the Remote Desktop services section in Server Manager, I get this message: "A remote Desktop Service deployment does not exist in the server pool. To create a deployment, run the Add Roles and features wizard and select the Remote Desktop Services installation option." From looking around on the Internet, at step 3. there should be a configuration step where Server Manager starts and configures the RD gateway, license manager, etc. I also found some articles on the Internet about disabling IPv6 or making sure the server is a member of a domain. I've already tried those things and it's still not helping. I also removed all the Roles and readded, but it still behaves the same. The configuration step doesn't start on reboot and no RDS server. I also installed a web certificate and installed it on the server from my CA. Is there a better way to do this? I haven't worked with RDS in a long time. Here's some event viewer messages Event ID 1306 Remote Desktop Connection Broker Client failed to redirect the user domain\administrator. Error: NULL Event 102 The Remote Desktop Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections. Ensure that you have obtained a valid SSL certificate, and then bind (map) the certificate by using RD Gateway Manager. For more information, see "Obtain a certificate for the RD Gateway server" in the RD Gateway Help. The following error occurred: "259" Event ID 2056 The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. Pooled virtual desktop collection name: NULL Error: Logon to the database failed. Event ID 85 The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Ensure that there is network connectivity between the license server and AD DS. To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool.SolvedralvarezOESOct 09, 2025Copper Contributor87Views0likes2Comments
Updating PowerShell5 via WSUS - possible and needed?
Good day, not sure if its the right subforum. If not, please move. I have a couple of 2016 servers in a domain where I handle updates via WSUS. On the WSUS, in the tab Products and Classifications, PowerShell - x64 is check marked but PowerShell Preview - x64 is not. I guess this refers to PowerShell 7 and it works on the servers on which PowerShell 7 is installed. But the PowerShell 5 versions are not updated via WSUS. The PSVersion on some servers show PSVersion 5.1.14393.8062 which is not the most current. Is there a way to update PowerShell 5 via WSUS, how's the Product named in the tab Products and Classifications? Is it possible to update PowerShell 5 via WSUS at all ?Is there a need to update it at all? Best RegardsSolvedhauer94Aug 12, 2025Copper Contributor109Views0likes1Comment
Wireless secure Windows server 2022
Hello everyone, I am trying to implement ‘wireless secure’ in my domain. I have followed various guides and everything seems to be configured correctly, but I keep getting this error: Reason: Explicit EAP error received Error: 0x40420016 EAP reason: 0x40420016 EAP root cause string: Network authentication failed\nThe authentication method required to connect to the network is not available in Windows. EAP error: 0x40420016 I have verified that communication via AP-WLC-NPS is working correctly, but it is unable to authenticate via eap-tls. Do you have any suggestions? I have collected several logs, but many of them may not be necessary. Thank you for your support.Solvedfranga92Aug 11, 2025Copper Contributor110Views0likes1Comment
Server 2022 WMI Issues
Hi there, I have a Server 2022 with WMI problems affecting the server in a few ways. The server is a domain controller, RD Broker and hosts some files also. The server actually operates ok for the users day-to-day. I discovered the issue when opening AD Connect, getting an Invalid Class error message. When running various fundamental commands at the command prompt (e.g. tasklist) I get the same error. When looking at the WMI Control in Computer Management again - Invalid Class. I have tried various fixes found online such as verifying the WMI repository (it comes back as consistent) but I think I've reached a dead end. I don't want to restore the server from backup as I believe this issue has been ongoing for a couple of months before it was discovered. I can't get in to the Remote Desktop part of server manager to replace the certificate, and the certificate expires next week. Does anyone have any ideas please? Any help greatly appreciated, thanks. ChrisSolvedChri5reynold5Apr 14, 2025Copper Contributor297Views0likes2CommentsWindows Server 2025 DC Won't Install / Uninstall MSI packages, NIC Domain Category issue.
In the last week I have set up a Win 2025 Server Std Hyper-V host with 2 VMs, one being a domain controller. I have discovered that once the machine is promoted to a DC I can no longer install any .msi packages. .exe packages seem to work fine. My scenario: After setting up the VM (before promotion to DC), I installed my RMM package (.msi - NinjaRMM) and all was fine at that point. I can see and access the VM in my RMM console. After promoting the machine to a DC, I noticed later that the status in my RMM was offline or disconnected. I soon discovered this problem with installing / uninstalling packages. Somehow I was able to uninstall the NinjaRMM, but could not re-install it. Also when Ninja installs the agent it also installs Splashtop. At this point I cannot uninstall Splashtop. Using something simple like the Putty 64bit .msi for testing. Can't install that neither. Any .msi I have tried just hangs for about 30 minutes then times out. Main error code in the .msi log is 1603, which is supposed to be closely related to permissions, but I have found no issues with permissions. Check GPO and have found nothing there either. I have Win 2022 DCs in the same domain and have no issues installing / uninstalling these packages. Internet search has found similar issues, but no answers. Secondly, when rebooting the 2025 DC, the NIC initially gets assigned the Public network category. Disabling / Re-Enabling the adapter the Domain category is immediately assigned. Secondly, I attempted to create a PS script to restart the adapter at startup (task manager...set to run as SYSTEM), and while the tasks starts, it never runs the script. After working with ChatGPT it was suggested to change the script to have a simple one line command 'Exit 0' statment. That doesn't run either. Seems that this problem has relations to being run as SYSTEM, which I believe is also related to the install issue. Internet searches found others stating they have encountered similar issues, but no resolutions. For the install issue, some have stated that if they demote the DC to a member server, .msi installs run successfullly (which seemed to be my case before I promted it a DC). I haven't tried demoting it to a member server, but I did spin up a second Win 2025 Server VM, joined it to the domain and at that point I have no issues installing / uninstalling anything...including .msi packages (oops, I did state this in an earlier paragraph). Tried contacting MS. Seems with no support plan they won't talk with me. That's awesome, you pay for a product, and they won't provide support for it. Such a joy. Hoping that someone might have seen these issues as well. LThibxSolvedlthibxMar 14, 2025Brass Contributor2.8KViews0likes4CommentsNo support for Protected Users in Microsoft Entra Domain Services?
I have been loooking into mapping best practices about configuring hardening / tiering model from on-premises Active Directory to Microsoft Entra Domain Services (MEDS). I'm well aware that MEDS is NOT a replacemenet for AD DS and have many restrictions and missing features, but that does not stop me from wanting to make it as secure as possible for member servers to be joined to. Since MEDS is a PaaS in Azure, deployed from within Azure and managed in another way than Active Directory, of course there are different ways of implementering a good tiering model. In my study I wanted to see if I could enable Protected Users feature (join users to Protected Users Group). However I find this group to be present but not possible to add members to (feature greyed out). I have a member server in the MEDS instance and have installed AD DS Tools. My user is member of AD DDS Administrators group. I would like to know if anyone have some knowledge on the subject to share?Solved115Views0likes1Comment
Resources
Tags
- windows server2,218 Topics
- Active Directory830 Topics
- management386 Topics
- Hyper-V333 Topics
- networking321 Topics
- security291 Topics
- storage213 Topics
- clustering152 Topics
- powershell147 Topics
- AMA102 Topics