Discussion Locked

Presenting a case to a small biz for an upgrade?

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

I am looking for ideas as to how to effectively approach the management of a small business to consider an infrastructure upgrade. I work for a small publishing company (around 25-30 employees I think) and relatively soon I'm probably going to be transferred from the production dept. (where I do graphic/layout work) to the MIS department (which is where my background is, anyway).

Now, I don't want to come off as an arrogant know-it-all who frivolously spends the company's money (after all it IS a small company) but the existing infrastructure is sorely outdated. I'm talking more than half the PCs running Windows 98 (at least one runs MILLENIUM); in fact the computers seem to run a mishmash of OSes.. a few run XP, quite a few run 98, I think one runs NT Workstation 4.0, etc.. Office 2000, you get the picture. There's also around 5 servers, I think. Our main in-house software program is written in Foxpro for Windows 2.5 (or 2.0, or something like that). We run Pagemaker 6.5 for layout, which as I understand it is no longer supported by Adobe. In short, I feel that the company would be better off with a complete infrastructure overhaul.

The problem, of course, would be explaining this to upper management since they're going to be reluctant to shell out the mega-bucks to do a complete revamp like I feel is needed. Also, they subscribe to the "If it's not brokeen, why fix it?" metality. There may or may not be legacy application issues as well; I am relatively new to the job and company so I'm not sure. In a case like this, should I just keep quiet or subtly suggest the upgrade, so I don't come across as wanting to overstep my bounds and end up getting fired? I *really* feel the company would benefit in the long run by reworking things from the ground up, but I doubt management will see it that way.

Any thoughts/suggestions for this neophyte?

28 replies

by tony hopkinson

How much is support costing now and how long will it be possible to keep supporting it vs how much would it cost to support new kit and and how much longer would it last for.

Or sell the MD a super duper spangly up to date PC that he can't use without an upgrade to the infrastructure.
Seriously, from the sound of it, your kit is old enough to have been depreciated, so the hardware itself has no value to the business.
So your only real angles of attack are that it will become obsolete and be unable to support a business function or it will become more and more expensive to support a business function.

Try a phased rollout, one server at a time. Can you with new kit reduce how many servers you need. Do check out the legacy software angle though that's the biggest potential cost looming on the horizon.

A good mental trick, is if you personally had to foot the bill for a change, having accepted it was necessary, how would you accomplish it at best ROI/least cost. Most ideas like this fall down because the proposer forgets that money trees don't exist. Steer clear of added value and go for reduced cost when you pitch. The former, if it actually happens is a bonus.

by trdgyrl

The best advice I ever got on this very same topic was this: you don't move into someone else's house and immediately rearrange the furniture.

Sure, it may be your space now, but if you move too quickly you will DEFINATELY come off as a know-it-all. And since you are still fairly new to the job and company that would be counterproductive, right?

It does sound like the company is in dire need of an overhaul and there are some ways to approach the situation.

First, I'd ask around your collegues if there are any plans to upgrade? Any phased approach already in the future plans. I'd also find out if there is any type of asset inventory available. If not, that could be a fairly simple task to take on initially that would yield HUGE results. List the equipment, OS or firmware version, applications running on each piece of equipment AND data that resides there.
After that asset inventory is complete you have the ammunition to develop a phased approach to upgrade. It is so very important to know what data resides where and also where it traverses.

