Dumb Q: How to manage sw licences?
Dumb Q: How to manage sw licences?
Hello everyone, I hope I came to the right place to ask my stupid question. I'm currently working in a company that stuck way way back in time. I'm talking some people are still working in DOS level back in time. There is some revamping of this in progres, but it's going to be a long run.
The "IT department" (called computing department, lol) consist basically of 2 people, boss and me. Boss loves the old days, he's "happily" using Win XP on his computer and hates everything newer than Win7, although half of everything he tries to do doesn't work there anymore (and don't even start with security of the OS). Anyway... that's about the company background and what to expect.
During currently ongoing upgrades to get this company at least to 21st cwntury, there will be some sw licencing happening. I'm expecting like buying dozens of Office 2021 keys and some other standalone soft too. But there's problem with managing those keys, as there is no precedence, no rules and everything's going to be from the scratch almost. People are coming and going, PCs are dying (remember, there are still some DOS machines), hard drives replacing, etc. etc. Windows domain? Not in this company. Ever.
So, how do you keep track of what is installed and where? Thank you very much.
Q: How do you eat an elephant?
A: One bite at a time.
Whilst you are faced with a multitude of issues, don't get lost in the weeds by details when you are trying to untangle the past to move it forward.
A simple spreadsheet to track hardware, licenses and other details like location, specs and primary contact is a perfectly reasonable starting point.
I say that because you don't know what you don't know yet. You might for example discover that some shops are doing their own thing, regardless of company policy.
Creating a ticketing system is useful to track stuff for everyone. I settled on
traxwith web access to people who need it, but the computer literacy levels might prevent some from using this.Burnout is a very distinct possibility in an environment like this, so make sure that you set aside time for you to think. Call it a meeting, call it an on-site visit, whatever you do, take time to think.
Also, remember to backup your work. It's not unheard of for it to vanish unexpectedly if you are perceived as a threat.
Source, I've been working in this profession for 40 years.
I’m not in tech anymore but must comment that I work at a major company in a dynamic field with young, ultra-qualified, ultra-smart personnel that is not horribly computer-unsavvy but I still think I’m the only one in the whole company who opens IT support tickets via a system instead of caling, even though IT pushes the system and even though you get good support via the system and horrible people by calling
I see this everyday.
The ticket system is for the IT department, allowing it to track activities, keep abreast of open tickets, build a knowledge base and share information with colleagues.
Users benefit from this indirectly.
Of course, some managers use ticket systems to manage performance metrics. That doesn't work, but they'll never learn.
If you're buying dozens of Office keys, then a site license for Windows and Office makes a lot more sense.
And those licenses are managed between you and MS. Then it's a simple count of Office installations and you know how many licenses you should be using. You typically do an annual license "true up" with MS.
Or Office 365. Yeah, I know people hate SaaS, but businesses love it. Licensing is flexible and scales up and down as you need it. And you get major updates as long as you have a license, unlike when you buy 2021 Pro Plus or whatever, where you'll always be on 2021.
I always wonder how these relics make any money using systems that old. To do business with some of our clients, they audit us for ISO 27001 compliance once per year. Anything out of support would be flagged and we could lose a lot of business.
It's small grocery store chain in the middle of European nowhere, with about hundred of stores run mostly in small villages. Some of those ancient software was made in-house decades ago for internal ordering from wholesaler (also run by the company) to individual shops. Everything in wholesale warehouse runs on the same DOS thing too, with stock inventory, invoice, ordering, ... There's already plan to (finally!!) put it to sleep and replace with something newer and more flexible, but given how low on resources and manpower the company is, it's not going to happen fast.
Mobile Device Management software to keep track of what’s installed on devices (probably won’t work with DOS)
I personally use a password manager to keep track of software keys, but realistically you should probably look for a way to get licenses that doesn’t involve typing a key everywhere.
MD is a great idea to promote during this transition.
I've found you also need a company system that is independent of system management tools - some places use a help desk ticketing system, some use a change management system.
Some friends in the SMB space use a single system for their company (IT consulting firms) to track their clients, client hardware purchase dates, contracts, warranty, every change they make, Admin accounts, device ID's, their billable time, etc.
This way all info on a client is maintained in a single place in case (this is the important bit) you get hit by a bus.
That's a common refrain - "what happens if bob gets hit by a bus?". Can't have any knowledge dependent upon a single person, everything needs to be maintained in a single, accessible form, hosted on company servers and backed up.
Being a small operation, this could be a hard sell. Maybe an open-source help desk solution that you can host internally would be acceptible. The hardest part with that is defining roles and who has access to what.
Something you may consider - small orgs have difficulty documenting their systems (basically it's a lack of manpower, you got shit to do, and documentation seems unimportant). Since there's a transition, it would be incredibly useful to introduce requirements gathering and documentation. A typical model defines Business Requirements, which are mapped to System Requirements, which are then mapped to Technical Requirements (e.g. One Business Requirement will often map to several System Requirements, which usually map to multiple Technical Requirements).
Look into Business Systems Analysis, there's some intro docs out there for how to do this, it's pretty straightforward, and you don't have to do all the detail, just having some documentation is better than none.
Thanks for deep reply. I'll chew through it.
Documentation is non-existent now and that's what bothers me the most. I, at least, started to put my agenda and acquired how-tos to plain txt files for future, because with so much shit going on I tend to forget stuff. I'd like to extend it and make it system-wide to cover all the IT related stuff in the company with some proper software to do it in (no idea which). But there's virtually no way this lack of documentation will change dramatically anytime soon. There's simply no will from higher ups and even if there was, there would be no manpower to do it :-( We're barely holding things running.
If you can get the organization to switch to Debian, you could do it all with free software and manage the whole thing with Ansible.
I mention this because if the org is running Windows software that old, then current generation FOSS software is going to be a breathe of fresh air, by comparison.
It might not work if someone with a C title has a specific magical Windows package they want.
But even then, I would manage one or two Windows PCs (for a couple of C suite execs) by hand, than a full organization full. And you would save the organization a boatload of money.
There are multitude of OS & software in running. Some people still use DOS, but most of those were already upgraded - to windows XP. These machines are currently being replaced with Win10 ones. But due to some specific old SW there still need to be some DOS machines running, at least for couple upcoming years. Linux is sadly not an option for typical office workers, again due to some software in use. There's at least open source in places where possible with more (Firefox, Thunderbird, tightVNC, ...) or less (LibreOffice) success.
I haven't tried to run DOS on Win10, but I haven't been able to get my old DOS programs to run on anything Windows XP or newer, myself. XP at least had some compatibility options to try. I don't think I've seen those options in Win7 or newer.
It will vary by program, but I've needed DosBox on Windows, as well as on Linux, for anything DOS based that I have run anytime recently.