Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Whats wrong with this picture? 5

Status
Not open for further replies.

group6

IS-IT--Management
May 19, 2005
42
US
Windows Server 2003 domain, only three servers:

1) Windows Server 2003 DC file server and Access db
2) Windows Server 2003 Terminal Server
3) Windows Server 2008 Enterprise running Exchange 2007 Enterprise, 150 mailboxes



 
What a dumb a**, I just realized I started this thread with a BIG typo. It should read:

1) Windows Server 2008 Enterprise DC file server and Access db
2) Windows Server 2008 Enterprise Terminal Server
3) Windows Server 2008 Enterprise running Exchange 2007 Enterprise, 150 mailboxes

_____________________________________________________________________________________________________________

Currently, DHCP on the PDC is using 1 scope. WINS on the PDC also.

Exchange will backup with Mozy Pro, as will the file server. Local backup to tape is also an option. Hadnt thought about SCR.

I know about the stop at 2003 on the way to 2007. I'll probably use one of the present PowerEdge's for the temp 2003 server. I didnt know about the wait after installation. Cant wait a week because its gotta be done in 3 days because the staff will have no access to network resources. (they might as well get 3 days off) I'll have to dig out the Exchange 5.5 media. Hope its where I left it 6 or 7 years ago.

The prospect of an extended 'settle in' period is utterly depressing. Can you elaborate?
 
Once you have Exchange 2007 in the environment, is there still a need for WINS? You don't need it with 2007.

I just noticed the mention of 5.5. You're right - you need to jump to 2003 first (unless you exmerge the data out, then int to 2007, but that brings up other issues), but you could virtualize that if needed.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Agre you need a second DC.
Access DB on a DC. No brainer if you do it right it will be fine.
Exchange 2007 - don't exmerge or the users will hate you. Virtualise a 2000 or 2003. Do SCR.

I'd do DC and terminal server virtualised on the first server sitting on Windows 2008 Enterprise with Hyper V.
Then a DC and Exchange SCR on another one.
Then Exchange 2007 on the third one though ideally you'd want more RAM.

This will give more flexibility and increased recoverability.
 
What is the the advantage of virtualization of the DC and TS over just making the TS a DC without it?

Thats the TS. 2 servers left.

File server as a DC with Exchange SCR.

Last one. Exchange. Are you saying 8GB RAM is not enough?
 
You should never make a TS a DC. Not a good practice to let users log directly into a DC.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
markdmac said
"I'd do DC and terminal server virtualised on the first server sitting on Windows 2008 Enterprise with Hyper V."

Im not up to speed on virtualization . Does this qualify?
 
Zelendakh recommended that and what he was saying was to have the host hold 2 different VMs on it. One for TS the other as a DC.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top