We will get the issue resolved as soon as possible. Thanks for understanding

Report This Post

Report This Post

No related posts.

We will get the issue resolved as soon as possible. Thanks for understanding

Report This Post

Report This Post

No related posts.

I just enabled Pep easing on the open source version of PrimaryWall. Easing is basically where the notes decellerate into place, making them have a much smoother move across the screen.

Using pep meant I can remove jquery UI which is a really overweight framework to include so hopefully page load will be faster too Over the next few months I will be optimizing page load and including more bug monitoring and hopefully updating the PrimaryWall.com version.

Enjoy

Report This Post

No related posts.

The employee had decided that he could not work his 30 day notice period and also would not communicate with us. In response, Primary Technology sent the employee a letter reminding him of his contractual obligations and asked him to re-consider opening communications with us.

The employee sadly did not re-consider and instead, one month later, initiated employment tribunal proceedings on the grounds of constructive dismisal. At this point he became the “Ex employee”.

Given that we had been accused of constructive dismisal, we decided to seek legal council. I don’t want to go into too much detail about how we used legal council and the approaches used, but it was safe to say that in my opinion the whole case was not handled very professionally. For example, the Ex Employee’s solicitor neglected to mention that the Ex Employee had actually stopped using their services some time before the tribunal hearing, despite the solicitor being duty bound to do so.

We arrived early and fully prepared for our tribunal case. Our legal team and senior managers were eager to hear the truth, myself especially because I was the main target of the accusations.

10AM came and went. At 10.30, we went into the chamber but our opposite hadn’t turned up; neither had his legal representation (we had the delay because the tribunal secretary had spent 30 minutes calling all the contact details available for the Ex Employee and his solicitor).

The case was dismissed with no orders for costs meaning Primary Technology were considerably out of pocket due to legal fees and time wasted. Unfortunately the truth was never investigated

So here it is, evidence that we went through the process only to be dissapointed that we didn’t have our long-awaited day in the tribunal courts.

We believe in transparency as default in Primary Technology and public records often aid us in fulfilling this so with that in mind here is a copy of the public documents that was published from the tribunal.

Report This Post

Report This Post

No related posts.

The employee had decided that he could not work his 30 day notice period and also would not communicate with us. In response, Primary Technology sent the employee a letter reminding him of his contractual obligations and asked him to re-consider opening communications with us.

The employee sadly did not re-consider and instead, one month later, initiated employment tribunal proceedings on the grounds of constructive dismisal. At this point he became the “Ex employee”.

Given that we had been accused of constructive dismisal, we decided to seek legal council. I don’t want to go into too much detail about how we used legal council and the approaches used, but it was safe to say that in my opinion the whole case was not handled very professionally. For example, the Ex Employee’s solicitor neglected to mention that the Ex Employee had actually stopped using their services some time before the tribunal hearing, despite the solicitor being duty bound to do so.

We arrived early and fully prepared for our tribunal case. Our legal team and senior managers were eager to hear the truth, myself especially because I was the main target of the accusations.

10AM came and went. At 10.30, we went into the chamber but our opposite hadn’t turned up; neither had his legal representation (we had the delay because the tribunal secretary had spent 30 minutes calling all the contact details available for the Ex Employee and his solicitor).

The case was dismissed with no orders for costs meaning Primary Technology were considerably out of pocket due to legal fees and time wasted. Unfortunately the truth was never investigated

So here it is, evidence that we went through the process only to be dissapointed that we didn’t have our long-awaited day in the tribunal courts.

We believe in transparency as default in Primary Technology and public records often aid us in fulfilling this so with that in mind here is a copy of the public documents that was published from the tribunal.

Report This Post

Report This Post

No related posts.

Why do we have two servers?

The traditional setup within primary schools has been two physically disjoint networks, one for curriculum users (teaching staff and pupils), and one for the administrative staff. This provided two sets of ring-fenced resources, both servers acting as file and print servers for their users, with the admin server also hosting the SQL databases for MIS systems. The security of these databases was often cited as a reason for keeping the two networks disjoint. However, using robust security practices will be just as effective at protecting sensitive data, and much less restrictive to users authorised to use that data.

What’s changing?

