Within the base OS MP state view 'Windows Server State' there is a column called 'Virtual Machine'. Next to each of my VMs within this view it says "False". Is this correct? I wouldexpect to see "true" here.ThanksMark

Hi Markne,Are you running vmware VM's? The property's are indeed not correct.Have a look at Pete's post on the discovery of virtual machines by Operations Manager http://www.systemcenterforum.org/downloads/virtual-machine-discovery-mp-for-opsmgr-2007/Grtz,Alex Alexandre Verkinderen | Microsoft MVP - Operations Manager | http://scug.be/blogs/scom

I have 5 machines running on my VS 2005 server and they all show Virtual Machine = True on my R2 RTM install. Same goes for a another group of virtuals running on Hyper-V RTM. What kind are yours?Thanks,JustinThis posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Hi JustinStrange though it may seem, there are other virtualisation solutions out there ;-) And for some sneaky reason Microsoft doesn't seem to want to accurately identify them!Virtual Machines running under VMware (and I think Xen)areboth incorrectly listed as virtual machine = false. Have funGraham

Thanks Graham, that's the info I was looking for. Is that what Markne is running as well?This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

strangely enough, we always populate this property with FALSE when we are not manufacturer of the baseboard. (I vaguely remember it had something to do with complains of this property having no value is causing some different discoveries (or workflows) to freak out). So ultimately, this would require some customization on your part (not just simple disabling of the discovery rule which sets the value to false)so agaihn, thiswas always up to discovery provided with particular solution to populate IsVirtualMachine. (but with us setting it to false, additional stepsarew nowrequired). One would need to "disable" discovery Microsoft.SystemCenter.DiscoverIsVirtualMachineFalse(thru override) and provide its replacement. Something like non-working sample belowin this sample I choose to say that manufacturer is "vmware", but I'm not sure this is correct value for vmware <Discovery ID="Microsoft.SystemCenter.DiscoverIsVirtualMachineFalse,Custom" Enabled="true" Target="Windows!Microsoft.Windows.Computer" ConfirmDelivery="false" Remotable="true" Priority="Normal"> <Category>Discovery</Category> <DiscoveryTypes> <DiscoveryClass TypeID="Windows!Microsoft.Windows.Computer"> <Property PropertyID="IsVirtualMachine" /> </DiscoveryClass> </DiscoveryTypes> <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.WmiProviderWithClassSnapshotDataMapper"> <NameSpace>\\$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$\ROOT\CIMV2</NameSpace> <Query><![CDATA[SELECT * FROM Win32_BaseBoard WHERE Manufacturer <> "Microsoft Corporation" And Manufacturer <> "<strong>VMWare</strong>"]]></Query> <Frequency>86400</Frequency> <ClassId>$MPElement[Name="Windows!Microsoft.Windows.Computer"]$</ClassId> <InstanceSettings> <Settings> <Setting> <Name>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Name> <Value>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Value> </Setting> <Setting> <Name>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/IsVirtualMachine$</Name> <Value>false</Value> </Setting> </Settings> </InstanceSettings> </DataSource> </Discovery> Marius Sutara My MSDN blog This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Alexandre has also listed a download that has an MP that does something similar. CheersGraham

What could cause nothing to be populated in the "Virtual Machine" parameter? I'm trying to create a dynamic group of ONLY physical servers and some of our physical servers don't report "False" under the "Virtual Machine" parameter. It leaves it blank. I'd like to resolve this so I can get my group to populate appropriately. I tried repairing the SCOM Agent on those servers and still nothing... They are Windows Server 2003 R2 (and NON R2) Standard edition servers.