I've put Linux on PCs for the occasional everyday user, usually multi-booting. But for labs, mostly they need excess help with Windows that they can't expect from IT.
Now when I started building labs it was before there was DOS or Windows and that kind of stuff, and naturally no IT yet either :)
So when I got to a place where they had the modern shitshow already in progress (or lack of progress), I could cry foul as soon as any significant delay was introduced by IT. Anything really that would not have been even a speedbump if there were no IT, much less a roadblock or show-stopper. But I didn't try to say there was an answer right away, I would say eventually nature took its course and delays alone accumulated enough to allow for a site-specific correction. So I stepped up to fill the gap.
>they are basically gaming machines that we bought and maintain independently of the IT department because we have specific computing needs.
Often the only effective approach, and one that nobody else would dream of.
Looks like you are already about in position :)
It may be uncharted territory and you may need to keep on going until you reach unquestionably more effective performance. Otherwise some pressure could develop to turn back
If you're going to get the most out of your scientific equipment, you're going to need a scientist on your team who can navigate the installation & maintenance of the specialized software for various vintages of instruments across multiple versions of Windows and different generations of PC hardware. At the same time moving toward mastery of each instrument itself as a primary goal, so much of the time you need Windows and the PC component of the apparatus to "just work", get out of the way, and never change. Not exactly a good fit for any IT roadmap when you have a PC with needs very far outside their routine or comfort zone. Must be able to do things with Windows that IT can not, resulting in a much more trouble-free experience overall compared to the routine office machines.
IT can rarely do an ideal job even when they have only the office machines to worry about, and some labs have really been needing a lot more than that for a while. If you don't do it, who will?
>if I could find some extra time.
Only took a few short years, and it's really like getting two years experience for every year :\
After that you sure can get a lot more out of the electronics though :)
Oh yeah, this is just Windows, that was challenging enough but the mission-critical instruments depend on it.
You must also be able to demonstrate comprehensive backup and rapid full recovery way more effectively than any alternative if you're doing your best.
As for Linux, the next step at this site would be migration of the internet and office machines to a stable Linux or two, but their IT is not ready for that and I don't know exactly how I would substitute for everything they are doing with Windows either.
I'm glad it's not my turf anyway and took the time to develop a good bridge to IT by reducing their headaches rather than encroaching on their domain. That could not have happened overnight but it was worth it to get stuff accomplished in the labs.
I was too.
I've put Linux on PCs for the occasional everyday user, usually multi-booting. But for labs, mostly they need excess help with Windows that they can't expect from IT.
Now when I started building labs it was before there was DOS or Windows and that kind of stuff, and naturally no IT yet either :)
So when I got to a place where they had the modern shitshow already in progress (or lack of progress), I could cry foul as soon as any significant delay was introduced by IT. Anything really that would not have been even a speedbump if there were no IT, much less a roadblock or show-stopper. But I didn't try to say there was an answer right away, I would say eventually nature took its course and delays alone accumulated enough to allow for a site-specific correction. So I stepped up to fill the gap.
>they are basically gaming machines that we bought and maintain independently of the IT department because we have specific computing needs.
Often the only effective approach, and one that nobody else would dream of.
Looks like you are already about in position :)
It may be uncharted territory and you may need to keep on going until you reach unquestionably more effective performance. Otherwise some pressure could develop to turn back
If you're going to get the most out of your scientific equipment, you're going to need a scientist on your team who can navigate the installation & maintenance of the specialized software for various vintages of instruments across multiple versions of Windows and different generations of PC hardware. At the same time moving toward mastery of each instrument itself as a primary goal, so much of the time you need Windows and the PC component of the apparatus to "just work", get out of the way, and never change. Not exactly a good fit for any IT roadmap when you have a PC with needs very far outside their routine or comfort zone. Must be able to do things with Windows that IT can not, resulting in a much more trouble-free experience overall compared to the routine office machines.
IT can rarely do an ideal job even when they have only the office machines to worry about, and some labs have really been needing a lot more than that for a while. If you don't do it, who will?
>if I could find some extra time.
Only took a few short years, and it's really like getting two years experience for every year :\
After that you sure can get a lot more out of the electronics though :)
Oh yeah, this is just Windows, that was challenging enough but the mission-critical instruments depend on it.
You must also be able to demonstrate comprehensive backup and rapid full recovery way more effectively than any alternative if you're doing your best.
As for Linux, the next step at this site would be migration of the internet and office machines to a stable Linux or two, but their IT is not ready for that and I don't know exactly how I would substitute for everything they are doing with Windows either.
I'm glad it's not my turf anyway and took the time to develop a good bridge to IT by reducing their headaches rather than encroaching on their domain. That could not have happened overnight but it was worth it to get stuff accomplished in the labs.