roles
2 TopicsVolume Activation role questions
We have a DC, running Server 2016 to decommission (call it old server). One of the roles it had was Volume Activation (VA). This is Active Directory based and the keys AD holds are both for clients (Win11) and servers (2016/19/22/25). I have removed the VA role from the server and tested with a server which I added to the domain and the OS activated successfully, so it looks like it is working. I noticed the _vlmcs SRV DNS record was not deleted and is still pointing to the old server. Since the old server is no longer having the VA role, is it safe to delete the DNS record for the _vlmcs SRV record? What else do I need to take into account? Thanks in advance34Views0likes0CommentsVBox: Remote Management / Add Roles & Features: The WS-Management service cannot process the request
Hello, I have installed Windows Server 2019 in a VirtualBox 6.1 machine. In the Server Manager I want to activate remote management and install roles like AD DS, but these error messages appear: Local Server \ Remote Management: "The WS-Management service cannot process the request because the XML is invalid." Add Roles and Features: "The WS-Management service cannot process the request. The service in configured to not accept any remote shell requests." I have created the VirtualBox virtual machine as "Windows 2016" and tried several options like EFI, I/O APIC, PAE/NX, nested VT-x, nested paging, NAT, bridged adapter. In the Local Group Policy Editor (Windows Server virtual machine), I have manually enabled "Allow Remote Shell Access" in Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Shell and run gpupdate /force. I have also installed Windows Server in VirtualBox on two other computers, but the same problem appears. I hope anyone can help me solve this problem. What has to be configured to make the WS-Management service work correctly?3.1KViews0likes3Comments