Forum Widgets
Latest Discussions
Hyper-V can not be installed because virtualization support is not enabled in the BIOS
Win 2022 Datacenter as Hyper-V host Win 2022 Datacenter as Virtual Machine ... after latest Windows Updates (troublemaker KB5034439 who require resize of Recovery partition to be able to be installed successfully) ... on the VM ... is Unable to install Hyper-V Role because of the error "Hyper-V can not be installed because virtualization support is not enabled in BIOS". Very first error it was a different one and it was fixed by enabling extensions who was fixed via this commands /Hyper-V Host /Elevated PowerShell #List of VM Get-VM Get-VMProcessor -VMName <name> #Check Nested (Get-VMProcessor -VMName <name>).ExposeVirtualizationExtensions #Configure Nested Virtualization Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true #Disable Nested Virtualization Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $false ... but the error "Hyper-V can not be installed because virtualization support is not enabled in the BIOS" is very tough and I not yet find any solution yet. I'm convinced that they (MS) disable Nested Support via latest Windows Update, but it is only my personal opinion. I even update firmware to the Bios of Host machine and triple check the Virtualization boxes to be enabled but since no one change it it is the same. Anyone having some idea how to Enabled Nested Virtualization on Hyper-V Host Machine ?Public network on NIC instead of domain network
On a Windows Server 2025 Standard Edition, I have 2 NICs: a 10Gbps NIC and 1Gbps NIC. Both NICs have a static IP address, but only the faster 10Gbps has a default gateway. The faster NIC correctly identifies as the domain network but the slower NIC says it is on a public network. The DNS settings and suffixes are the same for both cards. I have another Windows 2025 server with the same setup but both NICs identify as the domain network. Any ideas on how to fix this? Thanks.
Untagged VLAN - Server 2025 Hyper-V
Hi, I have a strage issue and not finding a solution. Using Server 2025 with two node Hyper-V cluster. Most of the machines using VLANs which works fine. Some machines using no VLAN config. Which usually means the "Access VLAN 1" regarding our switch configuration. With Server 2019 this worked fine. With Server 2025 same NIC port, same server/NIC hardware "Untagged" VMs don't get any network connection. If I add a second NIC to the VM "Untagged" the NIC get immidiatly an IP address and has a proper connection. If I remove the first NIC, the second NIC stop working. It looks like something has changed with Server 2025 (maybe already with Server 2022). Do you have any idea what kinde of problem I have found? Thanks Jack
Deploying Multiple NPS Servers
I have been working on ditching our password-based WiFi with WPA2-Enterprise. On DC1 I deployed internal CA, NPS, and group policies that auto-request certs and deploy wireless network settings. Cisco AP is pointed to DC1 as the radius server. NPS has been registered in AD and wireless network policy has been created. Test laptops get their cert and connect just fine. It's working. For redundancy, I installed NPS on DC2. This NPS instance has also been registered in AD, and I imported the NPS config from DC1 to DC2 NPS. Cisco AP has DC1 as first radius server and DC2 as second radius server. If I stop NPS on DC1 to force the Cisco AP to authenticate against DC2, test laptops won't authenticate and connect. What am I missing? They're configured exactly the same (except DC1 hosts the CA...I was under the assumption the CA is AD integrated).
Demoting DC Windows Server 2019
Windows Server 2019 with Domain controller forest version 2016. When demoting our Domain controller XYDC01 in Site XY, it is the only DC and DNS in the site, but all other 20 sites have a DC with DNS. We get this error when demoting our DC. Active Directory domain controller appears to be the last DNS server for the following Active Directory-integrated zones: enterpriseregistration.jens.be If you demote this domain controller, you may be unable to resolve any DNS names in these zones. If you wish to proceed, specify the 'IgnoreLastDNSServerForZone' option. I have tested: #other DC and DNS server in other site Resolve-DnsName enterpriseregistration.jens.be -Server XXDC02 Test-NetConnection XXDC02-Port 135 Test-NetConnection XXDC02-Port 53 Get-DnsServerZone -Name "enterpriseregistration.jens.be" repadmin /syncall /AdeP All test have passed and succesfull. Replication scope = Forest Other DCs have DNS role Zone contains NS records for other DCs Zone exists on other DCs But still having the same issue when trying to demoteAdvice for replacing a Windows 2012R2 file server
We have a small company network that includes one Windows Server 2012R2 file server necessary to run Sequel for two server hosted business applications, file and print services for the user accounts and is also the Domain Controller for the Active Directory local forest and domain. Six Windows 11 Pro workstations are domain attached to the file server. The workstations all have a local user account and after domain attaching to the file server, a user.Acme user account with Administrator rights to their local computer. Each has its own 192.168.1.x static address and uses their domain user account with mapped drives to access the fileserver. The existing file server name is ACMEWS2012R2, local public static ip 192.168.1.12, DNS Domain Acme.LAN, Netbios name ACME, local accounts are located in \Users\username, and runs SQL Server Express 2012 with default MSSQL database name and mixed security using the SA with password credentials. The new file server will be using Windows Server 2022 (the company apps are not yet certified for 2025) and SQL SVR Express 2022 and I am looking for information about what configuration decisions I can make to hopefully minimize the need to install new user accounts on the workstations, copy all the user folders between users accounts and reinstall applications. My understanding of Domain security is limited, knowing just enough to get workstations attached and properly accessing the file server SQL based applications. My Google results have provided some piecemeal answers, but I would like to better understand the big picture before starting the server upgrade and make some irreversible configuration choices that would cause unnecessary work re-attaching the workstations. I would first ask for recommendations whether and why to keep or change each of the following: The file server machine name The file server 192.168.1.12 IP address The file server Administrator account and password. The Acme.LAN forest and root domain name that was defined after adding the Active Directory Domain Service role that also added File and Print Services and Group Policy Management. The SQL Server Express default MSSQL database name The SQL Server Express SA account name and password I would also ask about the best steps for disconnecting workstations from the old domain then joining the new domain to hopefully retain the existing workstation user account, or if not, to minimize the need to copy users folders between the user accounts and / or uninstall then reinstall the workstation applications to properly authenticate to the new user account. I would greatly appreciate some experienced insights for how to best accomplish these upgrade goals. Thanks, all!
Not able to update the parameter "UserRightsGenerateSecurityAudits" for OSConfigDesiredConfiguration
Hello, I want to add my AD group as part of "UserRightsGenerateSecurityAudits" in order to be able to collect audit logs but when I run the command, the change is not applied (Processed 0 out of 1 settings) : "Set-OSConfigDesiredConfiguration -Scenario SecurityBaseline/WS2025/MemberServer -Setting UserRightsGenerateSecurityAudits -Value @("*S-1-5-82-3006700770-424185619-1745488364-794895919-4004696415","*S-1-5-20","*S-1-5-19","*S-1-5-21-2654652530-1219913000-911364509-1603") Warning : Cannot process the settings 'UserRightsGenerateSecurityAudits': 0x82d0000a. Verify the value and try again. Processed 0 out of 1 settings. Using GPO, I'm able to update the value, but OsConfig is overwriting it after some time after because the group is not part of defaut values allowed by OsConfig. Your assitance will be ready appreciated. Thanks
Allow “Edit/Save/Rename Without Delete” NTFS Permission
Problem Description: I manage shared folders using NTFS permissions. I want users to edit, save, and rename files without being able to delete them. Currently, if “Delete” and “Delete subfolders and files” are unchecked, users cannot delete, but they also cannot save or rename files because most applications temporarily delete/rename files during saving. If delete is allowed, users can save but also delete files. Request: Introduce an NTFS permission that allows file editing and renaming without granting delete rights, to prevent accidental data loss while maintaining normal file operations. Observation: This limitation is inherent in the current NTFS permission model. NTFS does not distinguish between: Intentional deletion by user File replacement/temporary deletion by application As a result, administrators cannot fully protect shared folder data while still allowing normal file editing workflows. Impact: Prevents enterprise administrators from enforcing safe file editing without risk of accidental deletion. Creates workarounds such as Shadow Copies or backups, but these do not prevent the deletion itself. Suggested Improvement: Introduce a new NTFS permission or enhanced behavior that allows: Edit, save, rename files without granting delete rights Deny manual deletion of files/folders by users Maintain compatibility with standard application save workflows Such a feature would significantly improve data protection in enterprise file shares, reduce accidental data loss, and simplify NTFS permission management.
