Jump to content

Recommended Posts

Posted

Looking to redesign the current network due to a number of factors and wondered if my fellow edugeekers would take a gander and let know if I have lost the plot or if it all makes sense.

 

I have 3 Hyper V Hosts currently running 2008 R2 with a HP SAN

 

My plan is to reinstall hosts from scratch with Server 2012 R2 DataCenter (Clustered)

 

Somewhere in this mix may be SCCM 2012 edition.

 

Domain Controllers - Server 2012 R2

=======================

DC01 (Physical) - DC, DHCP, DNS, Radius for Wireless Authentication.

DC02 (VM) - AD, DNS, WSUS, KMS

DC03 (VM) - AD, DNS, WDS & MDT 2013

 

 

User Servers - Server 2012 R2

===================

Approx 200 users per year group

 

US01 (VM) - Years 7, 9, 11

US02 (VM) - Years 8, 10, Exam/Controlled Assessments

US03 (VM) - Year 12, 13 & Staff

 

 

Thin Client/Remote Access - Server 2008 R2

===========================

Give users look and feel of Win7

 

RDP01 (Physical) - Thin client software (VSpace & NComputing)

RDP02 (Physical) - MS Remote Desktop & Gateway

 

 

File/Print - Server 2012 R2

=================

FP01 (VM) - Approx 50 Printer Queues, Staff & Student Shared Documents, Admin Documents

 

 

MIS - Server 2012 R2

=============

MIS01 (VM) - SIMS.net and related bits

 

 

Email (Legacy Server)

==============

Exchange 2010 (VM) - Mail to be migrated to Office 365

 

 

 

 

All comments or suggestions welcomed :D

Posted

Personally I'd forget WSUS, WDS and MDT and have a separate server for SCCM to do these tasks. Failing that I'd put WSUS on its own server and WDS and MDT on another server.

 

I'd also question why separate out the file services? Why not one file server with separate shares for each group?

  • Thanks 1
Posted (edited)

As above, you'll have difficulty with that. What happens with year changes? Do you then copy all the files from one server to another?

Probably better off simplifying it a bit; staff on one, students on another. Maybe even have replication set up on user areas as a failover?

Edited by synaesthesia
  • Thanks 1
Posted

Same as above really, i'd keep the print server separate and we have MDT on its own server as well....allows maintenance and restarts without affecting anything else. We currently have our file servers set up to be as below -

 

File 1 - Staff

File 2 - Students

File 3 - Shared

  • Thanks 1
Posted (edited)
I would separate the print server to be it's own device just so if you have any driver issues etc.... you can work on it separately.

 

I did think about that when looking at the design and tried to keep the number of VMs down - but yes would make more sense to split them

 

 

Personally I'd forget WSUS, WDS and MDT and have a separate server for SCCM to do these tasks. Failing that I'd put WSUS on its own server and WDS and MDT on another server.

 

I'd also question why separate out the file services? Why not one file server with separate shares for each group?

 

Hopefully getting approval to attend a SCCM training course, so if approved then I will be using SCCM instead of WDS, MDT etc... if no approval then will be using WDS etc....

 

My thoughts were since DC only dealing with logons requests etc then utilise the server to do additional roles - again to keep the number of VMs down. It does make sense though separating WSUS and WDS etc.

 

As above, you'll have difficulty with that. What happens with year changes? Do you then copy all the files from one server to another?

 

Sorry, my fault for not explaining my thought process properly, yes would be difficult moving users - my intention was to split the year groups between the the different VMs/hosts. The initial design would be for September. Once set up, a year group would stay on that server until they leave. When a year group leaves and archived, the incoming year group would take its place on that server (if that makes sense)

 

Currently have all Staff, Students and Shared Docs on one VM and at times it runs like a three legged donkey especially when students are creating/editing large files. So my intention was to spread the load/traffic between the servers.

Edited by mdrabble
Posted

My thoughts were since DC only dealing with logons requests etc then utilise the server to do additional roles - again to keep the number of VMs down. It does make sense though separating WSUS and WDS etc.

 

The beauty of VM's, you are not limited in the number of servers you can have (accepting appropriate licencing, ram and cpu capacity). I subscribe to the one server one role notion, thus we have about 30 VMs in total here. Even KMS has been spun off to its own server.

 

Also, especially with WDS, if you need to restart the server for any reason you'll be taking down a DC with it.

  • Thanks 2
Posted
If you plan on using 2012 R2 for your print server check drivers are available for all your printers in both 32 and 64 bit, we had issues with some older printers and 2008 R2 a few years back and reverted back to 2003 in the end.
  • Thanks 1
Posted
I'd totally break this down, I use SCCM 2012 on it's own 2012R2 server (VM), File server on it's own 2012R2 (VM), Print server on it's own 2012R2 (VM), DC1 is Server 2008 (VM), DC2 is physical. Exchange server on 2008R2 (VM), anti virus is on 2012R2 (VM), Microsoft Lync is on 2012R2 (VM), Sharepoint on 2012R2 (VM), Home access on 2008r2 (VM). I have about 20 servers, 2 VM hosts connected via a HP SAN, Physical forefront TMG server, 2 Physical Backup servers (DPM 2012 and VEEAM).
  • Thanks 1
Posted

Thanks for the all the comments and suggestion which have been taken on board and a new revised plan is in my notepad (a paper based one!)

 

For some reason I am finding it easier to write things in my notepad as and when I think of them and also helps as a handy guide :)

 

When I'm not so full of the lurgy I made find the notepad and put the revised version on here another once over :D

Posted
Wouldn't it make sense to put the print server on its own? In you have an issue with it you can power cycle it as needed without taking down the file storage too.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...