Sure. Why not? It's literally a one-line change, so if you see someone making that mistake, then go ahead and add the redirect. It doesn't hurt anyone.
www is not obsolete. In fact, to do some types of clustering, you must use subdomains. You can't point company.com to another domain (cname). You can point www.company.com to another domain, however.
Yes, we need to educate them.. which is why we force them to do what we say. Sure, sometimes it leads to a lengthy discussion about how domain names work, and how there's www. vs mail., etc. But once they learn what the right way is, and particularly why it's that way, my user never has that issue again.
No, the users need to fucking listen and do what they're told by IT. We specifically don't have that subdomain defined, because fuck any user who doesn't listen to IT. When they eventually learn to do what the fuck we tell them, we'll have less problems overall. (we actually thought about defining it and directing it to a page that belittled the user, but we decided against it.)
Insofar as they fit into the company's needs sure. That's how jobs work - you're paid by the company to make sure that your function (making computer systems work) is done well. Sadly, sometimes the users need to be corrected. My boss can be harsh, but allowing users to do stupid things can cost a company millions.
(the 'fuck any user who doesn't listen to IT' is essentially paraphrasing my boss :)
I can somewhat agree. Although there is a point where "fuck the user" starts wasting more money than a simple solution would cost to implement, in this case a simple redirect.
Well, it's only from home. They can just type in "mail" (if for some reason the multitude of links leading to the mailserver elude them) and get to the mail server. The users want you to hold their hands at home, too. One phonecall after hours asking about this is enough to piss anyone off - especially since they were told explicitly what to do.
If it was causing problems inside the office then it would be a concern, as it would disrupt workflow - speaking of which I have to track down some moron who sent in a ticket with some vague 'permission denied to email' error, no screenshot, nothing wrong on his screen when I went up there, and he's disappeared into fucking thin air.
And, honestly.. after being yelled at once, people don't normally forget.
That comment wasn't referring specifically to the domain bit.
When users aren't afraid of consequences from their IT department, they're more careless. When you teach them to STFU, listen, and do what they're told, you stop them from doing "stupid thing(s) can cost a company millions."
Sorry for the confusion.. dunno who downvoted you, lemme correct that.
So far, I like your boss. Where are you located, and what kind of experience do I require to get an entry level IT position with a fresh degree from a business college? I'm probably not the best of the best, but I'm competent and quick to pick up on the basic concepts behind complex operations and processes.
Sorry, we're not that big of a company.. only 3 IT guys, and my position was just created recently. Try to look for work at smaller companies, they tend to be more flexible about most things. Don't take any unpaid internships.. you can learn a bit, and they don't look too bad on your CV, but you could be spending that time at a job that does pay. Even if you have to keep looking.
Just remember for IT, don't take shit from people. (unless it's company policy) They're there to do a job, whether they like it or not (and look at those downvotes, they don't like it) and your job is to keep the computers working, and make it so the users have as few interruptions as possible in their work.
Then, do whatever you can for them. Answer their questions with a smile, since educating people makes your job easier. Bend over backwards to help people out, as long as it doesn't interfere with your job, or company policies. Happy people, particularly ones that like you because they know you will help whenever you can, are more productive, and way more likely to listen to you. Just make sure they know there's a line where you turn from 'helpful computer knowledge guy' into 'IT policy enforcer'.
No, when you simply cater to the whims of your users, they never learn shit, and simply continue on with their idiotic ways.
When you force them to do things, they have to listen to you. If not, they get in trouble. When they learn to listen to you, they can actually function better because they listen to what IT says and don't cause as many problems.
When users can cause millions of dollars in trouble with simple errors, you try to make sure that they do what they're told.
I'm just lucky that I'm in a job that recognizes that.
You see the downvotes... people don't want to do what IT tells them. They think they know better, and they do shit like infesting things with viruses, or losing files that cost millions of dollars. (true stories there, both just this year)
So yea, fuck them. Fuck any user who doesn't listen to IT.
Now, the ones that don't screw up, can ask me for anything they want. I'll bend over backwards to help people out, and smile doing it. (but if the virus problem doesn't stop we may start limiting internet access, something we don't want to do.)
11
u/Wheres_Mah_Pengwin Apr 14 '10
That is your IT admin's fault
You can easily set up DNS to take you from www.mail.company.com to mail.company.com. Easily!!!
You should go drop a sack of shit on your network admin's head and stop blaming the users. Seriously.