Develop a 3 year plan to upgrade/replace the equipment (yes, it sounds like a long time, but when you're talking big $$ figures short-term, large layouts are scary to upper management)

Some things to think about are:
-age of hardware vs. average lifetime of same hardware.
-is support still available for this hardware
-versions of software (start with OS and firmware first, worry about applications later assuming nothing is currently broken in the applications area)
-are those OS/firmware version still supported?
-are patches and updates still made available (NT for instance certainly is NOT supported anymore.)

here's the one that I like most: how are all the systems currently being managed? and kept up to date on their patches, security fixes etc? If there is no central management tool then upgrading and consolidating on a single platform would make the ongoing management simpler, more efficient and more cost effective over time.

Good luck!

by jc2it

I have heard something similar. Never make a major change until you have been in a new position for six months. This could be critical in IT. You may just not know what you are breaking until you have already broke it.

The three year plan is a great idea. I would also recommend that you triage the computers that need to be replaced.

Make sure the replacements fit the task they are required to perform. If someone does not need Internet access for thier job, then wait for the 2nd or 3rd years.

A Brief Example:
Year One: Replace many of the 98 boxes and any computer with significant issues (ME box). Replace at least one third of the desktop machines that need replacing for security purposes (98, NT4.0, ME).

Year Two: Replace the second third of desktops. Replace any older servers (This gives you pleanty of time to determine thier full usage).

Year Three: Replace the remaining old PC's.

Things to keep in mind. Someone's old PC might be someone else's new PC. You may need to replace an XP box in the design department in year 2, that can be given to a receptionist. ALWAYS reformat and wipe a disk drive before you get rid of it. Whether it goes out of the building or to another user.
Also, install the OS that you are standardizing with on all old PC's that have not outlived thier purpose (Probably XP PRO).
Help yourself out by standardizing hardware as much as possible. If you are replacing 10 PC's then buy them all at the same time and go from there. This will allow you to use tools like Norton Ghost more efectively.
Create as few Ghost Images as possible. This will help you in setting up a new PC, or fixing a bad problem.

by deadly ernest

The current system is mostly outdated and unsupported software. Almost none will run on the new versions of Windows and by the time you get them to agree it will be Windows Vista meaning mega-mega bucks - little chance. A new Windows operating system will generally mean brand new applications as well.

As previously suggested first check on what they have in the pipeline and budgetted for in coming years. While doing the rest below keep this info in mind at all times.

No down to the tin tacks. What ever happens there is going to be some costs and a high learning curve. The thing that will frighten people will be the learning curve. The biggest technical problem will be getting new peripherals to work with the older operating systems and applications. Soften the people blow, see what alternatives there are to allow them to extend the use of their existing software and thus lessen the learning curve.

One alternative that I can see right away is to use a version of Linux that looks much like their existing Win 98 systems, there are a few around, or near enough to make the switch over easy on them. Purchase and install programs like Crossover, or free ones like WINE; these will enable you to run the Windows based applications in Linux, especially the older applications that wont run in the newer Windows systems. This will reduce costs, and should also enable you to actually perform software updates that improve performance on the existing old hardware - thus reducing the immediate costs and buy more time for the hardware update expenditure. Such a move would enable you to standardise all the desktops and servers onto the same basic version of Linux and also reduce the learning curve for the technical staff.

What ever you do you will need a thorough cost analysis of the whole project over 5 years or more.

by obiwaynekenobi

Once I make the move I'll have to ask the MIS Director (who I'll be working under) if there are any plans to do a phased upgrade... how should I approach this matter though without again coming off arrogant? Obvoiously I should wait a while after my transfer to mention it...

by tony hopkinson

that there are any areas of concern you should concentrate on in your new position. What will he be looking for from you in the comming months.

by deadly ernest

if he has developed a strategy to deal with any problems that MAY arise from the software in use that is no longer supported. I would do this with a memo or such with attached print outs from the Microsoft website where they say that they no longer support Win 98, and the MS announced end of support dates for Win NT 4 and Win 2K (not sure when they are) and any other software that is already out of support. I would also mention the difficulty in getting working drivers for the older opertaing systems when new equipment is bought. No point buying a new printer if the thing can not be made to work with the old operating software.

Write it up along the lines of 'hey boss not sure if you know this?'

by blackcurrant

It has taken us almost 5 years to get our system up to date, and the final phase of that will occur during the next 6 months.

I work for a small company: 1 server, 30 PC's.

You mention you have 5 servers? Well, I would suggest that the first thing to do would be to consolidate these into 1 server with a professional backup application.

The new server will be able to communicate with all your existing PC's. The next step, later in the year perhaps will be to gradually replace the PC's with new ones. Once this starts happening, and management start to see the benefits that upgrading offers, they may be more amenable to a speedier rollout of new hardware.

It has taken my company this long to upgrade simply because the money for a full-single-upgrade does not exist. We had to prioritise hardware and software upgrades, initially replacing only what really had to be upgraded.

You need to be able to demonstrate how a phased upgrade would benefit the company. Your first step is to accept that this will be a gradual process. It would be great to be able to do this in one go, but it would be a lot of pressure for you in terms of training both yourself and your staff in the new equipment. A phased rollout allows you time to fix teething problems, and then have the solutions available for your staff should they require them.

Good luck

by obiwaynekenobi

I'm not 100% sure of the number of servers... there's at least three that I know of/use.

I've noticed that *every* small business I've ever worked for has always had at least 4+ servers... one had I think close to 14 (including two mirrored servers that were offsite). Most of them, when asked, said it was because whoever set up the network figured it would take a load off of the network server to split it into different servers for each function (files, email, web, Db, etc.). I somewhat agree but... wouldn't the cost of maintaining 5 servers outweigh the benefit for a 30-something strong organization?

I think this particular company could probably keep the servers at 3 to be efficient: one as the main network/DNS/Active Directory server, one to store data (we have very large databases in FOXPRO since we do research for the books that we publish, not to mention the fact that each book is typically around the 100MB area when finished), and one for a web server (we have a setup for our clients that give them an ASP-driven website; I'd like this to eventually move to .NET as well. The web server consistently crashes for unknown reasons, which is another case for an upgrade). This might actually be the setup they have now; again I'm not 100% sure yet but I'll make it a priority to find out after I get settled into my new position. I believe we also have a seperate ISA server, but I see no reason why this couldn't be consolidated to another server

Thanks again for the assist, everyone. I'll be able to post more information once I'm in the MIS department and I'm privy to all that knowledge.

by blackcurrant

The company I work for only uses one server - but we are looking to setup an SMTP server soon, so that would make 2, also, I would like another to provide redundancy - so you are correct - I was thinking of things from my perspective. Boy - if my management could get the money for a professional setup, I would be very happy :)

PS - I get to replace 3 remaining Win98 systems this year.. oh yes!

by paredown

Great advice above--to summarize and comment:

(1) I would speak frankly with your boss--that you want to make things better, not just fix what's there. This is the eternal tension in an IT shop & he maybe has been waiting for the right person to show up to get things moving;

(2) Document what's there (& try and understand why--somebody was trying to accomplish something with all those servers);

(3) Make the business plan argument to sell it up the chain. The strongest argument for upgrades is cost--we sold stingy managers on big screen displays when they were unbelievably expensive because of the time savings for pagemaker layouts for example. Same arguments for unsupported O/S, programs, security, cost of data loss, etc.

(5) Don't think of this as just x new computers; y consolidations, but think broadly--what are these folks trying to get done?--and plan from that basis. Ask them what do they need, and why? What improvements can the users expect, & involve them;

(6) Work out a phased program of improvement per previous posts. Leave room for future expansion--in the obvious areas like switch modules/ports, server capacity and less obvious areas (VISTA capable workstations??)

(7) DO NOT OVERLOOK THE NECESSITY (and costs) for user training--this should run parallel with the new IT implementations. Nothing freaks out a good desktop publishing person more than having a new O/S and program load dropped on their computer on a Friday, and they walk in on Monday and are expected to meet deadlines!!!

Work confidently, one piece at a time, stabilize it and go on. Implement some quick wins first that benefit the users. Document what you have done as you go!!! Course correct as new problems occur, and plan on an ongoing technology review/replacement program.

Cheers,
Dean

by coserve

and not about the technology.

you are right to be concerned about the costs of maintaining and supporting the "mishmash" you've described. however, as you've noted as well, most business owners and/or senior managers are unlikely to be moved by a proposal to spend lots of money in a way that doesn't directly translate to improving the business bottom line.

you've stated that "the company would benefit in the long run by reworking things from the ground up, but I doubt management will see it that way", so you need to work out a way of helping them see it that way.

perhaps you can suggest to your new manager that one of your first jobs should be to facilitate the development of an IT strategy that supports the plans for the business over the next few years (from your description it seems clear that the business has no IT strategy). this doesn't need to be a magnum opus and it doesn't need to be completed yesterday.

