Re: Two server in one domain
- From: "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com>
- Date: Tue, 21 Aug 2007 20:40:47 -0400
Hi Skippy:
The scenario SG describes as 1) A DC in each office, is further complicated
if there are more than 2 offices. With two, there are a total of 2 servers,
one in each office. With 6 offices there is likely to be a total of 7
servers, one for each office and one for the TS,which you will find out you
need at some point.
With TS, there remains a total of 2 servers so long as you stay in the
dominion of SBS, that is, under 75 licenses/connections.
OTOH, I have had a couple of sites where the IT contact claimed that his
users were incapable of opening and using a TS session because it meant they
had to "switch" between the "real desktop" and the TS. Either those
companies have the wrong employees or the wrong IT contact. :-)
Larry
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:O1ZGamD5HHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
inline
"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BB9B4E64-3D93-4480-89F6-82F4833D287E@xxxxxxxxxxxxxxxx
I have two site or location (Wide Area Network), thats why I installed two
servers. If Primary Domain Controller is installed with Win SBS 2003
(site
A), and the other site (site B) installed with Windows 2003 standart,
with my
assumption:
1. Only buying cal lisence in Win SBS 2003 (site A)
2. User in site B, i registered in Win SBS 2003
My question is:
1. Can user in site A login in site B (vica versa)?
yes, it is one AD, users can log in anywhere in the AD (assuming you cater
for machine setup to allow this)
2. Can User in site B have the same service like user site A
(exchange,sql,isa server etc)? Because in site B only have server Windows
2003 standart.
You need some sort of link (VPN, private network) between the sites to
allow communication between the servers, this also allows other service to
be accessed, but you may want to look at different setups.
I've done it both ways.
1) The second DC at the remote site. This allows for logon to the domain
even if the link between the sites is down. If there is a clear
distinction of files accessed betwen the sites you can also use this as
'local' storage for siteB. SiteB users can still access siteA, and vice
versa, file storage (if the link is up) but the speed of access depends on
the link. You could also possibly use DFS to share documents between the
sites.
2) The 2nd server is not a DC but a TS located at HQ. You optionally have
VPN/PN between the sites, allowing remote machines to be members of the AD
but remote users work mainly in TS. The private link is optional because
in theory the remote machines do not need to be members of the domain and
could access TS either as a published service or through RWW. This has
advantages in that fie access between the user session and SBS happens at
HQ network speed, and all data remains at HQ. The main problem would be
that the remote user must be able to establish a connection to the TS in
order to work, HQ internet must be up and the remote user must have
internet.
Originally I would do 1) but these days I prefer 2). Even in AU internet
is reasonably reliable so I can assume the connection between the sites is
possible (NOTE: Lack of comms can impact both scenarios). There is another
issue that applications must work under TS, some apps are fully supported
in TS, some apps work but operation under TS is not 'supported', some apps
will not install on TS.
The addition of a TS at HQ also has other uses, senior staff working from
home and/or while travelling. Lessened administration, particularly if you
swing the whole operation to TS, possibly allowing for just two members of
the AD, SBS + TS, and everyone else uses dumb terminals (thin PC's).
Thankyou for your help before.
"SuperGumby [SBS MVP]" wrote:
one of the base restrictions of SBS is 'one SBS per AD', there is no way
around this restriction.
"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EE8F6F7B-1917-4A9C-B204-269BB4F11440@xxxxxxxxxxxxxxxx
Unfortunately, I have buy couple of Win SBS 2003. What I have to do
now?
Can
I use it? :-(
I've planning use it to three server in my network...badly...:-(
"Montreal MCT" wrote:
Hi Skippy,
There is no problem with having multiple servers in an SBS domain,
though
there are a number of caveats to that:
1. You can only have a single SBS box on the network. All other
servers
should run Windows Server 2003 Standard.
2. The SBS box must be the (primary) domain controller.
3. The SBS box must hold the five Operations Master roles (commonly
refered
to as FSMO roles).
Aside from that you can go nuts... have fun!
M
--
Mitch Garvis, MCT
MCSA, MCITP, MCDST, MCTS
Microsoft MVP: Windows Server - Customer Experience
Visit my blog at http://blog.mitchgarvis.com
---
"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D153CFBF-D5B6-4B67-B3D2-761335A65ECA@xxxxxxxxxxxxxxxx
I have two server in one domain with windows advance server 2000
system
running on it. We decide to change our network operating system to
Windows
SBS 2003. My question is:
1. Can I change thats situation (2 server in one domain) to windows
SBS
2003?
2. How many server can grouping in one domain in Windows SBS 2003?
Thanks for your appreciate, sorry for my English.
.
- References:
- Re: Two server in one domain
- From: Montreal MCT
- Re: Two server in one domain
- From: SuperGumby [SBS MVP]
- Re: Two server in one domain
- From: skippy
- Re: Two server in one domain
- From: SuperGumby [SBS MVP]
- Re: Two server in one domain
- Prev by Date: Re: SBS2003 R2 / Wireless
- Next by Date: Re: Alternative to LCS in a SBS2003 Environment
- Previous by thread: Re: Two server in one domain
- Next by thread: Re: Two server in one domain
- Index(es):
Relevant Pages
|
