I currently have SBS 2000 running on a Dell PowerEdge
1400.

This install began 5 years ago with SBS 4.0 OEM on a
Compaq.

It was then upgraded to SBS 4.5

Then I migrated it to the Dell and then upgraded it to
SBS 2000. (This was fun because the OEM SBS 4.0 only
supported Compaq.)

Unfortunatley, neither upgrade went smoothly. After days
of working with MS, it has been pretty stable for the
last 18 months.

I now am running into a drive space issue on C:\ because
of the 4 gig limit inherited from NT 4.0

What I would like to do is to start over with a clean
install of SBS 2000 and migrate the users profiles and
Exchange Info. (Taking advantage of WIN 2Ks abillity to
increase the maximum size of C:)

Is there a way to export out the User SIDs?

Also what issues will I have with my Client Packs?
One is 4.0 , two are 4.5, and one is 2000.

Re: Clean Install of SBS 2000 by Daniel

Daniel
Tue Jul 22 15:50:41 CDT 2003

You could always use Partition Magic to increase the size of your C:
partition.

Daniel.

"Arthur Dubey" <adubey@winstead.com> wrote in message
news:00cb01c3507d$8332bb60$a501280a@phx.gbl...
> I currently have SBS 2000 running on a Dell PowerEdge
> 1400.
>
> This install began 5 years ago with SBS 4.0 OEM on a
> Compaq.
>
> It was then upgraded to SBS 4.5
>
> Then I migrated it to the Dell and then upgraded it to
> SBS 2000. (This was fun because the OEM SBS 4.0 only
> supported Compaq.)
>
> Unfortunatley, neither upgrade went smoothly. After days
> of working with MS, it has been pretty stable for the
> last 18 months.
>
> I now am running into a drive space issue on C:\ because
> of the 4 gig limit inherited from NT 4.0
>
> What I would like to do is to start over with a clean
> install of SBS 2000 and migrate the users profiles and
> Exchange Info. (Taking advantage of WIN 2Ks abillity to
> increase the maximum size of C:)
>
> Is there a way to export out the User SIDs?
>
> Also what issues will I have with my Client Packs?
> One is 4.0 , two are 4.5, and one is 2000.



Re: Clean Install of SBS 2000 by Arthur

Arthur
Tue Jul 22 15:55:06 CDT 2003

Thanks Chad,

Let me re-cap to make sure I've got my ducks in a row.

1. Load WIN2K Server sp3 on a Spare machine.(Not SBS)
2. Join the SBS Domain and run dcpromo.
3. Backup Exchange, All Databases User files etc.
4. Remove the SBS from the network and seize the FSMO
roles on the spare box. (Is there a White Paper on
seizing the FSMO roles.)
5. Wipe out the SBS Re-Partion / Format and install WIN2K
Server Sp3.
6. Join it to the domain and run dcpromo.
7. Run dcpromo on the spare box to demote it to a member
server.
8. Upgrade to SBS 2000.
9. Restore Exchange Backup / restore SQL Database etc.
10. Add CALs. (Your right, I forgot durring the 2000
install I ran through a routine to merge all of the CALs
to one SBS 2000 Pack.)

PS.
I forgot to mention this is a dual NIC install that is
also multi-homed.
Any words of wisdom or cautions concerning this config?

Thanks again,
Arthur

