Reinstall OS to fix corrupt system

MacbachsterMacbachster
edited June 2007 in Science & Tech
Hi Guy's,
I have a Win Small Business Server 2003, which I can't login to, I have reinstalled the OS to a new folder on the C: drive as it would not let me to a repair, is there a way of transfering the settings from the original setup to the new one and then delete the damaged one

cheers,
Macbach

Comments

  • kryystkryyst Ontario, Canada
    edited June 2007
    So if I understand this correctly you should now have the original system folder called Windows and probably now have another one called Windows.000. You are traveling down a dangerous path on a server. Why can't you log into it? Is it a case of forgetting the password or has something been damaged? You don't want to start messing around with a hacked up server it can screw up your AD and create all sorts of login issues down the road.
  • Your-Amish-DaddyYour-Amish-Daddy The heart of Texas
    edited June 2007
    Yeah man, you're better off blanking it, and restoring from a backup, which as a server admin, you should do that atleast once a month.
  • MacbachsterMacbachster
    edited June 2007
    The main Server is off getting fixed, I have an image and installed it on a stand alone, i tried to do a repair but it just kept going around in circles, had to do something drastic, this is a quick fix for a few days, i just want to have something for the users to continue to work while the main server is getting sorted, originaly a drive died, I installed a new drive and tried to do a rebuild but that died, more problems, I thought I read somewhere that it was possible to do this, normally I wouldn't touch this sort of thing but desperate times need desperate messures, so can it be done?
    cheers,
    Macbachster
  • Your-Amish-DaddyYour-Amish-Daddy The heart of Texas
    edited June 2007
    I've never done anything like THAT, but I have installed OVER an operating system with the same one. It worked for about five minutes, then it hit the OS and freaked out. Basically, unless you've got a small drive you can set up an OS on, and pull the data off manually, you're SOL and JWF'd.
  • kryystkryyst Ontario, Canada
    edited June 2007
    The problem lies in the domain naming structure your computers are looking to one server for their information if that information changes your whole network will get messed up. Worse case the users will loose accounts and everything will have to be recreated and then data moved over to the new counts etc....

    On a windows box you can sometimes get away with copying windows to windows.000 however there will be broken parts. So then you have to see what the broken part is and manually change it in the registry etc...

    On a server that sort of chore could drive a person insane. It's not worth doing. If the original server is being repaired I'd suggest having your users just log in locally without relying on the server and have your temp box just do file hosting and whatever else it was doing through IP connections and not through named device calls.
Sign In or Register to comment.