Slashdot Mirror


User: tinle

tinle's activity in the archive.

Stories
0
Comments
2
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 2

  1. Set limits (policies), stick to it. on How Do IT Guys Get Respect and Not Become BOFHs? · · Score: 1

    Been there, experienced that... took me a long time to learn how to deal with it properly.

    If you have not create one yet, do it now! I am talking about IT policies and a ticketing system.

    Create a priority system, plenty of choices. My personal choice is a 5 priorities system. Keep it simple. Users won't read more than one paragraph anyway.

    1 - very low priority, I get to it when there is nothing else to do.
    2 - low priority, but need to be taken care of sometime this quarter
    3 - normal priority, need to be taken care of within 5 business days
    4 - high priority, to be resolve within a business day
    5 - burning, must be dealt with now.

    Then setup a helpdesk ticketing system. Again lots of choices. Personally I'd use opensource, currently using OTRS (also used Cerberus, which I like). Let that be your records if your users want to know what you've been doing. Set it to have all incoming request default go 3 (or 4).

    At first your users will scream, make lots of noise, etc. Just stick to your policies. In the beginning there will be jerks who demanded they are taken care of first. Gently steer them to the helpdesk system, create their tickets for them. I've had people call me on the phone, IM me, badger me in the hall, while I am eating lunch, etc. Just tell them to open a ticket, or that you will open one for them when you are finish with what you are doing. Put up a web page that show your queue, what the priorities of those tickets are etc... Pretty soon it will be obvious who waste a lot of time, who always made their the highest, etc.

    One of a few things will happen...

    * all of your tickets will be 5 :-) tell them (and show them/your boss) and ask him/her to prioritize for you.
    * people learn to do things for themselves and you'll have time to handle more urgent company matters
    * you found another job

  2. Re:The real problem on NSI Changes the WHOIS Rules · · Score: 1
    You are lucky! At least your domain still has DNS records in the root servers. NSI, I assumed they are the one managing the database for the root servers, has managed to "LOSE" DNS records for two of my domains in the past two months!!!

    The latest incidence started last Friday to a domain, saigon.com, that I've had since 1980. It's always paid in full. Friday, mail started bouncing and when I checked the root servers, there were no record of my domain. Complaints to them just got stupid replies back about there is a record in the whois database. Well, no duh. I specifically stated in my message that the DNS record is missing and even provide nslookup sessions showing it.

    What a bunch of yahoos! I am going to start moving all my domains to the other .com and .net registrars.