Burned by Eschewing Best Practices

DustinB3403

Here we go, future "BBEBP".

EddieJennings

@dustinb3403 said in Burned by Eschewing Best Practices:

Here we go, future "BBEBP".

The answer to his actual question is to roll a d20 to see if you hit.

DustinB3403

Paging @scottalanmiller

Source

scottalanmiller

@dustinb3403 said in Burned by Eschewing Best Practices:

Paging @scottalanmiller

Source

He's definitely got a mess there.

scottalanmiller

And we are back in full swing, this one is a train wreck:

https://community.spiceworks.com/topic/2072941-virtual-machine-hosting

scottalanmiller

Taking bets, but we just know that this is the cardinal sin of AD. How do so many people, so often, deploy AD without knowing about the names that have to be used? If you get taught one thing about AD, that's it. If you look up AD problems, it's the one thing you always find. It implies that most people deploy AD without having ever seen so much as a discussion about it. How do they even know what AD is or how to acquire it?

https://community.spiceworks.com/topic/2084423-company-website

scottalanmiller

Used a SAN for a NAS task. Has no idea what a SAN is. Overfilled his SAN (not his LUN) and made the whole unit go read only. No means to clear up space because it's a LUN that was larger than his SAN capacity.

https://community.spiceworks.com/topic/2083765-synology-drive-is-full-and-cannot-delete-files-from-iscsi-drive

bnrstnr

@scottalanmiller said in Burned by Eschewing Best Practices:

Taking bets, but we just know that this is the cardinal sin of AD.

I am ashamedly guilty of this, too and we've been living with it for years. I just setup an A record in our AD DNS for www to point to our web host. If I had any issues other than this I would have fixed it by now, but it's not that big of a deal.

RojoLoco

https://community.spiceworks.com/topic/2083822-oh-no-the-feed-service-is-currently-down-nov-7-2017

"oops, we totally blew it when we decided to upgrade the backend during regular business hours.... No, we don't know when it will be fixed."

scottalanmiller

@rojoloco said in Burned by Eschewing Best Practices:

https://community.spiceworks.com/topic/2083822-oh-no-the-feed-service-is-currently-down-nov-7-2017

"oops, we totally blew it when we decided to upgrade the backend during regular business hours.... No, we don't know when it will be fixed."

That one is a pretty major best practice. Deploy off hours. So basic.

Reid Cooper

@scottalanmiller said in Burned by Eschewing Best Practices:

@rojoloco said in Burned by Eschewing Best Practices:

https://community.spiceworks.com/topic/2083822-oh-no-the-feed-service-is-currently-down-nov-7-2017

"oops, we totally blew it when we decided to upgrade the backend during regular business hours.... No, we don't know when it will be fixed."

That one is a pretty major best practice. Deploy off hours. So basic.

Indeed it is.

dbeato

@scottalanmiller Many have done it this way because in the past Microsoft "recommended it" and they did not understand the requirements and kept upgrading their DCs with the same domain name....