Unusual Behavior using GPO PowerShell Scripts During Restart/Shutdown in Hyper-V – Need Help
I have noticed strange behavior in Hyper-V. Group Policy is configured to execute PowerShell scripts for logon, logout, startup, and shutdown. The typical sequence of script execution is: startup → logon → logout → shutdown. However, an issue arises when a restart is initiated while logged in (i.e., after startup and logon scripts have already been executed). Upon clicking the restart button from the GUI, the following occurs: after the logout and shutdown scripts run as expected, the startup script is executed and the logon script (!)is triggered. This happens despite the fact that the lock screen is displayed after the restart, and no user has logged in yet. This phenomenon consistently occurs when restarting or shutting down from the GUI while logged in. It does not occur when restarting via the command line using shutdown /r /t 0 or shutting down with shutdown /s /t 0. Why does Hyper-V behave in this inexplicable manner, executing the logon script in such cases? Is it possible to configure something within the virtual machine to address this issue? Or are there specific Group Policies for script execution that could control this behavior? Could there be certain Registry entries that influence the shutdown or restart process to prevent this issue in Hyper-V? Alternatively, could the problem be resolved by modifying the startup or logon scripts, for instance, by adding conditions to verify if an actual login has occurred? Any ideas or suggestions to explain or resolve this behavior would be greatly appreciated.Step-By-Step: Enabling Hyper-V for Use on Windows 11
Want to use Hyper-V on Windows 11? Hyper-V is a virtualization technology that is valuable not only for developers and IT Professionals, but also for college and university students. This step-by-step guide will show you how to enable Hyper-V on your Windows 11 machine.
Windows Server 2022 Licensing
Hello Everyone, We currently have a server with 2x16 CPU cores. On this server, "Windows Server 2022 Standard" is installed. Five virtual servers are planned to run on this server. Currently, we have the following licenses: 1 x "WINSVR 2022 STD AddLic 16 Core ROK" 2 x "WINSVR 2022 STD AddLic 4 Core ROK" 1 x "Windows Svr Std 2022 64 Bit 1 pk DS P OEI DVD 24 Core" (This license was already activated on another server, which no longer exists. Is it possible to transfer this license to the new server?) Are these licenses sufficient, or which additional licenses would be required?
Hyper V Across 2 Server Rooms
Does Hyper V provide a method of running servers across 2 server room, so that if one server room is lost the VMs can start in the other server room. Does this require a witness node installed in a 3rd location (like VMware) ? Are there any reference designs available from the like of Dell or HP using current hardware ?
Hyper-V VMConnect failing after hardening crypto
I run Hyper-V locally on my laptop for testing and evaluation of various systems and services for my company. The laptop is running Win10, AMD Ryzen processor, 40GB RAM. The Hyper-V install had been running fine for a long while, but I just recently updated my crypto settings on my laptop (stopped the use of legacy/insecure ciphers, locked to TLS 1.2 and disabled older versions, etc.) and suddenly I can't connect using the Hyper-V VMconnect console to my VM's anymore. Reference: Setup Microsoft Windows or IIS for SSL Perfect Forward Secrecy and TLS 1.2 | Hass - IT Consulting A sample of the error I'm getting - pop up window as the VMConnect console is being spun up: An authentication error has occurred One or more of the parameters passed to the function was invalid My local EventViewer / Custom Views / ServerRoles / Remote Desktop Services1 channel has the follow error message crop up: RDPClient_SSL: An error was encountered when transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005). Seems to indicate that the VMConnect service is relying on some kind of SSL/TLS handshake to negotiate a secure connection but that it can't agree on the terms? Any ideas? Other than the obvious reversion back to the weaker crypto state :)Unable to Access Windows server remotely
Hello, we are hosting a VM on a local computer using Hyper-V. we normally access the VM and work on it using windows remote desktop. This morning, we are tried connecting to the VM and it is not recognizing any of our passwords. I have logged on to the VM through the Host computer, restarted the VM, checked to see that the remote desktop services is running and they are. but yet I can't seem to resolve the issue. What could be the reason or what can I check to resolve this issue.Hyper-V external Virtual Switch
Hello, I´ve a problem with external Virtual Switches and FailoverCluster(LiveMigration) configured. What is the recommended configuration for that? We have dropped SCVMM. old Hosts via SCVMM2022: BandwidthReservationMode : Weight BandwidthPercentage : 100 or 9 or 6 ... DefaultFlowMinimumBandwidthAbsolute : 0 DefaultFlowMinimumBandwidthWeight : 1 new Hosts via PS (W2022Server): BandwidthReservationMode : Absolute BandwidthPercentage : 10 DefaultFlowMinimumBandwidthAbsolute : 1000000000 DefaultFlowMinimumBandwidthWeight : 0 kind regards
