I have, myself, been an employee in a large organization’s IT Department. And we weren’t well liked, as a department, I tried to be a helpful person, making it that much more possible for people to do their jobs well by giving them the tools or, in most cases, building them for them. Customizing them for the things they wanted to do. I’m decently competent at that stuff, at least within the limited set of environments I’ve built in. I don’t claim to be all-around brilliant or anything like that.
As I said, we weren’t well liked, as a department. It’s an attitude, an anger and a contempt, a frustration and a sense of being trampled upon, like the IT person is here to push you around, not to help you do stuff and they resent it. I know what that’s like. So I want to say that up front. Before I rant at you.
You, the IT Department people where I work. Let me tell you about my day today, working from home. Doing so is a privilege, I don’t have to commute. I don’t have to shell out for the public transportation (rail passes, bus passes) nor do I have to wake up that early so as to arrive at the office. I don’t have to concern myself with other people’s exhalations in yet another COVID season, I’m inherently isolated from that by working from home, and I get to roll out of bed at 8:40 and climb a short flight of stairs to be in my office.
I invested in the situation, I have the hardware and the software to both connect to my workplace-issued computer and run it remotely and to also built tools in my personally owned environment that surrounds it and use them to be more efficient in what I do, and I pass information and file structures and code between the two environments, it’s a great toolbox in total. Oh and yeah, there’s an encrypted drive issued to me by the agency, and any and all files not saved on the agency’s networked drives are instead saved here to this encrypted drive, so in terms of any resources that are “on my local computer”, they’re in a secure space walled off from my personal world on my personal computer. Agency supplied the encrypted drive, I brought the computer.
This morning, I held my cellphone in hand for 2-factor, clicked the VPN connect button, and supplied passwords and codes that had been passed between computer cell and server, but then was told that my operating system on my end was not supported for this connection.
It’s only the VPN itself that declares me obsolete. The actual remote control software (Microsoft Remote Desktop Connection) works fine even from many versions older than what I’m running, and I tend to run the versions of software that I like as tools. But yeah, OK, the VPN is about security so I’ve got to follow your lead.
But you never ever warn us. “Hello, working-from-home folks running MacOS xxxx, you have to upgrade by March xxth; the minumum client OS on the Mac side will be xxxx”. That would be nice; I could upgrade at my convenience within the timeframe. Instead, I try to log on and I can’t get in and I don’t know the minimum OS I need to upgrade to.
I’m remoting in to you from within a virtual machine, an environment configured to run an OS that your picky security VPN software will treat as a legitimate critter. I have several others I could switch to, later versions of this OS and also other totally different operating systems, up to Sonoma on the Mac side and Windows 11 on the Microsoft side.
So I call you.
“I’m getting an error message. This operating system is not allowed in accordance with the security requirements.”
“Are you on a Mac?”
“Yes”
“Well that’s your problem”
“Huh? What do you mean? Did they completely drop support for the Mac last night?”
“No, it’s Apple, they rolled out an update last night and that makes it so it won’t work”
“That’s not what’s going on here…”
“Yes it is, I’m telling you…”
“No it bloody well isn’t, because I don’t have automatic updates turned on!”
“…”
“…Can you tell me the minimum, and the maximum, supported Mac operating system, so I can try with a version that it will accept?”
“Why are you bothering me with this? Just go online and research the product and see what the system requirements are!”
So I go to the company that actually makes the security VPN software package itself. The problem here is going to be that their product isn’t licensed to me, it’s licensed to my employer.
Sure enough, I’m going through a barbed-wire fence of “prove we’re supposed to answer any of your questions”, and I’m just trying to get the system requirements for their damn product. But I’m able to get myself transferred a few times and get connected to someone who at least tries to help. But they just had some outbreak of misbehaving evil code in the wild so yeah I’m a low priority. But he actually tries to find documentation of the current minimum host operating system. Can’t. Says really it should be my IT Department inputting the request because they have an account and can create a support ticket.
Yeah. That. Exactly that.
Fine. I’m guessing that they hopped it to MacOS 13; I do have a MacOS 13 virtual machine set up, but their connection software isn’t installed on it yet, and I’d need to move all my tools and either install or upgrade a handful of apps I was using in 12. What the hell else am I going to do with my time, okay…
I get the same message under MacOS 13. Well… MacOS 14 is the current latest and greatest… and the IT Department guy said “Apple just rolled out an update that isn’t compatible with the latest VPN software” when I called him. So just how narrow a range are they supporting? Not the bleeding edge but not far from it either.
I do eventually end up installing everything on my MacOS 14 virtual machine, and lo and behold, after a security update to the VPN software (which had not prompted on the other OS versions) and a reboot, I was able to connect.
Hey. Hey, IT Department. You weren’t helping. I got a better attempt from someone at the commercial VPN product support line, and I don’t have an account with them.