start with a user requirements study and needs analysis of some kind so that you have a clear understanding what the business expects from its technology. this should not only help to clarify what needs to be done with the current IT infrastructure (from a business perspective), but also help you to produce proposals for various ways of remedying the current situation(different implementation time-frames, technical options, financing options, etc.) the process of developing an IT strategy may also help you "sell" your technology vision within the company.

try to frame your proposals in a way that not only addresses the infrastructure life-cycle and technical support issues, but is also clear about how the proposals will help to achieve desired business outcomes. nominate how particular IT infrastructure investments will do such things as: enable new and improved ways of working; cut waste; reduce duplicated effort; and increase individual productiveness and so on.

there's plenty of work for you to do. i hope this helps.

cheers

by wayne m.

From what was described in the post, there does not appear to be a major business driver for an upgrade and with Vista on the horizon, now is not the time.

First, get your feet wet with the MIS department. Find out who your power users are. Find out about communications with external parties. Are there difficulties with inbound manuscripts and formats? How about accounting to the outside world? Once you have identified potential hot points, then you can identify specific spots that could benefit from an upgrade. You will also generate pull from the business side if you can get user buy in for the enhancements. You may never upgrade the entire network, but if Windows 98 is doing it for them, let it go.

Lastly, with Vista coming, I would probably recommend only replacing failing systems for the next year. Lay the ground work now to get a Vista evaluation system for December/January, but wait until next April or so before trying to update any systems.

The key is to find out where new technology sells itself as a benefit and not to be embarassed by old systems.

In

by too old for it

... for "we have no IT budget". Also means IT/MIS is going to be supporting whatever is thrown into the mix, as it sounds like you have had a "whatever was cheap at Sam's Club" IT purchasing policy.

By the way, if you have security issues, look to the Millenium box first. Using ME in a network bigger than zero nodes should be a jailable offense.

(Now I'm going to get flamed by all the people who think ME was Microsoft's best ever OS. Pthbt!)

Support has to come from somewhere, if nothing else on a "when it breaks, then we fix it" basis. (I start at $90 an hour, and it goes up depending on "stupid factors".) I can't tell you how many times I've re-loaded Win98 on a brand new AMD 1.4 ghz box because Sally Silly (the CEO's admin.) "doesn't like the new screen, and wants her old one back".

by jondoe2001

It's about time to start investing in new technology and increase the company productivity. Ideas are what they are, coming up with something that could benefit the entire company doesn?t sound like arrogance to me. Come up with a cute proposal that put emphasis on the need for change and it should be cost effective because it's for a small business. Tell your company that Microsoft and Adobe no longer support their current software. Good Luck and you are going to do well.

by obiwaynekenobi

Thanks for your kind words of wisdom :) I think the biggest problem is going to be that our existing software all runs on what we currently have... the hardest part of making the case will be trying to guarentee that things will work the same. So i will have to do some research before presenting a proposal, and probably have to contact Microsoft and/or Adobe, not to mention our printing company.

For example, the Foxpro 2.6 program we use outputs customized scripts (using Pagemaker formatting tags, I assume) to a .TXT file that enable us to import the data we need into Pagemaker and not format it by hand; it's going to take a lot of work if we were to rewrite that program in, say, VB.NET, to get it to work exactly the same way. So I feel it's going to be a hard sell, although I do honestly believe that a revamp would benefit the organization.

EDIT: I just realized that there's probably no way in hell that I could convince them to upgrade. For one thing, a rough estimate puts the price for all the new things up over $30,000, not including the cost of replacing obsolete machines/servers (which would probably double it). Second, I doubt that the Board of Directors and the actual owner of the company (it's a small biz, but a privately-held corporation) would approve of it. So I suppose it's best to not even try, lest I put my own job in jeopardy.

Still, I will keep these comments in mind in case I ever am in a situation where the company actually *wants* to upgrade its infrastructure and isn't worried about the cost of doing so.

by coserve

you've already committed quite a bit of thought and effort to working out what needs to be done.
devote a little more time to working out how you can achieve the result you "honestly believe ... would benefit the organisation".

