That sounds like it's a bug in the dynamic media capability. What happens if you create new media without the MP included?
J From: [email protected] [mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Thursday, August 8, 2013 1:48 PM To: [email protected] Subject: Re: [MDT-OSD] RE: [mssms] OSD boot selecting the wrong MP on CM12 sp1 cu2. This is happening during the initial boot when a client is trying to determine adver. TSs. On Aug 8, 2013 12:28 PM, "Jason Sandys" <[email protected]<mailto:[email protected]>> wrote: None of the above. MP use by clients is not in any way location aware. When you say "they wanting to connect to the new one", when is this? During the initial boot, during the TS, after the TS, some other time? J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of CESAR.ABREG0 . Sent: Thursday, August 8, 2013 1:05 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [mssms] OSD boot selecting the wrong MP on CM12 sp1 cu2. I have a situation when an unknown client boots to get imaged, it is trying to get policies from a newly created MP; however, this MP is not part of the preferred MPs on the boot media. This is the setup. - CAS (yes going over 100k soon)>Primary>MP1, MP2, MP3, MP4 (new on untrusted domain), 8 DPs. (no HTTPS) one cm site HQ1. - Boundaries: AD sites. the boot media was created to select any of the first 3 MPs but when the new MP was added they are wanting to connect to the new one to get policies. result, client fails since we are having some issues with this particular MP. Ultimately, we would like to prevent clients HQ from using the new MP, is that possible?. How can I prevent this? or where I would find the process of MP assignments for unknown clients? Can this be accomplished with boundary groups? or would this be a case of using AD site boundaries vs IP ranges. Any ideas or direction would help and be appreciated. Thanks, Cesar.
