We have experience that same exact issue, we brought a new MP online that encountered some connection issues and all our boot images were getting pointed to it even though it was not on the preferred list. I believe it's a bug on 'preferred' MP selection, DP selection list encounters that same symptoms I've heard but haven't experienced it with our DPs. I think Cameron replied stating that is getting addressed in R2 release.
On Fri, Sep 20, 2013 at 12:45 PM, Kim Oppalfens <[email protected]>wrote: > Well,**** > > ** ** > > You’re not allowed to rename a site system in a supported manner, so that > won’t work.**** > > You could try and make sure the publishing of this mp in Active Directory > isn’t accessible.**** > > ** ** > > Alternatively file a DCR to reverse the alphabet.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* 20 September 2013 20:46 > > *To:* [email protected] > *Subject:* RE: [mssms] How is MPLOCATION populated on the MPs?**** > > ** ** > > Yes actually it is. We thought about that as well, but don’t know a way > around it without removing the role.**** > > **** > > *Daniel Ratliff***** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kim Oppalfens > *Sent:* Friday, September 20, 2013 2:27 PM > *To:* [email protected] > *Subject:* RE: [mssms] How is MPLOCATION populated on the MPs?**** > > **** > > Any chance this happens to be the alphabetically "lowest" mp? > > Sent from my Windows Phone**** > ------------------------------ > > *From: *Daniel Ratliff <[email protected]> > *Sent: *20/09/2013 19:48 > *To: *[email protected] > *Subject: *[mssms] How is MPLOCATION populated on the MPs?**** > > We are troubleshooting policy issues in WinPE for OSD, no task sequences > available, and think it may be related to a specific MP. The problem is we > cannot figure out why the MPLOCATION always points to this specific MP for > this site. **** > > **** > > http://randomMP/SMS_MP/.sms_aut?MPLOCATION&ir=1.1.1.1&ip=1.1.1.0 **** > > **** > > <MPLocation SiteCode="*PRI*" AssignedSiteCode="* PRI*" MP="*http://BADMP*"; > **** > > **** > > We have a primary with 3 MPs on it and it always returns a specific MP. We > have ran the above URL on all three MPs and always get the BADMP. We are > publishing to AD but not DNS, would it be the publishing to AD? **** > > **** > > I did check the MP Component settings on the primary and it has all three > MPs listed, we have unchecked the culprit MP but everything still tries to > hit that MP. We also have tried disabling IIS and a few other intrusive > methods to prevent communication with the MP, pretty much everything > besides removing the role itself.**** > > **** > > Any ideas?**** > > **** > > *Daniel Ratliff* **** > > **** > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information.* > *** > > **** > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information.* > *** > > ** ** > >
