VMware VC-VLM4-C User Guide - Page 40

Customizing the Guest Operating System, Access the machine.id from an ESX Host

Page 40 highlights

Lab Manager User's Guide Customizing the Guest Operating System Lab Manager can customize the network settings of a guest operating system that was created from a virtual machine template. These settings include the machine name, IP settings, and security identifier (SID) for Windows guest operating systems. The customization allows you to create and deploy multiple, unique virtual machines based on the same virtual machine template without a machine name or network conflicts. When you configure a virtual machine template with the prerequisites for guest customization and create a virtual machine that uses this virtual machine template, Lab Manager creates a package with guest customization tools. When you deploy and power on the virtual machine the first time, Lab Manager copies the package, runs the tools, and deletes the package from the virtual machine. You can enable or disable customization for a virtual machine template or a virtual machine. To avoid conflicts when you are not using guest customization, access the virtual machine console through Lab Manager and manually set its network parameters to unique values. By default, Lab Manager enables guest customization when you create a new template. Access the machine.id from an ESX Host The configuration file for a virtual machine, the .vmx file, contains a machine.id line. The Lab Manager server system sets the values for this line while deploying virtual machines. Enabling guest customization on a virtual machine template configures a script to run every time the system starts up. This script reads the machine.id information and determines which action to take. The Lab Manager server system does not set any actions in the machine.id line while deploying virtual machine templates. As a result, the guest customization script does not perform any customization for the virtual machine template when it starts up. The Lab Manager server system does set customization actions in the machine.id line while deploying virtual machines or changing virtual machine network settings. When these virtual machines first start up, the guest customization script performs the relevant actions. To access the machine.id line from the ESX/ESXi host 1 From the ESX/ESXi host system, open the .vmx file. 2 Find the machine.id line. Access the machine.id from a Guest Operating System If you install VMware Tools, you can access the machine.id from the guest operating system of a deployed virtual machine. To access the machine.id line from the guest operating system 1 In the left pane, click Workspaces. 2 Move the pointer over the configuration name and select Open. 3 Move the pointer over the deployed virtual machine name and select Show Console. 4 Search for machine.id from inside the guest operating system.  From a Linux guest OS, type: # vmware-guestd --cmd machine.id.get  From a Windows guest OS, navigate to the directory where VMware Tools is installed (usually C:\Program Files\VMware\VMware Tools) and type: >VMwareService.exe -cmd machine.id.get 40 VMware, Inc.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180

Lab Manager User’s Guide
40
VMware, Inc.
Customizing the Guest Operating System
Lab Manager can customize the network settings of a guest operating system that was created from a virtual
machine template. These settings include the machine name, IP settings, and security identifier (SID) for
Windows guest operating systems. The customization allows you to create and deploy multiple, unique
virtual machines based on the same virtual machine template without a machine name or network conflicts.
When you configure a virtual machine template with the prerequisites for guest customization and create a
virtual machine that uses this virtual machine template, Lab Manager creates a package with guest
customization tools. When you deploy and power on the virtual machine the first time, Lab Manager copies
the package, runs the tools, and deletes the package from the virtual machine.
You can enable or disable customization for a virtual machine template or a virtual machine. To avoid conflicts
when you are not using guest customization, access the virtual machine console through Lab Manager and
manually set its network parameters to unique values. By default, Lab Manager enables guest customization
when you create a new template.
Access the machine.id from an ESX Host
The configuration file for a virtual machine, the
.vmx
file, contains a
machine.id
line. The Lab Manager server
system sets the values for this line while deploying virtual machines.
Enabling guest customization on a virtual machine template configures a script to run every time the system
starts up. This script reads the
machine.id
information and determines which action to take.
The Lab Manager server system does not set any actions in the
machine.id
line while deploying virtual
machine templates. As a result, the guest customization script does not perform any customization for the
virtual machine template when it starts up.
The Lab Manager server system does set customization actions in the
machine.id
line while deploying virtual
machines or changing virtual machine network settings. When these virtual machines first start up, the guest
customization script performs the relevant actions.
To access the machine.id line from the ESX/ESXi host
1
From the ESX/ESXi host system, open the
.vmx
file.
2
Find the
machine.id
line.
Access the machine.id from a Guest Operating System
If you install VMware Tools, you can access the
machine.id
from the guest operating system of a deployed
virtual machine.
To access the machine.id line from the guest operating system
1
In the left pane, click
Workspace
s.
2
Move the pointer over the configuration name and select
Open
.
3
Move the pointer over the deployed virtual machine name and select
Show Console
.
4
Search for
machine.id
from inside the guest operating system.
From a Linux guest OS, type:
# vmware-guestd --cmd machine.id.get
From a Windows guest OS, navigate to the directory where VMware Tools is installed (usually
C:\Program Files\VMware\VMware Tools
) and type:
>VMwareService.exe -cmd machine.id.get