I am defeated
-
@cakeis_not_alie said:
The long story short is that I created a Starwind configuration that was unsupported. I did so for rational reasons. At the time, this was literally the only way to get what I needed to do done and meet the various requirements on the table. (Which don't need going into, nor am I going to rehash a 1.5 year old build at this juncture.)
I knew at the time of the build that Starwind didn't support storage heavy setups. Sure enough, I paid for it. The damned thing ate some LUNs. I had about 6 months of fighting with the damned thing tooth and nail before I got it stable.
It isn't running a config that is supported by Microsoft or by Starwind. I know that. I also know there aren't any real good choices for this client. Now that it's stable, i expect to see 6 years of service from this thing, but here are rules being broken in order to do what "shouldn't" be done with what's to hand.
I'm wondering, would you do this same solution again knowing what you know now?
-
My guess is that yes, he would, only he would go straight to the working solution instead of the inbetween steps.
-
@Dashrender "I'm wondering, would you do this same solution again knowing what you know now?"
No. Given what I know now I would never touch Starwind with a 50-foot pole. I would instead have gone into a back alley and sucked an unlimited line of dicks to get money for a better solution then ever be in a position to be reliant on Anton for anything, ever.
Now, if Anton weren't involved with the company, I probably would use Starwind again, in the exact same circumstances. But today there are far better options. 1.5 years can change everything in this industry.
-
@cakeis_not_alie Related: today I learned that Spiceworks has an ignore feature: http://community.spiceworks.com/blogs/products/1785-community-preview-user-muting
This won't help the place become more friendly, but at least it will prevent me from righteously toothbrush shanking a few of them at the next Spiceworld. XD
Seriously though, it's amazing how big a difference such features can make. El Reg enabled it on the forums a while back, and they got a LOT better once you could clean off the worst of the trolls.
-
@scottalanmiller said:
My guess is that yes, he would, only he would go straight to the working solution instead of the inbetween steps.
LOL -usually the fact that you have to go through the bad again, and suffer the consequences of that bad are part of the question, not the ability to skip it. If you skipped it, it wouldn't really be doing the same thing again.
-
Need to come hang out in the PowerShell forum. Our troll quotient is almost zero except for a European complaining about date formats
I think we've managed to maintain the old school Spiceworks feel. But we're small, maybe that's the key. -
@Martin9700 Sounds nice. Except for the part where I am a sucky little GUI baby and not overly fond of PowerShell.
-
@cakeis_not_alie said:
@Martin9700 Sounds nice. Except for the part where I am a sucky little GUI baby and not overly fond of PowerShell.
I've started getting into PowerShell, granted most of my scripts consist of copy, paste and "OMGWTFBBQ! WHY YOU NO WORK!?", I am getting there... slowly
-
@nadnerB said:
I've started getting into PowerShell, granted most of my scripts consist of copy, paste and "OMGWTFBBQ! WHY YOU NO WORK!?", I am getting there... slowly
Hey, you never really leave that state, I'm afraid.
@cakeis_not_alie said:
@Martin9700 Sounds nice. Except for the part where I am a sucky little GUI baby and not overly fond of PowerShell.
Which seems odd if you're trying to do automation and NOT spend tons of money. So many things you can do with PowerShell! We have 2 dedicated servers at my work that ALL they do is run PowerShell scripts (maybe 1 old VBS)!
-
@Martin9700 "Which seems odd if you're trying to do automation and NOT spend tons of money. So many things you can do with PowerShell! We have 2 dedicated servers at my work that ALL they do is run PowerShell scripts (maybe 1 old VBS)!"
Not really. Group Policy handles almost all the automation I need. Windows is a wrapper for some legacy applications, that's about it. I don't need Windows to do much except "not crash".
99.95% of my "automation" is done on Linux systems. The overwhelming majority of that automation is pulling various kinds of information from various systems, translating, then injecting. For example, pulling an HTML report from one server, stripping out the useful information and then translating that to XML, which we then inject via API into another system.
I do virtually all of that work with PHP and shell scripts. All the rest of the automation I require is VMware-based, and most of htat is handled by actual applications (like Veeam).
For me at least, Windows is a legacy platform. It's something I'm forced to use, not something I choose to use. When and where there is a specific need to mount up a Windows application, I will. Outside of that, everything I run goes on Linux. The licensing is just easier.
