Hello all
Here is my scenario...I have installed SBS 2000 into an existing 2003 AD
domain. The Active Directory is in 2000 native mode. I made the dumb mistake
in assuming I could install the SBS as a member server and install Exchange
from the installation binaries on Disk 3. (without the entire SBS package)
All was fine until I got licensing errors as I connected more than 10 people
to their new mailboxes.

Does anyone have an intimate knowledge of SBS's licensing architecture? I
figured it would be OK because there is less than 25 users and I should have
50 and used the proper installation keys that came with the software. It
smells like it's the fact that it (SBS) is not the DC and the other DC
contains all of the roles (licensing in particular)

My initial thoughts on fixing this issue -
-Make a backup of the MS Exchange Information Store.
-Promote the Win2k member server (SBS 2000) to a DC.
-Transfer all Operations roles from the other 2003 DC (2000 native mode) to
the SBS.
-Reinstall the (entire) SBS suite.
-Restore the Exchange information store

Would this reset the license database?
Does anyone have any suggestions other than my plan..? MVP's?
Thanks in advance.
--

Regards
Tom

Re: SBS 2000 Licensing issues - help ! by Larry

Larry
Tue Feb 05 15:50:11 CST 2008

Because more eyes are watching, you may get more response in the SBS 2003
Newsgroup.

SBS public Newsgroups:

SBS 4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

if your current news server does not carry the mentioned groups you should
be able to connect directly to news.microsoft.com

--
Larry



"Tom D." <TomD@discussions.microsoft.com> wrote in message
news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> Hello all
> Here is my scenario...I have installed SBS 2000 into an existing 2003 AD
> domain. The Active Directory is in 2000 native mode. I made the dumb
> mistake
> in assuming I could install the SBS as a member server and install
> Exchange
> from the installation binaries on Disk 3. (without the entire SBS package)
> All was fine until I got licensing errors as I connected more than 10
> people
> to their new mailboxes.
>
> Does anyone have an intimate knowledge of SBS's licensing architecture? I
> figured it would be OK because there is less than 25 users and I should
> have
> 50 and used the proper installation keys that came with the software. It
> smells like it's the fact that it (SBS) is not the DC and the other DC
> contains all of the roles (licensing in particular)
>
> My initial thoughts on fixing this issue -
> -Make a backup of the MS Exchange Information Store.
> -Promote the Win2k member server (SBS 2000) to a DC.
> -Transfer all Operations roles from the other 2003 DC (2000 native mode)
> to
> the SBS.
> -Reinstall the (entire) SBS suite.
> -Restore the Exchange information store
>
> Would this reset the license database?
> Does anyone have any suggestions other than my plan..? MVP's?
> Thanks in advance.
> --
>
> Regards
> Tom
>



Re: SBS 2000 Licensing issues - help ! by Cris

Cris
Tue Feb 05 16:22:57 CST 2008

This is a multi-part message in MIME format.

------=_NextPart_000_01FC_01C86813.5E2305C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Larry he's installing SBS 2000

Tom. Why are you installing a version of SBS that is so old when you =
have an existing 2000 domain

At a minimum you should be installing SBS 2003. there is a white paper =
on the SBS 2003 into an existing AD domain

--=20
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in =
message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
Because more eyes are watching, you may get more response in the SBS =
2003=20
Newsgroup.

SBS public Newsgroups:

SBS 4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

if your current news server does not carry the mentioned groups you =
should
be able to connect directly to news.microsoft.com

--
Larry



"Tom D." <TomD@discussions.microsoft.com> wrote in message=20
news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> Hello all
> Here is my scenario...I have installed SBS 2000 into an existing =
2003 AD
> domain. The Active Directory is in 2000 native mode. I made the dumb =

> mistake
> in assuming I could install the SBS as a member server and install=20
> Exchange
> from the installation binaries on Disk 3. (without the entire SBS =
package)
> All was fine until I got licensing errors as I connected more than =
10=20
> people
> to their new mailboxes.
>
> Does anyone have an intimate knowledge of SBS's licensing =
architecture? I
> figured it would be OK because there is less than 25 users and I =
should=20
> have
> 50 and used the proper installation keys that came with the =
software. It
> smells like it's the fact that it (SBS) is not the DC and the other =
DC
> contains all of the roles (licensing in particular)
>
> My initial thoughts on fixing this issue -
> -Make a backup of the MS Exchange Information Store.
> -Promote the Win2k member server (SBS 2000) to a DC.
> -Transfer all Operations roles from the other 2003 DC (2000 native =
mode)=20
> to
> the SBS.
> -Reinstall the (entire) SBS suite.
> -Restore the Exchange information store
>
> Would this reset the license database?
> Does anyone have any suggestions other than my plan..? MVP's?
> Thanks in advance.
> --
>
> Regards
> Tom
>=20