The changes in the way technology is utilized mean that there is more and more cross-over between traditional admin and curriculum use.
Members of the senior leadership team, who have traditionally needed to connect to the admin network, may be teaching and also need access to the curriculum server resources; this would require logging on to a different computer, one connected to the curriculum network, with a different user name and password.
Teaching staff might wish to have access to the MIS systems on the admin server, whether this is for something simple like desktop registering, or more advanced, such as pupil progress recording.

So how is it changing?

The first step in closer integration is the physical joining of the two networks, to allow data to pass between them. This allows for the crossover of data between the systems, but doesn’t allow for some of the greater benefits that can be achieved through the joining of both servers into a single domain. With all machines at a site belonging to a single domain for the whole school, it doesn’t matter whether a user is a curriculum or an admin user, they can log on to any client machine, with a single set of user credentials, and have access to their data, whether it is stored on the curriculum server, the admin server or both. There is also potentially simplified access to shared resources such as printers, as well as greater flexibility in the event of a particular printer failure.

So can we just have one server?

The answer to this question is simple enough, yes, yes you can. With the relative power and storage capacity of computers increasing all the time, many schools who are keen to make budgetary savings see moving their current curriculum and admin servers on to a single machine to be an excellent way to cut costs. Essentially all you are really adding to your MIS server loading is the file and print server role for the curriculum users, and a little overhead for handling things like user authentication. Given that your new server will have a more powerful processor, more memory and probably a better disk subsystem, all that you need to do is add sufficient storage capacity for the curriculum users and you can happily run your school on a single server.

Should I have just one server?

In many ways this is a trickier question. The single server approach, whilst seeming attractive, does remove some of the potential resiliency you could achieve through retaining a two server architecture. In theory it would be possible to make the servers fully redundant with data being mirrored across both servers. Then in the event of one failing, a few minor configuration changes would allow the school to continue on virtually unaffected in the event of server failure, something which would be impossible in the single server school, (or even the traditional style two server school).

It is unlikely that the complexity of such a high degree of resiliency is necessary (or even desirable) in a primary school environment. However having a second server to help maintain the core server functions such as active directory, DNS, DHCP etc., would allow many I.T. functions to continue unaffected within the school whilst a failed server was replaced. This is something well worth considering in the current environment where the internet can provide access to teaching resources and applications in the event that local server based applications are unavailable.

Weighing it up. . .

Single server offers potential savings on hardware costs, and systems management overheads, only having to administer a single server. Its potential weakness is that the server becomes a single point of failure for the whole school, rather than just the curriculum users or admin the staff. However so long as the school have reliable backups, both of it data and active directory, a recovery shouldn’t take more than 48 hours (assuming access to replacement hardware).

Twin server systems have the advantage of maintaining the active directory in the event of a server failure. This will allow users to log on, and with a little forethought in implementation allow access to the internet, shared printers and whatever user data is available on the remaining server whilst awaiting the install and configuration of the replacement server.

Article by Steve Dulson, schools network engineer at Primary Technology

Report This Post

Report This Post

No related posts.

Why do we have two servers?

The traditional setup within primary schools has been two physically disjoint networks, one for curriculum users (teaching staff and pupils), and one for the administrative staff. This provided two sets of ring-fenced resources, both servers acting as file and print servers for their users, with the admin server also hosting the SQL databases for MIS systems. The security of these databases was often cited as a reason for keeping the two networks disjoint. However, using robust security practices will be just as effective at protecting sensitive data, and much less restrictive to users authorised to use that data.

What’s changing?

The changes in the way technology is utilized mean that there is more and more cross-over between traditional admin and curriculum use.
Members of the senior leadership team, who have traditionally needed to connect to the admin network, may be teaching and also need access to the curriculum server resources; this would require logging on to a different computer, one connected to the curriculum network, with a different user name and password.
Teaching staff might wish to have access to the MIS systems on the admin server, whether this is for something simple like desktop registering, or more advanced, such as pupil progress recording.

So how is it changing?

The first step in closer integration is the physical joining of the two networks, to allow data to pass between them. This allows for the crossover of data between the systems, but doesn’t allow for some of the greater benefits that can be achieved through the joining of both servers into a single domain. With all machines at a site belonging to a single domain for the whole school, it doesn’t matter whether a user is a curriculum or an admin user, they can log on to any client machine, with a single set of user credentials, and have access to their data, whether it is stored on the curriculum server, the admin server or both. There is also potentially simplified access to shared resources such as printers, as well as greater flexibility in the event of a particular printer failure.

