Virtual Connect Domain User Lacking Privileges

[zeroagemain]

Hi there,

We have numerous Virtual Connect Domains (VC-Eth Fware 3.17) but we find there is a difference between the Local Administrator account and a Domain account with full privileges.

We wanted to set a long string password for local admin and force people to use domain accounts but the issue above is hindering us.

The main problem is that as an AD domain account (even will ALL privileges) all options relating to "Directory Server Settings" are greyed out and cannot be updated unless we use the local admin account. We have this on all our VC's so it's not a glitch but an inherent issue.

Anyone else found this, or found a way around it?

Thanks in advance.

Brett

[Psychonaut]

Setting up LDAP yesterday I noticed the same thing and just figured it was designed that way.  It shouldn't be a big deal as you shouldn't be adding groups or changing those settings very often, if at all after the initial setup.

[zeroagemain]

Hi Psychonaut,

Thanks for the feedback and it's good to hear confirmation that  other people have noticed it.

Although not quite a 'big deal' it's still a pain for us as we don't use local accounts (auditable domain accounts only) except emergencies - so to meet security policy there is a lot of hassle involved around obtaining local admin pwds and then changing them after use. So you're right we don't change these settings often but when we do we have a lot of enclosures and it is a problem for us in our domain enforced environment.

Seems strange to add AD integration functionality but then restrict what AD accounts with full privileges can do. It may be done for a good reason which I'm not aware of, so it would be nice to hear from a HP rep on whether it's likely to be addressed?

Z

[Psychonaut]

Yes it does seem odd - it doens't work that way with the OA, just with the VC.  Perhaps it is corrected with 3.30 - has anyone who's upgraded have any input?

Thanks