Re: SBS 2000 install problems (need to reinstall from scratch)
- From: "Jeff Foster" <noone@xxxxxxxxxxx>
- Date: Wed, 30 Nov 2005 07:49:33 -0600
I did look at that site, but I need to do this at no cost. All I see there
is a website trying to sell a product and, while I'm sure it is very useful,
I don't have any budget for it.
Besides, I am NOT wanting to keep all of Active Directory. I purposely want
to rebuild it from scratch to ensure that there is nothing that would
corrupt the new install. I am not sure whether my problems lie in the
current Active Directory or in the main OS install but I don't want to take
the chance of having any problems copied over.
One of the many issues that we have had was that our default domain policy
in Active Directory became corrupted a few months ago with no apparant
reason why. I had to delete that entire policy and create a new one. That
tells me that there are probably some issues inside of Active Directory that
I certainly don't want to keep.
I am not even concerned about encrypted files at this point. I scanned the
user's PCs last night and did not find anything encrypted so I don't even
have any problem with recreating the user accounts at this point. The only
thing that still does concern me is whether or not the users computer will
create a new local account (documents and settings stuff) when they log onto
the new network and the computer finds new SID's for each user name.
I ran a test on my test box the other day and connected my laptop to it. It
connected fine and didn't change my local user settings. However, I set up
my user account on the test box to use the same username and password.
Since I don't have the passwords for each user right now, I am hoping that
the password reset at the same time the SID's change will not trip the
user's PCs into creating new documents and settings info.
(My test box was set up with identical network, Active Directory, DHCP, DNS,
and WINS settings as our existing network. To my computer, the only thing
that changed was the user account SID and possibly the computer account SID)
Jeff
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:OjGtVqS9FHA.3208@xxxxxxxxxxxxxxxxxxxxxxx
> SBS requiring itself to be the primary DC does not stop replication of the
> AD between servers.
> did you look at www.sbsmigration.com?
>
> "Jeff Foster" <noone@xxxxxxxxxxx> wrote in message
> news:OkUansP9FHA.1416@xxxxxxxxxxxxxxxxxxxxxxx
>> 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Prev by Date: Re: ISA Server isn't firewalling the external interface
- Next by Date: Promote 2k3 member server to SDC in SBS 2k domain
- Previous by thread: Re: ISA Server isn't firewalling the external interface
- Next by thread: Promote 2k3 member server to SDC in SBS 2k domain
- Index(es):
Relevant Pages
|
