I wonder if wpeutil updatebootinfo would help. I think one of the things it detects and writes in the registry is VM detection.
Sent from my iPad On Oct 7, 2016, at 2:34 PM, Mote, Todd <mo...@austin.utexas.edu<mailto:mo...@austin.utexas.edu>> wrote: Nope, the 2012 R2 is BIOS the 2016 is UEFI. So that’s another variable I guess. I’ll see if I can confirm that and boot a win10 PE on BIOS to see what it says From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Niehaus Sent: Friday, October 7, 2016 1:13 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] RE: VMWare EFI VMs Not Seen as Virtual Machines Are both of the VMs using UEFI? We’ve seen different results from VMware BIOS vs. VMware UEFI. And knowing VMware, it wouldn’t surprise me if there were even more ways to tweak it… Thanks, -Michael From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mote, Todd Sent: Friday, October 7, 2016 11:05 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] RE: VMWare EFI VMs Not Seen as Virtual Machines Something has changed, but I don’t think it’s the VM. I copied an existing Task Sequence in SCCM to test UEFI and Server 2016 deployments. My original TS that’s been working for literally years has this WMI query when determining VM or physical: select * from Win32_ComputerSystem where Model like '%Virtual%' My copied TS didn’t work the first time through and I ran into the same thing, same ESX VM I’ve used for testing for years, now reports the model like yours Mike. A quick look at WMI from winpe*10* using wmic: wmic computersystem get model Returns Model VMware7,1 But if I run the same command on a 2012 R2 esx vm on the same cluster running the same hardware version it returns Model VMware Virtual Platform The reason I used %virtual% was because I could detect either an esx vm or a hyper-v vm with that, because hyper-v returns Model Virtual Machine I can’t use just the one WMI query anymore to determine virtual or not if I use a win 10 PE boot wim. So Windows is the difference here. “8” code base vs “10” code base that returns different data for the same WMI entry on the same hardware. In my experience. Todd From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner Sent: Friday, October 7, 2016 11:59 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] RE: VMWare EFI VMs Not Seen as Virtual Machines MDT ZTIGather.wsf will try to determine isVM by reading the Make/Model in the firmware. Specifically what does: “Get-WMIObject Win32_ComputerSystem” return from Powershell ( or “wmic computersystem get Manufacturer,Model” ) from within the Virutal Machine? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Friday, October 7, 2016 7:16 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] RE: VMWare EFI VMs Not Seen as Virtual Machines Sorry. Having a DUH! morning today. It’s VMWare Workstation 12.1.1. My bad. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Friday, October 07, 2016 9:55 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] RE: VMWare EFI VMs Not Seen as Virtual Machines What specific VMWare environment? We have tested on VMWare Workstation 10 and 11 without issue. We have tested on eSX 5.0 and 5.5 without issue as well. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Friday, October 07, 2016 9:32 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] VMWare EFI VMs Not Seen as Virtual Machines Just a heads up. I ran into this problem this morning trying to build a VMWare VM as EFI. The task sequence variable “IsVM” is not set correctly. IsVM is set to “false” so logic we have in our build to bypass things like TPM management on VMs does not work. <image001.jpg> If the VM is set to BIOs then the variable IsVM is set properly. <image002.jpg> Mike Marable Microsoft Systems Engineer Lead Enterprise Device Engineering and Management MCPS, MCITP, MCTS, MCSA, MCSE, MS [ Profile<http://www.mycertprofile.com/Profile/5319166625> ] [ Blog<http://thesystemsmonkey.wordpress.com/> ] ---------------------------------------------------- "Knowing is not enough, we must apply. Willing is not enough, we must do." -Bruce Lee "A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty." -Winston S. Churchill "We may encounter many defeats but we must not be defeated." -Maya Angelou ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________
