Burned by Eschewing Best Practices
-
@scottalanmiller if doing windows updates is best practice, that's an easy one
I was thinking server configs that conflict or other goodies like that
-
@MattSpeller said:
@scottalanmiller if doing windows updates is best practice, that's an easy one
Don't confuse burned BY a best practice with being burned IN SPITE of a best practice. Not the same thing.
-
@scottalanmiller I don't really see much distinction in that difference but I get the gist of what you mean
-
@MattSpeller said:
@scottalanmiller I don't really see much distinction in that difference but I get the gist of what you mean
It is a HUGE distinction. It's like wearing your seatbelt. You can still get killed but it doesn't tell you that wearing a seatbelt was a bad idea. It still was the safer bet, even if it doesn't always save you.
-
Nothing protects you 100% of the time. There is always risk. Best Practices only exist when they reduce the risk or universally make sense. They can only reduce risk, though, not make it go away. So if it is truly a correct Best Practice sure, it might be wise to understand that they do not protect you 100%, but it is misleading to think of it as being burned BY the best practice which would lead to people saying that they are avoiding doing BPs because of these risks that they present. If anything hints at such behaviour, it is the wrong thinking.
-
Hopefully we managed to head this guy off at the pass. http://community.spiceworks.com/topic/1236071-postgresql-on-ad
Installing PostgreSQL on an already overloaded Active Directory servers! Linux VMs are not just better for this, they are free!!
-
The topic is all kinds of backwards, he offers nothing of what his goal is, just want he wants to do. Has no concept of how everything should work, and is just extremely ill informed.
Does he even have a hypervisor to run VM's on? I'm guessing not and that he's wanting to "make-do" with what he has at the companies disposal.
Which doesn't seem like much.
-
What RDS/Terminal Server on a DC.. Worst thing you could do.
-
@Jason said:
What RDS/Terminal Server on a DC.. Worst thing you could do.
Too late for that particular mistake. But at least, hopefully, kept him from turning his DC into a PostgreSQL server too!
-
@DustinB3403 said:
The topic is all kinds of backwards, he offers nothing of what his goal is, just want he wants to do. Has no concept of how everything should work, and is just extremely ill informed.
But this is typical. So we start with the standard, let's back up and ask what the goal is first before we consider any solutions.
-
This guy gets super defensive when he gets called out for attempting to do the worst possible things. Doesn't even manage a rational defense, actually proves why he was wrong in his response. http://community.spiceworks.com/topic/1237579-vmware-workstation-required-for-xp-32-bit
-
That topic sounds an awful lot like several others asking where to find cracked CD keys and what not. Doing everything illegally because it's "free" to do so.
Yet when the system needs support or work done, nothing can be performed because they aren't legitimately licensed. So then comes the question of "How do I do <insert something completely weird> ?"
The answer is always, license your self properly and upgrade as needed. Trying to maintain 20 year old software without any upgrades is insane.
-
What's weird is he was ONLY trying to spend money and specifically unwilling to even talk about free options, he claimed for the opposite reason. Since when is someone too poor to do something free but can waste money on a paid solution that is more effort? Makes zero sense. That guy is scamming his clients and hoping no one notices. He's just creating something complex so that he can charge more for supporting it.
-
Here's another topic for the pile where an IT person is a contractor for a customer assisting with domain administration, yet there are outside vendors who have domain admin rights, and are changing other domain admin credentials.
Nothings been burned yet, lets find out what's left after the smoke dissipates.
-
http://community.spiceworks.com/topic/1271282-windows-sbs-2003-standard
- Not virtualized
- No full backups, only data backups
- No DR or recovery plan
- Has not updated the OS for a dozen years
- Running SBS instead of the normal OS (not so much a BP as just rarely good)
- Stayed on a long dead server architecture, IA32 has been dead for servers for eleven years
-
@scottalanmiller you forgot one.
- Attempting to reinstall SBS 2003!
-
@DustinB3403 said:
@scottalanmiller you forgot one.
- Attempting to reinstall SBS 2003!
Well he is probably screwed on that point given his lack of other options. He would need new hardware to go to pretty much anything else. He could update to 2008 but he is limited to what will run on 32bit hardware and, I assume, needs to recover his lost data.
-
For an Unlimited amount of money, I may be able to help him
-
http://community.spiceworks.com/topic/1274399-bad-language-frusterated-with-server-boot-drives
- Not using backup software
- Not virtualizing
- Pulling drives out of a RAID array to "do stuff with them" and putting them back
-
@scottalanmiller said:
http://community.spiceworks.com/topic/1274399-bad-language-frusterated-with-server-boot-drives
- Not using backup software
- Not virtualizing
- Pulling drives out of a RAID array to "do stuff with them" and putting them back
haha.... sounds like someone needs to learn some of the basics of systems administration and configuration... should really make a book on that... and use these as wonderful examples of what to not F^&^((& do.
