Active Directory on App server

[AKPolarBear]

We are upgrading our network from NT to 2000 to 2003. In this first step, we will be adding two new W2K Terminal Servers to the domain to replace a tired NT WTS based one. We can’t go straight to 2003 so we will move all the NT servers (over time) to 2000 before moving/upgrading them all to 2003. I already have the Macola Application Server and MSSQL on W2K based servers. I know I need to set up an Active Directory so the new Term Servers can join the domain correctly and let users on to the network with their current permissions and such. My problem is that I can’t put AD on the Term Servers. My question then is, can I put the AD on the Macola App server? What are the ramifications of doing so? We have about 50 users.

 

[stravis]

Is your Macola Application Server also running SQL Server? Is it currently running any other services? What are the current specs on that server (processors, memory, drives, raid, etc...)?

Ultimately, it is possible, but based on your answers to the questions above we can determine if it is advisable.

Scott Travis

http://www.infoSpring.net

 

[AKPolarBear]

Macola is the primary application. It does run a tape drive during the off load time.
The server itself is a W2K Advanced, dual 2.86g Xeon, 2 gig ram. The C drive is down to about 6g free but d drive is about 35g. The load is not much.

 

[stravis]

It was not clear in your response if SQL Server is running on this server, but if it is not then the following information is true:

I would say that you can definitely run this server as an Active Directory Server as well as your Macola Application Server. You may see a small decrease in speed with Macola but it is something you can definitely work with for a time as you put all your servers online. You may even find that Macola runs fine with Active Directory and you can use it is a backup controller if needed for your future network.

Scott Travis

http://www.infoSpring.net

 

[abaldwin]

Even though Scott is technically correct, I would suggest that your goal, in the end, would be to have your Macola/SQL server as a Backup AD controller and not the primary.

In a small environment there may be no noticable impact in the beginning but networks only grow, data and response times only need to be quicker, not slower or smaller.

Just my $.02



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[AKPolarBear]

Forgot some details.

SQL is on another server built the same way as this one.

The Macola user base is about 40 - 45 users.

I do have a W2Kpro machine that I could upgrade to Server but it is not true server hardware so I am reluctant to do so.

 

[stravis]

I think it would work fine for now. I agree with Andy in that networks do grow, but the decision as to when you purchase that next server really comes down to internal politics and budgets. If you can react fairly quickly to changing network requirements and be able to bring a new server online in 30 days then sticking with what works is just fine in my opinion. If you are unable to react quickly to changing needs then I agree with Andy and you should not consider using your Macola Application Server as your primary Active Directory Server for any length of time.

Scott Travis

http://www.infoSpring.net