------=_NextPart_000_01FC_01C86813.5E2305C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Larry he's installing SBS =
2000</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom.&nbsp;&nbsp; Why are you installing =
a version=20
of SBS that is so old when you have an existing 2000 domain</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>At a minimum you should be installing =
SBS=20
2003.&nbsp; there is a white paper on the SBS 2003 into an existing AD=20
domain</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS -=20
MVP]<BR>-----------------------------------------------------------<BR>MV=
Ps Do=20
Not Work for Microsoft<BR>Please do not contact me directly regarding=20
issues</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Larry Struckmeyer" &lt;lstruckmeyer(at)mis-wizards(dot)com&gt; =
wrote in=20
message <A=20
=
href=3D"news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl">news:%23dw$VEEaIHA.=
2000@TK2MSFTNGP05.phx.gbl</A>...</DIV>Because=20
more eyes are watching, you may get more response in the SBS 2003=20
<BR>Newsgroup.<BR><BR>SBS public Newsgroups:<BR><BR>SBS 4.x:=20
microsoft.public.backoffice.smallbiz<BR>SBS 2000:=20
microsoft.public.backoffice.smallbiz2000<BR>SBS 2003:=20
microsoft.public.windows.server.sbs<BR><BR>if your current news server =
does=20
not carry the mentioned groups you should<BR>be able to connect =
directly to=20
news.microsoft.com<BR><BR>--<BR>Larry<BR><BR><BR><BR>"Tom D." &lt;<A=20
=
href=3D"mailto:TomD@discussions.microsoft.com">TomD@discussions.microsoft=
.com</A>&gt;=20
wrote in message <BR><A=20
=
href=3D"news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com">news:53A=
9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com</A>...<BR>&gt;=20
Hello all<BR>&gt; Here is my scenario...I have installed SBS 2000 into =
an=20
existing 2003 AD<BR>&gt; domain. The Active Directory is in 2000 =
native mode.=20
I made the dumb <BR>&gt; mistake<BR>&gt; in assuming I could install =
the SBS=20
as a member server and install <BR>&gt; Exchange<BR>&gt; from the =
installation=20
binaries on Disk 3. (without the entire SBS package)<BR>&gt; All was =
fine=20
until I got licensing errors as I connected more than 10 <BR>&gt;=20
people<BR>&gt; to their new mailboxes.<BR>&gt;<BR>&gt; Does anyone =
have an=20
intimate knowledge of SBS's licensing architecture? I<BR>&gt; figured =
it would=20
be OK because there is less than 25 users and I should <BR>&gt; =
have<BR>&gt;=20
50 and used the proper installation keys that came with the software.=20
It<BR>&gt; smells like it's the fact that it (SBS) is not the DC and =
the other=20
DC<BR>&gt; contains all of the roles (licensing in =
particular)<BR>&gt;<BR>&gt;=20
My initial thoughts on fixing this issue -<BR>&gt; -Make a backup of =
the MS=20
Exchange Information Store.<BR>&gt; -Promote the Win2k member server =
(SBS=20
2000) to a DC.<BR>&gt; -Transfer all Operations roles from the other =
2003 DC=20
(2000 native mode) <BR>&gt; to<BR>&gt; the&nbsp;&nbsp; SBS.<BR>&gt; =
-Reinstall=20
the (entire) SBS suite.<BR>&gt; -Restore the Exchange information=20
store<BR>&gt;<BR>&gt; Would this reset the license database?<BR>&gt; =
Does=20
anyone have any suggestions other than my plan..? MVP's?<BR>&gt; =
Thanks in=20
advance.<BR>&gt; --<BR>&gt;<BR>&gt; Regards<BR>&gt; Tom<BR>&gt;=20
<BR><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_01FC_01C86813.5E2305C0--


Re: SBS 2000 Licensing issues - help ! by Larry

Larry
Tue Feb 05 17:14:00 CST 2008

This is a multi-part message in MIME format.

------=_NextPart_000_02E8_01C86822.E1B03F20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I saw/see that Cris... just wanted him to get more feedback. Not many =
come here any more.

Besides, you must mean an existing 2003 Domain... :-)

Tom, imho, you should back this out and start over with SBS 2003 as Cris =
suggests.

--
Larry

"Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote =
in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
Larry he's installing SBS 2000

Tom. Why are you installing a version of SBS that is so old when you =
have an existing 2000 domain

At a minimum you should be installing SBS 2003. there is a white =
paper on the SBS 2003 into an existing AD domain

--=20
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in =
message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
Because more eyes are watching, you may get more response in the SBS =
2003=20
Newsgroup.

SBS public Newsgroups:

SBS 4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

if your current news server does not carry the mentioned groups you =
should
be able to connect directly to news.microsoft.com

--
Larry



"Tom D." <TomD@discussions.microsoft.com> wrote in message=20
news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> Hello all
> Here is my scenario...I have installed SBS 2000 into an existing =
2003 AD
> domain. The Active Directory is in 2000 native mode. I made the =
dumb=20
> mistake
> in assuming I could install the SBS as a member server and install =

> Exchange
> from the installation binaries on Disk 3. (without the entire SBS =
package)
> All was fine until I got licensing errors as I connected more than =
10=20
> people
> to their new mailboxes.
>
> Does anyone have an intimate knowledge of SBS's licensing =
architecture? I
> figured it would be OK because there is less than 25 users and I =
should=20
> have
> 50 and used the proper installation keys that came with the =
software. It
> smells like it's the fact that it (SBS) is not the DC and the =
other DC
> contains all of the roles (licensing in particular)
>
> My initial thoughts on fixing this issue -
> -Make a backup of the MS Exchange Information Store.
> -Promote the Win2k member server (SBS 2000) to a DC.
> -Transfer all Operations roles from the other 2003 DC (2000 native =
mode)=20
> to
> the SBS.
> -Reinstall the (entire) SBS suite.
> -Restore the Exchange information store
>
> Would this reset the license database?
> Does anyone have any suggestions other than my plan..? MVP's?
> Thanks in advance.
> --
>
> Regards
> Tom
>=20


