3

I have virtual center that manages a few ESX hosts and I would like to join it to my Active Directory domain. What things should I consider when making this move? Is there any reason why I would want to avoid this? I believe it will make user management in virtual-center easier.

Improve this question

2 Answers 2

Reset to default
6

I agree with voretaq7 - there is no reason NOT to put vCenter on a AD-joined server when you have the option.

A word of advice though - vCenter behaves bad if you mess around with service accounts etc. I'd strongly consider reinstalling vCenter (and all it's children) if you're planning to join the server to AD and already have vCenter installed.

Improve this answer
4
  • Can you expand on your comments about service accounts and the suggestion to reinstall vCenter (and it's children_?
    – ckliborn
    Dec 20, 2011 at 19:06
  • @ckliborn: I'm not sure what you would like me to say? vCenter has a ton of different services that runs with different user accounts.
    – pauska
    Dec 20, 2011 at 19:55
  • I guess I want to know why you recommend reinstalling vcenter after I join the server to AD
    – ckliborn
    Dec 20, 2011 at 23:36
  • 3
    Because you might experience problems with vCenter services crashing/not starting because of permission issues after the join to AD. I hope this is clear enough for you. Go ahead and put the server in AD without reinstalling, maybe it will work fine for you.
    – pauska
    Dec 21, 2011 at 11:58
1

I see no reason not to do this - In fact from my totally-not-a-windows-admin-and-VirtualCenter-runs-on-a-standalone-box chair it seems to be the Right Thing to do in a Domain environment.

Just be sure you set appropriate VirtualCenter rights for your users and you should be fine...

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .