Community archive

Ask something
Discussion Locked

When is enough...Enough

0 helpful
2 replies

by scupper

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The company has been trying to roll out a VPN solution. I refuse to sign off on the rollout to our users, based on these facts:

1. The client software behave irradict when loaded on NT
2. requires a registry hack to load on NT SP6a
3. This location has been unable to get a client functioning after testing on 21 different systems.

Problem is the main decision to go is based in another office, and we have to support. I have let them know that we would not support issues with this client, until it can be demonstrated to behave well under NT.

When is enough, enough...and you start to look for other solutions, instead of wasting time and energy on a product which is clearly not going to be a help, but a henderance to the Internal IS staff.

2 replies

by al macintyre

Who is the boss?

You must have a sweet job in which you can accept or refuse work from some management structure.

The only jobs I get away with refusing are those in which my statement goes like this ... I need certain software or hardware tools to do this job which cost $ xx,xxx,xx & the company has not in the past seen fit to give me those tools ... now without those tools, I might be able to do the job in 2 years of doing nothing else ... so run your request up the management ladder ... is your need great enough to justify the $ xx,xxx.xx which has not been justified in the past ... or is it great enough to justify me doing your task without this & me do nothing else for 2-3 years ... and what happens is I am permitted to remain productive where I typically satisfy 2-5 user requests per day.

Now it is not unusual in big business for companies to launch stuff that does not work well with the rest of the enterprise's computer infrastructure, because the launchers were sold on something by an effective vendor & management not understand implications.

If you had been doing your job well, management would know why you do not think this will work, so when it fails, they turn to you as an expert, or get a second opinion to confirm your story. The risk is that this might send company into bankrupsy.

We happen to be on VPN on NT on Ethernet on AS/400 & it works great, but it was a big ordeal to get started because of all the ultra specialized vendors that were needed for all the pieces & they did not know squat about anything outside their area.

A company needs a vendor that knows the whole picture & spells out what training is needed for all the players to get up to speed.

by scupper

I do have a sweet job, as someone who prefers to do things right the first time, I am looked to for my technical ability in rolling out solutions. Problem here is I was brought in after the fact, and many things were dropped or tested.
My VPN knowledge has increased ten fold over the last week. I have still refused to sign off, and now have to give a presentation, and documentation to substantiate my reasons. I only hope I have a job left when this is over.

This discussion is closed to new replies.