Jump to content

Recommended Posts

Posted
I will be finding out more shortly, but if - as I fear is the case - they have the same convention as us, which is the construct from year of intake plus name, then it makes it awkward because when combined the year of entry will relate to two different age ranges?!?!

 

Ah, we created a 'standardised' year of entry. ie. all those in secondary age had an entry year of the year they would've started the primary school rather than the secondary, that way there's no overlap.

  • Thanks 1
Posted

For those who have been through it, or have taken steps towards a merge, what do you consider the pros and cons of a single AD, a single network strategy? And how has it worked out in practice?

 

Cheers.

Posted
For those who have been through it, or have taken steps towards a merge, what do you consider the pros and cons of a single AD, a single network strategy? And how has it worked out in practice?

 

Cheers.

 

Well, its one ring to rule them all isn't it? Less complexity - less servers, deploying software can be as simple as a single GPO, sharing things across all schools (which will happen) is as simple as creating a share and adding it to a GPO or script.

 

Whereas different ADs/networks means having to double up on your work - maintaining multiple ADs etc...

 

It also has advantages of being able to 'unify' the schools in terms of teachers from one school being able to log in at any of the other schools etc...

  • Thanks 1

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...