Video
Notes
After configuring basic network settings through the DCUI, the next step is accessing and configuring your ESXi host through its web interface. This guide walks you through the essential configuration steps using the ESXi host client.
Accessing the Web Interface
Open a web browser and navigate to:
https://ESXi-2.zerotohero.dev
(if DNS is configured)https://192.168.1.102
(direct IP access)
Handle the SSL Certificate Warning:
- Click “Advanced”
- Click “Proceed” (expected for self-signed certificates)
Log in:
- Username: root
- Password: (configured during installation)
Understanding the Interface
The ESXi host client interface consists of:
- Left navigation pane for main menu items
- Right content area showing details and configuration options
- Recent tasks section at the bottom (can be minimized)
Configuring Time and Date Settings
Navigate to Manage > System
Under Time & Date:
- Click “Edit”
- Select “Network Time Protocol”
- Set NTP server startup policy to “Start and stop with host”
- Add NTP servers:
- Local: 192.168.1.100
- Or use public NTP servers
Starting the NTP Service:
- Go to Services
- Find NTP service
- Select Actions > Start
Network Configuration
Modifying IP Settings
- Navigate to Networking > VMkernel NICs
- Select VMK0
- Click “Edit Settings”
- Expand IPv4 settings
- Note: Changing IP requires reconnecting to the new address
Updating DNS Configuration
- Go to Networking > TCP/IP Stacks
- Select “default TCP/IP stack”
- Click “Edit Settings” to modify:
- Primary/Secondary DNS servers
- Search domain
- Default gateway
Enabling Remote Access
SSH Access
- Navigate to Host in the left menu
- Click Actions > Services > Enable SSH
ESXi Shell
- Navigate to Host
- Click Actions > Services > Enable ESXi Shell
- Note: Consider security implications before enabling
- Recommended to disable when not needed
Verifying SSH Access
Test SSH connection using a terminal emulator:
ssh root@192.168.1.102
# or
ssh root@esxi-2.zerotohero.dev
First-time connection will require:
- Accepting the host key
- Entering root password
- Confirming successful connection
Security Considerations
Self-signed Certificates:
- Default installation uses self-signed certificates
- Expected to generate browser warnings
- Consider proper certificate management for production environments
Remote Access Services:
- Enable SSH and ESXi Shell only when necessary
- Monitor access and usage
- Disable these services when not actively needed
Best Practices
- Always verify configuration changes before disconnecting
- Document all changes made to the system
- Keep security in mind when enabling remote access features
- Use DNS names instead of IP addresses when possible
- Maintain consistent NTP configuration across all hosts
Note: This guide assumes you’re working in a lab environment. Production environments may require additional security considerations and change management procedures.