Question : Secondary active directory not functioning as a login server

Hello.  I've taken over IT functions for our company and detect a possible disaster in our Active Directory logon system.  We have two servers running Active Directory on Windows Server 2000 (sp4).  Replication of directory changes seems to work fine, but if I disconnect our primary server (DNS, DHCP, Logon), DNS is provided by the secondary server; however, we get a message that says "no logon servers available to service the logon request."  I've read that both server should be a "general catalog" and clicked the appropriate box; however, this secondary server still isn't functioning as a logon server.  That means if our primary server fails, the entire company is affected.  How do I fix this?

Thank you.

Answer : Secondary active directory not functioning as a login server

I definitely recommend putting SQL on a separate server from Exchange. There is just too much resource contention otherwise. With only 12 users, you can actually get two lower powered servers for less than it'd cost to get one large server to run everything under one roof.  It is server 2008 though, so RAM is important no matter how many (or how few) users you have.