Active_Directory [SOLVED]: Joining VMware VSCA with separate PSC to the Microsoft AD

Active_Directory [SOLVED]: Joining VMware VSCA with separate PSC to the Microsoft AD

Home Forums Active Directory Active_Directory [SOLVED]: Joining VMware VSCA with separate PSC to the Microsoft AD

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #34627

    Anonymous

    QuestionQuestion

    I am considering an installing VMware vCenter Server Appliance for our pretty small production environment. After some time playing around it, I have narrowed down a number of questions that I need clarifications with. Can I somehow integrate my AD with the VSCA, so certain users will be able to manage VMware vCenter? An expanded version of this question: Will it be possible if I am running PSC separately from the vCenter itself? And last but not least, how to modify VSCA session timeout value? Any inputs are appreciated.

    #34628

    Anonymous

    Accepted AnswerAnswer

    I’m not so sure about the previous versions of VSCA, but you can easily join VSCA v6.5 to Active Directory Domain. It will allow central management for groups and users within existing AD, so you’ll be able to give them permissions to manage your vSphere infrastructure. And yeah, the integration will be possible even in case you’re running vCenter separately. The important thing here is that you’ll need to join only the platform controller service to AD, not the vCenter itself.

    To answer your last question, the timeout can be modified here: /etc/profile.d/tmout.sh. Find the detailed guidelines in this article: https://www.starwindsoftware.com/blog/vmware-vcenter-server-appliance-vcsa-and-after-install-tricks

    Source: https://serverfault.com/questions/884270/joining-vmware-vsca-with-separate-psc-to-the-microsoft-ad
    Author: Net Runner
    Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.