Re: Client push question - the plot thickens
- From: "Jeff Gilbert [MSFT]" <jeff.gilbert@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Feb 2007 22:21:16 -0800
OK I'll give this a shot Peter :-)
The executive summary here is: I believe they (PSS and Kim) are both right
:-) The difference here (I think) is in what we mean by client
push--enabling the site-wide setting for the client push installation method
or using the client push installation wizard to install clients.
Getting the client installed via the site-wide client push option requires
(very high level summary here) a Discovery Data Record (DDR) created by a
discovery method, and a Client Configuration Request (CCR) generated by the
site server for the discovered resource. CCR's are only created for systems
discovered that are (a.) within the site's boundaries (not roaming
boundaries as Thomas noted) and (b.) the discovered resource matches the
criteria you've set in the client push installation properties. Once a CCR
is processed by the site Client Configuration Manager (CCM) component, the
client installation process is initiated. I've tried to summarize this using
two scenarios:
1. Discovery and client push IS NOT enabled at the secondary site
2. Discovery and client push IS enabled at the secondary site
1. Discovery and client push IS NOT enabled at the secondary site. If a
resource is within the boundaries of a secondary site, how is it installed
using the site-wide client push installation method (when discovery and
client push at the secondary site IS NOT enabled).
So, Step 1 (DDR creation). If you have enabled a discovery method at the
primary site that discovers a resource within a secondary site's defined
boundary, the primary site will create a DDR for the resource. Because the
resource is not within the primary site's defined site boundaries no CCR
will be created (client will not be installed). The DDR created will be
stored in the database until it is deleted by the "delete aged discovery
data" maintenance task.
Here's where it get interesting.
Step 2 (CCR creation). If you use the Client Push Installation Wizard to
push the client out to discovered resources--AND uncheck the "Include only
clients assigned to this site" check box, a CCR for the DDRs for
non-assigned resources in the database will be created and an attempt will
be made to get the client installed on them. Once installed, the client will
be assigned to the primary site and report up via the secondary site's proxy
management point--if one exists at the secondary site.
2. Discovery and client push IS enabled at the secondary site. If a resource
is at a secondary site, how is it installed using the site-wide client push
installation method (when discovery and client push at the secondary site IS
enabled).
Step 1 (DDR creation). The discovery method at the secondary site discovers
a resource and creates a DDR (forwards to primary site to store in the site
database).
Step 2 (CCR creation). The secondary site sees that a discovered resource is
within its boundaries (and meets the defined site wide client push
installation properties) and creates a CCR for the resource itself (CCR's do
not travel up the hierarchy). At this point, CCM at the secondary site will
begin the client installation process by checking for a management point to
push the source files to the resource to get the client installed. If the
secondary site has a proxy management point the client install files will be
pushed from there, otherwise, the site's default management point will be
where the source files come from.
Either way, once CCM begins processing the CCR for a resource, it will
attempt to install the client once an hour for about 168hrs (one week)
before giving up.
Hope this helps clarify the process!
--
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation
This posting is provided "AS IS" with no warranties and confers no rights.
"Peter Lillington" <NospamTemp014@xxxxxxxxxxxxx> wrote in message
news:58ACE41E-53E1-4260-989B-E3BCC58E6DB3@xxxxxxxxxxxxxxxx
Thank you for that information Thomas.
The confusion seems to be with adv clients at sec sites - in particular
whether the sec site server will install these clients (which before they
are
installed will be assigned to the sec site, but after installation will be
assigned to the prim site).
I've heard so many things that I'm going to have to take the plunge and
setup a scratch lab to prove this one way or another. I'll post the
results
here hopefully to help somebody in the future.
Peter
"Thomas Lasswell" wrote:
The answers from Microsoft are correct. If you enable client push only
clients assigned to that site will be installed. This is determined by
the
site boundries (not the roaming boundries). Therefore, site boundries
defined
on the primary site will install only clients that are assigned to that
site.
The secondary site will also have to have this turned on because your
clients
are only assigned to the secondary site.
I'm not exactly thrilled by the fact that SMS only uses the site
boundries
and not the roaming boundries as well to determine assigned status,
however
this is the nature of SMS.
Hope this was helpful,
Thomas Lasswell
www.techcolumnist.com
"Peter Lillington" wrote:
This is the third look at the same question (see Client push questions
over
the last two days), and this time I have new information. The two
questions
I originally asked (with answers given) are below.
2) Enabling AD Discovery and Client Push Installation for theNope, enabling client push will push the client to all clients assigned
primary site
will result in only those clients within that site boundaries being
installed? I.e., computers at secondary sites will not get
installed?
to
that site. (Secondary site clients are assigned to that site as well,
but
aren't part of the site's boundaries)
3) Enabling AD discovery and Client Push Installation at a secondaryUnfortunately not, that is how we would like it to work.
site
will result in clients within the site boundary being installed, and
(in
our case) assigned to the primary site.
http://blogs.msdn.com/smsperfguy/archive/2004/05/13/131528.aspx
This blog post explains the issue in detail.
So, M$ did some tests and gave me the resulting logs. What they show
is
that regarding question 2) is that enabling AD discovery and Client
Push at a
primary site does not install clients at secondary sites. That is to
say,
the answer given was correct in a sense (only assigned clients get
installed), but at the time of discovery the primary site does not
recognise
the secondary clients as assigned and therefore does not install them.
Therefore, in reality only the clients in the primary site get
installed.
Regarding question 3) - enabling client push at secondary sites does
result
in advanced clients at the secondary site getting installed, according
to the
logs I was sent. I.e., the answer given was incorrect.
I'm descending deeper and deeper into confusion, as about 50% of people
are
telling me one thing and 50% are telling me another. Would anybody
else like
to chip in here?
Looks like a scratch lab setup coming up......
.
- Follow-Ups:
- Re: Client push question - the plot thickens
- From: Peter Lillington
- Re: Client push question - the plot thickens
- References:
- RE: Client push question - the plot thickens
- From: Peter Lillington
- RE: Client push question - the plot thickens
- Prev by Date: RE: Client push question - the plot thickens
- Next by Date: Advertisement
- Previous by thread: RE: Client push question - the plot thickens
- Next by thread: Re: Client push question - the plot thickens
- Index(es):
Relevant Pages
|
