Entries Tagged as 'Work'

The ultimate solution for company data loss…

Or your money back!

Sounds like a pitch for snake oil medicines. :D

Tonight I opened my company mail and I found a curious memo about a new guideline about backing up data on company owned machines. The first though that entered my mind was “WTF, another roadblock for doing backups?”

Reading the memo, it made some sense if you apply some common sense. And then I tried reading it from a “Security Expert slash Manager extraordinaire” perspective who follows everything by the book and then my world shrunk by a magnitude of ten. The phrasing combined with current practices is enough to give me the shivers if I think about embarking in a simple task of performing backups.

In line with the company’s commitment to protecting client data, effective immediately we are implementing the following process for backing up data on company-owned machines (desktops or laptops):

You may not back up any sensitive data residing on a company-owned computer (Laptop or Desktop) without permission of the IT Support team and obtaining a signed form. Only encrypted back ups are allowed, including copying files to flash media or CD.

Not bad eh? Not until you read that you need a very high approver before you can even think of performing a backup. If you need an analogy then think of the company as ruled by a god and you need the approval of the high priests. That approval is now on top of soaking one’s self in gasoline, rolling in live coals, and dancing a cha-cha number on top of broken blades and glasses.

To top it all, the last sentence was like adding insult to injury:

Further details will be released this week, as the IT Support team mobilizes to handle this task.

Yeah, I am brimming with confidence that the over-worked and ticket-closing trigger happy support team is able to take on this new task while spreading cheer and world peace. I am saying goodbye to backups then. I think it is easier to just slaughter some chicken and offer it to my anito to protect the company data that I am working on from sudden glitches and electronic crashes.

ciao!

Water leak == security leak?

Today I received a peculiar office memo; it gave five steps on what to do when a water/sprinkler leak occurs. The contents are pretty much in the realm of common sense

  • cover and shut down electrical equipment.
  • contact the company facilities department
  • don’t power up equipment until conditions have been verified.
  • if evacuation is required, follow proper evac procedures.

I merged two items since they are basically the same thing. What made this peculiar is that the memo was from the company’s information security department. I would expect this to come from the facilities department as it is a basic operational reminder but from the security team?

The only reason I can surmise is found in the last item. They are considering it as a localized disaster if it would require an evacuation. Nevertheless, this information should have come from the correct source as I am seeing a blurring of the distinction of the boundaries of the IT security team’s area of responsibility.

I am wondering though which office sprung the leak to prompt the memo. And how many employees actually tried to work while a leak or flooding is in progress. :)

ciao!

The office NTP server

I started the day in a bad mood, again due to draconian IT policies in the office but this real-life instance made the day a bit better and worse at the same time.

Noticing that I am always a couple of minutes early for international conference calls, I asked my counterpart for their local time and found out that my system clock is 12 minutes in advance. I asked around and found that we have varying system clocks so I asked Mike, a junior member of my team, to log a support ticket for the step on how to configure our machines to synchronize with an office NTP server as I know the local domain server has that service. I know because I already did it once using w32tm on my previous project but I can’t remember the name of the server that I used. Besides, it’s the support personnel’s job.

After some time, I was already in the call. I noticed that somebody was hovering near my station. He said something about a clock so I let him do his stuff on my machine since I only need the phone. I had to restrain from laughing when the support engineer started moving my trackball like a wireless mouse. Since if I let this continue I might blurt out laughing, I just pointed to the clock and when he nodded I took over the trackball and double-clicked the system tray clock. I was already wondering how to do it from there since I already inspected it a while ago and didn’t see anything.

And then the unthinkable happened, the support adjusted my clock by 8 minutes and pressed the Apply button. I was shocked but couldn’t say anything as my Madrid counterpart was discussing something important. I just heard the engineer talking to Mike about closing the ticket so I frantically waved my hand to get their attention, and hastily scribbled the characters “N T P ?” in a scratch paper. I just let Mike do the talking as I needed to focus on the call.

After the call I asked Mike what happened and he said the engineer stated that he just took a look at his system time before coming over and synchronized all of our machine clocks. Our system clocks are still surprisingly different (duhh!) but the engineer apparently said that it’s OK to have some discrepancies. Millisecond discrepancies perhaps may be alright but a full minute? And I didn’t know that we have a gifted engineer in the company that has his body clock synchronized with a NTP server.

I feel so safe in the reliable hands of our support personnel. /lol

ciao!

The problem is mine alone.

Scenario At Work: A required resource service is not functioning properly.

