cbs604

Taking over a network system from someone else is like trying to work in someones else's kitchen. You know what is to be achieved, but everything is not quite the same.

I have a client that I have done a bit of work for - dabbled inside their server, adding computers to the domain, administering users etc. The system is maintained from another state, and they visit about every six months or so. Their support has been very good, but for political reasons (long story) my client wants to give them the heave-ho, and have asked me if I am interested in taking over fully.

It is a system of about 100 workstations spread over about a dozen remote sites. I would love to take it over, but am very nervous for reasons as stated in the first para.

Assuming the current support people are co-operative, what info should I obtain from them? Maintenance reports? licence lists? warranties? passwords?

And if not, where should I start?

Any info would be greatly appreciated.

Cheers,
Brodie

bry623

Those are good. I'd also ask for any support logs they havepertaining to your client and any programs written specifically for them as well.

__________________
Scarlet and Gray in L.A. 9/13/08

crazijoe

I would breakout Visio and make a complete diagram of the network topology so you know what you are dealing with. Make sure all the licenses are on par and check with software vendors to see what annual licenses they have. Plus when they will expire. The only passwords you would need are the administrative passwords. You should not need any of the user passwords. Check with the ISPs in each location to see what contract they have.
Also check with the who you will be reporting to to see what they will be expecting from you and their future goals are (i.e. expanding company).

__________________
Microsoft MCSA + Messaging, MVP, A+, Network+





Do you want a real Republican?

HDD diagnostic tools / HDD data recovery software

yustr

Check who owns what - crazijoe's diagram will help. You'd hate for someone to show up a month from now and say "See this little bit here? It's ours."

Also, make sure you find any phantom/test users they may have set up through the years. Get an employee list and check it against your user list. Freeze any that don't match until you figure out who it belongs to.

__________________
I didn't mean to say it. But I meant what I said. J. McMurtry

In Vino Veritas

cbs604

Some good ideas there - thanks.

And what about the latter scenario - they don't provide any info at all?

I guess in that case I should get a clear understanding from the client of what difficulties (read: expensive) I will face at the transition and the early stages. Mapping out the sytem and getting a thorough understanding of how things have been set up, and why, will take time, and I hope nothing serious happens in the meantime.

There's nothing more deflating from a user than : " It was working OK before YOU came along"

Cheers,
Brodie

Cellus

In addition, depending on how much exposure your servers and workstations have to the internet, I would also consider having penetration tests or at the very least general security hygiene checking done to your network to see if your new ship has any leaks in it instead of bumping into problems down the road.

Take a peek at any and all company policies relating to your network and system to see if it meets your satisfaction.

Last but not least when you have the time (as it can be time consuming) to take a look at the Directory Service, DHCP, and DNS layouts to see if any kinks can be smoothed out. You'll undoubtedly be doing some of this as you acquaint yourself with the topology and look at the support logs, but getting yourself more intimately familiar with it will save you a lot of grief in the future.

__________________
TSF Networking Team

HijackThis 5 Step Process
Donate!