An HTC DoA: Part 3
Continued from Part 2.
It's day 5 now and still no shipping label. I called HTC again and got a slightly different answer out of this rep. This one told me that my ticket had *just* been escalated and was on it's way to the warehouse now. When I told him that the other agents had told me it had already gone up to the escalation team, he started backpedaling and said that although the ticket had been escalated it takes them time to look things over.
4 days? Ya, right.
So I asked for a supervisor. After waiting on hold (no music, just silence so you never know if you've been cut off), a 'supervisor' came on the line (supervisor is in quotes as, having working in a call centre before I have first hand experience pretending to be a co-workers supervisor - it's a very common practice). I asked again what was going on, and she had yet another story. Apparently, HTC's shipping system has been 'down' for 'a few days', and they have no ETA on things. She assured me, though, that (for real this time!) my ticket has been escalated, it should be at the attention of the warehouse, and I should have a label by Monday or Tuesday.
So, starting Monday afternoon (as nobody's around to man the phones on weekends), I'll continue with my daily phone campaign trying to find out when I can possibly expect to send back my wife's brick...err...Nexus One.
Continued in Part 4.
Rant: Microsoft Telephone Activation
I've blogged about Microsoft Telephone Action before, but now I'm off on a rant....
Click 'Continue Reading' for the wall-of-text!
Rant: Business Internets are Serious Business
I work for a non-profit that provides general employment services to the public. In part, we offer a large number of public-access computers for job search purposes, as well as a smaller number of systems for general use. Couple these with ~20 staff workstations and a video conference unit, and we chew through a large chunk of bandwidth each day.
Until now, our dual 6Mbit DSL connections have been making due, but really only because of a WSUS server and two IPCop servers acting and web and update caches. With the possibility of adding new offices and increasing the number of computers on our network, I've been looking in to alternative ways of boosting our throughput.
One of the first plans was to check in to a Fiber connection, but that was quickly scrapped. Unfortunately, we can't afford the $1500/month rates being offered for the lower-tier connections, and the staggering ~$5900/month for a 100Mbit up/down connection is completely impossible. As such, I started looking in to other business packages.
This brings me to the root of my rant. I've never been a big fan of DSL, so my first thought was to check out what was offered by our local cable provider, Shaw Cable. I've used them for my residential internet connection since 1997 and couldn't be happier, especially since they've just started to offer 100Mbit down 2Mbit up service in my area.
After several phone calls to them, however, my opinion has completely changed. Despite the fact that they provide faster service, Shaw is only willing to offer a 15Mbit down/1Mbit up service to businesses. That's the fastest you can go without switching to Fiber, which again is out of our price range. Although the service is slightly cheaper than the DSL equivalent, I need at least 4 static IP addresses, and which Shaw will provide--for an extra $50 on top.
Speaking with their customer service reps was a frustrating experience, because I couldn't get an answer as to why businesses aren't allowed access to higher tiered packages. "That's just the way it is" was all I was told.
As such, we'll be sticking with DSL, and Shaw has lost a potential customer. I hope they eventually decide to let businesses catch up with home users, but somehow, I have my doubts.

Seriously.
Short Non-Tech Rant: Tim Hortons
Wow. I've got quite a long history with Tim Hortons, but for some reason I keep going back (probably because of Roll Up The Rim). This morning at the drive-through was about par for the course.
Her: Welcome to Tim Hortons, how can I help you?
Me: Hi. Can I please get an extra-large tea, with two milk and two sugar?
Her: <several seconds of silence> Ummm, so you want a decaf tea?
Me: Actually, I just want a regular tea.
Her: Okay. Do you want anything in it?
Me: Yes. Two milk, and two sugar.
Her: <several seconds more of silence>. So two cream, and one sweetener?
Me (trying not to sound frustrated): No. Two milk. <pause> And two sugar.
Her: Oh! Okay!
I'm surprised that I didn't end up with a Double-Double instead, as has been known to happen before.
Short Rant: WSUS
I'm running WSUS 3.0 SP2, and it really helps to not only track the update status of my machines, but also because we're only on a DSL connection, and the update caching is a lifesaver. My main complaint with WSUS, though, is the update filtering.
In WSUS, you can tell it what products you want to get updates for, what classification (driver, critical update, service pack, etc...), and even whether to auto-approve them or not, but for some unknown reason, WSUS doesn't let you specify the damn architecture that you want.
Our organization doesn't have any Intanium hardware - why doesn't WSUS let me specifically block that architecture? I only want x86 and x86_64 updates. Is that so hard? Instead, my auto-approve rules happily let those updates download, and then sit and take up space until I run the cleanup wizard.
Come on, Microsoft. Think this one through, please? Maybe introduce it in the 4.0 update?

