Re: Active Directory - Virtualization for performance
- From: "Marcin" <marcin@xxxxxxxxxxxxxxxx>
- Date: Thu, 25 Sep 2008 19:21:36 -0400
Review http://support.microsoft.com/kb/888794 regarding virtualized
installations of AD domain controllers.
In general, the recommendation is to host AD on separate servers -
co-locating it with other apps/services might introduce
performance/compatibility issues and is likely complicate troubleshooting in
case of problems. What range of response times do your applications need
that you are concerned about LAN latency?
Do you know what mechanism is used by your apps to access AD? Do you have
any influence on their design? If so, you should take into consideration
info included in http://msdn.microsoft.com/en-us/library/ms806997.aspx
hth
Marcin
"flcgil" <flcgil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9F350F46-D2C2-4A42-9696-6866A29FF57D@xxxxxxxxxxxxxxxx
I am working on the design of a new environment where we are going to have
a
heavy load of access from the applications to the AD Server. In this
scenario, what are the mechanisms/solutions to get a high throughput?
I was wondering if we could make the AD Server available in the same
physical machine of the Application Server, using virtualization (AD and
the
Application Server run on different virtual machines). In this
configuration,
any access to the AD would not suffer the latency overhead of the LAN bus.
Does anyone have any information about this virtualization approach? Any
other suggestions to get the highest possible throughput?
Thanks
.
- References:
- Active Directory - Virtualization for performance
- From: flcgil
- Active Directory - Virtualization for performance
- Prev by Date: Re: Authentication woes
- Next by Date: Re: Active Directory - single server versus federated servers
- Previous by thread: Active Directory - Virtualization for performance
- Next by thread: Re: Active Directory - Virtualization for performance
- Index(es):
Relevant Pages
|