RE: Changing Assigned MP
- From: SMS Newbie in the Block <SMSNewbieintheBlock@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 20:55:23 -0800
Hi, Rob,
coolness...
Thanks for the info and clarifications
:-) Newbie
"RobM" wrote:
Your Advanced client has to be assigned to a Primary Site. A clients Assigned.
MP is the MP installed on to the site the client is assigned too. Resident MP
will be the nearest MP and in your case it's the PMP on the secondary. This
is normal behaviour. If you have the time sit through this webcast (and look
at the others related to the client)
http://go.microsoft.com/fwlink/?LinkId=25348.
Protecting your DP's ... you should protect them all to stop clients
bubbling out and using a DP outside of their network subnet or over a slow
network link. The list of DP's that a package is assigned to is given to the
client as part of the offer policy ... the client can decide to use the
first DP in the list, which isn't necessarily the closest so lock 'em down.
As for offers showing as only running on the primary ... believe this is by
design, the clients received the offer from the primary via the proxy
management point and thus show up as executing it there.
This webcast on advanced client roaming also discusses their interaction
with the MP\PMP's > http://go.microsoft.com/fwlink/?LinkId=25348
And this webcast goes deep in to the network traffic generated by the client
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032258879&Culture=en-US
Hope this helps,
"SMS Newbie in the Block" wrote:
My MPs are working oki as far a client being able to communicate with it,
etc...
However, using Policy Spy on a client systems located in a Secondary site, I
have discovered that the Assigned MP is set to the Primary's MP.
Assigned MP: <primary server name>
Resident MP: <secondary server name>
Proxy MP: <secondary server name>
Proxy State: Active
Not sure now if this should be this way...
I was hoping to see the Assigned Site to be the secondary sites MP (proxy to
primary).
Reason I am investigating on this is because during SW distribution, the
status reports that the package ran from the primary DPs not the DP
designated for the secondary.
I have set the DPs to be protected only for the site but it still ran from
the Primary DP...very weird :- (
Is there a way to force the secondary site clients to use the secondary MP
and DP ?
Thank you so much for any inout you can provide.
Newbie
- Prev by Date: SMS Administrator Console - connection Failed issue
- Next by Date: Network Discovery
- Previous by thread: SMS Administrator Console - connection Failed issue
- Next by thread: Network Discovery
- Index(es):
Relevant Pages
|
