Re: DP not function?
- From: Matthew Hudson <MatthewHudson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 20 Jan 2007 05:26:00 -0800
Yes, it suppose to be random according to MS:
"Systems Management Server (SMS) clients use existing connections from the
Client Access Points (CAPs) and Distribution Points (DPs) designated in their
site by default. If no existing connection exists, clients randomly select
from the CAP/DP list for their site. Sites are defined by local or fast
network connectivity, ensuring load balancing across all CAPs and DPs in the
site. "
I have a primary and 2 DPs serving all the computers, no boundaries or
protected areas. When pushing out a package you can watch it hit the primary
first then to the secondary DP once the primary is taking care of mulitple
computers. If you want to ensure the secondary does the work instead of the
primary the only option you have is to change the package to only look at the
secodary DP servers.
"Todd Hemsell" wrote:
" Since the Your primary is also a DP then it will go there first.".
That is not accurate.
1 -Client gets an Advertisement
2 -The client sends a content location request to the MP
3 - the MP queries the DB (contentDPmap table ) in real time to find all DP's that have that package and that are within the boundaries of the client
4 -The MP then formats that info into an xml file and returns it to the client.
Location services Orders the list of returned distribution points by
subnet distribution points,
Active Directory site distribution points,
local distribution points,
remote distribution points,
and distribution point from the client's assigned site.
Right below is what a content location reply looks like (from SDK)
ContentLocationReply is the XML returned by ISmsMessaging::Invoke in response to a ContentLocationRequest XML message.
<ContentLocationReply>
<Sites>
<Site>
<MPSite/>
<LocationRecords>
<LocationRecord>
<SMBPath>
<URL/>
<ADSite/>
<IPSubnets>
<IPSubnet/>
</IPSubnets>
<Metric/>
</LocationRecord>
</LocationRecords>
</Site>
</Sites>
</ContentLocationReply>
"Matthew Hudson" <MatthewHudson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:52705BC1-E400-4A32-ADD6-5EDDDE6BB510@xxxxxxxxxxxxxxxx
This is as it should happen. Since the Your primary is also a DP then it
will go there first. If the DP is busy then it will deny it. It will then
look for other dps it can use. Since the client is in a protected dp it will
then look at that one dp. Also check your packages to see what dps are
associated with each package. If you are pushing out say Adobe Reader and
you only want the dps to handle it then in your package shouldn't have the
primary DP listed.
"H. K." wrote:
> I had installed 1 SMS 2003 R2 primary server (SLP, MP, DP) and 5 secondary
> servers (MP, DP) in my network. All the DP has already set the protected
> boundary with different IP subnet. There is no error from the DP and the
> package can also distribute to all DP from the primary server. However when I
> make the advestisment, only the DP on the primary server report the
> advestisment status. The other DP did not report anything and suppose the
> client will get the update and package from their DP. All client seems get
> the package from the primary server's DP. Is there anything I had missed when
> setting up the DP. Please give me some suggestion.
>
> Thanks
- Prev by Date: Re: Admin Console problems
- Next by Date: OSD , Active Directory and SQL question.
- Previous by thread: Advice neeeded on the use of SMS 2003 as a replacement toolset
- Next by thread: Re: DP not function?
- Index(es):
Relevant Pages
|
