The network upgrade project has reached a milestone. The consultants are gone, training for some of our staff has been held, and we are now managing the network ourselves. The project is much more complex than the average user can imagine.
For employees, as soon as you are entered in the accounting system, there is software that automatically creates a new user account for you and assigns you to the correct site. When a student is entered into Infinite Campus, there is a network account created for that student with user name, password, and correct site. All accounts created are automatically put into the correct security groups which, theoretically, assigns them correct permissions to files and folders on the server. This automation has the potential to save many hours of labor creating and moving accounts. This is one of the really good benefits of the new network. It also is not very visible to the end user. And what about the staff members that might teach at more than one site? Those changes have to be made on a case by case basis, just as they were done in the past.
When the network was originally being set up, we wanted to make sure people had access to what they needed. The access and permissions set on the old network did not transfer to the new network. So, we had a dilemma. Do we grant access to everything to everyone (staff only). Or do we grant access and permissions on a case by case basis. We chose to grant everything initially and fix it as soon as we were notified. This was “ugly”. It took several days to get the different permissions correct. We may still have a few staff members that don’t have the access they need. If you don’t have what you need, contact your technologist or the help desk and we will resolve it as soon as possible.
One of the “bad” things was the change in how users logged in. The machines would no longer log in automatically. The user has to put in their user name and password. Several users are not happy with this. The reason to have things this way is for your security. If your machine automatically logs in as you, anyone has access to all of your personal information that you might be keeping on the computer. Another “bad” part of the users logging in is students having difficulty logging in with their credentials (user name and password). I understand this for younger students (k-2). But my personal opinion is any student from 3rd grade on should be able to accomplish this. I understand it takes longer at first, until they get used to it. And time in the computer lab at the elementary schools is limited to 30 minutes. But, this log in is one the student will use for the rest of their career in the Thompson School District. I think it is a good thing for students to know their 6 digit identification number – they need to put it into the machines in the lunch lines in the secondary schools. I don’t know what else it is used for, but it is like my employee number. It is valuable and should be protected like any other personal information.
Because of this difficulty, many sites asked for and were granted “generic log ins”. This is both good and bad. Let’s talk about the “good”. It made it easier for students to log in. That’s it. No other benefit. What about the bad. Well, users logging in as a “generic” user cannot save to the network. This is because they are not members of any security group. And, if a user is not a member of a security group, there is no access to network share points or home folders. That is the way these type of networks are designed. A second “bad” point of having generic users is any user using this account can lock out all other users of this account. This is usually an unintended consequence of a user logging in with the wrong password. After a certain number of attempts with the wrong password, the account is locked. It must be unlocked by someone in the technology department who has credentials to unlock it. For an account that may be district wide, this can not only affect one site, it can affect the entire district. And, with generic accounts, we have a very difficult time tracing where the problem started. As I was re-reading this part, I decided it can also be classified as “ugly”.
So let’s talk about some other good points. We have some new management tools that allow us to do things that were impossible in the past.
We can set up and deploy software district wide in a very short period of time. An example of this is the deployment of Fasttmath. Previously, we would have had a technologist go from machine to machine installing the software. We sometimes would send a small team of 2 or 3 technologists to install the software and it may take them most of the day. When we got the word that Fasttmath was ready for deployment we launched the installers remotely. Within 30 minutes it was installed on over 50 machines in the district without any manual involvement. Within 24 hours, it was installed on over 400 machines in the district. It is set up, on the Mac side, to be installed by a teacher if needed by launching an application called Self-Service and clicking the install button. It takes about 2 minutes. The Windows side has a similar feature although I am not familiar with exactly how it works.
We can re-image a machine in a very short period of time – without losing anything that currently exists on the machine. In the past, if we had a corrupted operating system, we had to back everything up and reinstall the operating system. Then, we had to reset up the machine. With our imaging tools, we just replace the operating system. The user files stay put. This is a very good thing. Many members of our department have not seen this in action yet. Those who have seen it are excited about having this tool available to them.
Another “good” tool at our fingertips is the ability to configure desktops, docks, web browsers, and applications so there is a consistent experience for all users. This can be deployed either per user group or computer group (it really shouldn’t be done on both at the same time). One of the biggest concerns in the past has been students changing docks and desktops and causing issues for students that follow them. We have the ability to customize the user experience to fit the needs of the different sites, and even different labs within the different sites. In the past there have been all sorts of attempts to use 3rd party software to configure the machines and keep them consistent. Some of these, such as Deep Freeze, had unintended consequences. Software updates and anti-virus updates weren’t allowed to be deployed on machines. Other problems, including decreased performance, resulted. With these new tools, those issues are a thing of the past.
But these new tools have brought with them some unintended consequences. For Mac laptop users, there is an issue of much slower log in times away from district sites. The reason this is happening is complex. It has to do with some hidden applications running in the background that allow us to use the tools mentioned above and how the internet works. We are currently working with the vendor of this product and other network engineers to find a solution to this problem. As soon as this is resolved, we will deploy the solution.
So, all in all, there is a lot of change. I have embraced it and am excited about the possibilities. I wonder if you were aware of some of these changes? Now that you are aware of them, how will you try to deal with them? Will you attempt to move forward and change, or will you continue to do things as you have always done them?