We still have two networks but we are working towards merging to one. Until then they are interlinked via trusts and the curriculum servers are dual homed on the admin network so that their resources are available to staff. Only reason we have two is because until recently the LEA mandated this.
Our sims runs fine on two totally different networks .
basically they both still access the server with the hosted SQL by adding the entry into DNS
And every night the SIMS data folder is copied to the other network ( which the client configs point to)
And now i think ive added yet another job to my summer job list !
i still have 8 servers to transfer to Server 2008 , a absolute ton of Computers to reimage to windows 7 ( including making the image)
Plus now got the added task of joining these things together .
And thats not including migrating exchange to 2010 then to another server !
O what fun im going to have doing all that on my ownsum.
Last edited by 2097; 20th October 2011 at 01:28 PM.
We have two networks here, one admin and one curric - it's been that way since the dawn of time. However, things just work here and therefore we do not see the need to merge them. Sims is available on all machines using a trust.
Maybe when the server needs replacing we might look into merging the two, but really can't see any major benefits from going out of my way to do it now. Like I say, if it ain't broke, don't tinker with it.
With Server 2008 now you can have several password policies if I am right?
I successfully had 3 password policies in place on 2008R2 so yes it is perfectly feasible.
Yes, there are various reasons why schools used to run them as two separate networks ... most of these have been touched on already ... the dreadful security in NT4, the management of 'admin' stuff being done centrally by the LA, security practices such as different password policies (have a search for previous discussions on here around ISO27001 also might shed some light) ... and so on.
The idea of security of the MIS being the reason went out the window when people starting splitting the MIS server across the 2 domains ... or when they started using tools to connect into the MIS (e.g. SLG, various learning platforms, SIF-enabled systems, etc)
However, merging the two networks is not a simple job. I have seen a few schools have serious problems when trying to do this, knackered permissions, a lot of duplication of files or loss of files, and worse. If you are thinking of this then I would advise a phased approach to wean people away from the admin network ... even to the point of virtualising the admin server before decommissioning.
Dorset LA still advise two networks and only recently have both my schools gone down the 'trust' route in order to get SIMS on the workstations for the teachers. Many Dorset schools have just merged their networks but there is another consideration, smaller schools often have part-time techs and if admin machines fail they tend to be a bit more mission critical than a teachers machine. If the tech isnt there to fix the machine, problems can ensue!
Also, speaking as a curriculum network person, the separation of networks keeps me away from, and not responsible for, SIMS, for which I am duly very thankful
So...sims goes down and there is a fire, your registers are electronic or are paper but not printed off for the week/kept in a place inaccessible during a fire on that instance...how do you fix this?
Admin is just as vital as teaching and learning, anybody that thinks otherwise is just fooling themselves.
Last edited by CyberNerd; 21st October 2011 at 11:50 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)