Re: SBS 2000 install problems (need to reinstall from scratch)

Sorry about that. They are just simple IDE drives running as dynamic disks
with mirrored volumes.

I am familiar with the Active Directory replication from one server to
another but even if I did set up a temp server, once I reformat and
reinstall SBS 2000, the reformatted server wouldn't take Directory updates
from the temp server since the SBS server has to be the primary domain
controller. At least, that's the way I understand it.

Besides, I don't want to keep the entire Active Directory. I only want to
retain the user accounts (SID's for the user accounts). Once I reinstall,
the SBS install will change the AD schema to accomodate Exchange. Even if I
could replicate the existing AD data to the reformatted server, the old data
doesn't contain the same schema changes and would likely cause problems
again.

Jeff


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:OSoXfRF9FHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
> No, if you're wanting to use the drive as a fallback point you do not
> first logically break the mirror, just shutdown and remove one of the
> drives.
>
> I'd probably take whichever is appearing as drive 0 out, make sure you can
> boot off the other. You don't mention whether it's IDE or SCSI, boot
> problems differ depending on the type.
>
> To retain your AD information (Users/Computers etc...) you would need to
> follow a procedure similar to that offered at www.sbsmigration.com. The
> basic process is that you install W2K Server to a temp box, dcpromo it
> into a DC role, allow the AD to replicate to it, format and install the
> original box. BUT there's a few more steps involved.
>
> "Jeff Foster" <noone@xxxxxxxxxxx> wrote in message
> news:OQZ8FcC9FHA.3996@xxxxxxxxxxxxxxxxxxxxxxx
>>I currently have an SBS 2000 server that has numerous problems. I think
>> most of these stem back to the way that SBS was originally installed. I
>> don
>> 't believe it was a clean installation. I think it may have been
>> installed
>> on top of a demo version or some sort of "upgrade" from a standalone
>> Win2K
>> server. Regardless, there are many features of SBS that are not
>> available.in fact, all of the SBS features are not available. It is
>> basically just functioning as a limited Win2K server. None of the SBS
>> consoles are installed, Exchange is not installed, shared fax, ISA, etc.
>>
>>
>>
>> I have tried to sit down with it and go through the SBS install but I get
>> errors that cause any installation of the SBS components to fail. I
>> spent 8
>> hours with it on Saturday when the office was closed trying to get
>> everything else installed but it just caused more problems. I have come
>> to
>> the conclusion that I am going to have to do a clean install to overwrite
>> the existing installation and get everything installed correctly and
>> working.
>>
>>
>>
>> Here's my situation. Our server currently has two mirrored 40GB HD's
>> divided into three partitions. Partition one is the SBS install (or
>> whatever part is actually installed), partition two is all the shared
>> folders, and partition three is empty.
>>
>>
>>
>> I will, of course, run a full system backup before I start any of this,
>> but
>> I also want to take out one of the mirrored drives and set it aside to
>> serve
>> as an easy restore method in case the reinstall fails for some reason.
>>
>>
>>
>> Do I need to go into disk management and break the mirror first or just
>> power down the computer and take out the mirrored drive as is? If I have
>> to
>> reboot from the mirrored drive, the other drive will have been
>> repartitioned
>> so I know that I would have to go into disk management to reset the
>> partitions and mirror. My concern is how to take the drive out. Will
>> breaking the mirror make the drive unbootable or is that what would be
>> necessary?
>>
>>
>>
>> Also, I prefer the idea of rebuilding as much of the settings as possible
>> (DNS, DHCP, Active Directory group policies), but is there any way to
>> keep
>> the user accounts (Security ID's) from the existing system to ensure that
>> any encrypted files that the users may not admit to having on their own
>> machine are still recoverable (File encryption is a company no-no due to
>> past issues with it), and also to keep the users desktop accounts intact?
>>
>>
>>
>> Thanks for any help or pointers that you can provide.
>>
>>
>>
>> Jeff Foster
>>
>>
>
>


.

Relevant Pages

  • Re: hardware for Exchange 2003
    ... your current server will work fine. ... in daily bases or weekly bases in order to commit the T.L files into Exchange ... one(or mirror or RAID 1) for Transaction Log files and let's call this D: ... ALL SCSI drives running at 15krpm for maximum throughput. ...
    (microsoft.public.exchange.design)
  • Re: Upgrade from SBS2K to SBS2k3 R2
    ... and re-run setup. ... seems ok now except my POP3 connector failed to install... ... Dell server, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2000 install problems (need to reinstall from scratch)
    ... logically break the mirror, just shutdown and remove one of the drives. ... a DC role, allow the AD to replicate to it, format and install the original ... > most of these stem back to the way that SBS was originally installed. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Worst monday of my life - please help...
    ... If that's the case, restoring the SQL ... but it finally did install with a few hiccups. ... >> or just leave the mirrored drives in the server on the secondary IDE ... I decided it was time to re-add the mirror. ...
    (microsoft.public.windows.server.sbs)
  • Re: Moving SCSI RAID array to new server
    ... Install the now blank array into the SBS2003, create the RAID volume, etc... ... I'd also probably lose the shirty SATA drives and eventually swing the whole ... > migrate the settings from the old server I just want to move the old RAID5 ...
    (microsoft.public.windows.server.sbs)