as suggested by a number of others you don't need to take a "big bang" and "big bucks" approach to this. you've already noted that some software support matters are going to cause trouble very soon, focus on how to resolve these issues first.

further your headline figure of $30,000 to replace obsolete servers, etc. is just that. for instance, why not talk to the accountant about the pros and cons of leasing replacement hardware instead? certainly talk first to those in the company you think would be most sympathetic to your ideas. they may give you ideas on how best to proceed.

anyway, if you develop a well thought out and financially viable plan to achieve the upgraded infrastructure you've envisioned (perhaps over a longer timeframe), and clearly show how this would directly contribute to the ongoing viability of the business, the directors would be very foolish to ignore your recommendations. to some extent making such recommendations is one of your responsibilities as an employee.

i've yet to come across a viable business enterprise that is not interested in looking at ways to improve how things are done. if you jeopardise your job by raising these matters with management, then frankly you're better off "out of there".

cheers

by obiwaynekenobi

As I said, this co.'s policy seems to be "If it worked before, why should we replace it?". I guess they are big on keeping things how they know it will work, however ineffiecient it might be. We had to have a printer driver updated and it replaced some pre-configured settings, so management is now concerned because those settings were lost and they don't ever want us to guess how it should work (whether it works or not is irrelevant, I guess).

by deadly ernest

You may be able to sell him on the 'saving' made if the existing system fails due to lack of support - can they afford the time to convert over to a new replacement in a hurry. bettre to do while the old one still works and you can test in parrallel.

In 1996 I had a client whose accounting computer stopped working, the hardware just died - an Intel 386 25 mhz. So I used his existing software to build a Pentium 166 mhz with MS-DOS and load his accounting software version 2, current at that time was version 8 and worked in Win 98. I pointed out that the software supplier no longer supported that version of his accounting software and that he would have a hard time finding DOS drivers for any new peripherals. To be on the safe side I instaled the old hard drive as a back up (e:) and had the accounting software copied onto it with the accounting data backed up to it automatically each night, left instructions for the computer to be left on 24x7.

I explained that he would be better off buying the current version of Windows and the accounting software, with auto backup and recovery facility, as any future hardware or software problems could mean total loss of data. he was not interested. Six months later a new accounts staff member made a mistake and zapped the d: drive, the data drive. They were lucky in that instead of having to rebuild everything from the last end of year back ups, 8 months old, they only had to rebuild one day's work as my jury rig back up enabled me to recover up to the previous day's close of business - but they did lose a days work waiting for me to get there and get the work done.

Three months later he bought new OS and accounting software as the printers finally died and they could no longer print any invoices etc as they had no dos drivers for the new printers he bought.

by obiwaynekenobi

Thanks again for your advice. Once I make my transfer I'm definatly going to discuss it with the MIS director; the company could improve productivity and efficiency if we did a complete overhaul. I mean, just yesterday (the driver thing, again) I was told that configuring *one setting* that enabled us to print from Word on 11x17 size paper to a Konica Minolta C450 bizhub printer took nearly *4 MONTHS* to configure properly; I was forbidden to experiment with it to try and figure out how to do it (They "don't want [me] spending all day playing around with it.").

