VirtuallyAware

From the Hyper-V Technet forums a question came about on how to get the number of processors for a non-active VM. You can see the varying answers here.

Thinking of the PowerShell options available with Hyper-V and SCVMM this is what came to mind for me using the Get-VMSummary and state attributes like EnabledState and Status.

With the Hyper-V PowerShell cmdlets installed (more info here http://bit.ly/hD38j2) you can use the following:

Get-VMSummary -server HOST1, HOST2, HOST3 | ? {$_.EnabledState -eq "Stopped"} | ft VMElementName, CPUCount, EnabledState

If you want to export it to a CSV you can do the following

Get-VMSummary -server HOST1, HOST2, HOST3 | ? {$_.EnabledState -eq "Stopped"} | Select-Object VMElementName, CPUCount, EnabledState | Export-CSV "C:\info.csv" -notypeinformation

From the SCVMM PowerShell command console you could do the following:

Get-VM | ? {$_.status -eq "PowerOff"} | ft name, cpucount, status -a

If you want to export to CSV from SCVMM prompt

Get-VM | ? {$_.status -eq "PowerOff"} | select-object name, cpucount, status | export-csv "c:\info.csv" –notypeinformation

My MVP for Virtual Machine came today. I am humbled and honored. Thanks to all that had a part in making that happen.

MVPs have helped me out tremendously over the years with supported and unsupported workarounds and guidance.  I am happy that I have been able to return some of the knowledge I have gained from them back to the community.

If you are looking to find out more about the Microsoft MVP award for Virtual Machine technology or any of the other application click HERE or feel free to drop me an email for more information my path to becoming an MVP.

Thanks again.

- Rob McShinsky

I have been following the release of Windows Thin PC that RTM’d on July 1st, and decided to see how it worked on Hyper-V.  If you are not familiar with Windows Thin PC, it is a version of Windows Embedded that is targeted toward using your older PCs and giving them new life as “Thin Clients” within your environment for connections to your Remote Desktop, Citrix or VDI environments.  It is similar to the Wyse PC Extender that utilizes a Linux (SUSE) kernel.  For more information on Windows Thin PC and all the details  you can go here.

In the description Microsoft notes that it has the capability of connecting to VDI sessions, but I wanted to see if this would be a good stripped down platform for platform for an actual VDI for Kiosk type scenarios.  According to this document, it isn’t officially supported in a virtual environment, but one thing jumped out at me in the testing that made it seem like the developers were at least thinking in this direction.  It has Dynamic Memory support. 

Can I run WinTPC in a virtual machine?
”WinTPC has been designed to help customers repurpose existing PCs
as thin clients. Since thin client OS’s are not designed for or supported
in a virtual machine (VM), WinTPC is not supported in a VM.”

Windows 7 Professional does not have Dynamic Memory Support.  Windows Enterprise/Ultimate does.  Now Windows Thin PC does as well.  See screen prints below.  More to come as I dig more into it.