Re: server application work load

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

inline

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

<phil2627@xxxxxxxxx> wrote in message
news:1177335899.997447.106270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We are not sure if we are posting this in the correct group, but we
are looking to implement AD. We have 5 critical applications with 2
being accessed by 20 to 125 users at a time and the others 20 to 50
users. Should we have each application on its own server or can we
have multiple apps on one server ?

If the applications are Paintbrush and Notepad you are fine with running
them on the same server. If they are Exchange and SQL Server 2005 then they
should be on seperate servers. The two examples I have given are extremes,
but my point is there is no way any one can make a decision based on the
information you have provided. My examples try to point out the complexity
of the app can dictate what you want to intermix with one another. This
really has nothing to do with AD. So as you make your decision you want to
try and keep systems that could be loading exe's and dll's into the windows
and system32 folder and polluting things seperate as much as possible, since
naming could be similar and they could step on one another. You can also
get yourself in trouble if one machine goes down (Say you have to upgrade
it, or apply an application patch) multiple apps are taken down. Memory,
disk, network and cpu demands can also dictate where you want to place apps.
The best thing for you might be to review Virtual services. This way you
can run multiple apps on a single piece of hardware.


Right now we are planning on putting the DHCP and DNS on the same server.
We are making all of these servers member servers. Thanks.

Placing DNS on a DC is the way to go you can integrate it with AD. There is
some discussion on placing dhcp on a DC and some security concerns. I read
through the article on this and it is extremely minor an das long as the DC
is internal the threat is very small. If I had to build a new system I
would probably place dhcp on a member server though, just because that is
the recommended path by Microsoft.

Having your apps on member servers is the correct architecture. Avoid
placing apps on DC's


.

Relevant Pages

  • Re: server application work load
    ... MVP - Directory Services ... Should we have each application on its own server or can we ... or apply an application patch) multiple apps are taken down. ... Placing DNS on a DC is the way to go you can integrate it with AD. ...
    (microsoft.public.win2000.active_directory)
  • Re: 64-bit - the desaster continues ...
    ... > Server operating systems. ... that hosts ten thousands of mailboxes, server apps using large ... I don't see any competitors rushing out to implement 64-bit ... shipped two 64-bit operating systems compiled with this compiler, ...
    (borland.public.delphi.non-technical)
  • Re: Permissions Chart ?? or web site ??
    ... The environments I deal in tend to have tens of thousands of file shares and thousands of local site admins, 99% of whom don't really understand in the slightest bit how Windows works so the most secure way of doing things is the most simple to understand easily automated way. ... In fact, in most environments I have to work on file share stuff for, I redirect them from ad hoc shares to three types of shares per server and the local site admins don't even have to understand what a share is let alone properly configure it. ... One single share per server for apps run from the servers. ...
    (microsoft.public.windows.server.active_directory)
  • Re: D8: first impression and uneasy feeling... (long)
    ... pack server apps and gui apps. ... I think people that defends .net here is people doing mostly server ... Borland has an incredible potential here, but it has to realize there ... with a .NET server and a win32 client. ...
    (borland.public.delphi.non-technical)
  • Re: adding a terminal server
    ... you will need the applications residing on the terminal server. ... I'm assuming the apps ... be a backstep to run apps and all local users and remote users. ...
    (microsoft.public.windows.terminal_services)