Step 1 – Add the external log server
Go to Manage > System > Advanced Settings and locate Syslog.global.logHost and edit settings.
Add the following: udp://SERVER.domain.com:514
Step 2 – Configure Firewall rules to allow access to external syslog server.
Go to Host > Networking > Firewall Rules and locate syslog and edit settings:
Select Only allow connections from the following networks and enter the external syslog server.
ESXi 5.x and 6.0
List the inventory ID of the virtual machine with the command:
vim-cmd vmsvc/getallvms | grep <vm name>
Note: The first column of the output shows the vmid.
Check the power state of the virtual machine with the command:
vim-cmd vmsvc/power.getstate <vmid>
Power-on the virtual machine with the command:
vim-cmd vmsvc/power.on <vmid>
ESX 4.0 and ESX 4.1
To list the path of all the virtual machines on the host:
Get the state of the virtual machine with the command:
vmware-cmd <path to the VMX file> getstate
Power on the virtual machine with the command:
vmware-cmd <path to the VMX file> start
- Run fdisk -l to see all the disks available to ESXi host.
- Run /dev/disks/ -l to find out VML ID, which will be used in the command to create RDM.
- Create a folder (i.e. RDMs) for mapping file(s) on the DataStore
- Create the mapping files with LSILogic controller using the following command
vmkfstools -r /vmfs/devices/disks/vml.01000000002020202020202020202020205733383132564439535431303030 RDM1.vmdk -a lsilogic
Two mapping files (RDM1.vmdk and RDM1-flat.vmdk) were created. (Note: file appears to your total disksize but it actually takes no space).
- Go to your VM and add the mapping file as a second disk. Select the option existing disk and point to the RDM1.vmdk file.
Enabling local shell access in direct console
- On ESXi host press the F2 button and log in with your credentials when prompted.
- In the list go on Troubleshooting Options and press Enter.
- Then choose Enable ESXi Shell and press Enter (On the right you will notice that ESXi Shell is Disabled changes to Enabled).
- To exit the menus and log out press ESC until you return to the main screen.
How to power on (or off) the VM (ESXi 5.x)
You need to know the id (VMID) of the VM you plan to turn on plus start up and shutdown commands
- Command to list the inventory ID of the VM
vim-cmd vmsvc/getallvms | grep VM_NAME
- Check the VM state (Is it powered on?)
vim-cmd vmsvc/power.getstate VMID
- Power on the VM
vim-cmd vmsvc/power.on VMID
- Shutdown and power off the VM
vim-cmd vmsvc/power.shutdown VMID
vim-cmd vmsvc/power.off VMID
Source: VMware KB
I would like to share my experiences installing Hyper-V on Windows Server 2008 Server Core. First you need a hardware that will support it. Then you should install the Windows Server 2008 Server Core on that hardware. When you are choosing server settings remember you have to install the OS using default language settings (EN-US). After the OS is installed take these steps:
* Change the computer name (before joining a domain):
netdom renamecomputer %computername% /NewName:newComputerName
* Check the IPv4 interface idx:
netsh interface ipv4 show interfaces
* Change the IPv4 address:
netsh interface ipv4 set address name=”IDx” source=static address=StaticIP mask=SubnetMask gateway=DefaultGateway
* Add the IPv4 DNS server address:
netsh interface ipv4 set dnsserver name=”IDx” source=static address=IPAddress
* Add the IPv4 WINS server address:
netsh interface ipv4 set winsserver name=”IDx” source=static address=IPAddress
* Join a domain:
netdom join %ComputerName% /domain:DomainName /userd:domain\user /passwordd:*
* Add a domain user to the local administrators group (if you need):
Net localgroup administrators /add Domain\UserName
* Enable Remote Desktop:
Cscript %WinDir%\System32\Scregedit.wsf /ar 0
Cscript %WinDir%\System32\Scregedit.wsf /cs 0
* Activate Windows:
Cscript %WinDir%\System32\slmgr.vbs –ato
* Change Windows Key (If activation failed, and then reactivate):
Cscript %WindDir%\System32\slmgr.vbs –ipk NewKey
* Reboot Windows:
Shutdown /r /t 0
When the server comes up you are ready to install the Hyper-V role. Use these commands:
* bcdedit /set hypervisorlaunchtype auto (so you don’t have to do 2 reboots)
* start /w ocsetup Microsoft-Hyper-V (after this is done reboot again)
After the server comes up verify that all hyper-v related services are up and running using net start to list running services. On my next post I’ll write down some general commands how to enable some general firewall rules in Windows Server 2008 Server Core.
Here is the link the the Microsoft Technet Step-by-Step guide about how to install Server Core.