------=_NextPart_000_02E8_01C86822.E1B03F20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I saw/see that Cris... just wanted him =
to get more=20
feedback.&nbsp; Not many come here any more.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Besides, you must mean an existing 2003 =

Domain...&nbsp;:-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom, imho, you should back this out and =
start over=20
with SBS 2003 as Cris suggests.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>--</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Larry</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Cris Hanna [SBS-MVP]" &lt;<A=20
=
href=3D"mailto:crisnospamhanna@cpunospamservices.net">crisnospamhanna@cpu=
nospamservices.net</A>&gt;=20
wrote in message <A=20
=
href=3D"news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl">news:uOKisWEaIHA.2268=
@TK2MSFTNGP02.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Larry he's installing SBS =
2000</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom.&nbsp;&nbsp; Why are you =
installing a version=20
of SBS that is so old when you have an existing 2000 =
domain</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>At a minimum you should be installing =
SBS=20
2003.&nbsp; there is a white paper on the SBS 2003 into an existing AD =

domain</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS -=20
=
MVP]<BR>-----------------------------------------------------------<BR>MV=
Ps Do=20
Not Work for Microsoft<BR>Please do not contact me directly regarding=20
issues</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Larry Struckmeyer" &lt;lstruckmeyer(at)mis-wizards(dot)com&gt; =
wrote=20
in message <A=20
=
href=3D"news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl">news:%23dw$VEEaIHA.=
2000@TK2MSFTNGP05.phx.gbl</A>...</DIV>Because=20
more eyes are watching, you may get more response in the SBS 2003=20
<BR>Newsgroup.<BR><BR>SBS public Newsgroups:<BR><BR>SBS 4.x:=20
microsoft.public.backoffice.smallbiz<BR>SBS 2000:=20
microsoft.public.backoffice.smallbiz2000<BR>SBS 2003:=20
microsoft.public.windows.server.sbs<BR><BR>if your current news =
server does=20
not carry the mentioned groups you should<BR>be able to connect =
directly to=20
news.microsoft.com<BR><BR>--<BR>Larry<BR><BR><BR><BR>"Tom D." &lt;<A =

=
href=3D"mailto:TomD@discussions.microsoft.com">TomD@discussions.microsoft=
.com</A>&gt;=20
wrote in message <BR><A=20
=
href=3D"news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com">news:53A=
9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com</A>...<BR>&gt;=20
Hello all<BR>&gt; Here is my scenario...I have installed SBS 2000 =
into an=20
existing 2003 AD<BR>&gt; domain. The Active Directory is in 2000 =
native=20
mode. I made the dumb <BR>&gt; mistake<BR>&gt; in assuming I could =
install=20
the SBS as a member server and install <BR>&gt; Exchange<BR>&gt; =
from the=20
installation binaries on Disk 3. (without the entire SBS =
package)<BR>&gt;=20
All was fine until I got licensing errors as I connected more than =
10=20
<BR>&gt; people<BR>&gt; to their new mailboxes.<BR>&gt;<BR>&gt; Does =
anyone=20
have an intimate knowledge of SBS's licensing architecture? =
I<BR>&gt;=20
figured it would be OK because there is less than 25 users and I =
should=20
<BR>&gt; have<BR>&gt; 50 and used the proper installation keys that =
came=20
with the software. It<BR>&gt; smells like it's the fact that it =
(SBS) is not=20
the DC and the other DC<BR>&gt; contains all of the roles (licensing =
in=20
particular)<BR>&gt;<BR>&gt; My initial thoughts on fixing this issue =

-<BR>&gt; -Make a backup of the MS Exchange Information =
Store.<BR>&gt;=20
-Promote the Win2k member server (SBS 2000) to a DC.<BR>&gt; =
-Transfer all=20
Operations roles from the other 2003 DC (2000 native mode) <BR>&gt;=20
to<BR>&gt; the&nbsp;&nbsp; SBS.<BR>&gt; -Reinstall the (entire) SBS=20
suite.<BR>&gt; -Restore the Exchange information =
store<BR>&gt;<BR>&gt; Would=20
this reset the license database?<BR>&gt; Does anyone have any =
suggestions=20
other than my plan..? MVP's?<BR>&gt; Thanks in advance.<BR>&gt;=20
--<BR>&gt;<BR>&gt; Regards<BR>&gt; Tom<BR>&gt;=20
<BR><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_02E8_01C86822.E1B03F20--


Re: SBS 2000 Licensing issues - help ! by Cris

Cris
Tue Feb 05 17:38:50 CST 2008

This is a multi-part message in MIME format.

------=_NextPart_000_0298_01C8681D.F83E4570
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

crap...I can't read either...lol
makes even less sense to install SBS 2000
All kind of headaches there

