Issue after adding Esxi 4.1 into Ad Domain

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

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

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

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 ?

Yes, 3.x, 4.x and 5.x are different!

type /sbin/ in front of the command

tried sudo su -  /sbin

in  all cases..showing command not found

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

/bin

Yes, that's the issue, update your path as posted.

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 ?

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)

Please advice  ,how to configure it in a way, so that domain user can use command ..as we use with root id

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

Thanks a lot, got it.

 but now i need to solve it some how?

There is no solution.

You will need to su, type in root password.

It's how it's been designed.

really.. then what is use of creating/adding user ?
if we cant use domain ids to run command like we do in 5.1.

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?

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

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 ?

Thanks a lot.