You can then easily use Excel or Power BI to perform additional analysis on your opened sessions. Export this data to a CSV file for further analysis.For each session discovered, measure the amount of memory consumed by the user.Time when last input was received from the user.Capture the Remote Desktop Services sessions core information:.Load the awesome PSTerminalServices.psm1 module (it hasn’t been updated in a little while though).Get a list of servers from Active Directory.Here’s what the script is doing at a high level: In our case, I built the following script to help us assess the situation.įor the latest version: Get-RDPSession.ps1 So how can we be aware of those lingering RDP sessions? The problem with this is that we end up wasting precious server resources in our environment for no valid reasons. I’m sure it happened to you or to your colleagues, we sometime disconnect our RDP sessions from our beloved pet servers and forget we ever logged onto those. That will change significantly with Windows Server 2016 but in the mean time, we have to manage this. While it’s a best practice to avoid logging on servers using Remote Desktop for management tasks, some things are just easier when you do and some things are almost impossible to do otherwise. Hopefully this article helped you get things started! Windows Server 2016 takes great advantage of an assigned GPU to offload compute intensive rendering tasks. In this particular screenshot, you can see what Internet Explorer consumes while running FishGL my workstation. As you can see below, you can see which process is consuming GPU resources. Here’s what it looks like in Process Explorer when you’re doing live monitoring. Here’s a recorded trace of the GPU utilization from the Azure VM while running FishGL in Internet Explorer that’s being visualized in Windows Performance Analyzer:Īs you can see in the WPA screenshot above, quite a few processes can take advantage of the GPU acceleration. ![]() In order to do a capture with Windows Performance Recorder, make sure that GPU activity is selected under the profiles to be recorded: Windows Performance Recorder and Windows Performance Analyzer which is part of the Windows Assessment and Deployment Toolkit (WIndows ADK).The tool does a good job at giving you an high level idea of the GPU cores utilization.Microsoft Sysinternals Process Explorer.To measure the GPU utilization, I ended up using the following tools: When this demo runs using only the software renderer, I observed CPU utilization close to 100% on a fairly beefy NV6 VM that has 6 cores and that just by running a single instance of that test. Only under Windows Server 2016 could high frame rate and low CPU utilization was achieved. ![]() This proved to be the scenario that differentiated Windows Server 2016 from Windows Server 2012 R2.Microsoft Fish Tank page which leverages WebGL in the browser which is in turn accelerated by the GPU when possible.Here’s what it looks like when you run this demo (don’t mind the GPU information displayed, that was from my workstation, not from the Azure NV* VM):.This scenario worked fine in both Windows Server 2012 R2 and Windows Server 2016.Island demo from Nvidia which is available for download here.For load generation I used the following: To validate the acceleration, I used a couple of tools to generate and measure the GPU load. Enable the Group Policy Setting Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment\ Use the hardware default graphics adapter for all Remote Desktop Services sessions as shown below:.Download and install the latest driver recommended by Microsoft/NVidia from here.In order to enable hardware acceleration for RDP, you must do the following in your Azure NV* series VM: While Windows Server 2012 R2 does deliver some level of hardware acceleration for graphics, Windows Server 2016 did provide a more complete experience through better support for GPUs in an RDP session. We did experiments with Windows Server 2012 R2 and Windows Server 2016. ![]() As we noticed that Internet Explorer was consuming quite a bit CPU resources on our Remote Desktop Services session hosts, I wondered how much of an impact on the CPU using a GPU would do by accelerating graphics through the specialized hardware. I recently spent some time experimenting with GPU Discrete Device Assignment in Azure using the NV* series of VM.
0 Comments
Leave a Reply. |