--=20
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in =
message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
I saw/see that Cris... just wanted him to get more feedback. Not many =
come here any more.

Besides, you must mean an existing 2003 Domain... :-)

Tom, imho, you should back this out and start over with SBS 2003 as =
Cris suggests.

--
Larry

"Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote =
in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
Larry he's installing SBS 2000

Tom. Why are you installing a version of SBS that is so old when =
you have an existing 2000 domain

At a minimum you should be installing SBS 2003. there is a white =
paper on the SBS 2003 into an existing AD domain

--=20
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in =
message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
Because more eyes are watching, you may get more response in the =
SBS 2003=20
Newsgroup.

SBS public Newsgroups:

SBS 4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

if your current news server does not carry the mentioned groups =
you should
be able to connect directly to news.microsoft.com

--
Larry



"Tom D." <TomD@discussions.microsoft.com> wrote in message=20
news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> Hello all
> Here is my scenario...I have installed SBS 2000 into an existing =
2003 AD
> domain. The Active Directory is in 2000 native mode. I made the =
dumb=20
> mistake
> in assuming I could install the SBS as a member server and =
install=20
> Exchange
> from the installation binaries on Disk 3. (without the entire =
SBS package)
> All was fine until I got licensing errors as I connected more =
than 10=20
> people
> to their new mailboxes.
>
> Does anyone have an intimate knowledge of SBS's licensing =
architecture? I
> figured it would be OK because there is less than 25 users and I =
should=20
> have
> 50 and used the proper installation keys that came with the =
software. It
> smells like it's the fact that it (SBS) is not the DC and the =
other DC
> contains all of the roles (licensing in particular)
>
> My initial thoughts on fixing this issue -
> -Make a backup of the MS Exchange Information Store.
> -Promote the Win2k member server (SBS 2000) to a DC.
> -Transfer all Operations roles from the other 2003 DC (2000 =
native mode)=20
> to
> the SBS.
> -Reinstall the (entire) SBS suite.
> -Restore the Exchange information store
>
> Would this reset the license database?
> Does anyone have any suggestions other than my plan..? MVP's?
> Thanks in advance.
> --
>
> Regards
> Tom
>=20


------=_NextPart_000_0298_01C8681D.F83E4570
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>crap...I can't read =
either...lol</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>makes even less sense to install SBS=20
2000</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>All kind of headaches =
there</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS -=20
MVP]<BR>-----------------------------------------------------------<BR>MV=
Ps Do=20
Not Work for Microsoft<BR>Please do not contact me directly regarding=20
issues</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Larry Struckmeyer" &lt;lstruckmeyer(at)mis-wizards(dot)com&gt; =
wrote in=20
message <A=20
=
href=3D"news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl">news:%23yVhLzEaIHA.=
3828@TK2MSFTNGP06.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I saw/see that Cris... just wanted =
him to get=20
more feedback.&nbsp; Not many come here any more.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Besides, you must mean an existing =
2003=20
Domain...&nbsp;:-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom, imho, you should back this out =
and start=20
over with SBS 2003 as Cris suggests.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>--</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Larry</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Cris Hanna [SBS-MVP]" &lt;<A=20
=
href=3D"mailto:crisnospamhanna@cpunospamservices.net">crisnospamhanna@cpu=
nospamservices.net</A>&gt;=20
wrote in message <A=20
=
href=3D"news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl">news:uOKisWEaIHA.2268=
@TK2MSFTNGP02.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Larry he's installing SBS =
2000</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tom.&nbsp;&nbsp; Why are you =
installing a=20
version of SBS that is so old when you have an existing 2000=20
domain</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>At a minimum you should be =
installing SBS=20
2003.&nbsp; there is a white paper on the SBS 2003 into an existing =
AD=20
domain</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS -=20
=
MVP]<BR>-----------------------------------------------------------<BR>MV=
Ps=20
Do Not Work for Microsoft<BR>Please do not contact me directly =
regarding=20
issues</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Larry Struckmeyer" =
&lt;lstruckmeyer(at)mis-wizards(dot)com&gt; wrote=20
in message <A=20
=
href=3D"news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl">news:%23dw$VEEaIHA.=
2000@TK2MSFTNGP05.phx.gbl</A>...</DIV>Because=20
more eyes are watching, you may get more response in the SBS 2003=20
<BR>Newsgroup.<BR><BR>SBS public Newsgroups:<BR><BR>SBS 4.x:=20
microsoft.public.backoffice.smallbiz<BR>SBS 2000:=20
microsoft.public.backoffice.smallbiz2000<BR>SBS 2003:=20
microsoft.public.windows.server.sbs<BR><BR>if your current news =
server=20
does not carry the mentioned groups you should<BR>be able to =
connect=20
directly to =
news.microsoft.com<BR><BR>--<BR>Larry<BR><BR><BR><BR>"Tom D."=20
&lt;<A=20
=
href=3D"mailto:TomD@discussions.microsoft.com">TomD@discussions.microsoft=
.com</A>&gt;=20
wrote in message <BR><A=20
=
href=3D"news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com">news:53A=
9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com</A>...<BR>&gt;=20
Hello all<BR>&gt; Here is my scenario...I have installed SBS 2000 =
into an=20
existing 2003 AD<BR>&gt; domain. The Active Directory is in 2000 =
native=20
mode. I made the dumb <BR>&gt; mistake<BR>&gt; in assuming I could =
install=20
the SBS as a member server and install <BR>&gt; Exchange<BR>&gt; =
from the=20
installation binaries on Disk 3. (without the entire SBS =
package)<BR>&gt;=20
All was fine until I got licensing errors as I connected more than =
10=20
<BR>&gt; people<BR>&gt; to their new mailboxes.<BR>&gt;<BR>&gt; =
Does=20
anyone have an intimate knowledge of SBS's licensing architecture? =

