There are a number of "undelete" utilities that can allow you to recover deleted files, even if gone from the recycle bin (or they never went there). If this is an option you are open to, please consider, before restarting the server.
You are correct - once restarted, it will surely fail. I'm deeply worried that restoring from your CD will restore old versions of critical system files, and it will be a disaster - in the registry, the file system, etc. If this server holds AD master roles (or is the phantom NT4 domain controller, yes, that exists even in Native mode), I strongly suggest moving them to a backup server while you still can. Furthermore, I trust that if this is a logon server, your clients point to another DNS in case the primary is unavailable.
Caveats to undeleting:
As time wears on, deleted file information will be lost, as will also be caused by installing a large product (such as a larger undelete util/suite).
Go here for a set of commercial undelete utilities. You may be able to find a freeware one, but it's harder, and you don't know what you're getting. I don't personally know if one of these is better than another; we always have backups.
I have managed to restore almost all files that was deleted in sys32 - 1496 restored of total deleted 1560
Software to restore was RStudio from R-tools Technology
Inc.
I have tried to copy the restored files back to the system32 folder but some files are in use (services) and can not be replaced at the moment. I cannot see how may files that are really back to system32.
I have also tried to reinstall servicepack 2 for Win2k but it needs 'Cabinet.dll'. I guess that this is not the only sys32 file that is needed to reinstall the service pack.
The critical services that is running right now are:
SQL-server
IIS
FTP
The databases are to big to copy elsewhere. So I'm planning to detach the databases before I try to restart the server.
I've now got myself hardware to enable backup so that I'm better prepared for future disasters.
It is possible to create a Windows 2000 installation CD with SP2 *integrated* into the installation - meaning that perhaps you could get cabinet.dll by creating one of these (I think it's called SlipStream). Since you got most of your files restored, I'm betting you're in significantly better shape.
One thing that you could look into is the registry key...I'm so annoyed that I don't remember its name (something like the pending file queue)...that is used for upgrades - upon restart, any files listed here replace files that were in use before the system starts. Though, making changes to registry increases the opportunity for failure, it could also reduce it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.