{"id":38245,"date":"2010-08-05T16:38:41","date_gmt":"2010-08-05T16:38:41","guid":{"rendered":"https:\/\/www.vmengine.net\/2010\/08\/05\/esxi-4-0-esxi-4-1-how-to-enable-cli-and-ssh-access\/"},"modified":"2025-05-23T17:08:38","modified_gmt":"2025-05-23T17:08:38","slug":"esxi-4-0-esxi-4-1-how-to-enable-cli-and-ssh-access","status":"publish","type":"post","link":"https:\/\/temp-new.vmenginelab.com\/en\/2010\/08\/05\/esxi-4-0-esxi-4-1-how-to-enable-cli-and-ssh-access\/","title":{"rendered":"ESXi 4.0 – ESXi 4.1 : How to Enable CLI and SSH Access"},"content":{"rendered":"

\"\"<\/a>\"\"<\/a><\/p>\n

As is known to operators in the sector, the fundamental difference between ESX and ESXi Hypervisors, in addition to the very convenient possibility of being able to use ESXi in free mode, is the lack of the Management Console.<\/p>\n

But in truth the CLI in ESXi is not missing, it is simply deactivated and here we describe the procedures to be able to reactivate it and be able to access via SSH remotely for particular administrations such as the installation of drivers not in the HCL of VMWare.<\/p>\n

It goes without saying that these operations are not supported by VMWare, so any malfunctions could cause the assistance to lapse.<\/p>\n

ESXi 4.0<\/h3>\n

In the case of version 4.0 just press
\n the Alt + F1<\/em>
\n<\/strong> keys and the console opens, at this point type
\n unsupported <\/em>
\n<\/strong>and
\n Enter <\/em>
\n<\/strong>and you will be asked for the root password. We have thus entered the CLI console. To allow remote SSH access we need to edit the
\n \/etc\/inetd.conf<\/em>
\n<\/strong> file by uncommenting
\n #<\/em>
\n<\/strong> on the
\n #ssh<\/em>
\n<\/strong> line and save. In this case we must use the vi <\/em> command<\/p>\n

<\/strong> <\/p>\n

Once this is done, we run the
\n services.sh<\/em>
\n<\/strong> restart command to activate SSH access.<\/p>\n

If the
\n unsupported <\/em>
\n<\/strong>operation should give problems, it is advisable to take a look at the
\n Advanced Settings<\/em>
\n<\/strong> via
\n VI client<\/em>
\n<\/strong>, uncheck the
\n VMkernel.boot.techSupportMode<\/em>
\n<\/strong> and restart the hypervisor.<\/p>\n

ESXi 4.1<\/h3>\n

The activation of the CLI and SSH access in this version is nicer, you should follow the screenshots below:<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

Now we can press the famous Alt + F1<\/p>\n","protected":false},"excerpt":{"rendered":"

As is known to operators in the sector, the fundamental difference between ESX and ESXi Hypervisors, in addition to the very convenient possibility of being able to use ESXi in free mode, is the lack of the Management Console. But in truth the CLI in ESXi is not missing, it is simply deactivated and here […]<\/p>\n","protected":false},"author":2,"featured_media":29079,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[97],"tags":[1784,1646,405,1725,1726,251,1785,1014,228,259,326],"class_list":["post-38245","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-en","tag-cli-en","tag-esx-en","tag-esxi-en","tag-esxi-4-0-en","tag-esxi-4-1-en","tag-hypervisor-en","tag-remote-cli-en","tag-ssh-en","tag-technical-en","tag-virtualization-en","tag-vmware-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t