I<BR>&gt; figured it would be OK because there is less than 25 =
users and I=20
should <BR>&gt; have<BR>&gt; 50 and used the proper installation =
keys that=20
came with the software. It<BR>&gt; smells like it's the fact that =
it (SBS)=20
is not the DC and the other DC<BR>&gt; contains all of the roles=20
(licensing in particular)<BR>&gt;<BR>&gt; My initial thoughts on =
fixing=20
this issue -<BR>&gt; -Make a backup of the MS Exchange Information =

Store.<BR>&gt; -Promote the Win2k member server (SBS 2000) to a=20
DC.<BR>&gt; -Transfer all Operations roles from the other 2003 DC =
(2000=20
native mode) <BR>&gt; to<BR>&gt; the&nbsp;&nbsp; SBS.<BR>&gt; =
-Reinstall=20
the (entire) SBS suite.<BR>&gt; -Restore the Exchange information=20
store<BR>&gt;<BR>&gt; Would this reset the license =
database?<BR>&gt; Does=20
anyone have any suggestions other than my plan..? MVP's?<BR>&gt; =
Thanks in=20
advance.<BR>&gt; --<BR>&gt;<BR>&gt; Regards<BR>&gt; Tom<BR>&gt;=20
<BR><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0298_01C8681D.F83E4570--


Re: SBS 2000 Licensing issues - help ! by TomD

TomD
Tue Feb 05 17:50:02 CST 2008

Thanks guys.
We currently own 2000 SBS. I understand in a perfect situation 2003 SBS
would be great. Please understand that the AD Domain is at 2000 native mode.
We simply want to take advantage of the fact that we own the software and
want to use Exchange.
Why are there so many 'headaches' ? There should be no interoperability
issues with the AD mode at 2000.
Please elaborate on the headaches, I think I must be missing something.
Your responses are most appreciated.
Thanks!!
--
Tom

"Cris Hanna [SBS-MVP]" wrote:

> crap...I can't read either...lol
> makes even less sense to install SBS 2000
> All kind of headaches there
>
> --
> Cris Hanna [SBS - MVP]
> -----------------------------------------------------------
> MVPs Do Not Work for Microsoft
> Please do not contact me directly regarding issues
> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
> I saw/see that Cris... just wanted him to get more feedback. Not many come here any more.
>
> Besides, you must mean an existing 2003 Domain... :-)
>
> Tom, imho, you should back this out and start over with SBS 2003 as Cris suggests.
>
> --
> Larry
>
> "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
> Larry he's installing SBS 2000
>
> Tom. Why are you installing a version of SBS that is so old when you have an existing 2000 domain
>
> At a minimum you should be installing SBS 2003. there is a white paper on the SBS 2003 into an existing AD domain
>
> --
> Cris Hanna [SBS - MVP]
> -----------------------------------------------------------
> MVPs Do Not Work for Microsoft
> Please do not contact me directly regarding issues
> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
> Because more eyes are watching, you may get more response in the SBS 2003
> Newsgroup.
>
> SBS public Newsgroups:
>
> SBS 4.x: microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
> if your current news server does not carry the mentioned groups you should
> be able to connect directly to news.microsoft.com
>
> --
> Larry
>
>
>
> "Tom D." <TomD@discussions.microsoft.com> wrote in message
> news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> > Hello all
> > Here is my scenario...I have installed SBS 2000 into an existing 2003 AD
> > domain. The Active Directory is in 2000 native mode. I made the dumb
> > mistake
> > in assuming I could install the SBS as a member server and install
> > Exchange
> > from the installation binaries on Disk 3. (without the entire SBS package)
> > All was fine until I got licensing errors as I connected more than 10
> > people
> > to their new mailboxes.
> >
> > Does anyone have an intimate knowledge of SBS's licensing architecture? I
> > figured it would be OK because there is less than 25 users and I should
> > have
> > 50 and used the proper installation keys that came with the software. It
> > smells like it's the fact that it (SBS) is not the DC and the other DC
> > contains all of the roles (licensing in particular)
> >
> > My initial thoughts on fixing this issue -
> > -Make a backup of the MS Exchange Information Store.
> > -Promote the Win2k member server (SBS 2000) to a DC.
> > -Transfer all Operations roles from the other 2003 DC (2000 native mode)
> > to
> > the SBS.
> > -Reinstall the (entire) SBS suite.
> > -Restore the Exchange information store
> >
> > Would this reset the license database?
> > Does anyone have any suggestions other than my plan..? MVP's?
> > Thanks in advance.
> > --
> >
> > Regards
> > Tom
> >
>
>