>-----Original Message-----
>Hi Arthur -
>
>The only way to migrate your domain (maintain your SID)
is to join another
>server to your domain and make it a DC. In order to do
this, you'll need a
>copy of plain Win2k (or Win2k3) server. Install this on
a spare box, join
>it to your domain and run dcpromo. Take a full backup
of your SBS and
>optionally migrate any shares / databases from your SBS
to the temp server.
>Remove the SBS from the network and seize the FSMO roles
on the spare box.
>Wipe your SBS and install plain Win2k(3) server, join it
to the domain and
>run dcpromo. Throw in SBS CD1 and upgrade to SBS.
Restore Exchange /
>shares / etc. Run dcpromo on the spare box to demote it
to a member server,
>unplug it from the network and remove it from AD.
>
>As for your CALs - you need SBS2k CALs - you can't use
SBS4 or SBS4.5 CALs
>with SBS2k. CAL disks are tied to the internal nic on
the server they were
>first installed on. Therefore, if they were originally
installed on the
>Dell server (and you haven't changed your nics), there
shouldn't be any
>problem. Even if they were installed on a different
server first (or you've
>changed your nics), a call to MS will be able to unlock
the disks so they
>can be reused. However, you will need to get SBS2k CALs
for your current
>SBS4.0 and SBS4.5 CALs.
>
>--
>
>Chad A. Gross
>
>Lerman's Law of Technology: Any technical problem can
be overcome
>given enough time and money. Corollary: You are never
given enough
>time or money.
>
>
>.
>

Re: Clean Install of SBS 2000 by Arthur

Arthur
Tue Jul 22 16:04:14 CDT 2003

I'm not real crazy about Partition Magic. I've used
before on some WIN 95 FAT partions. It seem to work, but
we had some realy weird stuff going on. I finally just re-
formated all of the work stations and upgraded to WIN 2K
Prof.

In addition the Dell is running a PERC Raid 0 SCSI
configuration. (NTFS) Not sure Partion Magic will work in
this environment.

AD
>-----Original Message-----
>You could always use Partition Magic to increase the
size of your C:
>partition.
>
>Daniel.
>
>"Arthur Dubey" <adubey@winstead.com> wrote in message
>news:00cb01c3507d$8332bb60$a501280a@phx.gbl...
>> I currently have SBS 2000 running on a Dell PowerEdge
>> 1400.
>>
>> This install began 5 years ago with SBS 4.0 OEM on a
>> Compaq.
>>
>> It was then upgraded to SBS 4.5
>>
>> Then I migrated it to the Dell and then upgraded it to
>> SBS 2000. (This was fun because the OEM SBS 4.0 only
>> supported Compaq.)
>>
>> Unfortunatley, neither upgrade went smoothly. After
days
>> of working with MS, it has been pretty stable for the
>> last 18 months.
>>
>> I now am running into a drive space issue on C:\
because
>> of the 4 gig limit inherited from NT 4.0
>>
>> What I would like to do is to start over with a clean
>> install of SBS 2000 and migrate the users profiles and
>> Exchange Info. (Taking advantage of WIN 2Ks abillity to
>> increase the maximum size of C:)
>>
>> Is there a way to export out the User SIDs?
>>
>> Also what issues will I have with my Client Packs?
>> One is 4.0 , two are 4.5, and one is 2000.
>
>
>.
>

Re: Clean Install of SBS 2000 by Chad

Chad
Tue Jul 22 16:52:25 CDT 2003

Hi Arthur -

If it were me, I'd dcpromo the spare box down to a member server, unplug
from the network and remove from AD as you last step (vs step 7 in your
list). Also - if you have access to an imaging product (even Ghost 2003),
take an image of your SBS before starting the process, so if you run into
problems after wiping your SBS you have a safety net to get back to a known
good configuration if you need to abort the process.

--

Chad A. Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.

In news:042e01c35093$87c47680$a401280a@phx.gbl,
Arthur Dubey <adubey@winstead.com> posted:
> Thanks Chad,
>
> Let me re-cap to make sure I've got my ducks in a row.
>
> 1. Load WIN2K Server sp3 on a Spare machine.(Not SBS)
> 2. Join the SBS Domain and run dcpromo.
> 3. Backup Exchange, All Databases User files etc.
> 4. Remove the SBS from the network and seize the FSMO
> roles on the spare box. (Is there a White Paper on
> seizing the FSMO roles.)
> 5. Wipe out the SBS Re-Partion / Format and install WIN2K
> Server Sp3.
> 6. Join it to the domain and run dcpromo.
> 7. Run dcpromo on the spare box to demote it to a member
> server.
> 8. Upgrade to SBS 2000.
> 9. Restore Exchange Backup / restore SQL Database etc.
> 10. Add CALs. (Your right, I forgot durring the 2000
> install I ran through a routine to merge all of the CALs
> to one SBS 2000 Pack.)
>
> PS.
> I forgot to mention this is a dual NIC install that is
> also multi-homed.
> Any words of wisdom or cautions concerning this config?
>
> Thanks again,
> Arthur
>
>> -----Original Message-----
>> Hi Arthur -
>>
>> The only way to migrate your domain (maintain your SID) is to join
>> another server to your domain and make it a DC. In order to do
>> this, you'll need a copy of plain Win2k (or Win2k3) server. Install
>> this on a spare box, join it to your domain and run dcpromo. Take a
>> full backup of your SBS and optionally migrate any shares /
>> databases from your SBS to the temp server. Remove the SBS from the
>> network and seize the FSMO roles on the spare box. Wipe your SBS and
>> install plain Win2k(3) server, join it to the domain and run
>> dcpromo. Throw in SBS CD1 and upgrade to SBS. Restore Exchange /
>> shares / etc. Run dcpromo on the spare box to demote it to a member
>> server, unplug it from the network and remove it from AD.
>>
>> As for your CALs - you need SBS2k CALs - you can't use SBS4 or
>> SBS4.5 CALs with SBS2k. CAL disks are tied to the internal nic on
>> the server they were first installed on. Therefore, if they were
>> originally installed on the Dell server (and you haven't changed
>> your nics), there shouldn't be any problem. Even if they were
>> installed on a different server first (or you've changed your nics),
>> a call to MS will be able to unlock the disks so they can be reused.
>> However, you will need to get SBS2k CALs for your current SBS4.0 and
>> SBS4.5 CALs.
>>
>> --
>>
>> Chad A. Gross
>>
>> Lerman's Law of Technology: Any technical problem can be overcome
>> given enough time and money. Corollary: You are never given enough
>> time or money.
>>
>>
>> .




Re: Clean Install of SBS 2000 by SuperGumby

SuperGumby
Tue Jul 22 17:01:44 CDT 2003

I hope you're not really running your domain controller on a raid0 set.

"Arthur Dubey" <adubey@winstead.com> wrote in message
news:033501c35094$ce4c61c0$a501280a@phx.gbl...
> I'm not real crazy about Partition Magic. I've used
> before on some WIN 95 FAT partions. It seem to work, but
> we had some realy weird stuff going on. I finally just re-
> formated all of the work stations and upgraded to WIN 2K
> Prof.
>
> In addition the Dell is running a PERC Raid 0 SCSI
> configuration. (NTFS) Not sure Partion Magic will work in
> this environment.
>
> AD
> >-----Original Message-----
> >You could always use Partition Magic to increase the
> size of your C:
> >partition.
> >
> >Daniel.
> >
> >"Arthur Dubey" <adubey@winstead.com> wrote in message
> >news:00cb01c3507d$8332bb60$a501280a@phx.gbl...
> >> I currently have SBS 2000 running on a Dell PowerEdge
> >> 1400.
> >>
> >> This install began 5 years ago with SBS 4.0 OEM on a
> >> Compaq.
> >>
> >> It was then upgraded to SBS 4.5
> >>
> >> Then I migrated it to the Dell and then upgraded it to
> >> SBS 2000. (This was fun because the OEM SBS 4.0 only
> >> supported Compaq.)
> >>
> >> Unfortunatley, neither upgrade went smoothly. After
> days
> >> of working with MS, it has been pretty stable for the
> >> last 18 months.
> >>
> >> I now am running into a drive space issue on C:\
> because
> >> of the 4 gig limit inherited from NT 4.0
> >>
> >> What I would like to do is to start over with a clean
> >> install of SBS 2000 and migrate the users profiles and
> >> Exchange Info. (Taking advantage of WIN 2Ks abillity to
> >> increase the maximum size of C:)
> >>
> >> Is there a way to export out the User SIDs?
> >>
> >> Also what issues will I have with my Client Packs?
> >> One is 4.0 , two are 4.5, and one is 2000.
> >
> >
> >.
> >



Re: Clean Install of SBS 2000 by Brent

Brent
Wed Jul 23 11:54:49 CDT 2003


>-----Original Message-----
>Hi Arthur -
>
>The only way to migrate your domain (maintain your SID)
is to join another


So, if I am moving my SBS to a NEW box (not reinstalling
on the same) is there an easier way? I have tried just
backing up and restoring the system state, but that just
kills the new box.

Thanks

--Brent Hoover
Computer Weasel
audioMIDI.com

Re: Clean Install of SBS 2000 by Chad

Chad
Wed Jul 23 12:31:00 CDT 2003


Brent Hoover wrote:
>> -----Original Message-----
>> Hi Arthur -
>>
>> The only way to migrate your domain (maintain your SID) is to join
>> another
>
>
> So, if I am moving my SBS to a NEW box (not reinstalling
> on the same) is there an easier way? I have tried just
> backing up and restoring the system state, but that just
> kills the new box.
>
> Thanks
>
> --Brent Hoover
> Computer Weasel
> audioMIDI.com

Nope. As you've discovered, restoring the System State doesn't work because
doing so restores the registy, which includes references to your old
hardware which kills the new box. In order to maintain an AD domain in this
type of migration, you have to have another DC preserving the domain (SID &
SAM). SBS2k cannot natively join an existing domain, and you cannot have
more than one SBS on the same network. Therefore, your only option to
preserve the domain is to have a Win2k (or Win2k3) server as a DC. The way
I see it, you've got a few different options:

1) Use the method mentioned in my eariler post - grab a spare box and set
it up as a DC in your domain. Unplug the old SBS from the network, seize
the FSMO roles on the spare box. Load up plain Win2k on the new server,
join the domain & upgrade to SBS. Dcpromo the spare box down to a member
server, unplug & remove from AD. Restore Exchange / network shares etc. to
new server. The primary benefits of this method are that you not only
maintain your existing domain, but you're able to give your new server the
same name as your old server, so client drive mappings, scripts, etc.
continue to work without a hitch.

2) Pretty much the same as #1 above, except you don't use the spare box.
Just load up Win2k on the new server, join it to your domain & make it a DC.
Remove the old SBS, seize the FSMO roles and upgrade to SBS. Down-side is
that the new box cannot be named the same as the old server.

3) Go with a clean install / new domain. Just install SBS on the new
server. Restore Exchange / shares, etc. You'll have to recreate all of
your user accounts and if you have any NT / Win2k / XP clients, they'll have
to be joined to the new domain, and when that happens all new profiles will
be created - so you'll have to manually recover user profiles on each
machine as well.

4) Wait for SBS2003 which will allow you to join an existing domain
(including SBS2k). This will be similar to #2 above, just that it you don't
need a copy of Win2k and it is part of the scripted install . . .

--
Chad A Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.