Re: Two server in one domain

You cannot install SBS components on anything but SBS.

Services on the SBS will only be available if the link between the offices
is up.

"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:87456F5E-FA7B-4DB8-8542-93C49976793F@xxxxxxxxxxxxxxxx
Hello SG,
Thankyou very much for your suggestion. I've succed to combine our server.
Yes, you right...this is because different version of server installation
CD.
And now I have more question,
"How I activated many service in Branch site which is running Windows
Server
Standart 2003. You know in HQ which is running Windows SBS 2003, have many
service like MSExchange, MS Share Point, MS SQL Server, etc. How I
activated
in Win Server 2003 standart?
Is it true I must installed from Cd Installation of Windows SBS 2003? How
to
installed them?
Thanks before... :-)


"SuperGumby [SBS MVP]" wrote:

sounds like that new Windows Server 2003 is R2, you need to run ADPREP
from
the 2nd (ie. NOT the 1st) CD of that set on the SBS. This 'expands' the
SBS
AD schema to accept 2003 R2 DC's.

Search for terms like 'add R2 server 2003 domain'.

SuperGumby will do fine, no Mr necessary. Friends even shorten this to
SG.

Should be a simply resolved issue, now that the details are known :-)

"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BC1EA35A-6321-4CB2-8772-9376145697ED@xxxxxxxxxxxxxxxx
Hello Mr SuperGumby,
I have a condition like this:
1. HQ with Windows SBS 2003, my branch Windows Server 2003 Standart
2. I have two different block IP, in HQ the IP is 192.168.1.0 and the
branch
is 192.168.2.0
3. In network side, there is no problem. I can ping from HQ to brach
site
and vice versa.
And I have problem :
When I setup server role in my branch office's server, in order to
connect
AD with HQ's server, I use Active Directory Installation Wizard with
this
step:
1. Choose "Additional domain controller for an existing domain"
2. Fill the user name, password and Domain from HQ server
3. Fill the domain name, with HQ domain name, so on
4. And then, when AD Installation Wizard is configuring AD, I have the
error
like this:
"The Operation failed because:
The AD Installation Wizard cannot continue because the forest is not
prepared for instaling WIndows Server 2003. Use the adprep command-line
tool
to prepare both the forest and the domain. FOr more
information........"
This is the same error when I used the same ip block for the HQ and
branch's
server or when I split it them.
Please help, why I receive the message error like this...
Thanks for your kindness...

"SuperGumby [SBS MVP]" wrote:

Skippy, troubleshooting is about details.

I have no idea what 'your condition' currently is. Is the new server
at
HQ
or remote? If remote how are the sites linked? Did you get rid of the
2nd
SBS? If you have attempted the linked procedure, at what point is it
going
wrong? What error are you getting?

Personally, if adding a 2nd server which I intended to be a DC at a
remote
site I would first bring it to HQ, join the domain and dcpromo it ,
allow
the AD to sync, shut it down, disconnect from the HQ LAN, fire it up
and
reconfigure for remote operation, ship to remote. Note that in order
to
login to the domain while disconnected, and allow local login for PC's
at
the remote, the 2nd server needs to be a GC.

"skippy" <skippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D065C8E3-07B5-43A6-8F57-9A7AA3D04F77@xxxxxxxxxxxxxxxx
I have a problem to connect those server each other
I try step by step from microsoft technical support
(http://technet2.microsoft.com/WindowsServerSolutions/SBS/en/library/bd070f5b-3b90-4496-b427-99f1ab0eca671033.mspx?mfr=true)
Is that right I used that solution if I want to connect two server
with
my
condition? Or is there any solution ? Please help....

"SuperGumby [SBS MVP]" wrote:

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.















.

Relevant Pages

  • Re: How do I reinstall setup.exe file for clients in server?
    ... Deployment on SBS to rebuild client setup application. ... We need to select "Windows Small Business Server 2003" but not ... | installation was made late September. ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Office Configuration Suggestions?
    ... The additional DC at the remote site, could not be the SBS server, as you ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Remote Desktop Problem
    ... connectivity issues in SBS Server: ... This newsgroup only focuses on SBS technical issues. ... |> this computer on the Remote tab of properties of My Computer on SBS ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot Connect via remote desktop
    ... please ensure the domain name vpn.XXX.co.uk resolve to the ... As you want to connect the SBS via VPN, I suggest you also perform the ... select Disable Routing and Remote ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)