Re: SBS 2000 Licensing issues - help ! by TomD

TomD
Tue Feb 05 17:51:28 CST 2008

One more question...
Is there an issue to installing SBS 2000 into a existing AD domain opposed
to installing 2003 SBS into an existing AD domain?
--

Thanks
Tom

"Cris Hanna [SBS-MVP]" wrote:

> crap...I can't read either...lol
> makes even less sense to install SBS 2000
> All kind of headaches there
>
> --
> Cris Hanna [SBS - MVP]
> -----------------------------------------------------------
> MVPs Do Not Work for Microsoft
> Please do not contact me directly regarding issues
> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
> I saw/see that Cris... just wanted him to get more feedback. Not many come here any more.
>
> Besides, you must mean an existing 2003 Domain... :-)
>
> Tom, imho, you should back this out and start over with SBS 2003 as Cris suggests.
>
> --
> Larry
>
> "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
> Larry he's installing SBS 2000
>
> Tom. Why are you installing a version of SBS that is so old when you have an existing 2000 domain
>
> At a minimum you should be installing SBS 2003. there is a white paper on the SBS 2003 into an existing AD domain
>
> --
> Cris Hanna [SBS - MVP]
> -----------------------------------------------------------
> MVPs Do Not Work for Microsoft
> Please do not contact me directly regarding issues
> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
> Because more eyes are watching, you may get more response in the SBS 2003
> Newsgroup.
>
> SBS public Newsgroups:
>
> SBS 4.x: microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
> if your current news server does not carry the mentioned groups you should
> be able to connect directly to news.microsoft.com
>
> --
> Larry
>
>
>
> "Tom D." <TomD@discussions.microsoft.com> wrote in message
> news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> > Hello all
> > Here is my scenario...I have installed SBS 2000 into an existing 2003 AD
> > domain. The Active Directory is in 2000 native mode. I made the dumb
> > mistake
> > in assuming I could install the SBS as a member server and install
> > Exchange
> > from the installation binaries on Disk 3. (without the entire SBS package)
> > All was fine until I got licensing errors as I connected more than 10
> > people
> > to their new mailboxes.
> >
> > Does anyone have an intimate knowledge of SBS's licensing architecture? I
> > figured it would be OK because there is less than 25 users and I should
> > have
> > 50 and used the proper installation keys that came with the software. It
> > smells like it's the fact that it (SBS) is not the DC and the other DC
> > contains all of the roles (licensing in particular)
> >
> > My initial thoughts on fixing this issue -
> > -Make a backup of the MS Exchange Information Store.
> > -Promote the Win2k member server (SBS 2000) to a DC.
> > -Transfer all Operations roles from the other 2003 DC (2000 native mode)
> > to
> > the SBS.
> > -Reinstall the (entire) SBS suite.
> > -Restore the Exchange information store
> >
> > Would this reset the license database?
> > Does anyone have any suggestions other than my plan..? MVP's?
> > Thanks in advance.
> > --
> >
> > Regards
> > Tom
> >
>
>

Re: SBS 2000 Licensing issues - help ! by Larry

Larry
Tue Feb 05 19:00:18 CST 2008

This is why I suggested taking this issue to the SBS 2003 ng. I am not an
expert on the schema differences, but I am willing to bet there are enough
of them that this is more headaches than you want to take on.

OTOH, it may be easy... tweak this and that, add a bit of fairy dust, and
some everything beans and viola!

I might ask the q in the SBS 2003 ng along the lines of: I have this, I own
it, can this be done?"


--
Larry

