To import computer information into Configuration Manager for OS deployment you have to enter the computer name and then one or both of the following unique identifiers: MAC address or SMBIOS GUID, aka UUID. Many customers use the MAC address because it is shorter and typically more accessible. However, if the UUID is required this can seem difficult to obtain especially when the target systems are VMware guests. When the guest is initially created it is assigned a UUID which is stored in the VMX configuration file as the uuid.bios property. Here is an example line from the VMX file:
Similar the old client vmwareclient, vmware client that connect to esxi or vcenterVMware 5.0, 5.5 6.0, 6.5 and 6.7, uses the python APIs. Works in linux using putty (yes, there is the putty in linux) and the Remminia to connect with RDP. And work in Windows, the putty is necesary to add the path and work MacOs too. VSphere Client 5.0 Update 2 20 DEC 2012 Build 913577. Installing vSphere support tools fails with the error: The application does not support IP link-local addresses. Clone operations fails because vCenter Server MAC address space is. /usr/lib/vmware/hostd/hmo/hostProfileEngine.py -cgi.
uuid.bios = “42 38 d4 b6 00 90 3e 75-94 06 b3 10 ea fa 2b 1e”
This does not look like a usual SMBIOS GUID in the standard (8)-(4)-(4)-(4)-(12) format. When the system boots and attempts to PXE boot, the same UUID is visible although formatted differently, for example:
![Simple Local Client Vmwareclient Pyvmwareclient For Mac Simple Local Client Vmwareclient Pyvmwareclient For Mac](https://i2.wp.com/virtualcloudsolutions.info/wp-content/uploads/2015/07/VDP8.jpg)
Network boot from Intel E1000
Copyright (C) 2003-2008 VMware, Inc.
Copyright (C) 1997-2000 Intel Corporation
Copyright (C) 2003-2008 VMware, Inc.
Copyright (C) 1997-2000 Intel Corporation
CLIENT MAC ADDR: 00 50 56 B8 00 14 GUID 4238D4B6-0090-3E75-9406-B310EAFA2B1E
CLIENT IP: 192.168.1.100 MASK: 255.255.255.0 DHCP IP: 192.168.1.10
GATEWAY IP: 192.168.1.1
…
CLIENT IP: 192.168.1.100 MASK: 255.255.255.0 DHCP IP: 192.168.1.10
GATEWAY IP: 192.168.1.1
…
Looking at the actual SMBIOS GUID via the UUID property of the Win32_ComputerSystemProduct WMI class (or the comparable System UUID property on the ConfigMgr System Resource), it appears as:
UUID = “B6D43842-9000-753E-9406-B310EAFA2B1E”
The difference between these two (uuid.bios up above and UUID directly above), which are identical except for formatting, is explained in an older Remote Installation Services article on TechNet. The VMware VMX uses the “raw byte order” format while Windows and Configuration Manager use the “pretty print” format. (Thanks to Michael Kelley for that nugget of information.)
So taking a UUID from a VMware VMX to import into Configuration Manager for OS deployment requires some conversion. The attached script does a simple conversion; there may be a more elegant method relying upon the underlying mathematics of the UUID, but that’s beyond my current knowledge.
The script usage is as follows:
.Convert-UUID.ps1 -rawUUID '<uuid>'
where <uuid> is formatted as follows:
01 23 45 67 89 ab cd ef-fe dc ba 98 76 54 32 10
such as used in the uuid.bios property of a VMX file. For example, the above rawUUID yields the following output:
67452301-ab89-efcd-fedc-ba9876543210
Disclaimer: The information on this site is provided 'AS IS' with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use.
Hi,
I'm a newbie in VMware Workstation. I've been create an device which demonstrate a similar connecting way as a handphone named GFDdevice.
I have a Lubuntu Desktop guest OS running on my VMware Player 5.0.2. I create a simple server in this guest OS written in Python language. I need to access this server using LAN and WAN too. In LAN network, I need to access this server by another computer as a client. In WAN network, I need to access this server by another computer as a client and GFDdevice using Local IP Address and Global IP address (www.myipaddress.com).
I've tried this tutorial and it correctly worked. However, I just can access this server using another computer with Local IP address and using the GFDdevice with global IP address, it's always fail if I access this server using another computer with Global IP address. Here is my detailed information about this problem:
- Host OS: Windows 7 Professional
![Simple local client vmware client pyvmwareclient for mac download Simple local client vmware client pyvmwareclient for mac download](/uploads/1/2/6/3/126340580/810270866.png)
- Router : TP-Link 150mbps Wireless N ADSL2+ Modem Router
- Guest OS: Linux Lubuntu Desktop
- Router's DHCP starting address: 192.168.1.30 / 255.255.255.0
- VMware DHCP starting address: 10.0.0.128 / 255.255.255.0
- VMware DHCP starting address: 10.0.0.128 / 255.255.255.0
I've tried this discussion too but it still not solve this complex problem.
What should I do to make this server accessible by another computer using Global IP address? There isanincorrect NAT settingsonmyrouter or on my VMware's NAT configuration or on my guest OS? Anyone can help me?
Any help would be very appreciated.
Any help would be very appreciated.
Thanks in advance.
Andromeda
Andromeda