My work needs some new IT

[grepcomputers]

Obviously I don't know much about this situation or your company or IT department (apart from what is posted here). How large is your IT department?

Is it possible that when they tried to get the server back up, something went FUBAR and now they are desperately trying to fix it, and don't yet have an ETA (it happens)? Would you rather have an inaccurate ETA, or none at all?

When you said "new IT" did you mean "new, additional IT" or "replace the existing ones because they are no good"?

 

[dabuddha]

Originally posted by: Billzie7718

Originally posted by: dabuddha
IT was not called because of the power outage. IT was called because the server he needed access to was not up.

Reading comprehension FTW!

A power outage is a likely cause for a downed server. Computer Science FTW!

Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

 

[Jack Ryan]

Give the guy a break. It is infrastructure's responsibility for the server to be up. If the power comes back and it is a few hours later (with no server still) then I would say he has a valid complaint (especially with no ETA!).

 

[Billzie7718]

Originally posted by: 3cho

Originally posted by: Billzie7718

Originally posted by: dabuddha
IT was not called because of the power outage. IT was called because the server he needed access to was not up.

Reading comprehension FTW!

A power outage is a likely cause for a downed server. Computer Science FTW!

well i would have thought IT would know to bring the server back up 2-3 hours after the outage.

Why does everyone assume that if the server is down that in an hour or so it should be back up? If the server simply needs to be rebooted, then ya, an hour is plenty. But, if they had a RAID drive go defunct, which occurs most often in power outages, or some other major problem, it may take a while to correct. I would guess by the fact that he couldn't give an ETA (which is admittedly not a good practice) that he wasn't simply waiting for the server to boot.

 

[dabuddha]

Originally posted by: Billzie7718

Originally posted by: 3cho

Originally posted by: Billzie7718

Originally posted by: dabuddha
IT was not called because of the power outage. IT was called because the server he needed access to was not up.

Reading comprehension FTW!

A power outage is a likely cause for a downed server. Computer Science FTW!

well i would have thought IT would know to bring the server back up 2-3 hours after the outage.

Why does everyone assume that if the server is down that in an hour or so it should be back up? If the server simply needs to be rebooted, then ya, an hour is plenty. But, if they had a RAID drive go defunct, which occurs most often in power outages, or some other major problem, it may take a while to correct. I would guess by the fact that he couldn't give an ETA (which is admittedly not a good practice) that he wasn't simply waiting for the server to boot.

QFT. People just assume computers are magical boxes that you just have to hit the big round button and voila! It's up and running!

 

[JDMnAR1]

Originally posted by: Billzie7718

Originally posted by: 3cho

Originally posted by: Billzie7718

Originally posted by: dabuddha
IT was not called because of the power outage. IT was called because the server he needed access to was not up.

Reading comprehension FTW!

A power outage is a likely cause for a downed server. Computer Science FTW!

well i would have thought IT would know to bring the server back up 2-3 hours after the outage.

Why does everyone assume that if the server is down that in an hour or so it should be back up? If the server simply needs to be rebooted, then ya, an hour is plenty. But, if they had a RAID drive go defunct, which occurs most often in power outages, or some other major problem, it may take a while to correct. I would guess by the fact that he couldn't give an ETA (which is admittedly not a good practice) that he wasn't simply waiting for the server to boot.

Likewise, not knowing the size of the IT shop in question it could be that the particular server he was trying to hit was 95th on the list to be brought back online in the case of a catastrophic failure. Back in May we lost a critical part of our cooling system in the data center - about 18 hours later we had everything back online.

 

[CVSiN]

Originally posted by: 3cho

Originally posted by: j00fek
now you need to post to your EMO BLOG OVER THERE --------------------->

EMO? dont fvcking use that sh1t on me again.

ROFL... you are the freaking defintion of EMO... weak ass whiner rant..

get a life man... IT and Telecom get very busy after an outage.. and things dont magically just pop back up and work 100%..

 

[skace]

Originally posted by: dabuddha
Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

It's not a matter of who he called. It's a matter of who he is blaming for a power outage that is not the responsibility of IT. The power went out while he was working, so either he missed a memo or it was unscheduled. If it was unscheduled then there is a very good risk for failed hardware. All depends on his companies disaster recovery and redundancy plans.

The fact is he put in his topic that the comapny needs new IT people because of an unscheduled power outage that took down servers. We don't even know what kind of hardware support contracts his company has.

 

[Nerva]

Originally posted by: skace

Originally posted by: dabuddha
Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

It's not a matter of who he called. It's a matter of who he is blaming for a power outage that is not the responsibility of IT. The power went out while he was working, so either he missed a memo or it was unscheduled. If it was unscheduled then there is a very good risk for failed hardware. All depends on his companies disaster recovery and redundancy plans.

The fact is he put in his topic that the comapny needs new IT people because of an unscheduled power outage that took down servers. We don't even know what kind of hardware support contracts his company has.

