BYOD and personal device policies in K12 and schools
BYOD is quickly becoming a standard throughout all types of organization, but how does it come into play for K12 schools?
BYOD policies in schools are an effective method of improving and increasing software access and digital learning without the need to invest in hardware.
It may be easier to manage, cheaper to implement and much more realistic to scale in comparison to its higher education counterpart. This is due to a greatly reduced number of students to deliver to and software titles to deliver in K12.
With fewer students to deliver to and fewer software titles to deliver, byod policies in schools are able to provide better access to software for a lower overall investment than is required in higher education. Enabling BYOD reduces the hardware investment necessary for computer-aided learning as, without it, schools would have to fill classrooms and learning areas with managed machines, or provide each student with a machine. This is compounded by higher demand for support and maintenance on IT to ensure organization-owned machines are set up and running correctly.
Current technologies are capable of leveraging and delivering to a multitude of electronic devices, including ultrathin or zero clients such as Chromebooks. Windows applications can be delivered to iPads and Android tablets, or even smartphones and games consoles. While this doesn't immediately sound useful, it's important to remember that all of those mobile devices are keyboard and mouse compatible, allowing virtualized software to be used exactly as it is on computers.
Pupils and students’ lives are heavily weighted toward digital media. They’ll likely be more comfortable with software and computers than textbooks and handwriting. Familiarity helps to improve students’ capacity for learning and performing in almost all aspects; especially when it comes to digital devices used as it directly correlates with productivity and how effectively time can be used. The concept of cognitive ease is highly relevant, and familiarity and comfortableness are two key contributors to this.
Greater familiarity with the medium they’re working in, and with the device they’re working on removes obstacles to learning and achieving. Digital platforms, by their nature, also provide countless additional avenues to keeping students engaged with their learning, caters to a multitude of different learning styles, and allows students to use a wide variety of methods for work output.
Engaged students working in the ways most comfortable and familiar to them are capable of higher results, and better retention of subject matter. There are many studies showing how engaged students are more likely to meaningfully learn rather than just memorize.
2020’s COVID19 pandemic is highly demonstrative of how:
With BYOD policies implemented, students have access to the same electronic devices at home, at school, and when off sick or away. This helps to mitigate interruptions to teaching and working.
It is likely that students will be either required to or able to use their own devices once in higher education and in professional employment. Even if not, it is also likely that they’ll have a one-to-one relationship with the machine they use. This is especially true for employment, should their job entail computer use. For students who are used to working from their own machines regularly and to needing their own machines on a daily basis, the transitions between various life stages will be smoother and less turbulent, helping them succeed and perform more consistently.
Requiring students to own their own machines could result in exclusion/less opportunity for those of a lower socioeconomic status. In the very worst-case scenario, students who do not own their own machines may not have access to the same opportunities and learning experience as other students. They may need to be provided with machines or lessons may need to be structured with both groups of students in mind.
While this is much less of an issue in higher education and employment, it is worth considering in schools and K12 organizations. Younger BYOD users have the potential to be distracted by their own device. This is especially true of their own mobile devices, as well as the electronic devices, mobile devices and personal machines of others as they will have access to resources not related to their lessons, such as websites, video games, and video content. Novelty plays a part in this, and so if BYOD is not new to that student, distraction will be less of an issue.
With BYOD enabled, students will most likely be using their own personal devices and nothing else. This could result in a lack of exposure to other device types and operating systems, making them less agile in how and when they can work digitally.
Enabling BYOD requires giving students access to organizational networks on unchecked machines that IT doesn’t have access to. There are obvious security risks associated with this, many of which can be mitigated through the use of various firewalls and VPNs.
Should any issues arise, schools are less likely to have dedicated IT departments with staff on hand to help in the event of issues. Troubleshooting and fixing any issues will likely be entirely down to teachers of any given session and whether or not a problem can be fixed is dependent on that teacher's IT expertise. This is compounded by unique device types/models per student.
BYOD involves capturing user and usage data on end-machines in order to select the most appropriate delivery technology for any given context. A lot of the data collected isn’t sensitive personal data, rather information on device type, platform, whether the end-user is on-site or off-site. However, it is still a responsibility of any school that collects user data from its students to keep that data safe.
According to research by trendmicro.com 40% of data breaches in US organizations were caused by lost or stolen electronic devices and 50% of organizations that allow BYOD were breached by employee-owned devices. This is demonstrative of how BYOD can result in a weak point in data security for organizations. It is safe to assume that these statistics may be higher in organizations whose users include younger children due to a higher frequency of lost devices. School students may also not be the only user of their personal device, perhaps sharing it with siblings or parents.
It is important to consider each layer of security carefully. With the previously mentioned statistics in mind, limiting the use of SSO as an authentication method. If stolen or lost electronic devices are a leading cause of data breach and devices themselves are being used as identity-verification then there is a potential compromise to security. Two-factor authentication (2FA) may be a useful tool here to keep workflow smooth and security tight.
Password protection will be a necessity for BYOD policies for many reasons, however, the frequency of requiring a password should be considered. Will your users be required to input their password every login/launch (most secure option, compromised user experience), will they be prompted to re-enter it at regular intervals, such as monthly (middle-ground for security and UX) or will they only need to enter it once after checking a ‘remember my credentials’ box (best UX, compromised security)?
BYOD entails allowing users to connect to organizational networks, files, and resources from unchecked and non-managed devices and networks. This opens up organizations to more potential points of infection from malware or viruses. VPNs and firewalls help to mitigate these risks and keep resources clean and uncompromised. With younger BYOD users there may be a higher likelihood of their machine having become infected, therefore increasing the chance of exposure to infection for an organization’s IT systems.
Obviously, there are unique cases and nuances to what each school needs. The following recommendations are generalized to represent the majority of schools’ needs. In reality, the best advice will differ from school to school based on a wide variety of variables, such as number of students, specialisms of the school and ever geographical/logistical features, such as local weather or distance travelled by students to attend classes.
BYOD policies in schools at this stage is useful as an introduction to educational software and academic usage of digital devices. However, students of pre-Kindergarten and Kindergarten age will likely be learning key life and soft skills such as handwriting, reading, mental arithmetic and social interaction. While specialist software and hardware can help with this, it may be detractive to offer BYOD to these young age groups.
With digital electronic devices becoming ever more intrinsic to modern society, kids will begin using them from younger and younger ages. Students of this age may well already be more familiar with digital devices than they are with other forms of information consumption. However, despite being used to working on and learning from computers, tablets and smartphones, they may still lack the discipline to avoid becoming distracted by their own devices. Elementary students may still be too young for BYOD to represent a viable tool for educating them effectively.
At middle school age, students will be used to working more independently and using available resources to complete schoolwork and projects. They will also need skills and experience with digital devices going into high school, and so middle school age is a good age to begin introducing the principles and routine of BYOD.
By high school, students will be well into the routine of completing work and projects at home for school. They will likely be using their own devices, including mobile devices, to accomplish this and will be familiar and comfortable with their specific personal device. Allowing them to continue using their own devices in school and even offering academic software to them on their own devices helps to remove obstacles to learning and achieving and opens up the options of where and when they can work on academic projects.
In this webinar you’ll learn:
Auto validation is still available as an option. We aim to ensure there are as few occasions of attempting to launch but being unable to as possible, and where they occur, explaining why.
Detection occurs during validation - the client is given a list of directories to look in and it returns what it finds.
Dark mode wasn't something we were able to do for this version, but it is something that we are looking to include in the future.
If client download is not available in that instance - such as in labs mode or if client install is suppressed, then the client link will not appear. The client download link will also only appear on platforms which have a client - i.e. Windows and macOS.
If you would like to upgrade to 2.12 please submit a support request and the team will be touch.
To implement BYOD in a cost-effective and sustainable way, schools will need a clear idea of a number of key data points to understand which technologies are necessary and how many licenses of each technology are required: Number of users/devices Weighting of device type/platform (Windows vs Mac vs Linux) Software titles to deliver Usage data on software titles for licensing User groups requiring specialist software You can read more about implementing BYOD policies in schools in the SecurEdge article, ‘How to successfully implement a BYOD program into your school’ > https://www.securedgenetworks.com/blog/how-to-successfully-implement-a-byod-program-into-your-school
With a BYOD policy implemented, schools can begin working to introduce centralized communication points such as Virtual Learning Environments (VLEs) or Learning Management Systems (LMSs). Software delivery tools such as AppsAnywhere also provide areas that can be used to communicate with students. Once BYOD is enabled, schools can be more confident that students are actively accessing digital academic resources through specific channels, and that communication propagated through those channels is much more likely to be seen.
Yes, it can do. While BYOD technologies may be expensive, with the correct provisioning and tools implemented, the decrease in hardware investment required from schools by allowing students to bring their own device and insight from reporting data can help schools save money on their software delivery.
BYOD policies in schools reduce the hardware investment of electronic devices, including mobile devices, needed for schools to offer equal access to digital academic resources to all students. By leveraging student-owned hardware, BYOD policies in schools can increase the resources available to students, such as software, digital media and digital learning environments, at a fraction of the cost of ensuring there are enough organization-owned machines for every student to use. Furthermore, BYOD allows students to access school resources outside of school and outside of teaching hours via their own device.
BYOD policies in schools help to introduce students to completing work from their own devices in preparation for higher education and employment. In an ever-more-digital world, getting used to using personal devices to complete work can help desensitize students to the potential distractions offered by those devices. BYOD can also help students learn to manage their time effectively in a society where the lines between work time and free time are becoming more and more blurred.
We’re excited to be releasing AppsAnywhere 3.0 in December 2022, in time for January enrolment. Your dedicated Customer Success team will be in touch when it’s available to ensure your institution gets the most out of AppsAnywhere.
To get the latest version if you are currently using AppsAnywhere, schedule a call with your specialist implementations team and we can help you to start benefiting from AppsAnywhere 2.12 now.
Most IT professionals get excited when considering new technologies and solutions. Without a doubt, the prospect of a VDI deployment project is likely to get your team’s juices flowing. However, deploying VDI is complex and often includes a host of new infrastructure and unique software management tools. The best advice is to engage with a vendor partner early on so that the design for your campus can be vetted by experts who work with VDI on a daily basis. A vendor partner can also help guide through different architecture scenarios, use cases, and potential pitfalls. All of the knowledge transfer gained will put the IT team in a far better position to successfully deploy and support VDI for your campus.
As is the theme throughout the rest of this article, there isn’t really an objective victor in DaaS vs. VDI. However, when it comes to Higher Ed, we rarely see full DaaS deployments. They’re often saved for more limited use cases, such as temporary BYOD access, or delivering to satellite campuses. For the scale of delivery required by HEIT, VDI will usually come out on top. However, you still need to decide whether to go for legacy VDI, or newer, hosted solutions…
DaaS refers to virtual desktops being provided to organizations as a service-based solution. It will include support for managing, upgrading and maintaining virtual machines. It is a more complete out-of-the-box solution with a price tag to match. Fully-hosted VDI is just like legacy VDI, except you don’t need on-premise server infrastructure, and they are often pay-as-you-go. Fully-hosted solutions are also referred to cloud-hosted solutions and they are the same as VDI, except hosted for you, as the name suggests.
Both VMware and Citrix have a robust product offering across many different solution suites. Historically, Citrix has excelled in the realm of remote app delivery or app remoting solutions. On the other hand, VMware leads the way with full desktop VDI delivery. Deciding on the right approach is solely dependent on the needs of the institution and what goals they are hoping to achieve with the project.
A formal BYOD policy helps to ensure a high chance of success and adoption as well as communicating practical information to users on how to interact with and use software on their BYO devices.
To put it concisely, a BYOD policy should include any or all of the following: Device type Operating system Available resources Security Usage conditions
A BYOD policy is a formal definition and agreement between the BYOD provider (universities) and the BYOD users (students). It is similar to an SLA (Service Level Agreement) between service-providers and outlines how users can expect to interact with their university's BYOD program, as well as any limitations, usage conditions, and compatibility information.
Sign up to our newsletter.
AppsAnywhere is a global education technology solution provider that challenges the notion that application access, delivery, and management must be complex and costly. AppsAnywhere is the only platform to reduce the technical barriers associated with hybrid teaching and learning, BYOD, and complex software applications, and deliver a seamless digital end-user experience for students and staff. Used by over 3 million students across 300+ institutions in 22 countries, AppsAnywhere is uniquely designed for education and continues to innovate in partnership with the education community and the evolving needs and expectations of students and faculty.
Register your interest for a demo and see how AppsAnywhere can help your institution. Receive a free consultation of your existing education software strategy and technologies, an overview of AppsAnywhere's main features and how they benefit students, faculty and IT, and get insight into the AppsAnywhere journey and post launch partnership support.
Register your interest for a demo and see how AppsAnywhere can help your institution. Receive a free consultation of your existing education software strategy and technologies, an overview of AppsAnywhere's main features and how they benefit students, faculty and IT, and get insight into the AppsAnywhere journey and post launch partnership support.