I am the new developer replacing the old developers for a coldfusion (4.5?) / sql server (2000) website

The client is worried that the old developers will sabotage the site when they learn they are being canned. Neither of us are sure whether this is a realistic concern.

I currently have access to webroot with FTP and to SQL server via enterprise manager, but the client doesn't have any more information. I don't have access to the web admin panel, the coldfusion administrator or the cf_root directory. I think I can contact the host to get that stuff, but they MIGHT be connected to the developer in some way.

I'm trying to develop a strategy so that I can get as much access as possible first without raising suspicions, and then start to ask the old developers questions and get as much help from them as possible in the transition. If they cooperate it will be very valuable because the site is a mess. If they don't, I want to be in a position to take control of the site - i.e. change all the passwords and lock them out.

So my questions:
* What do I need to get from the host aside from what I list above?
*Once I have full access, what steps can I take to prepare to lock them out if necessary?
* Should I just preemptively lock them out now?
* If they cooperate, what should be my priorities in asking them for help? My list so far is
1)info on all installed components and custom tags
2)current procedures


Thanks for reading this far and any responses!



***if this is off topic - pls let me know (and if there is somewhere you know of where it would be ontopic. I also posted to ATOT)***

bzq,

Maybe you should have the person that you are going to be working for get the information. For they have every right to know the passwords for their things. Other then that is it a dedicated server? How about some sort of VPS? Answeres to the these questions can help this community, help answer your questions better.

Good luck,
Loren

it is a shared server. The client is definitely going to be doing the communicating with the old developers, and he will either contact the host or ask me to do it directly. What he wants to do is get as much information as possible before it is obvious why he is asking the questions.

bzq,
Was the client that you will be working for, to still pay the old developers for work that has already been rendered? If not your client should simply tell them that he would no longer like to do business with them. If they destroy the content or do not give services that were paid for. Then your client will have to take legal actions or of course you would have more work to do.

well the client is considering offering them a fee for the time they will spend helping me, but basically they owe him a lot of work that he has paid for and he is willing to forego that. A legal remedy would not be ideal as they are in another country and very small (not much to sue). The goal is to avoid the potential disruption. I have backed up almost everything, so I don't think they could do any permanent damage, but they could certainly cause great inconvenience

bzq,
I would just suggest starting from scratch and relaunching the site once you have completed the stuff. Possibly find a diffrent host and change the DNS for the site, is the save way to do it I would suggest.

Best of Luck,
Loren

why not just have the client tell them he is moving the site to a new host and you are helping them. Then request all the info you need about the site, as you might need to know this information to sucessfully move the site without disruption.

what whw said might work also. Unless they are directly connected to the hosting company that hosts the site. :-(

that is a good idea. There are 2 weird things about this site, and maybe that approach would convince the developers to fix them:
1) site is 2 GB, most of which is verity collections and redundant scripts (almost 2000 cfm files!)
2) most important table in database has bad data in it preventing me from making a copy through DTS

since no new host would be able to handle the site as it is, they would have to clean it up to hand it off.... boy I think I like that

woohoo!

I thought up a good idea for once! :D

be proffesional about this.
i know if i was being laid off....i wouldnt like it. and i would carry on the knowledge transfer very well.

but...ur not dealing with me.
obviously u will have a backup of all cfm files. open the entire story how its going to be to all the developers, etc.

3 possible outcomes:
1. if they co-operate and help u...good for all.
2. if they dont....u gotta learn on ur own....CF really isnt rocket science....and all the admin passwd can be bypassed (if not...at most...u will have to reinstall...no biggie)
3. if they react badly and start wrecking stuff (as unprofessional as one can be) THEN and only THEN u lock them out and restore backups (database AND cfm files)

u will have application.cfm in the backup...so no worries about advanced settings. and if u cant bypass the CF admin passwd (its very easy actually) then just reinstall. heck!...for sql2000 u dont even need to do anything...just a few clicks n ur set.

now...as for the "hosting" side of the story....im new to this whole hosting thing....if u and hosting company have a contract...they shouldnt so poop. if they still do....contract is broken...sue the hosting company (lots of money there...wreck the company) and move to new hosting company with ur backups.

i dont see why ur even so worried about all this...its all by the books...thats how it is done in the industry.