My idea is to do a combination of Microsoft's suggested guidelines for small businesses and midsize businesses; we're a small business but our computer systems are integral to the business process and we *do* have dedicated IT staff (even if it is just one or two people). Currently, my planned changes (sorry, just getting the ideas out there... it'll help me later when I draw up the upgrade plan) include:

- Migration of existing systems to a reliable and scalable solution based on Windows Server 2003 and Windows XP Professional. Replace existing hardware if required (almost certainly will be)

- Enable increased communication and collaboration via Sharepoint Services.

- Upgrading of Office 2000 software to Office 2003, Small Business edition.

- Migrate existing FoxPro (.DBF) databases to Microsoft SQL Server 2005.

- Convert/rewrite existing FoxPro for Windows 2.6 applications to [probably] VB.NET (* This one is going to be a REALLY hard sell.. since the company runs off of these FoxPro apps [the former MIS director developed them, I believe]. But they at least operate under XP so this one isn't a priority).

- Convert/rewrite some in-house (I think?) *DOS (!!)* program that our researchers use. This one would need a lot of work to see if it CAN be re-written.. it might be some legacy app that we need to communicate with a business partner. From a cursory glance all I know is that research's machines ALL look at least 7 years outdated (except for the supervisor's PC) and run some kind of DOS-based software (might be a form of Foxpro)

Thanks again for the assistance.

by deadly ernest

The things to keep in mind with any proposal are (in order) cost, cost, cost, performance enhancement, longevity, and cost. Dollars drive business.

You are looking at some big dollars in software above, you may want to reconsider your aims. Some questions that will need very good ansers,

1. Why go from Office 2000 to Office 2003 - what real benefit is there and is it worth the cost?

2. MS have 5 year obsolescence programs now, a couple of years and Server 2003 and XP will no longer be supported. You will be at the same point again.

3. What sort of enhanced capability will be obtained from converting the existing software, is that needed?

4. How big a learning curve can the business sustain for everyone to learn how XP and the other software works differently.? This will be a very big issue with staff and management - down time.

If everyone is happy with the existing in-house special programs and they still do the job well, the only issue is that the operating systems are no longer supported. Look at ways around the operating system issue. There is a big difference between in-house, own supported software and purchased software that is out of support (the case in my story was off the shelf software).

5. You already acknowledge that selling them on VB.NET is going to be hard, and there are issues with VB.NET anyway - so why go that route?

----

I would recommend that you seek an opertaing system that will allow them to extend the use of the in-house software that they are happy with. That way you can set up a non-production test and see how it goes. In would not cost all that much to get a PC that is only a few years old and set it up with a Linux version like Linspire (Windows look-alike type) or Fedora Core 4 or any other Linux. You do not have to be a LInux guru to use the general Linux platforms, you can easily learn on the job if need be. Then load it up with the latest WINE (like an Windows emulator) and then load copies of your in-house software on that and see if it works. I am using Linux with WINE to run some old DOS, Win 95, Win 98 games that XP refuses to run properly - goes great.

Such an 'outside the square' approach would save big dollars and get management on side as they will have a very low learning curve, say all of 30 minutes. But best is that this can be done without interfering with the production set up and can the be phased in one machine at a time if need be. Will also save tens of thousands of dollars in softwrae costs, buy one copy of the Linux (with manual) and download WINE free.

by obiwaynekenobi

I'll certainly keep your ideas in mind.. not too sure on using Linux, though.. I'm a MS guy myself but I have dabbled in Linux and it wasn't too shabby.

I'm probably deluding myself, since I don't think *any* plans to upgrade will be seen as convenient. Especially not the revamping of the programs... from what I've been told, the DOS-based Foxpro program is integrated with the phone system so that if someone calls in, it automatically pulls their record from the database based on the caller ID and information that we have; so our rep doesn't need to pull up anything; it's automatically there. Guy who wrote it was apparantly a genius, since I didn't think something like that was even POSSIBLE with modern programming languages, let alone an outdated one like Foxpro 2.0. So it'd be harder than convincing Bill Gates to use Linux to persuade them to move something that tightly-integrated.

Will definatly consider the other advice, though. Thanks once more.

by deadly ernest

mad and my MS skills are very high, Linux skills very low. However, with the way that software costs have been rising (especially here in Australia) and MS have been changing how the new operating systems look, the clients are now reconsidering if the idea of staying with Windows do save on staff learning curve justifies the costs involved.

I have been investigating Linux and trying different versions on some older computers at home (saves a fortune on software). What really got me interested is the ability to play my older games that are just too imcompatible with Win XP.

The fact that the Foxpro 2.0 program is so good and integral to your operation means that you should focus very tightly on ensuring that you find a way to port it to use in the new system. I have not been able to get any good DOS programs to run in XP as Windows does not use the full DOS anymore, this means you should be looking at Macintosh, Unix, VM, or something similar as your compatibility and support problems will be a major issue with any but the latest MS Windows options.

If you can get a test machine to load opertaing systems onto you could then test the viability of the Foxpro application on the various opertaing systems - this would have to be listed as a must for whatever you do end up considering.

by obiwaynekenobi

It seems to me that the network was probably set up when the company was started (~12 years ago) and never bothered to upgrade... we have at least a machine or two that run Windows 95, in addition to the other things I mentioned.

I think reliance on the legacy Foxpro app is so great that management never saw the need to upgrade existing systems for fear of it not working properly, and for whatever reason never decided to rewrite it (cost, probably) using a modern programminglanguage. Thus I think my best bet once I transfer would be to examine ways of consolidating the IT infrastructure without resorting to upgrading all desktops. The funny thing is, and I need more info on this, is that it was mentioned to me that they were discussing changing the system over from Foxpro. Given all the bells and whistles it can perform, though, I have no clue what would be a viable replacement. I guess I have something to ask of my new supervisor once I am entrenched in the MIS department :)

