Apples angle? If you have to backup everything anyways – why not just move over to a Mac?

At work, we have finally begun the process of upgrading our access control software (Cisco ACS) from an antiquated version to a more recent one. The issue of upgrading has been forced because of necessary features and our version is nearing End of Life. In addition, we are moving the services off dedicated servers and putting them on VMs. I thought this would be fairly straight forward – it’s become anything but.

You see, there are 2 versions in between where we are and where we want to go. (Much like someone upgrading from XP trying to get to 7). Unfortunately for us, a backup from one version can’t be restored to a new version. Upgrading our production boxes also isn’t an option we want to pursue (because if it fails, we’re really hosed).

So our upgrade path? Build two new VM boxes with the old version. Backup our production boxes and restore onto the new ones. Upgrade the new boxes. Then upgrade them again (because you can’t do a full upgrade, it has to go step-by-step).  Of course, this whole process has to be done under a “lockdown” period – seeing as once we start, we can’t have users changing passwords or have new users created.

If you couldn’t tell it’s a lot of fun…

It’s led me to believe that software developers should be gifted with the ability to see down the road 5-10 years. They should be able to know exactly where they will be tomorrow, so they can better plan for today. I mean – really – how hard can it be?

Realistically however, I know that software progresses rapidly – and often requires a complete redesign every couple iterations. Software has to be re-written to take advantage of newer technology and hardware and scrap the old. Upgrade paths aren’t always the cleanest, and we should be prepared for that. However, wouldn’t it be amazing if software could be coded to evolve? No one would ever need an “upgrade” – unless of course your software evolved into something bad. Or somehow we became slaves to this evolution.

Maybe we’re already there. Perhaps now is a good time to move to a Mac.

But where does one draw the line between designing something user-friendly but also secure?

A prime example of this is the User Account Control (UAC) feature that was implemented in Windows Vista. I’m sure the reasoning Microsoft had was to try and educate, as well as warn users, when potentially harmful activity was occurring. This feature would literally pester the user – constantly. While I skipped the Vista flavor of Windows (I recently moved from XP to Windows 7 and love it), I can recall countless times that users would turn off the function – or simply click Ok without a seconds hesitation. Truly convenience of getting on with whatever the user was trying to do outweighed the warning. (Granted – Windows implementation of this feature wasn’t the greatest…I’m just using it to prove a point. )

Passwords are another point of concern on this topic. I believe it was one of the temps from “The Office” that indicated the only thing she learned was that half the employees used “password” as their password. While this is just a TV show – it’s probably more true than not in the actual workplace. A secure password could be defined as one that is changed every 30-45 days, does not contain family names or words found in a dictionary. It also contains uppercase, lowercase, symbols, numbers, and should range from 8 characters to 16 characters. This seems to be a daunting task for any user – let alone your average Joe.

Recently some changes have been made to the wireless on BYU campus. A secure SSID that implemented WPA or WPA2 and required the user to pass a scanning process that ensured the user was up-to-date with Windows patches and had installed a up-to-date antivirus program. While this added 10-20 seconds more time (after the initial setup) from the previous process – the end result was far more secure than the previous implementation (no security, no scanning). According to the network security team, the amount of viruses, attacks, and malicious activity on the network dropped to rates not before seen. So in reality – not only was the network more secure, but performed better. So a win for the user? No – a number of users were annoyed at the extra time this “inconvenience” caused. I even heard complaints that it was an invasion of privacy – that the network team had no right to know what was on a users computer. Sometimes you just have to sigh.

I think this will continue to be a struggle – until users have a deep enough understanding as to why administrators seem to cause so much “inconvenience.”

Until then…I’m not even sure.

There are also two gates that lead to on-campus driveways – roads that are only accessible to full-time staff. Cars would have to get a little RFID that would open the gate when the antenna came in range of the gate.

Recently, BYU has decided to switch over to a system that uses license plate recognition in lieu of parking stickers or gate openers. It’s a pretty novel concept – instead of issuing stickers or passes, students and faculty merely register their license plates online. Parking lots are now enforced by a car that drives around with a camera on it’s roof that reads license plates to verify parking entitlement. Additionally, cameras were installed by the gates that lead on to campus so that when a car pulls up to the gate, it reads the plate and opens it.

Awesome – no more stickers, no more passes, and no more officers having to be out in the cold during the dead of winter…now only if it worked.

Unfortunately, of the 5 times I’ve had to use the gates on campus – it’s worked for me once. After being instructed to contact parking services – I was told that the system “has issues” and that they’re “working on it.”

Luckily for me I only have to use the gate a couple times a week – I can’t imagine the annoyance daily users must encounter. Perhaps they need to upgrade their new system, because systems are available that “can scan number plates at around one per second on cars traveling up to 100 mph.”

Perhaps BYU employees just need to slow down.