Increase the size of user profile disk in my remote desktop server
Hi all experts. I have a server for remote desktop services purposes, Windows 2016 standard, and domain joined. It is configured using User Profile Disk, and the maximum limit is set to 5GB. I want to increase the maximum limit but I can't do it under the collection's properties because that field is grayed out. My questions: How to increase the maximum limit? Please guide me and let me know how. Can I increase the maximum limit for 1 single user only? If yes, please let me know how. I found some info from the web that this can be done by the Diskpart command, is it true? If I follow the Diskpart method, do all user profiles encounter data lost? I need your guidance and input, I appreciate it. Here are some images:
Hyper-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?
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
Launching EXEs on File Server Slow on Hyper-V Host
We have a Server 2019 Hyper-V host that hosts a Server 2008 file server (yeah, I know, too old) and other virtual machines we use as work stations that access various EXE files on the file server. Recently, (not sure when it's started) launching EXE files stored on the 2008 server from one of the workstations (all on the same host) is getting delayed, sometimes as long as 20-30 seconds. An odd thing is that when you first log on to the work station and run the EXE it starts in what I think is a reasonable time, until now a second launch would be a little faster, I'm assuming due to caching. But not, launching it a second time gets the delay. Other file types seem to be OK. Opening large PDFs, for instance, does not have the problem. Working on a virtual machine hosted on our OTHER, older 2012 R2 Hyper-V host (yeah, again, I know) and going across the network, host to host, to access those same EXE files never has the delay problem. Because of virtual machines the 2012 host not having the problem, I'm thinking there's something on the 2019 host that's been updated. Update history shows KB5052000 installed in February and KB5050182 in January. I see that the January update mentions "Remote Code Execution" but the info seems to be specific to Visual Studio so I'm not sure that would apply. Has anyone seen this behavior or can maybe give me a clue as to where to start even looking? Thanks, KenWhat MAC address
Create a new virtual switch and connect the management OS to it: New-VMSwitch -Name 'Ext' -AllowManagementOS $true -NetAdapterName 'Prod' A new VMNetworkAdapter was created, get name and MAC address: Get-VMNetworkAdapter -ManagementOS | Format-Table -Property 'Name', 'MacAddress' The MAC address is for example: 00155D05ED13 (the first three octets indicate "Microsoft"). Get MAC address pool of the Hyper-V host: Get-VMHost | Select 'MacAddressMinimum', 'MacAddressMaximum' | Format-Table My understanding is that this pool is used when creating VMNetworkAdapters for VMs. What I see in my case is that the MAC address of the new VMNetworkAdapter is different from the possible pool values. Question: From what pool are MAC addresses pulled for VMNetworkAdapters that are located in the management OS realm?Windows Server 2022 Hyper-V guest state not saved on host reboot
Windows Server 2022 with latest updates. All VMs are set to "Automatic Stop Action" = Save But on every reboot the VMs lose their state and the Windows VM reports "The system has rebooted without cleanly shutting down first." On the host machine there is an error in the system event log Service Control Manager event id 7043 "The Hyper-V Virtual Machine Management service did not shut down properly after receiving a preshutdown control." This error occurs around 48 seconds after the reboot is initiated. Setting WaitToKillServiceTimeout in the registry to a higher timeout didn't change anything. Manually stopping the Hyper-V Virtual Machine Management service often shows the error 1053: The service did not respond to the start or control request in a timely manner but after 3 to 5 minutes the service is in stopped state but the virtual machines are still running, so even when this service is killed it shouldn't be the cause of the problem. There are 3 VMs running and manually setting them to the save state only takes a few seconds. Two of the VMs are Linux VMs, the third is Windows Server 2022 There are no other errors in the system or application eventlog when reboot the host. Thanks, ReinhardBLOG: Windows Server / Azure Local keeps setting Live Migration to 1 - here is why
Affected products: Windows Server 2022, Windows Server 2025 Azure Local 21H2, Azure Local 22H2, Azure Local 23H2 Network ATC Dear Community, I have seen numerous reports from customers running Windows Server 2022 servers or Azure Local (Azure Stack HCI) that Live Migration settings are constantly changed to 1 per Hyper-V Host, as mirrored in PowerShell and Hyper-V Host Settings. The customer previously set the value to 4 via PowerShell, so he could prove it was a different value at a certain time. First, I didn't step into intense research why the configuration altered over time, but the stumbled across it, quite accidently, when fetching all parameters of Get-Cluster. According to an article a LCU back in September 2022 changed the default behaviour and allows to specify the live migrations at cluster level. The new live migration default appears to be 1 at cluster level and this forces to change the values on the Hyper-V nodes to 1 accordingly. In contrast to the commandlet documentation, the value is not 2, which would make more sense. Quite unknown, as not documented in the LCU KB5017381 itself, but only referenced in the documentation for the PowerShell commandlet Get-Cluster. Frankly, none of the aren't areas customers nor partners would check quite regularly to spot any of such relevant feature improvements or changes. "Beginning with the 2022-09 Cumulative Update, you can now configure the number of parallel live migrations within a cluster. For more information, see KB5017381 for Windows Server 2022 and KB5017382 for Azure Stack HCI (Azure Local), version 21H2. (Get-Cluster).MaximumParallelMigrations = 2 The example above sets the cluster property MaximumParallelMigrations to a value of 2, limiting the number of live migrations that a cluster node can participate in. Both existing and new cluster nodes inherit this value of 2 because it's a cluster property. Setting the cluster property overrides any values configured using the Set-VMHost command." Network ATC in Azure Local 22H2+ and Windows Server 2025+: When using Network ATC in Windows Server 2025 and Azure Local, it will set the live migration to 1 per default and enforce this across all cluster nodes. Disregarding the Cluster Settings above or Local Hyper-V Settings. To change the number of live migration you can specify a cluster-wide override in Network ATC. Conclusion: The default values for live migration have been changes. The global cluster setting or Network ATC forcing these down to the Hyper-V hosts based on Windows Server 2022+/ Azure Local nodes and ensure consistency. Previously we thought this would happen after using Windows Admin Center (WAC) when opening the WAC cluster settings, but this was not the initial cause. Finding references: Later the day, as my interest grew about this change I found an official announcement. In agreement to another article, on optimizing live migrations, the default value should be 2, but for some reason at most customers, even on fresh installations and clusters, it is set to 1. TLDR: 1. Stop bothering on changing the Livemigration setting manually or PowerShell or DSC / Policy. 2. Today and in future train your muscle memory to change live migration at cluster level with Get-Cluster, or via Network ATC overrides. These will be forced down quite immediately to all nodes and will be automatically corrected if there is any configuration drift on a node. 3. Check and set the live migration value to 2 as per default and follow these recommendations: Optimizing Hyper-V Live Migrations on an Hyperconverged Infrastructure | Microsoft Community Hub Optimizing your Hyper-V hosts | Microsoft Community Hub 4. You can stop blaming WAC or overeager colleagues for changing the LM settings to undesirable values over and over. Starting with Windows Admin Center (WAC) 2306, you can set the Live Migration Settings at cluster level in Cluster > Settings. Happy Clustering! 😀ACPI/INTC1085 driver is not installed
Hello. I have a server platform ASUS RS300-E12-RS4 with Intel(R) Xeon(R) E E-2478. After installation microsoft hyper-v server 2019 and install all drivers from asus site, i have 1 not installed device. ACPI\INTC1085\2&DABA3FF&1 driver "INTEL_Serial_IO_V30.100.2237.26.zip" not compatible for this device. BIOS version is 0803 BMC version is 1.0.9 The support of the hardware manufacturer could not help me, they recommended to contact the OS manufacturer.feature Installation Error
I am facing this issue in Windows Server 2019 STD. i am also tried to solve this issue to select sources\sxs path from the OS media but still i am getting the same error. Mistakenly i have removed .Net framework from this server and after that i am facing this issue. please help me to solve this issue.