Manager: Get somebody to fix it. ASAP!
Me: Will do.
[Me contacts internal support]
Me: Did we change something in the configuration? Product X is borked.
Internal Support: Nope. Everything is dandy. Try contacting the provider.
[Me contacts provider's support hot line]
Me: Your service is not working properly. Please check.
ABC Support: Thank you for contacting Company ABC’s support hotline where (long spiel about how they are $DEITY’s gift to my poor existence). We’ll ask our technical team to look at it. Here is your cookie reference number.

[after an hour]
Manager: Well?
Me: (looking up from the pile of tasks being worked on) Err, ABC support hasn’t called back yet. Ill follow it up.
Manager: Should have done that eons ago…
Me: right! (whispering inside my head: and i am just twiddling my thumbs here… )

[calls ABC hot line]
Me: Im calling regarding reference number 123456. Any updates?
ABC Support: Thank you for contacting Company ABC’s support hot line where (long spiel about how they are $DEITY’s gift to my poor existence). Tech team has stated that they don’t see any problem with your service. It must be something internal (read between the lines: you are a stupid customer. all of your problems are your imagination. ITS NOT OUR FAULT, ITS YOURS). Please check your lines again.
Me: [groan]

[calls internal support]
Me:ABC said there is no problem from their side. Are you sure there isn’t any test that we need to do to isolate this?
Internal Support: We already executed all tests. Everything is still dandy.
Me: (whispering in my head: Oh crap) Uhhh, ok.

[puts down phone, somebody speaks up from behind]
Manager: Well?
Me: (startled) uhh, wait a second.

[pulls open the drawer, takes out the gun, points it in my temple and pulls the trigger]

Problem solved.

Note: Manager, ABC company, and Internal support are all fictitious characters. But they represent somebody real though may not be their literal counterparts.

ciao!

Goosefraba….

Just venting.

I think I am nearing the “warning” levels of my stress tolerance. I am now easily affected by the inconsideration of everyday strangers. I haven’t been awake for more than 4 hours and my temper already flared with:

  • The jeepney driver who stopped in the middle of the road, checked out the “prospective” passenger in the sidewalk, and then start again when I was overtaking his vehicle and directly in line with his vehicle. This is one of the reasons why I hate driving. This person needs to be hit by a “driving for dummies” bat.
  • In a tight two lane street (the breaker of a floodway circuit) that already have a lot of vehicles parked smatteringly on each side, a pedicab driver stopped in the middle, and then exhanged a long bantering with a pedestrian who he has just passed by. Here is your stupid and inconsiderate sign, and a generous amount of honking as a bonus.
  • The elevator going up to the office floor only has a few passengers since it is still early. I normally go to the back since I dismount at the next to the top floor being serviced by the elevators but since this time I was near the door. In the floor before my stop, a female rider carrying 3 bags: a typical oversized female handbag, a paper bag, and a laptop backpack, alighted. The problem was that the backpack was only slung using one of the straps so it was dangling and it hit me. Since the woman was from the same company as I am (we are occupying that floor also), I just smiled and raised my right hand in a typical open-palm pinoy fashion to sign “no worries, everything is alright”. Then the frigging woman (I refuse to call her a lady), stopped when she was out of the elevator door, and gave me the evil eye. Here is your stupid and inconsiderate sign, if you have been careful to make sure you carry your belongings securely then your heavy laptop bag won’t have dangled and hit me. And I don’t care if you are a manager, you deserve to be hit by a large etiquette bat in the head.
  • The Indian support engineer handling my ticket that got redirected to the India support team (WHY oh WHY?). My tickets are usually handled by the Manila server team who are much more competent at this. Even with me painstakingly exerting every effort to make my ticket description as detailed and complete as possible, the engineer had the gall to send me an email with this thinly veiled ultimatum:

    After reviewing the ticket, it has been determined that some information will have to be verified from you before we proceed with your request. Please refer to the questions/clarifications below:
    1) Managers approval required
    2) Kindly let us know in which project id needs to be created

    or reply to this email with your answer/s on or before <28-05-2008>.

    Your reply is very important to us as we aim to provide quality services through better management of tickets. Please note that failure to provide the information needed on or before the date mentioned above may result in ticket closure.

    Why am I mad? Because I have attached the approval in the original ticket, all of the details are already in the description, and I created the ticket yesterday (>>May 28, 2008< <) at 7PM (GMT+2), received the reply at 9:45PM (GMT+2). Apologies to all of my friends in the support business but this one needs to be bashed by a big “reading comprehension” bat.

As they say in the street: Ang aga-aga, pinapainit nyo ang ulo ko! (It’s still early and you are already testing my patience!)

File system consistency check you all. :(

Goosefraba… Goosefraba…

Now I feel better.

ciao!