by deadly ernest

it is clear that the Foxpro is a core system and what ever is done needs to keep that operational or duplictate its operations. They may be discussing the need to replace the Foxpro because they may be as aware as you are of the need for a new infrastrutcure and have already found out that the Foxpro won't run on the current Windows versions. If that is the case and you can come up with a way to upgrade without paying out big money for a new replacement they will love the option.

The key points are to consider the cost, think outside the square, and have the technology meet the business needs not the otherway around.

by obiwaynekenobi

Well, I haven't made the transfer yet (prob. in another week or two... if they don't decide not to) but we're discussing replacing one of the Millenium machines (still a few more...) and upgrading our production software to Adobe Creative Suite 2. It hasn't been approved yet, however.

It's a start, at least. Now to just figure out a way to make them want to upgrade the rest of the junkheaps (especially in our Research department... ALL of those machines are at least 8 years old; I think they all run 98 or 95). Of course, I'm certain I'll get the counter-argument that research doesn't do anything to warrant newer machines... so if that's the case I presume that security would be my best route? Reliability too, since we had the supervisor's computer not work which meant research couldn't even get their jobs done (supervisor loads contacts for the researchers from a program off of her computer; probably that same outdated Foxpro program).

by obiwaynekenobi

There are roughly 35 PCs total in the company (not sure if all of them are being used, I think our Research dept. works rotating shifts so that might be why some of them are vacant during the day). There are *six* servers; two run Windows NT (main domain controller is running Small Biz Server 4.5 with Exchange 5.5), two run Windows 2000 and the two newer ones run Windows 2003. Of these, one is a Firewall server (ISA 2000), one is for data (has some strange thing from Borland called InterBase that I've never heard of), two I believe are web servers of some sort, one is a file server and then of course the PDC.

Program-wise, we of course have the foxpro for windows 2.6 program (as well as the DOS-based version running on some machines in Research; Research has their computers locked down and can only do what we want them to), and from what I'm told something probably written in Delphi, but we have no source code for any of it (the person who developed them left, although he still does maintenance work [on contract, I presume] and the MIS Director has mentioned trying to get the source code) so if we ever need to maintain/add to it, we're S.O.L.

Cost is (obviously) the biggest issue with them upgrading anything (from a brief discussion, they wouldn't spend $2000 or so for Software Update Services [I thought that was included with Server 2003?]), and probably the main reason why they're still using such outdated technology. I suggested to my new boss that I could research the benefits of moving the domain controller to SBS 2003 (he said he heard nothing but horror stories about migrating from SBS 4.5), so that's a start, at least.

Any other advice/tips? I don't think the "it's no longer supported by the vendor" argument will fly since the probable answer will be "That's why we have an MIS department!". However, I am not going to let that discourage me from researching the information (on my own time, if necessary) and at least show them the benefits of upgrading. If they choose to do so is out of my hands, but I feel as an IT professional it's my *duty* to inform the company I work for of anything that can benefit their business and provide a greater ROI.

by obiwaynekenobi

Having asked around and gotten some opinions.. there are no plans to ugrade, and from the way things look there never will be. As I was told "Remember, you work for a company that doesn't like to spend money." So it looks like I'm stuck with this legacy, 10-year old stuff that barely works. Oh well.. thanks for the input, everyone.

This discussion is closed to new replies.