tjie

<div>
Do you have access to all of the virtual hosts? If so, that may really speed up the process.<br><br>If you want to use powershell, it can be done too:<br><a href="https://vmin.wordpress.com/2018/04/17/powershell-script-to-find-a-server-is-physical-server-or-virtual-machine/" rel="ugc">https://vmin.wordpress.com/2018/04/17/powershell-script-to-find-a-server-is-physical-server-or-virtual-machine/</a>
</div>


Do you have access to all of the virtual hosts? If so, that may really speed up the process.

If you want to use powershell, it can be done too:
https://vmin.wordpress.com/2018/04/17/powershell-script-to-find-a-server-is-physical-server-or-virtual-machine/ [https://vmin.wordpress.com/2018/04/17/powershell-script-to-find-a-server-is-physical-server-or-virtual-machine/]

<div>
@Andrew Hancock:<br />
You said that “Network Interface MAC Address” may help.<br />
Here is the MAC address: 00-15-5D-28-6D-19<br />
How would you know the above MAC address is Physical or VM server?<br />
<br />
Thanks,<br />
Tjie
</div>


@Andrew Hancock:
You said that “Network Interface MAC Address” may help.
Here is the MAC address: 00-15-5D-28-6D-19
How would you know the above MAC address is Physical or VM server?

Thanks,
Tjie

<div>
00-15<br />
<br />
Microsoft Hyper-V network adapter
</div>


<div>
Put the MAC Address in here<br />
<br />
<a href="https://macvendors.com/" rel="ugc">https://macvendors.com/</a><br />
<br />
Microsoft Corp. (they don't make network interface cards!)
</div>


Put the MAC Address in here

https://macvendors.com/ [https://macvendors.com/]

Microsoft Corp. (they don't make network interface cards!)

<div>
<div class="content wysiwyg-content fr-view">
Hi,<br><br>This is in Windows 10, Office 365, Server 2016 and Server 2019 environment.<br><br>I have most of the NAMES of the servers in the network. The GOAL: I want to know whether the servers are PHYSICAL servers or VM (Virtual Machine) servers.<br><br>I want to RDP to the servers: Question#1: Would I have to RDP to EACH of the servers for the above goal? Or just a few of them? ( please explain a little bit with your answer)<br>&nbsp;<br>I heard that I can use the powershell. Question#2:: Somebody would explain how to do it please.<br><br>Thanks,<br>Tjie
</div>
</div>



Hi,
This is in Windows 10, Office 365, Server 2016 and Server 2019 environment.
I have most of the NAMES of the servers in the network. The GOAL: I want to know whether the servers are PHYSICAL servers or VM (Virtual Machine) servers.
I want to RDP to the servers: Question#1: Would I have to RDP to EACH of the servers for the above goal? Or just a few of them? ( please explain a little bit with your answer)
 
I heard that I can use the powershell. Question#2:: Somebody would explain how to do it please.
Thanks,
Tjie

How do I know whether the server is Physical server or VM server?

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.