Hey, What's the average hourly rate for client-server installs

[TheDisciple]

Hey, What's the average hourly rate for client-server installs? I don't wanna get ripped off & consequently hurt myself financially, ya know.

Also, how long will an install, config, testing usually last? I've done numerous peer-to-peer setups w/ Cat5, Hubs, Shared folders, printers, addin protocals,wrkgrps etc;
Is the learning curve for someone w/ p-to-p bkgrnd steep???

H/w are as follows:

(1) w2k srvr
(6) w2k Pro clients (currently up & running StandAlones)
(1) 3Com hub
All Cat5's & nics presently on-hand.

 

[AlexIT]

I charge 125USD per hour. Config is pretty quick and easy if clients do it correctly (the way I tell them to do it), about 3-4 hrs for each server and about 1-2 for each workstation for setup and 2-3 days extra on hand for testing. I don't train users included in this. If client has something bizarre, like antique 9" floppy from discount/used computer store, then we start at 2-3 days per server, full day for each workstation, and testing can last a month. I also add about 20 min per computer for each extra piece (printers, extrnal modems...) just because they can be real pain...

http://www.driverguide.com

can be best friend working with old junk. Get a good Win2k book and read it cover to cover twice. Plan the network out too before you touch anything as fixing a wrong config in the server usually requires complete re-install.

Alex

 

[TheDisciple]

Hey AlexIT, "budd(ie)" I must say that ure response time
is more than reasonable!!! Another non-let down :-}
U have recommended a bk by Mark Minerva right? What about
having a w2k Svr bk as a supplement to that; Is there any positive feedbk that ure aware of concerning the way IDG handles the w2k Svr topic?

=TheDisciple

 

[HebieBug]

The market around the world does not seem to have a set rate when it comes to this one.
Desktop machines are easy enough to do the install on. When it comes to Server install make sure that you get someone who knows exactally what they are doing...
If your desktop machines are of a standard build then it is worth getting your hands on Norton Ghost which will cut your install from 21/2 hours to 25minutes which can save you cost.
As for cost which is what your really after anywhere from 40AU to 400AU

 

[TheDisciple]

"Plan the network out too before you touch anything as fixing a wrong config in the server usually requires complete re-install."

As far as I saw, the net has already been planned.
ie: ea. wrkstn has w2k Pro up & running;
Srvr has w2k Server too.

all that's left to do is running Cat5 from wrkstns
to the hub & from the server to hub & connecting a ext. mdm.
At this point, how hard is it to finally get things rolling?

=TheDisciple

 

[ShackDaddy]

Your billing amount might be substantially different depending on the industry that you are consulting for and the area you are consulting in, even in different areas of the continental US.

I don't even charge an hourly rate. I sit down and estimate how long it should take someone of my expertise to do the job, with a tad of padding and I quote the client a lump sum for the 'project'. If the installation and configuration and testing goes really well, I come out further ahead than I would have. If things go wrong and I spend several hours more than I had planned, the customer is protected, but all in all, I find myself working at exactly the right pace, being just as careful as I need to be, since it is now _my_ money that I'm spending, not the clients. Customers appreciate the fact that costs aren't going to skyrocket, since they are precalculated, and while they sometimes balk at the initial outlay figure, a known quantity is easier to deal with.

The key thing to working this way is to do thorough pre-planning. Creating very detailed project specs and not allowing the customer to add extra work to the project without accounting for it cost-wise. Often it's easiest to add small dollar sub-projects that are bid and signed for and sometimes even billed, separately.

ShackDaddy

 

[tertone100]

I totaly agree with you guys, planning is a CRITICAL part that canno't be bypassed if you want success with any project. There are soo many reasons that i will not even bother to mention. Sorry to say that many,many of these postings are from people who have not done any planning at all. Someone once told me that anyone that anything on there production network without proper planning, documintation research is a moron and desirves the nightmares that they will have.

In montreal, the rates are quite low thats why I want to go work with AlexIT.

 

[SteveTheGeek]

Disciple,
Once things are physically hooked up, the real fun begins. What's your IP addressing scheme (please, make it a reserved-for-internal-use subnet)? DHCP or fixed? Domain name? DNS? Active Directory setup? User accounts, shared folders, backup/recovery, security/administration, shared printers, plan for eventual internet connectivity, anti-virus, networked applications... The list goes on.
Where are you located? In relatively remote areas I'd bill between $50/hr and $100/hr for this kind of work, but you might consider giving your client a fixed cost or a really cut rate since you sound kind of inexperienced in server/client issues. Also, running your planning by a friend or colleague who does have more experience before you start installing will help prevent your building a tarpit network...
-Steve

 

[tertone100]

If i'm not mistaken the planning and deployment guide (resource kit) is about 650 pages and none of it is garbage. That should tell you about the complexity of W2k.

 

[Quetzalcoatl]

Totally agree with Steve and tertone100. Documentation is the basis of any network. Like CISCO says, when you have a problem, the first place to take a look at is your documentation, so if you don´t have your documentation, How do you know that you have a problem?

Just stick to the administration proccess: Planning Organization, Direction and Control, that's all.

Believe me when I tell you this, I hope you don´t have any problem, but if you have some, you'll be wishing to have your docs if you don't.

 

[AlexIT]

Disciple,

Steve nailed it! That network you described is not remotely setup, as maybe they only have the HARDWARE figured out (or maybe the hardware is flexible too) You will need to figure out a Domain name, IP addressing scheme, DHCP structure, name resolution plan (i.e. DNS is recommended by me!), Active Directory setup, User accounts, user groups (maybe not, too few users I think), shares, backup/recovery system, security&admin for after you are gone, internet connectivity scheme, network anti-virus, networked apps; all of these are a must before you install Win2K server (I'd re-install it, as who knows if the setup is correct now.) Even if the workstations are running, I'd plan to wipe them and re-install everything (or ghost if IDENTICAL hardware) because you don't want to find someone has the "coolest" screen saver installed...and it contains some lovely virus that will be YOUR fault if it infects the network.

Hit the books, and Tertone had a good one too, read the deployment guide and it will pretty much cover the whole mess (even if it describes some overly complex systems.)

Alex

 

[TheDisciple]

Thnx people, will do some in-depth reading as well, prior to giving it a shot; will also speak w/ a colleage...think he's doing some w2k it work.

Thnx.