Forum Widgets
Latest Discussions
Noob needs help with RDP Services
I am new to Windows server management. I setup a 2019 Server in a VM (Hyper-V). I installed the licenses we got for RDP from MS after installing the Remote Desktop Services. I am getting an error about Remote Desktop Licensing Mode is not configured. Tells me to use Server Manger to specify RD Connection Broker. Either I neglected to install it or configure it, not sure. Articles I find say go to Server Manager -> Remote Desktop Services -> Overview... BUT, that tells me I am logged in with a local account but must use a domain account to manage servers and collections. Again, not using a DC. This server is not part of a domain. We do not run AD internally only AzureAD online. We have 1 program we still run internally and users RDP to it. Should I remove the service and reinstall? What about the licenses I added already? How to I keep them? Any assistance will be greatly appreciated... JJuJuBeeOct 08, 2025Copper Contributor58Views0likes2CommentsLDAPS and Certificate Creation
Hi, I've been asked to setup secure LDAP and convert all of our LDAP services to LDAPS. Something totally new to me, so I've been trying to teach myself. One issue I've run into is I'm not finding much information on how to create the secure certificates, so I'm looking for guidance. An ex-colleague stood up a certificate authority server (CA) and an intermediate certificate authority server (IA). Currently, the CA is powered down, which seems to be a best practice. The IA server is up and running, however, when I go to my domain controller (DC) and look at the Local Computer\Personal\Certificates section I do see a certificate, but it was issued by the CA and expired last summer. Shouldn't that certificate have been issued by the IA? How do I go about issuing certificates for this and other purposes, like all of the web-based control systems in my network like vCenter that complain about not being secure when I log into them? I've been searching for tutorials on the subject but only seem to find tutorials on how to install it, not how to use certsrv to issue and renew certificates. Does anyone know of any tutorials or walk-throughs like this? Thanks in advance!lkublerOct 08, 2025Copper Contributor71Views0likes3CommentsHyper-V: How do VMs communicate with external?
Simple scenario: VM --> vNIC --> vSwitch (external) --> physNIC --> physSwitch The vNIC assigned to the VM has MAC address aa:aa:aa:aa:aa:aa, the physical NIC (physNIC; the vSwitch of type external is connected to it) has bb:bb:bb:bb:bb:bb. What mechanism ensures that when the VM sends a network packet to the external network (the physical network connected to the physical switch physSwitch), the MAC address of its vNIC (aa:aa:aa:aa:aa:aa) is used, and not the MAC address of the physNIC (bb:bb:bb:bb:bb:bb)? In other words: what makes physSwitch "see" aa:aa:aa:aa:aa:aa when the VM communicates to an external endpoint?ahinterlOct 08, 2025Brass Contributor70Views0likes1CommentISO version reporting
Is there a standard way in which the Windows installer ISOs can be interrogated for which version of Windows is on them? This is a bit convoluted so I'll explain the use case. When installing W10 on one of the last generation of x64 Apple Macs, the Boot Camp installer will take the ISO and prepare it by injecting drivers - particularly that for the T2 security chip which handles the first part of the boot process and is the storage controller, among other things. With W10 going out of support (and W11 not really an option due to the hardware requirements) I have been looking at trying to install one ofthe W10-based server versions instead. These are obviously very similar in structure and would probably install and work from a technical standpoint - but if I try it the Boot Camp installer reports that the ISOs aren't Windows 10, and won't proceed. I'm basically looking to clarify whether there is any minor editing of the ISO (or files on it) which can be done to convince Boot Camp that actually this is W10. Anyone know? ThanksDavidYorkshireOct 08, 2025Iron Contributor61Views0likes1CommentPowerShell counterpart for Failover Cluster Manager "Live Migration Settings"
In Failover Cluster Manager, there's "Live Migration Settings" where I can define what cluster networks I want to carry live migration traffic. Even after some research, I cannot find a PowerShell cmdlet that lets me do the same...ahinterlOct 08, 2025Brass Contributor71Views0likes1CommentDNS Server cannot lookup domain AWS
Hi Everyone, I have an issue with the DNS service on Windows Server 2019. I have a CNAME record pointing from an internal domain to a domain hosted on Route53. However, this record frequently returns an 'unknown host' error. My server is already connected to the internet, and the record has a TTL 60. Please help me with this case.DucTranOct 08, 2025Copper Contributor61Views0likes1CommentImplementing LAPS
Translated with google Good morning, in the test environment I am trying to activate the LAPS features. The activation seems to have been successful. From the computer that acts as DC in AD it shows me the DSRM user password. While from the computer account of the test PC for LAPS no account or password is displayed. Obviously I created a GPO for the application of the LAPS parameters I have already restarted the PC several times and performed a GPupdate /force What can I check to have LAPS active on the client too? This is the data of the test network PC: W11 Pro 10.0.26100 build 26100 Server: W2025 srv Datacenter 10.0.26100 build 26100 Domain functional level 2025 Forest functional level 2025 ----------------------------------------------------------------------------------------------------------------- Buongiorno,in ambiente di test stò provando ad attivare le funzionalità LAPS. L'attivazione sembra essere andata a buon fine. Dal computer che fà da DC in AD mi fà vedere la password dell'utenza DSRM. Mentre dall'account computer del PC di test per LAPS non è visualizzato nessun account e nessuna password. Ovviamente ho creato una GPO per l'applicazione dei parametri LAPS Ho già riavviato più volte il pc ed eseguito un GPupdate /force Cosa posso verificare per avere LAPS attivo anche sul client? Questi i dati della rete di test Pc: W11 Pro 10.0.26100 build 26100 Server: W2025 srv Datacenter 10.0.26100 build 26100 Livello funzionale del dominio 2025 Livello funzionale della foresta 2025badog1Oct 08, 2025Copper Contributor52Views0likes1CommentWindows 2022 server to Windows 2025 Active directory migration
Hi In the lab I had 2 servers dc1 which is Windows 2022 and dc2 which was 2025 server. I transferred all roles from 2022 and this was working perfect but then I made one mistake by demoting dc1 2022 using GUI server and looks like that took out whole domain dc2 2025 has all the roles however when I try to open Active directory users and computers this is what i get Naming information cannot be locateed because the specified domain either doesnt exist or couldnt be contacted This is when I try to open Active directory users and computers. Interestingly enough in my workspace I just shut down domain controller that i want to decomission and then cleanup metadata but in this instance i wanted to try demote domain controller and this is the process that took domain out Now I dont have backup all I have ntds dit file and I am not sure whether it is possible to restore domain with just this file dc2 is still domain controller but even netdom query fsmo says no domain controllersdaliborazureOct 08, 2025Copper Contributor115Views0likes1CommentPassword change error message too generic on Windows Server 2025 domain
Hi everyone, In two different production environments running on Windows Server 2025 (fresh Active Directory installations), users reported an issue when trying to change their password via Ctrl+Alt+Del → Change a password. If the new password doesn't meet complexity requirements, the system returns only a generic error: "Unable to change the password at this time." There’s no indication that the failure is due to the password not meeting policy requirements (length, complexity, history, etc.), which creates confusion and unnecessary support tickets. In previous environments running on Windows Server 2016 or 2019, the error message was more informative, clearly stating when a password was too weak or did not meet domain policy. Is this generic message a known change in Windows Server 2025? Has anyone else encountered the same issue? Is there any way to re-enable the more detailed error descriptions? Thanks in advance for any insight!DanieleCapuanoOct 08, 2025Copper Contributor248Views0likes1Comment
Resources
Tags
- Windows Server2,204 Topics
- Active Directory823 Topics
- management385 Topics
- Hyper-V330 Topics
- networking317 Topics
- security288 Topics
- storage213 Topics
- clustering151 Topics
- powershell147 Topics
- AMA102 Topics