Re: Client Push Question - MVP Kim vs Microsoft ?!
- From: "Kim Oppalfens" <Kim Oppalfens <MVP>>
- Date: Fri, 9 Mar 2007 20:57:08 +0100
My ex-training colleagues referred to me as sms-knowledgeable because I am more often right then wrong when sms is concerned.(51% right, is more right than wrong).
They usually added that this the only domain where this was true :-).
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
"John Trask" <JohnTrask@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F3C975AA-44AA-47A4-9060-20CB14904E61@xxxxxxxxxxxxxxxx
My money is on Kim.
I have a primary site and 12 secondary sites. I'm out of the office, so I
can't double check (I could but I'm too lazy), but I believe when I setup a
secondary site, I install SMS, configure the site server to be a management
point, and make sure the distribution point is using BITS. Other than this,
I don't configure any other site settings and things work wonderfully.
"Peter Lillington" wrote:
Yesterday I posted a question regarding client push that Kim Oppalfens was
kind enough to answer. I've copied out the thread at the bototm of this post.
At the same time I had a call in to Microsoft regarding the same problem.
Now, they say that Kim is wrong regarding both question 2. and 3.
I.e., that regarding 2. only clients within the primary site boundary will
get installed - secondary clients will not get installed even if they are
assigned because they are not within the primary site boundaries, and
regarding 3) that enabling both discovery and client push on secondaries will
result in the advanced clients getting installed at the secondaries.
Case# is SRZ070213002848.
Exactly who do I beleive? On one hand I have a MVP and a good blog entry.
On the other hand I have an official M$ answer plus a KB article 925282 that
under the section "SMS Advanced Clients are not installed on secondary sites"
tells me "Make sure that the Advanced Client Push Installation method is
turned on at the secondary site. Additionally, make sure that the necessary
discovery methods are enabled at the site."
Any more help would be very very appreciated!
Thanks,
Peter
Hum, I think you missed on 3 out of 4.
Inline.
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP
"Peter Lillington" <NospamTemp014@xxxxxxxxxxxxx> wrote in message
news:2DCFC81D-B1FE-49F4-9024-3758D101B574@xxxxxxxxxxxxxxxx
> Hi, I'm designing a new SMS 2003 R2 infrastructure. We are going to go
> with
> a single primary site / multiple secondary site topology. We will be
> using
> client push installation to get the clients installed. Only Advanced
> clients
> will be installed.
>
> I *think* I understand how this should work, but I would be grateful > for
> any
> clarifications to my understanding:
>
> 1) AD system discovery finds records in AD, cross-references them with
> DNS,
> and if they are within the site boundaries pings them before creating a
> DDR?
> Therefore, each site will only discover the computers that are actually
> within the site?
The cross-reference with dns is correct, will more or less correct sms tries
to resolve the name to an ip it couldn't care less whether it does this
through wins, broadcast, host, lmhost or dns. The ping thing never happens,
hence all systems that have a dns entry are discovered.
>
> 2) Enabling AD Discovery and Client Push Installation for the primary
> site
> will result in only those clients within that site boundaries being
> installed? I.e., computers at secondary sites will not get installed?
Nope, enabling client push will push the client to all clients assigned 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 secondary > site
> will result in clients within the site boundary being installed, and > (in
> our
> case) assigned to the primary site.
Unfortunately not, that is how we would like it to work.
http://blogs.msdn.com/smsperfguy/archive/2004/05/13/131528.aspx
This blog post explains the issue in detail.
>
> 4) In our case, client agent settings only need definining at the > Primary
> site?
Correct.
>
> Thanks,
>
> Peter
>
>
Thank you for the information - I thought something was off. Now I remember
that SMS is just weird in how it does stuff....
Just one point to clarify: Even though a secondary site computer is not
within the primary sites boundaries, it will still be installed by the
primary site Client Push because it is assigned to the primary site? I
thought, perhaps incorrectly, that the assignation only happened after the
client was installed (particularly as before the client is installed we do
not know whether we are installing legacy or advanced, as such the client
could be assigned to either prim or sec).
Hmm, one other q - I note in that link you posted it is possible to do a
focused AD discovery for resources within the primary boundaries only. How
can this be achieved?
Thanks again,
Peter
.
- Prev by Date: Re: SMS Distribution point
- Next by Date: Re: Client Push Question - MVP Kim vs Microsoft ?!
- Previous by thread: Re: SMS Distribution point
- Next by thread: Re: Client Push Question - MVP Kim vs Microsoft ?!
- Index(es):
Relevant Pages
|
Loading
