User Profile
kazuo_yamauchi
Brass Contributor
Joined 8 years ago
User Widgets
Recent Discussions
Re: Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
I confirmed that the pair of rules of reception of "DNS Server Forward Rule TCP - XXXXXXXXXXXXXXXX - 0" and "DNS Server Forward Rule UDP - XXXXXXXXXXXXXXXX - 0" increases forever with the influence that the Default Switch is recreated. The "XXXXXXXXXXXXXXXX" is GUID of port of Default Switch that was recreated. If we do not delete wasted rules, will one day overflow?85KViews1like2CommentsRe: Server 2019 Hyper-V VM using GPU
You can also use RemoteFX vGPU feature on Windows Server 2019. Although the config UI of RemoteFX vGPU has been removed from Hyper-V Manager of Windows Server 2019, you can configure RemoteFX vGPU by using Powershell on Windows Server 2019. 1) Check your Host GPU (You need RemoteFX Compatible GPU Card and Remote Desktop Virtualization Host role) Get-VMRemoteFXPhysicalVideoAdapter CompatibleForVirtualization: True Enabled: True 2) Enable/Disable Host GPU for RemoteFX vGPU Disable/Enable-VMRemoteFXPhysicalVideoAdapter 3) Add RemoteFX vGPU to your VM: Add-VMRemoteFx3dVideoAdapter -VMName <vmname> 4) Open VM Settings dialogbox, you can configure RemoteFX vGPU. 5) Start VM124KViews1like3CommentsRe: Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
17763.194 has same issue. According to the Microsoft-Windows-Hyper-V-VmSwitch/Operations log, it shows that the Default Switch is recreated each time the machine is booted. (When started in safe mode with networking, it is not recreated, so it remains on the same subnet as last normal boot.)119KViews2likes3CommentsRe: Remote Desktop not working in Admin Center
Exactly. It is important that there is at least one value in this place. The name, type, and data of that value can be anything. This bug was probably fixed in Windows Admin Center 1809.5 Insider Preview. https://blogs.windows.com/windowsexperience/2018/12/11/announcing-windows-admin-center-1809-5-insider-preview/51KViews1like2CommentsRe: Remote Desktop not working in Admin Center
I could fix this problem by enabling "Allow users to connect remotely by using Remote Desktop Services" policy settings (gpedit.msc or gpo). This policy add fDenyConnection=0 value to "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services", so $resgistryKey never set to null.52KViews1like2CommentsRe: Remote Desktop not working in Admin Center
Perhaps it is only necessary for something to exist in the "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" key. If there is no value in this reg path, $regisgtryKey vaiable (you can see it by using [>_] show power shell script button) set to null, and followed script will cause error. $registryKey = Get-ItemProperty -Path $RdpGroupPolicyRegistryKey -ErrorAction SilentlyContinue if ((Get-Member -ImputObject $registryKey ... <- Error52KViews1like7CommentsRe: Remote Desktop not working in Admin Center
I also had problems with remote desktop connection not working on-premises. And Settings > Remote Desktop page show "Get-Member" errors. But when setting up in the Azure VM environment, Remote Desktop Connection worked without any problems. Therefore, when comparing Remote Desktop settings in the registry, I confirmed that the following two values exist on the Azure VM side and do not exist in the on-premise side clean installation environment. HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services KeepAliveEnable REG_DWORD 1 KeepAliveInterval REG_DWORD 1 I created the same registry by running these command line on a remote server on-premises, the problem was solved. Settings > remote desktop page's error was also gone. （You do not need to restart the server.) REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveEnable" /t REG_DWORD /d 1 /f REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveInterval" /t REG_DWORD /d 1 /f52KViews1like8Comments
Recent Blog Articles
No content to show