Transitioning From Small Shop IT To Enterprise? 259
Imaginary Friendly asks: "I'm the 3rd guy in a three-person IT firm. We're good and we're expanding. Our clients range from three computers to 30, with our largest client having six servers. We can handle the work but, thanks to my efforts and love (or just luck), I may be signing up two new clients who have 200 networked computers each. We're spread thin as it is, and hiring competent IT staff has been difficult. We're now doing 60-hour work weeks, so re-education has remained passive. How do we transition from manual rebuilds and CD deployments, to full scale (proper) IT administration?"
drink the koolaid (Score:4, Insightful)
yup, do like the government and clueless big corps (Score:2)
Re: (Score:2)
The Windows GUI is inseperable from the OS, and has to run on the machine's built in video adapter and keyboard. You can't fully administer it through a console connected via RS232, for example, without hardware hacks to virtualize the video. And as the GP mentioned, many operations tend to require or at least strongly encourage a session logged in on the server's console. Th
Re: (Score:2)
Re: (Score:2)
BTW, I'm not some Unix zealot. I grew up on DOS & Windows and have been using Windows 32-bit versions since the first betas of Windows NT and the Win32 API. But Microsoft got lazy, and stopped improving their architecture
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
They should be, but...
Right. And the point is that you shouldn't have to resort to that sort of thing just to do routine remote maintenance of a server. All the (Unix) servers I run have a remote console capability, but I almost
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
by creating an oem install disk, you make the emergency reinstall of a complete system including all standard apps by, say the sectretary or the copy boy easy for non-tech users. enabling the end user thru education and easy to use tools will in the e
Re: (Score:2)
Obviously, though, more details about the environments involved would have helped a lot if the submitter was aiming at getting useful information.
Re: (Score:2)
Notice that they support workstations as well as servers so odds are they are windows machines.
Get ready for the fun of spyware or the fun of dealing with locked down windows systems.
Re: (Score:2)
Done properly, locked down Windows systems aren't that much of a hassle. The only bad obstacles are getting all those legacy and poorly written apps to run correctly, and getting user acceptance. Difficult, but not insurmountable. You definitely still have to drink the kool-aid, though.
Re: (Score:2)
Re: (Score:2)
I'm a little pissed off
Re: (Score:2)
Re: (Score:2)
OTOH I doubt you can get Exchange to interface with as many networks sendmail supports out of the box or that you can rewrite rules dynamically the way it can (admittedly with line-noise like syntax).
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
SBS is a complete nightmare if you're used to dealing with the real deal. We picked up a client who had the Geek Squad from Best Buy come in and setup a server for them. Of course they used SBS. All of the administrative tools are different. The layout of AD is different. The whole product just sucks big, smelly donkey nuts. We scrapped SBS and setup Server 2003.
Re: (Score:2)
If you learn that, you can also support it. The disadvantages of SBS are not obvious, and customers will prefer buying SBS with 10 CALs for 1000US$ than buying W2003 Standard + Exch2003 Standard with 10 CALs each for 10'000US$. You can't have a second DC with SBS (it will complain and shut down, it's also in the license agreement and everything). SBS is a product for very small shops which don't want to spend much money.
What about Win2003 + some open source tools? (Score:2)
I want to change this but I don't want the expense of Active Directory. Can Mac OS X Server's Open Directory be use
Re: (Score:2)
Samba has some sort of Windows Domain functionality, but last time i've worked with it (~2yrs ago), it was still en par with NT4 domains.
If you have 150 desktops, using Active Directory can reduce the managment overhead in a great deal. You can specify lots of client settings using group policies. AD also has some rudimentary software deployment support (using MSI files).
Centralised authentication, roaming user profiles, folde
First... (Score:5, Insightful)
-matthew
Re: (Score:2, Insightful)
If you can use telecommuters, do, it will broaden your labour market immensly.
One last point, Train your customers as you go. It may seem counter intuitive, but teaching your customers to solv
Re: (Score:2)
This is not true in my case. My primary concern when looking for an IT job is finding an environment that fits my personality best. I am currently making nearly *half* of what I potentially could jus
Re:First... (Score:5, Interesting)
By your own admission, you are stretched thin and can't handle your current load. Now you want to take on new clients, but not just any new clients, new clients with large needs that you don't know how to address.
Do you really think that you are going to be able handle your current load (which you say that you can't already), the load from these 2 new big clients (whom are each about 7 times bigger than your current largest client), and be able to figure out how to change the way that you do things to meet the demands of these new clients (when do you plan to have time for this)? No, no, and no, on all counts.
Fix your staffing problems.
Serve your existing clients without killing yourself, then expand.
You are risking your current client base in order to add more business that you admittedly can't handle. You will likely ruin your existing reputation and relationships, just to pick up some clients that you can't serve. It's hard to say "no" to new business, but sometimes you have to. If you grow to fast, it will get out of control.
Re: (Score:2, Informative)
In the meantime, you can get great technical insight about large scale IT management here [infrastructures.org]
Grow fast, grow hard (Score:2)
Re: (Score:2)
Re: (Score:2)
They like it a hell of a lot more than being told "We can handle that no problem" only for you to either screw their network up or fail to deliver anything.
By telling the big customers that you're not ready, you're losing the big customer, at least for now. By attempting to take them on when you can't handle what you've already got, you'll more than likely lose the new customer, your existing customer
Grow orderly, grow well (Score:2)
As others have noted, the consequences of doing business poorly can be worse than the results of not doing it at all. But the other dimension is what I call "bullshit factor". It works like this: You're a small IT shop serving, let us say, 30 small-bus
Staffing it... (Score:2)
1. Shell Scripting, can your person make changes to dozens of machines at one time when you have a crunch.
2. Obscene famialiarity with the OS.. A headphone jockey can walk a user through hell and back, if they know exactly what is popping up an
Remote Desktop Takeover (Score:2)
Re: (Score:2)
The key that you'll have to find, is finding a manager who is both technically experienced (important), and managerially experienced (not cheap).
You can also find someone to replace you in the organization and learn how to become a better manager yourself. By d
Re: (Score:2)
Re: (Score:2)
So how exactly does this solve the technical and capacity shortcomings of their current IT staff. Yeah, good managers are important, but if you don't the staff, you can't take on bigger clients, PERIOD.
-matthew
Re: (Score:2)
Engineers do make great CEOs - in France. Seriously. I'm not
sure why.
--chuck
Re: (Score:2)
But there are thousands of small companies that exist for decades providing a good secure income for their founders. If this is your aim then taking large risks is something you should leave to those with VCs breathing down their necks.
There's nothing wrong with small, safe, organic growth, and not pissing off your existing customers can be a worth
Re: (Score:3, Interesting)
The "you can work 80hr weeks instead" attitude is not a way to succeed. If you're demanding more from your people and they get nothing in return, some of them are going to leave. Hourly people who do get paid more for working more aren't all going to be interested in giving up all their free time to benefit the company. If people leave, that substantially increases the workload - not only do you have to take up the slack, but you al
It is all about using the right TOOLS (Score:2)
disk imaging(roll out an entire office full of workstations in 30 min)
antivirus server(pick your vendor)
backup systems(BackupPC is one I love, doesn't do bare metal restores though)
tools like 'Nagios' for server/device monitoring
Groupware packages like Zimbra
and of course VMWARE...why have 10 test machines taking up space and heating up the room...test new stuff on a virtual m
Re: (Score:2)
Depends on your clients' needs... (Score:2)
But if you havn't figured out already, this will only work in a Sun Solaris house. The same will be said of solutions to every other problem, they will be machine/OS/client sp
Service Management (Score:3, Insightful)
You mentioned manual rebuilds etc. It would pay to automate this as much as possible (I'm sure you'll get some responses on this). Quality can often be equated with consistency. If you give your customers the same thing over and over they will know what to expect, even if it's only 80% of everything they need. They'll be much happier in the long run than if you give them brilliant service one day and crap service the next.
Re: (Score:2)
No, I work for a mining company you've heard of.
Not doing documentation and not holding change approval meetings are precisely the kinds of behaviours that get you into a situation where the the Information Stores are offline and 500 people are screaming at you. HP and others estimate that 80% of Incidents are caused by poorly managed changes. Think about that - most organisations could save themselves 80% of their incidents by tightening up
Plan (Score:3, Insightful)
what you need to is to plann everything. train people that the locations to handel minor things and make them a fire fighting team.. no company is going to complain that you train their people to handel the minor issues so that they don't have to call you. try to make everything in rounds.. if problems can wait let them untill the guys schedualed to come by can get there and have his list and go about his job.
with a good work order system you can plan for the jobs and have job kits for your workers.. a check list
and if you can put this in place then hiring people to do the work is alot easier as they don't all have to be experts.
also set up remote admin and monitoring.. companies might fight back alittle but make it fit their policies.. because if you can see a problem and fix it before they notice that is a good thing. also if it is something that could be done remotely you don't have to send people out there..
and for the multi server people a single port KVM over IP connected to a normal KVM rocks.. they arn't cheap but if you are making money from them droping the 500$ for a single port KVM over IP isnt' that bad.. also you can get them with modems so you can dial into them.. makes remote admin easy.
make network maps and keep them where everyone can get to them so that you don't have jsut one guy that can work at a specific place because he is the only one that knows how it is done
just some ideas.. but always plan..
Re: (Score:2)
This is all good stuff.
The only thing I'd recommend is skipping some of the remote access stuff, and just setting up a VPN connection to their building or network. Of course, this depends on whether or not they're down with it.
I used to work for a small IT firm, and most of our larger companies allowed us to set up VPN tunnels to their networks. This way we were able to do things like regular remote backups and troubleshooting. When you can solve the problem remotely, they like that. They don't have to
Re: (Score:2)
Re: (Score:2)
But go ahead and write like a moron. It just reduces people's impression of you regardless of your actual technical skill and inte
Re: (Score:2)
Unattended. (Score:3, Informative)
I have been using this at our companies for the past two years and has GREATLY simplified our redeployment strategy. If you have different clients who use different computer systems that all run Windows. Do yourself a favor and check it out.
As others have said... (Score:2)
Deployment on a budget. (Score:2)
As far as application deployment goes, a combination of the psutil psexec.exe and msi installers can make life a breeze. For example, scripting an office 2003 install is as simple as remotely executing the following:
msiexec.exe
Where do you need someone? (Score:2)
Yes, but what do you DO? (Score:2)
One thing to do is compile a list of best practices for your shop. This will help commu
Re: (Score:2)
Or a four year college. A lot of colleges with IT programs give a general overview of the field, and the programs are found wanting in some, or many, areas.
Been there (Score:2)
Establish Procedures, hire someone who knows them (Score:5, Insightful)
Please.
I've dealt with too many "three man IT shops" who treat IT work like auto mechanics. "try it, tweak something, try it again, tweak something, try it again, tweak something, try it again, tweak something". All the while, the company is offline. Corporate IT is about establishing procedures BEFORE the issues happen and about having backup plans for WHEN they happen, all of which is designed to minimize downtime.
Working with an office of 2-3 people... if you're diddling with their router for 2 hours, your time is probably worth more than the time the company has lost. But if you diddle with 200 people's connection for 2 hours, you've just cost their company $20,000, possibly more. Imagine what sort of investments could have prevented that downtime, how much cheaper they are than that downtime and why you should have implimented them
FYI, Documentation is more important than you think.
Stew
Re: (Score:2)
And just as important, a *good* backup system. I had to fix a system down issue not that long ago where a configuration file had been strangely corrupted. Sure, I could probably find it somewhere in the system documentation what all the settings there was supposed to be, but it was a lot easier to check when it was last good, fire up the backup tool and say "I want file X from last friday". It's sort of like documenting code - for the love of Christ, docum
This is correct (Score:2)
Re: (Score:2)
People can say what they want about windows but for managing an enterprise network where there are novice users? It's the only way to go.
You give some good advice but this is simply not true. Unix/linux remote management for novice users is different but is every bit as easy/hard as M$Windows remote management. In some ways easier because of better file system semantics and much less need for update reboots. I've done both and as always it depends on the competence of the administrator.
---
I love th
Re: (Score:2)
There should be a very limited duration between when you bring on a contractor and when you cut th
Read: Bootstrapping an Infrastructure (Score:2)
Bootstrapping an Infrastructure [infrastructures.org].
It describes good design patterns for computer infrastructure design.
Document, Document, Document, baby! (Score:2)
Develop a knowledge
"good help is so hard to find" (Score:4, Insightful)
Businesses love to complain about how hard it is to find employees when they're being cheap on labor, or how they can't retain good help.
There's no talent problem; there's a "how the IT industry treats workers" problem. Here's the current IT talent pool "problem", as I see it:
Is it any wonder that IT staff leave the industry in droves after just a few years?
Re: (Score:2)
Re: (Score:2)
Oh
S.A.R. (Score:2)
1) Standardization
2) Automation
3) Redundancy
1) Standardization.
The more they are the same, the easier it is to administer. Try to have the same hardware and image for each department. Use ghost like its going out of style. Use standard naming conventions. The borg naming convention is NOT standa
Re: (Score:2)
Cool!
from reactive to proactive (Score:2)
Some of these essays are a bit dated especially with regards to the tools they are suggesting but the mindset is still quite sound.
Contract some of the work out (Score:2)
I say small because 200+ workstations is not the enterprise, the enterprise is something much much bigger (talkin multiple platform
Lesson #1 of IT (Score:2)
aka
Do not LEARN on the job. LEARN in class or in a proper lab... not during an outage or during an install.
That is proper IT, anything else is flying by the seat of your pants which will cost
Huge decision to make (Score:2)
The job you don't want to do, you need to hire for. If that's the mangerial role, you need to make sure you don't end up a lowly surf by managing the hiring process very very carefully to ensure you retain control at all times.
If you are unable or unwilling to find
Simple (Score:2)
Step 1: Think of the coolest things you can do to make things quick and easy.
Step 2: Implement it.
Step 3: Document it.
Really, whether it's thin clients, giving all the pc's bootable nics, setting up network images for reimaging, using VNC or other remote service/admin tools... think outside the box and then do it. Because with 200 people you're not going to have time to walk to every machine, nor can you spend time bringing the boxes in for simple reimage.
And d
SMS/AD/RIS (Score:2)
400 desktops (Score:2)
Work Harder (Score:2)
You wind up maintaining solutions to help you maintain your solutions. You train people to train people. You automate your processes, and in return you get to create a whole slew of new processes to oversee the automation. You lose techs thanks to the new "productivity", but you gain project manage
Re: (Score:2)
Maybe it's hypnosis. A company will sell it's software solution on how it will enable the client to do great things, and then get that client to pay *more* for complementary services because the developers did a bad job of making it actually easy to achieve great things.
Particularly when aspects of the infrastructure are Unix based, a lot of vendors out there will sell tools to help manage the whole picture, including managing *ni
Read This Book! Live This Book! (Score:4, Insightful)
Hire a Sys Admin (Score:2)
Above all don't pretend that you know how to manage IT infrastructure. Systems and infrastructure administration is a compeltly different world than most developers ever work in. Your automated systems and production environment
Not all too difficult (Score:2)
We didn't have any trouble or asset management except for what came with Active Directory and right now I'm implementing a central command, asset collector etc.
I can't elaborate on it due to NDA but if you're looking for someone to take care of your IT support management problems, contact me, I might be able to give you some tips.
You aren't successful unless you turn down work. (Score:2)
BTW, if you're already doing 60-hour work weeks, you had better be making some really really good money (*), because the alternative is that you're already losing the game. What if one of you comes down with a flu that puts you on your back for 3 weeks? The other two gonna work 90-hour weeks? Doubtful. 60-hour weeks a
Sorry, just to confirm.... (Score:2)
Errr whats unusual about this?
This may sound jokey but I am being serious. Every IT job I have had (7 in 10 years) I have worked these sorts of hours due to a) bad management, b) stupid sales people (promising stuff that is not ready/spec'd out for a months time) c) understaffing d) poor staff that are so bad at their jobs they should be fired e) general incompetence e) etc.. etc...
From experience the good programmers end up hav
Rubbish. (Score:2)
If there was the smallest hint that hours would become insane I was posting my CV to agencies and prospective employers faster than you can say "overtime".
IT people are all too willing to put put macho bravura performances, when in reality weeks of 60 hours are pointing to poor management and personel with lack of self respect.
Hire The Best, Work Together (Score:2)
Work tickets, audits, normalization, documentation (Score:2)
#1. Have a ticketing system in place or built. This is probably the most crucial thing you can do, because it will become the core of your job. Nothing gets done without a ticket, period. The ticketing system will also allow you to document (1) the problem, (2) the time spent on the problem, and (3) your interaction with the customers.
#2. You need to do an audit, so you know what services are being used (and requi
Re: (Score:2)
Sub-Contract (Score:2)
Interview for a qualified partner in crime (PIC) that has skills that fill the bill.
Hire, then train him/her.
The subcontractor will cost you plenty but will allow you to play catch up and snag the accounts.
Be up front with your customers about this, either they will support you in this, or you find out what you're really up against early.
It's all about being "reasonable".
Spend money - make money.
Eh?
I was told (Score:2)
Re: (Score:2)
"..., and hiring competent IT staff has been difficult."
Re: (Score:2)
I second this. It is hard as hell to find anyone competent with REAL WORLD EXPERIENCE for less than $75,000 a year. There plenty of guys out there who you can pay $50,000 and throw into the breach, but as soon as they have to recover a corrupt Exchange message store or bring up a crashed domain controller, they're going to end up causing more problems
Re: (Score:2)
Re: (Score:2)
When you say "looking for" you probably mean, how do we pick the resumes. HR does keyword searches on resumes posted on Monster and other resume farms. We also post jobs and look through all applicants who are interested in US. We contact, with the desire to bring in for an inter
Re: (Score:2)
As for scientific discoverie
Re: (Score:2)
So when these people move up the ranks and become Microsoft/HP/Cisco/IBM/etc certified they have a natural affinity to their chosen vendor.
Re: (Score:2)
Re: (Score:3, Insightful)
This is better advice than the poster may have intended. With your current size you really don't want to add FTE's just for two clients. Use that good old "people network" and see who you can shanghai on board temporarily (with an eye towards possibly making them FTE down the road). Otherwise you're investing heavily on what is essentially a gamble at this point.