well, my IT dept has been notorious for its incompetence. and i never blamed the power outage on IT, i blame IT for not getting the server back online in time for me to do my work.

 

[Billzie7718]

Originally posted by: 3cho

Originally posted by: skace

Originally posted by: dabuddha
Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

It's not a matter of who he called. It's a matter of who he is blaming for a power outage that is not the responsibility of IT. The power went out while he was working, so either he missed a memo or it was unscheduled. If it was unscheduled then there is a very good risk for failed hardware. All depends on his companies disaster recovery and redundancy plans.

The fact is he put in his topic that the comapny needs new IT people because of an unscheduled power outage that took down servers. We don't even know what kind of hardware support contracts his company has.

well, my IT dept has been notorious for its incompetence. and i never blamed the power outage on IT, i blame IT for not getting the server back online in time for me to do my work.

It's easy to lay blame at the feet of IT. Even if they are as bad as you say they are, they are probably working harder during an outage than you realize. Even if they don't care about getting you up and running, they certainly don't want to listen to people whining all day about how they can't get to their email or network drives.

If someone in IT asked you to perform YOUR job in the amount of time HE felt was adequate, do you think it would be enough?

 

[Nerva]

Originally posted by: Billzie7718

Originally posted by: 3cho

Originally posted by: skace

Originally posted by: dabuddha
Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

It's not a matter of who he called. It's a matter of who he is blaming for a power outage that is not the responsibility of IT. The power went out while he was working, so either he missed a memo or it was unscheduled. If it was unscheduled then there is a very good risk for failed hardware. All depends on his companies disaster recovery and redundancy plans.

The fact is he put in his topic that the comapny needs new IT people because of an unscheduled power outage that took down servers. We don't even know what kind of hardware support contracts his company has.

well, my IT dept has been notorious for its incompetence. and i never blamed the power outage on IT, i blame IT for not getting the server back online in time for me to do my work.

It's easy to lay blame at the feet of IT. Even if they are as bad as you say they are, they are probably working harder during an outage than you realize. Even if they don't care about getting you up and running, they certainly don't want to listen to people whining all day about how they can't get to their email or network drives.

If someone in IT asked you to perform YOUR job in the amount of time HE felt was adequate, do you think it would be enough?

your first point is a valid one.

 

[CVSiN]

Originally posted by: 3cho

Originally posted by: skace

Originally posted by: dabuddha
Duh. But that doesn't change the fact that most of the people are wrong because they're ASSuming he called IT because of the power outage.

It's not a matter of who he called. It's a matter of who he is blaming for a power outage that is not the responsibility of IT. The power went out while he was working, so either he missed a memo or it was unscheduled. If it was unscheduled then there is a very good risk for failed hardware. All depends on his companies disaster recovery and redundancy plans.

The fact is he put in his topic that the comapny needs new IT people because of an unscheduled power outage that took down servers. We don't even know what kind of hardware support contracts his company has.

well, my IT dept has been notorious for its incompetence. and i never blamed the power outage on IT, i blame IT for not getting the server back online in time for me to do my work.

Again cry more....
you obviously are one of those users we as IT people tend to laugh at... semi-educated.. nose in the air.... and a know it all no matter whose job it is..

you're the type of guy that when IT guys see your user name we drag our feet slower on purpose.. just because you think you're so much better than those in the trenches.

with an attitude like yours coming across like this on ATOT I bet youre just loved by your IT guys..

IT Service Center "oh great guys check it out whose crying again.. that guy 3cho... what shouild we do?"
IT tech #1 throw his ticket under that stack over there .. well get to him a week from never.."

 

[grepcomputers]

We also don't know what kind of budgetary and resource (and management) constraints his IT department has to work with. They can be a bit of a handicap at times. And it sucks when you get labeled as incompetent when you are doing your best with very limited resources.

 

[Fraggable]

How about this: You make your own backup plan. You know servers can go down. You should have kept it on your own hard drive, or better yet on an external drive, or better yet on a CD, or better yet on a USB drive, or better yet on 2 systems at once, or better yet all 5 solutions. IT cannot be expected to make sure you are able to access your data 24/7 without interruption.

 

[Fraggable]

You're one of those users I hate. You call because something doesn't work, and get mad when we don't give you an ETA. There is almost never a way to calculate an ETA in the IT industry, expecially with a hardware failure.

You need new 'IT'. What exactly does that mean? I'm sure you don't know. In reality it means you need new information services, which is not what you need.

 

[ViviTheMage]

Originally posted by: kevnich2
I'm in charge of IT at my company and we get called for anything and everything. Apparently working in IT makes me a carpenter, electrician, the fire department and of course the keeper of the internet with a master switch that turns it off on certain people

YUP. I get this one all the time

 

[JDMnAR1]