"Tom D." <TomD@discussions.microsoft.com> wrote in message
news:A125AA16-623A-4A00-9C1F-58E10DB0E596@microsoft.com...
> One more question...
> Is there an issue to installing SBS 2000 into a existing AD domain opposed
> to installing 2003 SBS into an existing AD domain?
> --
>
> Thanks
> Tom
>
> "Cris Hanna [SBS-MVP]" wrote:
>
>> crap...I can't read either...lol
>> makes even less sense to install SBS 2000
>> All kind of headaches there
>>
>> --
>> Cris Hanna [SBS - MVP]
>> -----------------------------------------------------------
>> MVPs Do Not Work for Microsoft
>> Please do not contact me directly regarding issues
>> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
>> message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
>> I saw/see that Cris... just wanted him to get more feedback. Not many
>> come here any more.
>>
>> Besides, you must mean an existing 2003 Domain... :-)
>>
>> Tom, imho, you should back this out and start over with SBS 2003 as
>> Cris suggests.
>>
>> --
>> Larry
>>
>> "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote
>> in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
>> Larry he's installing SBS 2000
>>
>> Tom. Why are you installing a version of SBS that is so old when
>> you have an existing 2000 domain
>>
>> At a minimum you should be installing SBS 2003. there is a white
>> paper on the SBS 2003 into an existing AD domain
>>
>> --
>> Cris Hanna [SBS - MVP]
>> -----------------------------------------------------------
>> MVPs Do Not Work for Microsoft
>> Please do not contact me directly regarding issues
>> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
>> message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
>> Because more eyes are watching, you may get more response in the
>> SBS 2003
>> Newsgroup.
>>
>> SBS public Newsgroups:
>>
>> SBS 4.x: microsoft.public.backoffice.smallbiz
>> SBS 2000: microsoft.public.backoffice.smallbiz2000
>> SBS 2003: microsoft.public.windows.server.sbs
>>
>> if your current news server does not carry the mentioned groups you
>> should
>> be able to connect directly to news.microsoft.com
>>
>> --
>> Larry
>>
>>
>>
>> "Tom D." <TomD@discussions.microsoft.com> wrote in message
>> news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
>> > Hello all
>> > Here is my scenario...I have installed SBS 2000 into an existing
>> 2003 AD
>> > domain. The Active Directory is in 2000 native mode. I made the
>> dumb
>> > mistake
>> > in assuming I could install the SBS as a member server and
>> install
>> > Exchange
>> > from the installation binaries on Disk 3. (without the entire SBS
>> package)
>> > All was fine until I got licensing errors as I connected more
>> than 10
>> > people
>> > to their new mailboxes.
>> >
>> > Does anyone have an intimate knowledge of SBS's licensing
>> architecture? I
>> > figured it would be OK because there is less than 25 users and I
>> should
>> > have
>> > 50 and used the proper installation keys that came with the
>> software. It
>> > smells like it's the fact that it (SBS) is not the DC and the
>> other DC
>> > contains all of the roles (licensing in particular)
>> >
>> > My initial thoughts on fixing this issue -
>> > -Make a backup of the MS Exchange Information Store.
>> > -Promote the Win2k member server (SBS 2000) to a DC.
>> > -Transfer all Operations roles from the other 2003 DC (2000
>> native mode)
>> > to
>> > the SBS.
>> > -Reinstall the (entire) SBS suite.
>> > -Restore the Exchange information store
>> >
>> > Would this reset the license database?
>> > Does anyone have any suggestions other than my plan..? MVP's?
>> > Thanks in advance.
>> > --
>> >
>> > Regards
>> > Tom
>> >
>>
>>



Re: SBS 2000 Licensing issues - help ! by TomD

TomD
Tue Feb 05 19:00:02 CST 2008

Forgive me if I am cross posting in the wrong group...but I was advised that
the original (SBS 2000) group may not be a good place to start a thread.
--
Regards,
Tom

"Tom D." wrote:

> One more question...
> Is there an issue to installing SBS 2000 into a existing AD domain opposed
> to installing 2003 SBS into an existing AD domain?
> --
>
> Thanks
> Tom
>
> "Cris Hanna [SBS-MVP]" wrote:
>
> > crap...I can't read either...lol
> > makes even less sense to install SBS 2000
> > All kind of headaches there
> >
> > --
> > Cris Hanna [SBS - MVP]
> > -----------------------------------------------------------
> > MVPs Do Not Work for Microsoft
> > Please do not contact me directly regarding issues
> > "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
> > I saw/see that Cris... just wanted him to get more feedback. Not many come here any more.
> >
> > Besides, you must mean an existing 2003 Domain... :-)
> >
> > Tom, imho, you should back this out and start over with SBS 2003 as Cris suggests.
> >
> > --
> > Larry
> >
> > "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
> > Larry he's installing SBS 2000
> >
> > Tom. Why are you installing a version of SBS that is so old when you have an existing 2000 domain
> >
> > At a minimum you should be installing SBS 2003. there is a white paper on the SBS 2003 into an existing AD domain
> >
> > --
> > Cris Hanna [SBS - MVP]
> > -----------------------------------------------------------
> > MVPs Do Not Work for Microsoft
> > Please do not contact me directly regarding issues
> > "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
> > Because more eyes are watching, you may get more response in the SBS 2003
> > Newsgroup.
> >
> > SBS public Newsgroups:
> >
> > SBS 4.x: microsoft.public.backoffice.smallbiz
> > SBS 2000: microsoft.public.backoffice.smallbiz2000
> > SBS 2003: microsoft.public.windows.server.sbs
> >
> > if your current news server does not carry the mentioned groups you should
> > be able to connect directly to news.microsoft.com
> >
> > --
> > Larry
> >
> >
> >
> > "Tom D." <TomD@discussions.microsoft.com> wrote in message
> > news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> > > Hello all
> > > Here is my scenario...I have installed SBS 2000 into an existing 2003 AD
> > > domain. The Active Directory is in 2000 native mode. I made the dumb
> > > mistake
> > > in assuming I could install the SBS as a member server and install
> > > Exchange
> > > from the installation binaries on Disk 3. (without the entire SBS package)
> > > All was fine until I got licensing errors as I connected more than 10
> > > people
> > > to their new mailboxes.
> > >
> > > Does anyone have an intimate knowledge of SBS's licensing architecture? I
> > > figured it would be OK because there is less than 25 users and I should
> > > have
> > > 50 and used the proper installation keys that came with the software. It
> > > smells like it's the fact that it (SBS) is not the DC and the other DC
> > > contains all of the roles (licensing in particular)
> > >
> > > My initial thoughts on fixing this issue -
> > > -Make a backup of the MS Exchange Information Store.
> > > -Promote the Win2k member server (SBS 2000) to a DC.
> > > -Transfer all Operations roles from the other 2003 DC (2000 native mode)
> > > to
> > > the SBS.
> > > -Reinstall the (entire) SBS suite.
> > > -Restore the Exchange information store
> > >
> > > Would this reset the license database?
> > > Does anyone have any suggestions other than my plan..? MVP's?
> > > Thanks in advance.
> > > --
> > >
> > > Regards
> > > Tom
> > >
> >
> >

