EISNet has been improved in all areas as we have mentioned many times. However, one aspect that we have not discussed so far is folder redirection.
A common problem for EISNet users prior to v1.8 is the limitation of remote working and saving files to the desktop. For example, it has not been easy to allow users to work from home using their EISNet laptop. We implemented a homework user to get around the issue, but for v1.8 we have opted to complete re-invent the way users home and desktop folders are managed.
We have implemented folder redirection for many of the common user folders. A notable benefit of this is any user can now save files to the desktop without fear of having the files deleted when they logoff.
 |
| The users desktop folder as seen from the server |
Previously in v1.7 and below, when a user logs in the Desktop would be created by our LoginScript tool. It looks for allocated software and whether that software is installed on the device. If it is, it creates the shortcut. When the user logs off, the profile, and more importantly, the desktop folder is deleted because it's stored locally on the PC or laptop. This meant, if a user had saved any files to the desktop, they would ultimately be deleted as soon as the user logs off.
In v1.8, the Desktop folder is now redirected to the users personal folder. When LoginScript runs, it now only deletes shortcuts it has previously created and ignores any other files.
In addition, we also redirect their documents, download, favourites, music pictures and videos folders.
 |
| Personal folders for a test user |
This offers us the ability to allow users to work completely offline, as long as they are assigned a roaming profile. Offline Files are assigned to these folder which means Windows synchronises them at login and logoff.
Now that the desktop folder is held and used centrally it creates a problem where a user logs into two devices at the same time. The desktop folder is shared between the two devices, so if you create a text file on one, it will immediately appear on the other. This may seem a benefit, but actually it creates an issue with software shortcuts. When the 2nd PC logs in, Loginscript will delete any shortcuts it's previously created meaning the 1st devices desktop icons will be removed. Further more, the 2nd device will create shortcuts for software that the 1st does not have, resulting in blank unusable links.
We foresee this as being a significant issue for end users.
Restricting Duplicate Logins
As a result of this problem, EISNet v1.8 now stops users logging in at the same time on two different machines.
If a user attempts to login when are already using another device, a friendly message is shown and will return them to the login screen.
Introducing the Logoff Button
With the introduction of Windows 8.1 support to EISNet, we have evaluated where it will work for children of all ages. One particular issue in relation to Windows 8.1 is the inability to logoff the device easily.
A regular user would need to click on the Start Button, which then presents the All Apps view on EISNet. From there, the user would need to go to Metro, then click their Username, then select Sign Out. It seems simple when written in this blog, but a teacher trying to teach KS1 children how to do this is particularly challenging.
As a result, we have added a friendly Log out button for pupils of all ages.
The Log out button is a site wide option and can be turned off from within EISNet Management Studio.
