Solved

Issue after adding Esxi 4.1 into Ad Domain

Posted on 2014-09-23
22
54 Views
Last Modified: 2016-06-21
added my host using vi client to Ad domain.

Tried to login with domain id part of  AD Group named : ESX Admins  -login is fine.

but unable to use any command like we are able to perform in 5.1 for domain ids ?

kindly advice if any more config required to use domain id  with root privilege ?

 and  how can we add local user on esxi 4.1 with root privilege ?
0
Comment
Question by:patron
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 11
  • 10
22 Comments
 
LVL 121
ID: 40341092
if connecting using the vSphere Client with An AD Account in ESX Admins, can you manage the host server?

See here for details, and the video

http://blogs.vmware.com/vsphere/2011/01/esxi-41-active-directory-integration.html
0
 
LVL 1

Author Comment

by:patron
ID: 40341715
everything is fine using vi client.

but if i take putty using domain id and run any command like esxtop  or esxcfg-nics -l
showing output :ash: esxtop or esxcfg :not found

please advice if any more config required for it, id is already part of group named Esx Admins
0
 
LVL 121
ID: 40341855
This is because the path is not set for your user.

change to /sbin

and try the commands, and you may also need to su to root
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 1

Author Comment

by:patron
ID: 40343200
In 5.1, we simply added host to ad domain and all user form group named Esx Admins were able to do everything as earlier doing with root.

but here after adding host Esxi 4.1 to ad domain, we are able to do everything form vi client using domain id part of Esx admins group..but when trying to run any command form putty saying not found ?

Please help to get this resolved..or if any specific configuration we have to do using any command line /file ?
0
 
LVL 121
ID: 40343381
Yes, 3.x, 4.x and 5.x are different!

type /sbin/ in front of the command
0
 
LVL 1

Author Comment

by:patron
ID: 40343453
tried sudo su -  /sbin

in  all cases..showing command not found
0
 
LVL 121
ID: 40343476
so if you do the following it does not work...

cd /sbin

./esxcfg-nics

or

/sbin/esxcfg-nics

it works for me.

and it's bcause your path does not include /sbin

type echo $PATH

what is your path ?

This is ALL standard UNIX/LINUX stuff
0
 
LVL 1

Author Comment

by:patron
ID: 40343601
/bin
0
 
LVL 121
ID: 40343608
Yes, that's the issue, update your path as posted.
0
 
LVL 1

Author Comment

by:patron
ID: 40343657
great, i tried for /sbin/esxcfg-nics

got output for options..but i use any of options like /sbin/esxcfg-nics -l

showing Error:Error During version check:Failed to get vmkernel version:Operation not permitted[Running as non root?]

would be great help  if we can get this fixed ?
0
 
LVL 121
ID: 40343679
Yes, you are non ROOT!

type su (followed by root password)

see here

Local ESX/ESXi 4.1 users are not able to issue any administrative commands (2005299)
0
 
LVL 1

Author Comment

by:patron
ID: 40343815
Please advice  ,how to configure it in a way, so that domain user can use command ..as we use with root id
0
 
LVL 121
ID: 40343867
You need to use SU

This is normal for ESXi 4.1! (yes different to ESXi 5.x)

This is an expected behavior in ESX/ESXi 4.1. Non-root users are not permitted to run administrative commands on an ESX/ESXi 4.1 host. This is true even if they have been granted the administrator role.

Source
http://kb.vmware.com/kb/2005299
0
 
LVL 1

Author Comment

by:patron
ID: 40343970
Thanks a lot, got it.

 but now i need to solve it some how?
0
 
LVL 121
ID: 40344182
There is no solution.

You will need to su, type in root password.

It's how it's been designed.
0
 
LVL 1

Author Comment

by:patron
ID: 40345225
really.. then what is use of creating/adding user ?
if we cant use domain ids to run command like we do in 5.1.
0
 
LVL 1

Author Comment

by:patron
ID: 40345363
Thanks for all ur supportive info here,but still m looking if we can have some way to get this configured, with out using root cred. each time?
0
 
LVL 121
ID: 40345503
Did you read the VMware KB ? There is a workaround published, which is to use su, maybe it's a bug, but VMware ESXI 4.1 is no longer supported, and unlikely to be fixed.

This is an expected behavior in ESX/ESXi 4.1. Non-root users are not permitted to run administrative commands on an ESX/ESXi 4.1 host. This is true even if they have been granted the administrator role.

Source
http://kb.vmware.com/kb/2005299
0
 
LVL 1

Author Comment

by:patron
ID: 40378939
su is fine..to use su everything..it will again ask for root cred right ?

so what's the use of using this su every time

m looking for solution like where root should not be used in any case ?
0
 
LVL 121

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40378962
su is fine..to use su everything..it will again ask for root cred right ?

Correct.

so what's the use of using this su every time

You would need to ask VMware Support.

You are looking for a solution which does not exist.

This is an expected behavior in ESX/ESXi 4.1. Non-root users are not permitted to run administrative commands on an ESX/ESXi 4.1 host. This is true even if they have been granted the administrator role.

Source
http://kb.vmware.com/kb/2005299

I would consider upgrading to a supported platform.
0
 
LVL 1

Author Comment

by:patron
ID: 40388023
Thanks a lot.
0

Featured Post

Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question