Re: SBS 2000 Licensing issues - help ! by TomD

TomD
Tue Feb 05 20:10:00 CST 2008

Thanks Larry. I don't think the Schema mods will have too much impact. Keep
in mind this is a 2000 native domain, regardless that the Windows 2003 DC is
running 2003, the version of the Directory is 2000 native. I am still trying
to understand the other responses regarding 'issues or problems' with the
version I am running. When a 2003 domain controller is running in the 2000
native mode it is conforming to the way a SBS 2000 DC would present it's
schema. Hoping someone will really shed some light into this.
--
Thanks Bud
Tom

"Larry Struckmeyer" wrote:

> This is why I suggested taking this issue to the SBS 2003 ng. I am not an
> expert on the schema differences, but I am willing to bet there are enough
> of them that this is more headaches than you want to take on.
>
> OTOH, it may be easy... tweak this and that, add a bit of fairy dust, and
> some everything beans and viola!
>
> I might ask the q in the SBS 2003 ng along the lines of: I have this, I own
> it, can this be done?"
>
>
> --
> Larry
>
> "Tom D." <TomD@discussions.microsoft.com> wrote in message
> news:A125AA16-623A-4A00-9C1F-58E10DB0E596@microsoft.com...
> > One more question...
> > Is there an issue to installing SBS 2000 into a existing AD domain opposed
> > to installing 2003 SBS into an existing AD domain?
> > --
> >
> > Thanks
> > Tom
> >
> > "Cris Hanna [SBS-MVP]" wrote:
> >
> >> crap...I can't read either...lol
> >> makes even less sense to install SBS 2000
> >> All kind of headaches there
> >>
> >> --
> >> Cris Hanna [SBS - MVP]
> >> -----------------------------------------------------------
> >> MVPs Do Not Work for Microsoft
> >> Please do not contact me directly regarding issues
> >> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
> >> message news:%23yVhLzEaIHA.3828@TK2MSFTNGP06.phx.gbl...
> >> I saw/see that Cris... just wanted him to get more feedback. Not many
> >> come here any more.
> >>
> >> Besides, you must mean an existing 2003 Domain... :-)
> >>
> >> Tom, imho, you should back this out and start over with SBS 2003 as
> >> Cris suggests.
> >>
> >> --
> >> Larry
> >>
> >> "Cris Hanna [SBS-MVP]" <crisnospamhanna@cpunospamservices.net> wrote
> >> in message news:uOKisWEaIHA.2268@TK2MSFTNGP02.phx.gbl...
> >> Larry he's installing SBS 2000
> >>
> >> Tom. Why are you installing a version of SBS that is so old when
> >> you have an existing 2000 domain
> >>
> >> At a minimum you should be installing SBS 2003. there is a white
> >> paper on the SBS 2003 into an existing AD domain
> >>
> >> --
> >> Cris Hanna [SBS - MVP]
> >> -----------------------------------------------------------
> >> MVPs Do Not Work for Microsoft
> >> Please do not contact me directly regarding issues
> >> "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in
> >> message news:%23dw$VEEaIHA.2000@TK2MSFTNGP05.phx.gbl...
> >> Because more eyes are watching, you may get more response in the
> >> SBS 2003
> >> Newsgroup.
> >>
> >> SBS public Newsgroups:
> >>
> >> SBS 4.x: microsoft.public.backoffice.smallbiz
> >> SBS 2000: microsoft.public.backoffice.smallbiz2000
> >> SBS 2003: microsoft.public.windows.server.sbs
> >>
> >> if your current news server does not carry the mentioned groups you
> >> should
> >> be able to connect directly to news.microsoft.com
> >>
> >> --
> >> Larry
> >>
> >>
> >>
> >> "Tom D." <TomD@discussions.microsoft.com> wrote in message
> >> news:53A9226C-5B6E-434E-8DB1-736FE0A27713@microsoft.com...
> >> > Hello all
> >> > Here is my scenario...I have installed SBS 2000 into an existing
> >> 2003 AD
> >> > domain. The Active Directory is in 2000 native mode. I made the
> >> dumb
> >> > mistake
> >> > in assuming I could install the SBS as a member server and
> >> install
> >> > Exchange
> >> > from the installation binaries on Disk 3. (without the entire SBS
> >> package)
> >> > All was fine until I got licensing errors as I connected more
> >> than 10
> >> > people
> >> > to their new mailboxes.
> >> >
> >> > Does anyone have an intimate knowledge of SBS's licensing
> >> architecture? I
> >> > figured it would be OK because there is less than 25 users and I
> >> should
> >> > have
> >> > 50 and used the proper installation keys that came with the
> >> software. It
> >> > smells like it's the fact that it (SBS) is not the DC and the
> >> other DC
> >> > contains all of the roles (licensing in particular)