Re: Secondary Sites
- From: "Cathy Moya [MS]" <camoya@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Jul 2007 08:55:53 -0700
The answer is always, It Depends. If you are crossing a slow WAN link, IDo I need secondary sites?
would generally recommend creating an additional site, either primary or
secondary, to manage your bandwidth. However, I have seen networks where
there were only 3-4 clients in a remote location, they had no domain
controller, they weren't running SMS features that would consume huge
amounts of bandwidth except for the occasional large software package, and
they were fine being part of a site that was across the WAN link. If you are
not crossing a slow WAN link, then it is more of an
administrative/political/organizational question and I don't know enough
about your organization to make a recommendation. (Though I will add, if you
cannot cleanly separate the two sites by boundaries, don't create the
additional sites. Having overlapping boundaries is NOT recommended.)
Can the advanced client talk to the existing primary site server ifYes. If you install secondary sites, you cannot assign clients to them. When
installed on the new PC's being added to the forest?
you configure the site boundaries, you configure the primary site boundaries
and then you configure the secondary site boundaries (and hopefully they do
not overlap.) The parent automatically knows that the child secondary exists
and has its own boundaries. The advanced clients in the secondary site will
assign to the parent primary, never to the child secondary, but it all just
works.
Will the secondary site help me organize the PC's for software rollouts?I'm not sure what you mean by "help you organize" the PCs. Secondary sites
help manage bandwidth. The advanced clients in that secondary site are
considered to be roaming in the secondary site (because they are assigned to
primary site) but it's OK. They try to get the packages from a distribution
point in their resident site (the site who's boundaries they are in, meaning
the secondary site). If they can't get the package there because it doesn't
exist, they can do fallback to their assigned site (the parent primary) and
install the package from there, though I wouldn't want that to happen if it
was across the slow WAN link. I would make sure the package exists at the
secondary. If all you want to do is group certain computers together, and
you don't have to cross a slow WAN link, then you could group computers
using collections and organize them that way.
--
Cathy Moya, CISSP, MCSE: Security
Technical Writer, Management & Solutions Division User Assistance
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided AS IS with no warranties and confers no rights.
"mshill2" <mshill2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BFB9E82F-39B1-4AEB-A7C6-10C567844B2C@xxxxxxxxxxxxxxxx
Thanks for the follow up. So... I don't have to create secondary sites?
With my network configuration as discribed, installing the advanced client
on
the pc's being added to the site will they then start to commuicate with
primary site server? Or, for organization.... Adding two secondary sites
would be a better choice. I guess I am confused on the secondary site
configuration.
Couple of questions...
Do I need secondary sites?
Can the advanced client talk to the existing primary site server if
installed on the new PC's being added to the forest?
Will the secondary site help me organize the PC's for software rollouts?
"Cathy Moya [MS]" wrote:
Generally you create additional sites (primary or secondary) because you
have to cross a slow link or because you have different business or
technical requirements, or because you need to have different language.
If
you get REALLY big sites, you might want to divide them for performance
reasons, but you're talking tens of thousands of clients, not just the
1000
you mention. Your SMS sites do not have to have any correlation at all to
your domains. If anything, your SMS sites tend to correlate with your
Active
Directory sites, not your AD domains.
You mention that you have a child domain within your LAN. Do you need to
manage that separately for some reason? Maybe the parent domain needs to
use
remote tools but the child domain doesn't, or vice versa. Maybe you want
to
collect inventory more frequently at the child domain than at the parent.
In
those cases, it would make sense to create a separate SMS site. But if
you
will manage them the same, they child domain could be part of the
existing
SMS site.
Whether you make the addtional site a primary or a secondary depends on
how
you want to manage the other site. Secondary sites dont' require an
additional server license, and don't require their own SQL server, so
that's
fiscal happiness. On the other hand, for that child domain within your
LAN,
it is possible for you to create it as a primary site and keep it's
database
on the same SQL server that hosts the current SMS site database. (You
just
can't put the SMS Provider for two different sites on the same database,
so
one Provider would have to be installed on the site server.)
That's why Kim gave you the standard answer: It depends. Depends on what
your goals are.
--
Cathy Moya, CISSP, MCSE: Security
Technical Writer, Management & Solutions Division User Assistance
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided AS IS with no warranties and confers no rights.
"mshill2" <mshill2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:310C7F7B-543A-4CBA-B40A-0FC270052143@xxxxxxxxxxxxxxxx
Bandwidth should not be an issue. One child domain will be within my
LAN
and
the other has a 6mb MPLS circuit. Total client count for all locations
will
be in the neighborhood of 1000. IT support will be local at each
location.
Not sure how to comment on the last part of your question "same general
settings possible". Thanks for your response.
"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:
mshill2 wrote:
What would you like to know?Bandwidth available, number of clients, it personnel present, same
"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:
mshill2 wrote:
I have a primary site and 2 child domains coming in the nearWhether it is the right direction is difficult to tell without more
future.
Is
adding the child domains as secondary sites the right direction?
If
so, will
I have to install SMS 2003 on a member server of the child domain?
Or... will
advanced client talk across the domains? This is a single forrest
AD
domain.
Thanks for any input.
technical information. But it is definitely technically feasible.
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
general settings possible?
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
.
- References:
- Re: Secondary Sites
- From: Kim Oppalfens [MVP]
- Re: Secondary Sites
- From: Kim Oppalfens [MVP]
- Re: Secondary Sites
- From: Cathy Moya [MS]
- Re: Secondary Sites
- From: mshill2
- Re: Secondary Sites
- Prev by Date: Re: HELP!! SMS clients not assigning
- Next by Date: Re: firewall ports
- Previous by thread: Re: Secondary Sites
- Next by thread: Re: Propagated objects
- Index(es):
Relevant Pages
|
