Looking for Info and or opinion

[sbeaver]

Hey all I would like to get some feedback from you all on a question.

If you were presented an application, lets say something for virtualization but to run it or even install the application, the server that the application would be installed on would have to be a member of a domain.

What are you guys thoughs on that? Would that be a show stopper for you or would it not really matter to you at all?

Any feedback would be great here please

Steve Beaver

VMware Communities User Moderator

VMware vExpert 2009

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

(ISBN:1420070274) from Auerbach

Come check out my blog: www.theVirtualBlackHole.com

Come follow me on twitter

*Virtualization is a journey, not a project.*

[Lightbulb]

I know there are a number of monitoring tools like this that don't really work unless part of AD.

As to whether I would let it in the domain it depends who owns the domain. If it my domain and I want what the app does and am confident it wont cause problems, sure, cause it is my call and my a#$ if something goes south.

If it is a client's domain and they OK it, I will simply state that I cannot support the app and then let them at it.

If it is my domain that the clients servers resides on (with other client systems) then emphatically no.

As long as the App is not making schema updates it usually will not harm AD. Sometimes these apps need pretty elevated privileges to fully function. So there is the security angle to consider.

[Ken_Cline · Accepted solution]

Hi Steve,

I think it's going to depend on the environment. If I had a dedicated test environment, I wouldn't mind dropping something in for evaluation purposes (that's what a test environment is made for, right?) - as long as it didn't mess with my AD schema. If an app messes with the schema, then you're talking about a "project" to do even a simple evaluation - unless I stand up a dedicated virtual domain, which is, in itself, a royal pain.

My guess is that most larger customers are going to have a dedicated test environment that they can drop a product into. The same is not likely to be true for the SMB space, but then, SMBs are not as likely to be saddled with change control requirements as an enterprise customer...

Ken Cline

VMware vExpert 2009

VMware Communities User Moderator

Blogging at: http://KensVirtualReality.wordpress.com/

[Texiwill]

Hello,

I suggest you use what every authentication modes are available to the machine upon which the app is installed....Not everyone uses AD, there is eDirectory, LDAP, NIS, nothing, etc. etc. If it required a domain, not sure it would fit in my environment.

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

[jamieorth]

Hey all I would like to get some feedback from you all on a question.

If you were presented an application, lets say something for virtualization but to run it or even install the application, the server that the application would be installed on would have to be a member of a domain.

What are you guys thoughs on that? Would that be a show stopper for you or would it not really matter to you at all?

Any feedback would be great here please

Steve Beaver

VMware Communities User Moderator

VMware vExpert 2009

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

(ISBN:1420070274) from Auerbach

Come check out my blog: www.theVirtualBlackHole.com

Come follow me on twitter

*Virtualization is a journey, not a project.*

Steve I guess I would chime in with and have to aks "what are the business requirements for the application?". I have had business units aproach IT with an application that they want, usually becuase it serves one purpose. Typically in smaller organizations there is little research done prior to picking an application. Where I get frustrated is when the IT department is not part of the initial conversations, or not even involved before a decision is made. In a previous job we had a department purchase software that had so many requirements that did not fit our environment it was a nightmare to try to implement and way over budget.

As far as your specific question, my personal experience is that is didn't matter to me that AD was a requirement as that is what I have always had......

Regards...

Jamie

If you found this information useful, please consider awarding points for "Correct" or "Helpful".

Remember, if it's not one thing, it's your mother...

[sbeaver]

Good feedback!! Thanks Guys

Steve Beaver

VMware Communities User Moderator

VMware vExpert 2009

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

(ISBN:1420070274) from Auerbach

Come check out my blog: www.theVirtualBlackHole.com

Come follow me on twitter

*Virtualization is a journey, not a project.*