Re: Second server on SBS2003



You want to have a terminal server configured as a domain controller next to
the SBS server and then install the accounting software on it, right?
Normally, Terminal Servers are not configured as domain controllers, rather
they are added to the SBS network as member servers.

Deploying Windows Server 2003 Terminal Server to Host User Desktops
http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/adstrmsr.mspx

Deploying Terminal Services in a Windows Small Business Server 2003 R2
Environment
http://technet2.microsoft.com/WindowsServerSolutions/SBS/en/library/965bf1ce-c2a2-404b-a212-459ed00ac5a41033.mspx?mfr=true

--
Merv Porter [SBS-MVP]
============================

"NikkitaKMiles" <NikkitaKMiles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F727A52-282E-41BE-9BDB-410E9D1DDE9C@xxxxxxxxxxxxxxxx
Is there a document on what I wanted in the first place. I have been
going
around in circles getting people to understand that's what I want to
accomplish. Sorry.
--
Nikkita K. Miles


"NikkitaKMiles" wrote:

Merv. I am at one location. The Windows 2003 server is a remote server
at
the same location. All I am trying to do is add it to the network.
--
Nikkita K. Miles


"Merv Porter [SBS-MVP]" wrote:

Still trying to understand your goal...

So, the remote Windows 2003 will be recommissioned as a terminal server
and
remain at the remote site?

Unless there is an absolute need for a server at the remote site, or
there
isn't a reliable Internet connection, it seems like what you may want
to do
is bring the Windows 2003 server back to the SBS site and set it up as
a
terminal server next to the SBS server. Then the remote users would
access
the terminal server using RWW (Remote Web Workplace). This would keep
data
management and maintenance centralized in one location. Is this what
you
want to accomplish?

--
Merv Porter [SBS-MVP]
============================


"NikkitaKMiles" <NikkitaKMiles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:52104A23-AE41-4CF5-A38A-1820486E4254@xxxxxxxxxxxxxxxx
yes pretty much. the SBS server was here when i got here. I need to
take
there propritary account software and place it on another domain
server.
Windows 2003 server, however the exchange and printer resources are
remaining
on sbs. The clients will be using terminal services to get to the
windows
2003 server. I am attempting to get the two servers on the same
network.
--
Nikkita K. Miles


"Merv Porter [SBS-MVP]" wrote:

I think you may be swimming upstream, if I understand your
requirements.
SBS does not support trusts, so having two separate domains, one of
which
is
an SBS domain, talk to each other is not a straight forward project.

By "drop down", I presume you mean the domain field in the login
screen.
I
don't really see how this applies here.

Is this (diagram) the physical setup you have?


Workstations (DomainA)
| | | |
Switch
|
SBS Server (DomainA)
|
Router (DomainA)
||
....Internet...
||
Router (DomainB)
|
Windows 2003 Server (DomainB)
|
Switch
| | | |
Workstations (DomainB)


--
Merv Porter [SBS-MVP]
============================

"NikkitaKMiles" <NikkitaKMiles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:F84E2F4F-DCE6-4728-9103-30814D1AF2F7@xxxxxxxxxxxxxxxx
I have two domain controllers:

One is a sbs 2003 domain controller called ACCDC01
The second one is a Windows 2003 server domain controller called
SWS1.

When I attempt to add the second server to the manage server
computers
area
it gives the error of "The sbs cannot run adomain controller or a
sbs
server
computer.

All I am trying to do is have two domains that can use the same
resources
and see each other from the client's machines. In the drop down
they
would
be able to select which server they would like to connect to as
well as
the
go throught the sbs (ACCDC01) using terminal services to the
windows
2003
server (SWS1)
--
Nikkita K. Miles


"Holz" wrote:

On Mon, 11 Feb 2008 12:10:03 -0800
NikkitaKMiles <NikkitaKMiles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

It tells me that you cannot add a domain controller into sbs
domain
controller. This appears to defeat the suggestion that this
can be
done. I need two domains that see and work with each other's
resources
Two separate domains or a second domain controller? Your post is
confusing..

--
:-)










.



Relevant Pages

  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • Re: wds, how many computers can be imaged at the same time
    ... SBS itself must be the FSMO roles holder. ... you can have additional member server. ... Windows Server 2008 WDS supports multicasting. ... domain controller, ...
    (microsoft.public.windows.server.general)
  • RE: the dns service cannot open active directory
    ... SBS 2003 machine as an additional domain controller of a Windows 2000 ... The new SBS 2003 computer must be a global catalog server and must be the ... On a Windows 2000 domain, you must prepare Active Directory before you ...
    (microsoft.public.windows.server.sbs)
  • Re: Small Business Server 2003 Premium Edition automatically shuts
    ... I have had to place SBS as my internal server connecting to 'Enterprise Edition' via a hub, which is then connected to my router. ... I have been told that placing SBS on the edge of my network as a domain controller is dangerous. ...
    (microsoft.public.windows.server.general)
  • Re: Terminal services advice
    ... I emailed Andy. ... Here's a paper on implementing a Terminal Server in an SBS 2000 network. ...
    (microsoft.public.backoffice.smallbiz2000)