With the Windows 10 launch on the horizon, many of you will be wondering when will EiSNet support it. We are aiming to support Windows 10 approximately six months after the release (29th July), but why the delay? As it currently stands, Windows 10 is far from ready for testing. The builds available are still quite unstable and contain many bugs, especially when it comes to deployment. EiSNet also takes advantage of MDT, again this is still being updated and tested by Microsoft. The current release is unable to deploy the recent Windows 10 builds without some heavy modifications.
The six month road map is also in line with Capita. This means that once they are ready to support SIMS on Windows 10, we should be ready with EiSNet. This is crucial as SIMS in the classroom has become more common place, we need to ensure everything is supported and tested before we make it available to you.
We will endeavour to keep you updated on the progress, so please stay tuned.
Thursday, 11 June 2015
Wednesday, 8 October 2014
IOS 8.0.2 Issues
IOS 8.0.2 Issues
After the latest update which was rolled out late September,
I’ve had installs and testing time to see what effects this is having on the
MDM system.
In terms of features it doesn’t really offer much more than
the previous update, the installation of enrolling iPads onto the MDM is where
the major issue is.
I now have two schools which once the iPads are updated to
IOS 8.0.2 are having issues with pushing Apps. Once the iPads are enrolled onto
the MDM, pushing out Apps is an issue. Apps will appear on the main screen on
the iPad but will hang on waiting. I’ve kept an iPad waiting overnight, once
returned in the morning the Apps were still stuck on Waiting. Any iPad on IOS
version 8.0.1 and below will work fine when rolling out Apps.
There has been installs where the latest IOS update has
worked fine so the issue is under investigation at the moment. I have a feeling
that we may need to wait to next IOS release which is rumoured for release 20th
October.
NOTE: I would advise that any iPads that need updating are
put on hold until a working update is released.
Please keep checking the Blog for latest updates.
Monday, 8 September 2014
MDM deploying apps without Apple ID prompt on each iPad
Below are a set of instructions which will resolve the issue
with Apple ID prompting each time an App is deployed.
Open iTunes and sign in with the same Apple ID and password
used on your iPads. This is important because using the same Apple ID and
password to which is used on the iPads is what causes the Apple ID prompt NOT
to display when deploying Apps.
Once signed in, search for the free App you wish to roll out
to your iPads. The search field is located in the top right hand corner.
Once iTunes has searched it's library you will see a list of
related iPhone Apps, iPad Apps and songs.
Select the App you wish to download under the “iPad Apps”
section.
Once downloaded iTunes will store the download file in the
following location:
Music>iTunes>iTunes Media>Mobile
applications.
Now the App/Apps have been downloaded, you then need to
login to your MDM page, Select the group level to where you want to upload your
App.
Once the correct the group level has been selected, click on
the Apps button.
Towards the right hand of the screen you will see the option
“Upload App” Click this option.
You will now need to browse to the App you wish to upload onto
the iPads. Browse to the Mobile Applications folder (Location is shown towards
the beginning of this guide). Select the App and click the Upload App button.
Once the upload App button has been clicked the uploading process will take
place, please be patient because the time the upload process can take all
depends on the size of the App and your upload speed.
Once uploaded, the App will be listed and deployed onto your iPads.
Wednesday, 27 August 2014
We need your help!
As you may know, EISNet Management Studio is about to be re-written from scratch. EiS has spent the last few years developing EISNet into the best Curriculum Management tool in Kent, Medway and Bromley. We are about to embark on re-designing EISNet from scratch which is a huge leap especially as we are thinking the product could be used for the next 5-10 years. So while the core design is extremely important right now, we want to maintain the essence of simplicity EISNet gives, whilst becoming more flexible for those who want it. We have to do this right, from day one.
We have started to mock up a design for EISNet Management Studio and this is where we need your feedback.
In this blog post, you will see some of our ideas in a wire frame layout. The idea of a 'mockup' is so that it's easy to tweak without any programming, and so that everyone works from the same design principle when the coding actually begins.
So how can you help?
Once you have had a quick look below, we really welcome your feedback - whether it's a resounding YES! or a simple 'No - that doesn't work'. All feedback is good. You can either use your Google account to post a comment below this article, or if you don't have one, you can email me directly: kevin dot figg at eis.kent.gov.uk and I will post it on your behalf. If you would prefer your message was not posted here, just let me know in the email.
What are the designs?
While most of the design is yet to be finalised, I can confirm one aspect which cannot be changed. The Management Studio will be Ribbon based. This offers us the functional benefits of Microsoft's design specification for Ribbons, but also allows us to hide it, for those who do not like, nor wish to use it.
Therefore, in the wire-frame drawings below, you will see tabs running along the top. These are in fact ribbon tabs, with buttons just below them. The only exception to this is the Dashboard, which will have no buttons, just the tabs.
User Management
In reality the ribbon would look something like this;
Notice how you no longer see Intakes in the school structure. Listening to feedback, we understand that this is not how schools want their structure. So we will therefore allow any form of structure you wish because our 'Intakes' are now 'Classes'. It will mean a promotion at the end of the year is needed, if you have keystage folders configured - but you do not have to. Below the Pupils level, you are in complete control of the structure and can have as many levels as you wish. This will be the same for Managers and Staff, who can now optionally be separated into multiple folders.
The help window will disappear from the main window - but can be slid back into place. The important design change for the help window is that when you want it, it is always visible. In previous versions of EISNet, the Help panel was visible, unless you were editing packages for example, because the Package Manage window was always on top. You could of course, open the help window in a browser but it was far from ideal.
Device Management
Similar to the user management layout, you would have one dedicated tab page for managing tablets, laptops or PC's.
The initial package management tab/page is a simple list of all available packages. If you select a package, you will be given basic information about it - such as its name, notes and path. You will also be shown where it is deployed to and it's status. You will also be able to see what users it is enabled for. We will also give an optional deployment graphic. This looks empty at the moment - we are keen to add more information.
Notice how you can group packages into folders. This will allow you to deploy the package 'group', rather than select packages individually.
Editing packages is similar to the existing method - but will have a slightly different layout.
The tabs down the left hand side will not look like the sketch. It will appear much more modern than this. If I get chance, I will produce a proof of concept to demonstrate how it will actually look.
The only significant addition above is the ability to add a registry key to determine if a non-MSI package deployed successfully. We are looking at ways of determining the success or failure of a package that is not MSI based. One option which is highlighted above, is that we will mark the package as successfully installed, if the defined registry key exists. We may also add a file based check as well - or a more advanced logic builder.
You will be able to specify which operating system the package is allowed to be deployed on. In this instance, you can still deploy the package to a site, building or room, but the installation will be declined, if the Operating System doesn't meet the requirements.
We will also add the ability to specify a supersedes package. This means if you are trying to deploy Adobe Reader 11, or example, you can specify that it supersedes Adobe Reader 10. Therefore, version 10 will be removed before v11 is installed. (please ignore the misspelling of supersedes in the graphic)
Introducing the Dashboard
Creating a dashboard which collates all areas of interest based on your own selection is something we want to introduce however, we are not 100% sure it will be used, or even wanted in EISNet. This is something we are keen to hear from you about.
Dashboard events
An area where you can see what events are scheduled relating to EISNet. For example, you will be able to see when the backup is scheduled and whether it worked or not. You may also want to put in a reminder to import users in August, or archive users. You could schedule package installation of a night time which integrates with Smart-Lan to allow devices to automatically wake up and shutdown.
Service Status
This enables you to add any device to monitor for its status. For example, check that the internet, SIMS or your telephone services are available.
Reported Problems
You will have a list if issues that staff (or optionally pupils) report to you via their desktop or mobile device. For example, they might want to report their Printer is not working. Rather than leave the class, they simply type a message so you pick it up next time you open Manager. Of course, major issues that prevent learning, will be done the traditional way.
Job List
The job list is your personal work load from either a service status issue, or reported problem. You could also use it as a simple ToDo list that you maintain yourself.
All the Dashboard items are widget based, meaning you can add as many as you wish and organise the in any way you want. It will be personal to your user account so settings will be maintained between sessions.
Finally - I have put a quick proof of concept into an actual application so you can see what the theme would look like, outside of the wire-frame you have in this blog.
So far, that's what we have. All the sketches above are purely our ideas and are likely to change. Do you have any ideas? What have we got badly wrong? Do you think we have got some bits right? We welcome your feedback!
We have started to mock up a design for EISNet Management Studio and this is where we need your feedback.
In this blog post, you will see some of our ideas in a wire frame layout. The idea of a 'mockup' is so that it's easy to tweak without any programming, and so that everyone works from the same design principle when the coding actually begins.
So how can you help?
Once you have had a quick look below, we really welcome your feedback - whether it's a resounding YES! or a simple 'No - that doesn't work'. All feedback is good. You can either use your Google account to post a comment below this article, or if you don't have one, you can email me directly: kevin dot figg at eis.kent.gov.uk and I will post it on your behalf. If you would prefer your message was not posted here, just let me know in the email.
What are the designs?
While most of the design is yet to be finalised, I can confirm one aspect which cannot be changed. The Management Studio will be Ribbon based. This offers us the functional benefits of Microsoft's design specification for Ribbons, but also allows us to hide it, for those who do not like, nor wish to use it.
Therefore, in the wire-frame drawings below, you will see tabs running along the top. These are in fact ribbon tabs, with buttons just below them. The only exception to this is the Dashboard, which will have no buttons, just the tabs.
User Management
In reality the ribbon would look something like this;
The users page would be your one-stop page to do anything with users. For example, it could enable a package for a user or class and also manage the administration network if that is enabled and you are granted enough rights to do so.
Notice how the user list would then be a column based list (or grid as it's officially known). It will enable you to show what ever information you think is important. It will be customisable per administrator who runs the software. For example, a network manager might want to see slightly different information than a teaching assistant or technician.
The general idea is you will only see users you are allowed to manage. For example, a class teacher would then be able to manage the pupils in their class. You may like a technician to manage all pupils, but not staff.
Notice how you no longer see Intakes in the school structure. Listening to feedback, we understand that this is not how schools want their structure. So we will therefore allow any form of structure you wish because our 'Intakes' are now 'Classes'. It will mean a promotion at the end of the year is needed, if you have keystage folders configured - but you do not have to. Below the Pupils level, you are in complete control of the structure and can have as many levels as you wish. This will be the same for Managers and Staff, who can now optionally be separated into multiple folders.
The help window will disappear from the main window - but can be slid back into place. The important design change for the help window is that when you want it, it is always visible. In previous versions of EISNet, the Help panel was visible, unless you were editing packages for example, because the Package Manage window was always on top. You could of course, open the help window in a browser but it was far from ideal.
Device Management
Similar to the user management layout, you would have one dedicated tab page for managing tablets, laptops or PC's.
The main difference with the device structure is the ability to have multiple Sites, Buildings and Rooms. You are no longer restricted to the one level approach in the current version.
Package Management
Notice how you can group packages into folders. This will allow you to deploy the package 'group', rather than select packages individually.
Editing packages is similar to the existing method - but will have a slightly different layout.
The tabs down the left hand side will not look like the sketch. It will appear much more modern than this. If I get chance, I will produce a proof of concept to demonstrate how it will actually look.
The only significant addition above is the ability to add a registry key to determine if a non-MSI package deployed successfully. We are looking at ways of determining the success or failure of a package that is not MSI based. One option which is highlighted above, is that we will mark the package as successfully installed, if the defined registry key exists. We may also add a file based check as well - or a more advanced logic builder.
You will be able to specify which operating system the package is allowed to be deployed on. In this instance, you can still deploy the package to a site, building or room, but the installation will be declined, if the Operating System doesn't meet the requirements.
We will also add the ability to specify a supersedes package. This means if you are trying to deploy Adobe Reader 11, or example, you can specify that it supersedes Adobe Reader 10. Therefore, version 10 will be removed before v11 is installed. (please ignore the misspelling of supersedes in the graphic)
Introducing the Dashboard
Creating a dashboard which collates all areas of interest based on your own selection is something we want to introduce however, we are not 100% sure it will be used, or even wanted in EISNet. This is something we are keen to hear from you about.
Dashboard events
An area where you can see what events are scheduled relating to EISNet. For example, you will be able to see when the backup is scheduled and whether it worked or not. You may also want to put in a reminder to import users in August, or archive users. You could schedule package installation of a night time which integrates with Smart-Lan to allow devices to automatically wake up and shutdown.
Service Status
This enables you to add any device to monitor for its status. For example, check that the internet, SIMS or your telephone services are available.
Reported Problems
You will have a list if issues that staff (or optionally pupils) report to you via their desktop or mobile device. For example, they might want to report their Printer is not working. Rather than leave the class, they simply type a message so you pick it up next time you open Manager. Of course, major issues that prevent learning, will be done the traditional way.
Job List
The job list is your personal work load from either a service status issue, or reported problem. You could also use it as a simple ToDo list that you maintain yourself.
All the Dashboard items are widget based, meaning you can add as many as you wish and organise the in any way you want. It will be personal to your user account so settings will be maintained between sessions.
Finally - I have put a quick proof of concept into an actual application so you can see what the theme would look like, outside of the wire-frame you have in this blog.
So far, that's what we have. All the sketches above are purely our ideas and are likely to change. Do you have any ideas? What have we got badly wrong? Do you think we have got some bits right? We welcome your feedback!
Tuesday, 22 July 2014
Introducing Smart-Lan v2
Firstly - what is Smart-Lan?
Smart-Lan is a simple scheduler that enables schools to automatically wake up and shutdown devices at predefined times. For example, you may want the computers in the IT suite to turn on just before 9am and shutdown again shortly after 3pm. It gets the computers ready for class and saves power at the same time.
There are a number of tools on the market that allow this, so why is Smart-Lan different? Built into the scheduler is the ability to define school holiday periods. This means, the computers will not turn on during the summer holiday, wasting power. Its a great little tool that few know about. EIS traditionally set this up for the school after a new network has been installed, and it is often forgotten about. Which is exactly what the developer of a tool wants to hear. Their product is not noticed. It means it's working.
Having said that, a number of annoying issues have crept over over the past few years but mainly an annoying crash when assigning computers to groups.
The problem with version 1 is that it was written about 4-5 years ago using third party controls that are no longer supported. Therefore, the only real option is to re-write it completely.
Having the past few days spare (and wanting a small break from EISNet if I'm perfectly honest) I decided to see what it would take to rewrite it. Now, a few days later, it's almost ready. Its a reasonably simple tool for what it does, so didn't take long to do.
The benefit of re-writing a product is the ability to do things a new way, and improve on what previously existed.
So what's new?
As a taster, I've included a number of screenshots below
Looks good, but what else is planned?
Well, already built into the core is the ability to assign schedules to devices, not just groups. However, I am not happy with the impact this has on the GUI and have left it out for the time being. I will return to that at a later date.
It is also planned that Smart-Lan will have the option of synchronising with EISNet v1.7 and above. This will allow for automatic syncing of devices and rooms. Further more, we plan on integrating Smart-Lan and EISNet v1.9 much more tightly.
While the core GUI side of the almost completed, we are still a way off being able to use it live in schools. I will update here, on our blog with a release date.
Smart-Lan is a simple scheduler that enables schools to automatically wake up and shutdown devices at predefined times. For example, you may want the computers in the IT suite to turn on just before 9am and shutdown again shortly after 3pm. It gets the computers ready for class and saves power at the same time.
There are a number of tools on the market that allow this, so why is Smart-Lan different? Built into the scheduler is the ability to define school holiday periods. This means, the computers will not turn on during the summer holiday, wasting power. Its a great little tool that few know about. EIS traditionally set this up for the school after a new network has been installed, and it is often forgotten about. Which is exactly what the developer of a tool wants to hear. Their product is not noticed. It means it's working.
Having said that, a number of annoying issues have crept over over the past few years but mainly an annoying crash when assigning computers to groups.
The problem with version 1 is that it was written about 4-5 years ago using third party controls that are no longer supported. Therefore, the only real option is to re-write it completely.
Having the past few days spare (and wanting a small break from EISNet if I'm perfectly honest) I decided to see what it would take to rewrite it. Now, a few days later, it's almost ready. Its a reasonably simple tool for what it does, so didn't take long to do.
The benefit of re-writing a product is the ability to do things a new way, and improve on what previously existed.
So what's new?
- The whole product is targeted for .Net 4.5.1 which adds significant performance increases all over.
- Simplified group management
- Ability to specify that a schedule never expires.
- Import data from Smart-Lan v1
- Import from DHCP Server
- Import from EISNet v1.7 and above
- Search for devices, schedules and groups on the fly
- Flexible holiday periods
- Import holiday periods from iCal files
- Download holiday periods from the web
- Manage group members from device properties
- Manage devices from group properties
- Filtered device listings
- Reboot devices (for scheduled Windows updates)
- Manually invoke reboot, shutdown or wake of devices, groups or multiples of each
As a taster, I've included a number of screenshots below
This is the basic layout of Smart-Lan v2
Adding devices to a group
Group properties. From here you can remove devices from that group
Device properties. From here you can remove the device from a group.
Schedule editor
Search / filter devices. You can also do the same for schedules or groups
Schedules created and ready to go
When downloading the holiday periods you are presented with a choice of LEA calendars
Once downloaded, all the school holidays are downloaded and ready
Looks good, but what else is planned?
Well, already built into the core is the ability to assign schedules to devices, not just groups. However, I am not happy with the impact this has on the GUI and have left it out for the time being. I will return to that at a later date.
It is also planned that Smart-Lan will have the option of synchronising with EISNet v1.7 and above. This will allow for automatic syncing of devices and rooms. Further more, we plan on integrating Smart-Lan and EISNet v1.9 much more tightly.
While the core GUI side of the almost completed, we are still a way off being able to use it live in schools. I will update here, on our blog with a release date.
Thursday, 19 June 2014
LIght Speed MDM v3
Hi, my name is Dean and I'm part of EIS, working in the Technical Support team for over 3 years gaining training and experiences to support and manage schools networks across Kent.
Part of my day to day job is installing and maintaining LightSpeed MDM for schools who wish to manage their IPads this way. This Blog is just a introduction to the new MDM v3 which is due for release on July 1st 2014. When the product is released I will further investigate the pros and cons of the new version.
You may not be aware but LightSpeed are updating their platform to v3.
I haven’t yet had the chance to test and play around with the new platform but during my visit to IT14 I managed to get a closer look into the product from the LightSpeed stand. From my perspective the new version feels and looks modern, and features are now on one page rather than using tabs and pages to display different options.
The new platform uses Charts and graphs to display information about the MDM. For Example you can now view recently added Apps and recently enrolled devices.
According to LightSpeed the following are the main reasons why customers should upgrade:
Managed Distribution – V3 allows you to take advantage of Apple’s managed distribution program to seamlessly pass out and retrieve apps, as well as silently push apps to supervised Devices.
Smart Groups – You’ll automatically get two “smart” (Automatic and dynamic) groups with v3. Such as Teachers and students. This makes it easy to push apps and set Policies based on roles.
Dashboard – Get a snapshot view of your mobile deployment, including recently deployed apps and recently enrolled devices.
For EIS customers the migration will be completed by July 1st 2014. EIS are currently working with LightSpeed so you will not have to do anything. Your login will stay the same but the old MDM website will change from www.lsmdm.com to next.lsmdm.com
According to LightSpeed, v3 is fully supported for IOS7 so any bugs you may have come across hopefully will resolved with the new version.
Monday, 16 June 2014
EISNet v1.8 is out the door. Now for v1.9
Project Nessy is officially released and now being installed in schools. We will be working on an upgrade script so that existing v1.7 sites can be upgraded to v1.8 (providing there are no Windows XP devices). Once that is done, our attention starts to focus on EISNet v1.9
So what is the plan?
Our intention has always been to move to the .Net Framework for the entire EISNet product. We have successfully achieved this for all Client side tools in v1.8. We now need to start work on the bigger task of rewriting Management Studio. This is the primary focus for v1.9.
We have no time scale yet. We need to evaluate the task ahead in the coming months, but it will be released in 2015.
We are hoping to include some new features, which include;
So what is the plan?
Our intention has always been to move to the .Net Framework for the entire EISNet product. We have successfully achieved this for all Client side tools in v1.8. We now need to start work on the bigger task of rewriting Management Studio. This is the primary focus for v1.9.
We have no time scale yet. We need to evaluate the task ahead in the coming months, but it will be released in 2015.
We are hoping to include some new features, which include;
- Class/group based structure
- Vastly improved tools for teachers to manage children and their devices
- Improved importing of users directly from SIMS
- Better package management and deployment
- Improved feedback when completing all types of tasks
- Jobs continue to run (for example, importing users) once Management Studio is closed
- Ability to view whether a device is on-line and who is logged onto it.
Subscribe to:
Posts (Atom)