In news:C1640304.4DC%(E-Mail Removed),
Altair Brito <(E-Mail Removed)> typed:
> Hello.
>
> I looked at your other reply thus the reason why I posted the
> step-by-step procedure of what I was planning on doing.
But you didn't post it as a reply in that thread, which is what I'd asked.
:-) This sort of thing can get very confusing....
http://www.dts-l.org/goodpost.htm
> If there's
> another thread that you posted that I haven't seen please let me know
> where it's at because I believe I saw them all. Sorry for my
> ignorance about this, but I really appreciate your help.
OK. I'm quoting myself & your previous post below:
--------------------------------------------------
In news:C162B069.137%(E-Mail Removed),
Altair Brito <(E-Mail Removed)> typed:
> Hi.
>
> I have a network with 3 servers. 2 SBS
You can't do that, sorry....
> and 1 Enterprise. The Entp.
> Server is the domain controller. One of the SBS servers is an
> Exchange 2003 server and the other one is just for storage.
>
> This message: "the server SERVERNAME doesn't meet the licensing
> requirements. SERVERNAMER will shutdown in 60mn"... 30mn... Off.
>
> How do I find out what license it is referring to and/or how do I go
> about fixing this problem.
>
> Thanks in advance,
> Altair
Sounds like you bought the wrong products - if you wanted SBS, you'd have
had to install it either *first* - or properly installed it into your
existing AD domain as per
http://support.microsoft.com/kb/884453. But you
can have only one SBS box in the domain, and if you have one of these in use
'just for storage' you'd probably have been better off buying a NAS box for
that.
<snip>
>>> So this is what I understand and am planning on doing:
>>>
>>> -Only one of the SBS Servers can remain on the network (the
>>> Exchange Server):
What's the reason you've got SBS in this picture at all, btw?
> I will install Enterprise on the the Storage
>>> server that is currently SBS
OK - but just pull that box off the network for now.
>>> -This SBS server (Exchange) must be the first DC on the list
Yes. However,
>>> . So I will DCPROMO the other server (enterprise server) and
>>> . Check so that the Exchange SBS server is the first DC on
>>> the list
Well - wait. How was this SBS installed? Was it installed into the existing
domain using the method mentioned in the MS article I provided the link to?
> -Before I DCPROMO the Enterprise Servers I set ALL FSMO
>>> roles
>>> to the Exchange Server using NTDSUTIL
>>
>>> If these are not correct please indicate me on the right track. This
>>> would be a lot easier if I had a copy of Exchange Enterprise
>>> Edition.
Hmmm - I'm not sure how that's relevant!
>>>
>>> QUESTION: Being that the current Enterprise Server is the MAIN
>>> server on the network, if I DCPROMO if will this cause any
>>> problems..? If so, how would I go about fixing the issue?
It's really hard for me to see how you're going to do this, as I don't know
how you installed SBS.
I'm going to suggest that you post a brand-new message in
microsoft.public.windows.server.sbs. Be *very* concise and explain what
you've got, how it was all installed.... also mention how many
users/desktops you have, and the reason you're using SBS as well as the
other servers.
Pull back a bit and look at the desired goal. You can have SBS and
additional servers, but SBS will not play nicely in an existing domain
unless you do things right - and I would suspect that the setup was not done
right, or you wouldn't have ended up with two SBS boxes on the same domain.
Depending on the size of your user/computer base, you may actually be better
off starting over from scratch....I know that's probably not what you wanted
to hear, but it's probable.
<snip>