Originally posted by: 3cho
So now I have lost an hour and half of sleep (very crucial in my profession), and sitting here, twiddling my thumb, and converting O2 to CO2. whiskey tango foxtrot!

How could I have neglected this part?? You lost an hour and a half of sleep - well boo frickin' hoo. Those IT guys that you are badmouthing most likely had to come in and get things up and running at midnight for who knows how long, and then put in a full day and be bright eyed and bushy tailed to support whiny users like you.

 

[altonb1]

Originally posted by: JDMnAR1

Originally posted by: 3cho
So now I have lost an hour and half of sleep (very crucial in my profession), and sitting here, twiddling my thumb, and converting O2 to CO2. whiskey tango foxtrot!

How could I have neglected this part?? You lost an hour and a half of sleep - well boo frickin' hoo. Those IT guys that you are badmouthing most likely had to come in and get things up and running at midnight for who knows how long, and then put in a full day and be bright eyed and bushy tailed to support whiny users like you.

QFT.

 

[ScottFern]

This is the reason why my boss was looking at getting a generator for our server room.

 

[Phoenix86]

Originally posted by: 3cho
(work) needed to go out this morning at 9.

i will just wake up early get in at 8

Waiting 'till the last minute and blaming others for your inability to complete your work FTL.

 

[Nerva]

Originally posted by: Phoenix86

Originally posted by: 3cho
(work) needed to go out this morning at 9.

i will just wake up early get in at 8

Waiting 'till the last minute and blaming others for your inability to complete your work FTL.

dude, did you read the op? the power went out the night before. and before you say i procrastinated the night before, that's how my profession works, nothing gets truly finished until the very last second.

 

[CVSiN]

Originally posted by: 3cho

Originally posted by: Phoenix86

Originally posted by: 3cho
(work) needed to go out this morning at 9.

i will just wake up early get in at 8

Waiting 'till the last minute and blaming others for your inability to complete your work FTL.

dude, did you read the op? the power went out the night before. and before you say i procrastinated the night before, that's how my profession works, nothing gets truly finished until the very last second.

thats a "your" problem.. not an "IT" problem... you should of had your work on a local backup solution as well as the network... not our problem pal.

 

[Feldenak]

Originally posted by: 3cho

Originally posted by: Phoenix86

Originally posted by: 3cho
(work) needed to go out this morning at 9.

i will just wake up early get in at 8

Waiting 'till the last minute and blaming others for your inability to complete your work FTL.

dude, did you read the op? the power went out the night before. and before you say i procrastinated the night before, that's how my profession works, nothing gets truly finished until the very last second.

Lack of preparation on your part does not necessitate an emergency for me.

 

[RadiclDreamer]

Originally posted by: Billzie7718

Originally posted by: dabuddha
IT was not called because of the power outage. IT was called because the server he needed access to was not up.

Reading comprehension FTW!

A power outage is a likely cause for a downed server. Computer Science FTW!

QFT FTW!

 

[Mr Pickles]

You just walked into the Ohio stadium wearing Texas colors...

We work as fast as we can on something just like you work as fast as you can. Telling us it is of the utmost importance that we expedite something does not make us work harder or faster; its a pointless statement. Had this been low priority we would have done what we can as fast as it could be done anyway.

Just to point out, the priority levels in IT don't go 1 to 5 depending on how much the user really really needs something done - they go 1 to 5 depending on how many users are affected and how severe the situation is. I don't care if your outlook archive folders aren't opening and you are late for a deadline and your going to call my CEO and boss' boss' boss if my entire boston office can't login. OP's problem would definately be considered high priority, which means its all helpful hands on deck. I come from a very well respected IT department that expects no less from our customers... we arent OA, we aren't your pages, we aren't at your beckoning for everything and anything, we don't restock paper towels... we are trained certified and well schooled professionals that have just as much pull in a company as you do.

The whole "notorious for being bad IT" thing is definately related only to how well a user understands our priority level. Most drama queens that flip out when their icons aren't where they normally are that have to wait an hour or two to get someone to fix something that takes all of 30 seconds just don't understand and look down on us. If they are a Corporate IT Department in a business then they are professionals at what they do, not some geek squad or renta-support from another country. Your company hired you because you are good at what you do... they hired your IT guys for the same reason, so cut them some slack...

The power issue on hand could have had several critical issues that IT need to take care of. They have a ticket system, you have seen it. When you called them they know you called them and are monitoring it and will not forget you no matter how long it takes to respond because no one wants a pending ticket in their queue for a long time (that was a run-on sentence and I'm too lazy to fix it). Asking for an ETA on something that they are working on is not only worthless but I consider it insulting. Each issue like this that IT deals with is different, its not the same old sh1t, so an ETA on an issue they didnt know they were going to have isn't a fair question to ask. Kick and scream all you want... I'll let you know when its fixed on my own time.

Grab a hanky and stfu, they will fix it when they can.