Burned by Eschewing Best Practices
-
And it turned out... he'd not even tried basic troubleshooting steps, was only trying to bully a vendor into giving him free out of warranty support that he refused to pay for and then took something out of context and lied about what the vendor said.
Quite the piece of work.
-
This statement here about the level of support he gets, determines if he will replace it with a ubiquiti product or a competitors.
"I am not expecting a replacement unit here. I don't think the unit is completely bricked yet. I think it is in a failed flash state. What I was looking for was some help in returning it to a working state. I have been using this one for quite some time. I have also deployed quite a few of these at different small companies I have worked for over the last several years, so I know they are not bad products. This one just happened to be the one I use at home so it is a little annoying. If I cannot get it working, I will replace it. The level of support I get determines if I replace it with another Ubiquiti product, or a competitors product. It also determines if I keep considering these during evaluations of future deployment scenarios or recommend them to others when asked.
Either way is not that big of a deal for me. "
That right there is "I never needed support during the life of the product, but now I don't want to spend for support or a new product if they don't get me free stuff"
-
@DustinB3403 yeah, they guy has no place in a professional community. He was there only to attempt to extort the vendor.
-
Honestly the vendor did a great job and gave him support for free already.
What more can he expect. If he wants to dick around with the unit and try to get it back to working shape, then use the community forums on Ubiquiti's site and see if they'll help him out.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
Honestly the vendor did a great job and gave him support for free already.
What more can he expect. If he wants to dick around with the unit and try to get it back to working shape, then use the community forums on Ubiquiti's site and see if they'll help him out.
Yeah, that guy is a jackass. 3+ year old AP dies and he tries to wring a new one out of the vendor (who tried to help him, but he boned his device via incompetence) instead of just buying a new one for 80 bucks. I have a feeling he will eventually buy another Ubiquiti since most other APs cost tons more.
-
@RojoLoco said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Honestly the vendor did a great job and gave him support for free already.
What more can he expect. If he wants to dick around with the unit and try to get it back to working shape, then use the community forums on Ubiquiti's site and see if they'll help him out.
Yeah, that guy is a jackass. 3+ year old AP dies and he tries to wring a new one out of the vendor (who tried to help him, but he boned his device via incompetence) instead of just buying a new one for 80 bucks. I have a feeling he will eventually buy another Ubiquiti since most other APs cost tons more.
Yet another "I just realized that if my boss saw this how much trouble I would be in..." threads.
-
Here's a fresh post that will probably turn out to be hilarious...
-
@RojoLoco said in Burned by Eschewing Best Practices:
Here's a fresh post that will probably turn out to be hilarious...
That topic is weird, he needs XP because he needs an old version of chrome. Um. . . why. . . chrome is an application, and can be installed to just about any operating system.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@RojoLoco said in Burned by Eschewing Best Practices:
Here's a fresh post that will probably turn out to be hilarious...
That topic is weird, he needs XP because he needs an old version of chrome. Um. . . why. . . chrome is an application, and can be installed to just about any operating system.
No, you are misreading it. He needs XP and THAT means only old Chrome will run.
-
Burned by thinking money isn't an issue. Oh and IPOD.
And he know's he's burned by bad design.
-
I mean... wow. I would hate to be in his shoes right now. He knows the system is horribly designed, but is forced to implement it anyways. With the only option (according to the topic) the protocol used, either FC or iSCSI.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
Burned by thinking money isn't an issue. Oh and IPOD.
And he know's he's burned by bad design.
yeah, he just gave too much in the OP so it was really confusing.
-
https://community.spiceworks.com/topic/2004966-dwell-poweredge-t110-raid-10-issue
Oh man. Pulled drives in a really bad way.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
https://community.spiceworks.com/topic/2004966-dwell-poweredge-t110-raid-10-issue
Oh man. Pulled drives in a really bad way.
feels bad man -
As much as that thing was set up poorly, he prompted the disaster. He had time to ask what to do before he did it and didn't bother and did the one thing that you really never do, then he did the second thing that you never do. Had he Googled at all, he'd have been fine. Had he followed proper procedures, he would have been fine. If he would have called the vendor, he'd have been fine. So many ways to have not had this happen.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
As much as that thing was set up poorly, he prompted the disaster. He had time to ask what to do before he did it and didn't bother and did the one thing that you really never do, then he did the second thing that you never do. Had he Googled at all, he'd have been fine. Had he followed proper procedures, he would have been fine. If he would have called the vendor, he'd have been fine. So many ways to have not had this happen.
He probably didn't want to tell the client "let me Google that"
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
As much as that thing was set up poorly, he prompted the disaster. He had time to ask what to do before he did it and didn't bother and did the one thing that you really never do, then he did the second thing that you never do. Had he Googled at all, he'd have been fine. Had he followed proper procedures, he would have been fine. If he would have called the vendor, he'd have been fine. So many ways to have not had this happen.
He probably didn't want to tell the client "let me Google that"
We need to call the vendor is definitely good in this situation though
-
Really sounds like an IPOD issue here, but he has 3 NAS which are hosting his VM's, but for some reason no longer work with Hyper-V.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
As much as that thing was set up poorly, he prompted the disaster. He had time to ask what to do before he did it and didn't bother and did the one thing that you really never do, then he did the second thing that you never do. Had he Googled at all, he'd have been fine. Had he followed proper procedures, he would have been fine. If he would have called the vendor, he'd have been fine. So many ways to have not had this happen.
He probably didn't want to tell the client "let me Google that"
He didn't need to tell them, he needed to just do it.
-
Violated the "First Rule of VoIP"... he went to his ISP for his SIP trunk. Big time burned. Also, expected his ISP to inform him of the small print and tried to blame them for his mistakes.
https://community.spiceworks.com/topic/2005735-sip-redundancy