So can we just have one server?

The answer to this question is simple enough, yes, yes you can. With the relative power and storage capacity of computers increasing all the time, many schools who are keen to make budgetary savings see moving their current curriculum and admin servers on to a single machine to be an excellent way to cut costs. Essentially all you are really adding to your MIS server loading is the file and print server role for the curriculum users, and a little overhead for handling things like user authentication. Given that your new server will have a more powerful processor, more memory and probably a better disk subsystem, all that you need to do is add sufficient storage capacity for the curriculum users and you can happily run your school on a single server.

Should I have just one server?

In many ways this is a trickier question. The single server approach, whilst seeming attractive, does remove some of the potential resiliency you could achieve through retaining a two server architecture. In theory it would be possible to make the servers fully redundant with data being mirrored across both servers. Then in the event of one failing, a few minor configuration changes would allow the school to continue on virtually unaffected in the event of server failure, something which would be impossible in the single server school, (or even the traditional style two server school).

It is unlikely that the complexity of such a high degree of resiliency is necessary (or even desirable) in a primary school environment. However having a second server to help maintain the core server functions such as active directory, DNS, DHCP etc., would allow many I.T. functions to continue unaffected within the school whilst a failed server was replaced. This is something well worth considering in the current environment where the internet can provide access to teaching resources and applications in the event that local server based applications are unavailable.

Weighing it up. . .

Single server offers potential savings on hardware costs, and systems management overheads, only having to administer a single server. Its potential weakness is that the server becomes a single point of failure for the whole school, rather than just the curriculum users or admin the staff. However so long as the school have reliable backups, both of it data and active directory, a recovery shouldn’t take more than 48 hours (assuming access to replacement hardware).

Twin server systems have the advantage of maintaining the active directory in the event of a server failure. This will allow users to log on, and with a little forethought in implementation allow access to the internet, shared printers and whatever user data is available on the remaining server whilst awaiting the install and configuration of the replacement server.

Article by Steve Dulson, schools network engineer at Primary Technology

Report This Post

Report This Post

No related posts.

DEBUNKED – Everyone can see the code therefor it’s easier to exploit it.

All software has security holes. Open-source is more secure because people spot security holes early on and patch them. You can actually see what authentications are used and how badly/poorly they are written. Passwords in open source software have even more security because the methods used to access them are completely open so they are often encrypted/hashed which is more than can be said for Sony and some big Edu tech companies who’s name I won’t mention..

DEBUNKED – Anyone can add to the project therefor it’s easier to add exploits.

Projects have maintainers and many contributors, pull requests (requests to put code into the software) are publicly view-able and have to be merged by a maintainer IE a person of considerable experience/authority. Most pull requests on large projects are often checked by multiple people and tested using unit, integration and full stack tests PRIOR to merge into a final release. Open source projects also publish their patched exploits as security advisories, this gives sysadmins the ability to quickly respond to potential threats. Propriety software has no incentive to accept they had a security hole so tend to quietly patch security fixes in major updates.

DEBUNKED – Surely by default a house with an open door is less secure than a house with a door?

Open source projects have doors and windows just like any propriety software but the doors and locks are specifically designed to be secure by default. Open source projects tend to encourage active security testing and try to engage with the security community to co-operate on security vulnerabilities instead of shutting them out. This means the open source community is not as frequently targeted with malicious hacks, most of the successful hacks are reported to the site admin by the hacker themselves.

If you believed any of these misconceptions ask yourself why and who has lied to you?

C’mon people, OAuth is open source and we all use that every single day (Google, Twitter, Facebook etc.). The common miss-conception that open-source is less secure than proprietry software is just bonkers, we know better and it’s our job to spread the message!

Report This Post

Related posts:

1. How Bradford Primary Schools use Open source without knowing it We find lots of schools opting for services provided by...
2. Being part of an open source project isn’t just for geeks. Since 2009 I have been working on an open source...
3. Top 5 ways people in Primary Schools can contribute to open source projects People working and learning Primary Schools benefit greatly from open...

Today we are pleased to announce the launch version 1.1 of our popular School Holiday Dates website, My School Holidays.

Report This Post

Today we are pleased to announce the launch version 1.1 of our popular School Holiday Dates website, My School Holidays.

Report This Post