Re: Replacing a failed SBS 2003 Machine

Thanks for charing this info.

Ian, if rejoining your workstation, read this linkbelow.

How to properly rejoin a client workstation to an SBS 2003 Domain
http://techsoeasy.spaces.live.com/blog/cns!AB2725BC5698FCB8!278.entry

--
Henrik Arenblad, MCP SBS,

"MurwinTec" <MurwinTec@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F10ACA6-7D85-48EB-8EDD-53380ED8CACC@xxxxxxxxxxxxxxxx
After trying serveral different methods for disaster recovery of SBS 2003
the
one that worked for me was;
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d62bcc9/BKU_BkupRstr.doc
You may also run into some issues that I encountered after restoring to
the
new hardware;
When I ran Internet Connection Wizard I got the message that there was no
DHCP scope and one would be created, which did not work because DHCP was
not
running.
I fixed it by it by cleaning out folder c:\windows\system32\DHCP
I also had the same issue with WINS which I fixed by cleaning out folder
:\windows\system32\WINS (see KB 205100)
The other problem I was experiencing was that the system log kept getting
corrupted, which I fixed by getting a hotfix from Microsoft (KB 899416)
Once your new server is running you will have to join your workstations to
a
workgroup then rejoin the domain on the new server.


"Ian UK" wrote:

We're a small company and have been running SBS 2003 with 15 clients
successfully for the last three years. Earlier in the week we suffered a
complete server failure. We've tried everything possible to fix the old
server but trying to replace three year old kit has proved to be a
nightmare.
We actually got hold of an identical mb and cpu but unbelievably these
failed
in the same way as the first within 10 minutes! It's something ridiculous
like a faulty AGP card frying the mb. Anyway, we've given up on trying to
save the old server and have replaced it with a brand new Dell Poweredge
2900
due to arrive tomorrow.

What I'd like to know is whether there is a way of installing the new
server
and getting it to recognise our existing clients or will we have to
re-connect each client individually & loose all existing client settings?

Any help/advice very much appreciated.

Rgds

Ian


.

Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • RE: Unable to ping client2
    ... I understand that the server box can not ping one ... client workstation after upgraded to SBS 2003 SP1. ... Reboot the SBS Server. ... On the client workstation, run "ipconfig /release" and then run ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW-RDP
    ... It utilizes a cross-over cable between it and the SBS Server. ... Ehternet from hub to server and from hub to workstation ... Ethernet adapter Server Local Area Connection: ... Also, Merv, I can connect to the server and client machines on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Redirecting data sent to a local printer to another host and port on the network
    ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
    (comp.unix.sco.misc)
  • Re: RDP Problems
    ... If you try to input the IP address of the client to RDP to the client, ... Is ISA server installed on the server? ... Microsoft Online Newsgroup Support ... | Workstation to workstation works. ...
    (microsoft.public.windows.server.sbs)
Loading